In a Disaster Recovery (DR) Policy, scheduling defines when and how often replication occurs between the source and target systems. Choosing the right schedule ensures that your recovery objectives (RPO/RTO) are met while balancing cost and performance.
The Disaster Recovery (DR) Policy provides a structured approach to maintain business continuity during unexpected outages, disasters, or critical failures.
Points Covered
- DR Policy create for Passthrough Sync.
- DR Policy creation for Stage1 sync.
- DR Policy creation for Stage1+2 sync.
DR Policy create for Passthrough Sync.
What is PTSync: create a KB separate.
How to set up PT DRP
1. To create a DR policy, you need to log in to the SWIFT dashboard and navigate to the ‘DR Policy’ under the Business Continuity & DR menu and click on ‘New’ button. Please see below screenshot.
2. After a click on ‘New’ you will get a new prompt to create a DR policy by selecting Sync type. Please check the screenshot below for more details.
3. If you look at above screenshot, you will see sync type, periodicity in General options.
a.Policy name: You can provide what you want.
b.Sync type: Here we have selected Passthrough.
periodicity: There are multiple periodicities; here, we have selected by schedule in the above screenshot.2. By Frequency: If you select this option, you can set any frequency, for example, every 1 hour or 20 minutes, and your DR Policy will run accordingly. Additionally, you can specify an exclusion period using ‘Exclude From’ and ‘Exclude To.’ Here, we have selected 1:10 to 2:00.
4. Continuous: If you select the Continuous option in DR Policy creation, the sync will run continuously, one after another, and your sync will run continuously.
5. Email alert: You can set your email id to receive any email alerts on sync failure. Based on yor requirement , add both cases. with screesnhot.
4. If you look at ‘Advanced options’, there are two options as below.
1. Pre/Post script config: If you need to stop a specific service or background process on the source side before the sync begins, you can upload a pre-sync script to handle this.
Similarly, if you want to perform any tasks after the sync is completed, you can upload a post-sync script on the source side.
YAML: If you want to create or update Kubernetes objects at the source or target side before or after sync, you can use this option.
2. Max. Parallel Sync Config: Here, you can set the maximum number of parallel syncs that can run on the K8S cluster. For example, if you set the maximum parallel syncs per cluster to 2, and 2 syncs are already running, any additional sync attempts will fail, indicating that the parallel sync limit has been reached.
- Then you can create a DR policy by clicking on ‘Create’ button.
- After creation, you will see the DR policy in an Idle state because the sync has not started yet or is not configured for this DR policy. You can view many details such as Type, Status, Sync Schedule, Alert Settings, and so on. Please find below snippet for more information.
DR Policy creation for Stage1 sync.
1. You can create a DR Policy for stage1 sync also. SAme as PT sync
2. You need to select the ‘Stage1’ sync type; the rest of the settings will be the same as the Passthrough sync mentioned above.
3. If you go to the Advanced options in Stage1 DR policy. You can set the maximum number of parallel syncs that can run on the K8S cluster. For example, if you set the maximum parallel syncs per cluster to 3, and 3 syncs are already running, any additional sync attempts will fail, indicating that the parallel sync limit has been reached as same as PT sync.
3.1 In the ‘Backup Schedule Options’ of the Stage1 DR policy, there are two backup options: ‘Local’ and ‘Remote’.
3.2 If you want to back up locally, select the Local Backup option and provide a short-term backup interval and the time to retain the short-term backup.
3.3 Specify the duration for short-term backups in terms of days and weeks on the SWIFT server, as well as the ‘Number of Backups’ you want.
3.4 Local backups will be stored in the ZFS storage pool.
3.5 Additionally, if you want to back up remotely, you can choose the 'Remote Backup' option while creating a DR policy.
3.6 This is a planned and implemented use-case for remote backup that allows HA for SWIFT during DR. In case you lose SWIFT, you can spin up another instance and restore the backup from the cloud.
3.7 Here, we have selected Remote Backup, as you can see in the above screenshot.
3.8 We have set the long-term backup interval to 1 hour and configured the number of long-term backups to 4. Remote long term backup is the maximum backup count maintained by the DR policy.
3.9 After created a DR policy for stage1 , it looks like as below. In that you will see parameters that you have configured while creating stage1 DR policy.
DR Policy creation for Stage1 sync.
1. You can create a DR Policy for stage1 sync also. SAme as PT sync
2. You need to select the ‘Stage1’ sync type; the rest of the settings will be the same as the Passthrough sync mentioned above.
3. If you go to the Advanced options in Stage1 DR policy. You can set the maximum number of parallel syncs that can run on the K8S cluster. For example, if you set the maximum parallel syncs per cluster to 3, and 3 syncs are already running, any additional sync attempts will fail, indicating that the parallel sync limit has been reached as same as PT sync.
3.1 In the ‘Backup Schedule Options’ of the Stage1 DR policy, there are two backup options: ‘Local’ and ‘Remote’.
3.2 If you want to back up locally, select the Local Backup option and provide a short-term backup interval and the time to retain the short-term backup.
3.3 Specify the duration for short-term backups in terms of days and weeks on the SWIFT server, as well as the ‘Number of Backups’ you want.
3.4 Local backups will be stored in the ZFS storage pool.
3.5 Additionally, if you want to back up remotely, you can choose the 'Remote Backup' option while creating a DR policy.
3.6 This is a planned and implemented use-case for remote backup that allows HA for SWIFT during DR. In case you lose SWIFT, you can spin up another instance and restore the backup from the cloud.
3.7 Here, we have selected Remote Backup, as you can see in the above screenshot.
3.8 We have set the long-term backup interval to 1 hour and configured the number of long-term backups to 4. Remote long term backup is the maximum backup count maintained by the DR policy.
3.9 After created a DR policy for stage1 , it looks like as below. In that you will see parameters that you have configured while creating stage1 DR policy.
DR Policy creation for Stage1+2 sync.
1. You can create a DR Policy for stage1+2 sync also. Same as PT and how to setup
2. You need to select the 'Stage1+2' sync type; the rest of the settings will be the same as the PT & Stage1 sync mentioned above.
3. The only change is that once you choose the periodicity for Stage1, you need to select the option for Stage2 that will execute after Stage1, . Here, we have selected 'Execute after Stage1 sync for example’.
4. There are multiple options for Stage2 periodicity, but 'Execute after Stage1 sync' is different. Here, we have selected 'Execute after Stage1 sync’. You can check in below screenshot.
5. The rest of the advanced and backup options are the same as for Stage1.
6. After creating a Stage1+2 DR policy, it will look like the snippet below.
Next step to How to set up DR Policy sync job follow KB. PT Stage1 and stage2, how to schedule sync jonb with DR Policy
https://rackware.freshdesk.com/a/solutions/articles/5000890839?lang=en