Table of Contents
< All Topics
Print

[SCP-Disaster Recovery] The Scheduled Backup/local backup the Disaster Recovery strategy was not executed within the specified time, resulting in abnormal RPO

Problem Description

Scheduled Backup/local backup Disaster Recovery strategy is set to be performed every 12 hours. However, Scheduled Backup/local backup sometimes only performed in the early morning and not at noon.

Warning Information

RPO Abnormal

Effective troubleshooting steps

Check the Disaster Recovery policy of the VM to see if any Node has been Shut Down and has no image backup for a long time.

Root cause

PRO is 24 hours. The local triggers are 0:00 and 12:00, and the remote triggers are 0:00, 8:00, and 16:00. At 12:00 noon, the VM does not meet the RPO, is_dst_protect_meet_rpo, and will filter out the Node that meet the RPO (24 hours) and add them to the server_list that does not execute the policy. The hosts added to the server_list will not perform Scheduled Backup/local backup, which ultimately results in the Scheduled Backup/local backup every 12 hours not being triggered at 12:00 noon.

solution

Remove the VMs that are Shut Down for a long time in the Disaster Recovery policy.

Operation Impact Scope

Modify the Disaster Recovery strategy

Troubleshooting content

Disaster Recovery strategy Node.

Original Link

https://support.sangfor.com.cn/cases/list?product_id=36&type=1&category_id=19581&isOpen=true