You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pitr/README.md
+29-19Lines changed: 29 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,25 @@
1
1
# Content
2
2
```shell
3
-
Prerequisition
4
-
Servers
5
-
Environment
6
-
Compilation (optional)
7
-
SSL Configurations
8
-
Generate new SSL keypair (Optional)
9
-
Deployment
10
-
Step 1: Get Pitr tools
11
-
Get binary release
12
-
Compile it yourself
13
-
Step 2: Get ShardingSphere Proxy Configurations
14
-
Step 3: Set OpenGauss Configurations
15
-
Step 4: Deploy SSL certs for Pitr Agent
16
-
Step 5: Start Pitr Agent
17
-
Test
18
-
Prepare Test Data
19
-
Test Case
20
-
Backup
21
-
Recovery
3
+
README
4
+
Prerequisition
5
+
Servers
6
+
Environment
7
+
Compilation (optional)
8
+
SSL Configurations
9
+
Generate new SSL keypair (Optional)
10
+
Deployment
11
+
Step 1: Get Pitr tools
12
+
Get binary release
13
+
Compile it yourself
14
+
Step 2: Get ShardingSphere Proxy Configurations
15
+
Step 3: Set OpenGauss Configurations
16
+
Step 4: Deploy SSL certs for Pitr Agent
17
+
Step 5: Start Pitr Agent
18
+
Test
19
+
Prepare Test Data
20
+
Test Case
21
+
Backup
22
+
Recovery
22
23
```
23
24
24
25
# README
@@ -378,3 +379,12 @@ Verify data:
378
379
select * from t_user;
379
380
```
380
381
382
+
# Restrictions
383
+
384
+
- Global backup tasks need to be executed while there is no uncommitted transaction, and this will be ensuranced by ShardingSphere lock.
385
+
- The backup metadata of ShardingSphere will be stored on the same host with the Pitr cli. You need to copy this metadata backup to the another host first where you want to start recovery.
386
+
- The recovery operation need to stop service, and it is a synchonized operation. Users have to make sure the success of the recovery operation.
387
+
- OpenGauss data nodes should use the same IP and port while backup and recovery
388
+
- Only one Pitr cli could successfully if multiple cli are executed simutaneously
389
+
- OpenGauss servers may under inconsistent status if recovery fails. Users need to try to recovery again until it is succeed.
390
+
- Using the same version of ShardingSphere while backup and recovery to make sure the metadata is compatible.
0 commit comments