|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page History
...
If you are using CDP to protect data on a large server, [merging| CDP3:Merging Recovery Points] Recovery Points can become a lengthy process and can sometimes take longer than the actual replication. For this reason, a new option has been added to CDP version 3.14 that allows you to schedule Recovery Points merging separately from the policy schedule. You can select an option to merge Recovery Points after every replication or merge them with specified frequency. Follow the instructions below to schedule the Recovery Points merge.
1. Open the Web browser connected to the CDP Server Web Interface and log in. (See [CDP3:Accessing Standard Edition Web Interface], [CDP3:Accessing Enterprise Edition Web Interface], and [CDP3:Accessing Advanced Edition Web Interface].)
!logging.png!
!logging.png!
21. Click on "Policy" in the Main Menu to open the "Policies" window.
|| Standard Edition || Enterprise Edition || Advanced Edition ||
| !pol-st.png! | !pol-ent.png! | !10.png! |
| !pol-st.png! | !pol-ent.png! | !10.png! |
32. Select the policy from the list and click "Edit."
!poll.png!
43. In the "Policy Settings" tab, click on the "Edit Schedule."
!taar.png!
54. Select the trigger type from the drop-down menu. It will determine the recurrence of the merging:
* *After successful replication*
* *Hourly*
* *Hourly*
...!trigger.png!
65. Depending on the trigger type, you will need to define the time/date of the merging. For example, for the "Daily" Trigger Type, define Starting Minute and Hours of Day.
!trigger2.png!
76. Click "OK."
{info:title=Note}
A Merge Recovery Points task is always shown separately from the policy in [CDP3:Task History], even if the "Merge After Every Replication" trigger is selected. This way you can have a better perception of tasks since merging can run for long periods of time.
A Merge Recovery Points task is always shown separately from the policy in [CDP3:Task History], even if the "Merge After Every Replication" trigger is selected. This way you can have a better perception of tasks since merging can run for long periods of time.
...