Copy To Another Data Store

Create a Copy to Another Data Store task to further protect your data by copying your backup data from one recovery point server to another recovery point server. You may also copy your backup data from one data store to another data store in the same recovery point server or in the remote recovery point server. The replication destination must be a data store in the recovery point server. You can create multiple replication tasks to perform multiple replications.

This section provides information about how to add tasks to copy recovery point to another data store.

Follow these steps:

1. On the left pane, click Tasks, click the add (+) symbol on the RPS section, and then click the newly added RPS section.
2. On the What to Copy tab, from the Activity Type drop-down list, select Copy to Another Data Store.
3. On the Where to Copy tab, do the following:
• Site Name: Select one of the available sites.
• Policy: Select one of the available policies.
• Note: The Policy field appears only when you select the remote shared site.
• Recovery Point Server: Select one of the available recovery point servers.
• Data Store: Select one of the available data stores.
• For When Copy Job Fails, provide the following details:
• Start Retry: Specify the time in minutes in the range of 1 to 60 to restart the copy job.
• Retry: Specify the value in the range of 1 to 99 for number of times you want to start the copy job.
4. On the When to Copy tab, do the following:
Add Copy Job Schedule
• To add the Copy Job schedule, next to the Copy Job Schedule heading, click Add.
• The Copy Recovery Point Merge Schedule section refreshes and displays the following fields:
• Run Schedule Days: By default, all the days of the week are selected. If you do not want to merge jobs on a specific day, click the day of the week to clear the selected day.
• Start Time: From the hour and minute drop-down list, select the start time for the merge job.
• End Time: From the hour and minute drop-down list, select the end time for the merge job.
• For Retention Policy, provide the following details:
• Daily Backups: Type the number of backups that you want to retain in a day.
• Weekly Backups: Type the number of backups that you want to retain in a week.
• Monthly Backups: Type the number of backups that you want to retain in a month.
• Other Backups: Type the number of backups that you want to retain in custom/manual.
• Note: The above options are automatically enabled if you add the corresponding copy job schedule.
Add Merge Schedule
To add the Merge schedule, next to the Merge Schedule heading, click Add.
The Merge Schedule section refreshes and displays the following fields:
• Run Schedule Days: By default, all the days of the week are selected. If you do not want to merge jobs on a specific day, click the day of the week to clear the selected day.
• Start Time: From the hour and minute drop-down list, select the start time for the merge job.
• End Time: From the hour and minute drop-down list, select the end time for the merge job.
Add Copy Throttle Schedule
To add the Copy Throttle schedule, next to the Copy Throttle Schedule heading, click Add.
The Copy Throttle Schedule section refreshes and displays the following fields:
• Throughput Limit: Type the throughput limit in Kbps and Mbps unit.
• Run Schedule Days: By default, all the days of the week are selected. If you do not want to run the copy throughput job on a specific day, click the day of the week to clear the selected day.
• Start Time: From the hour and minute drop-down list, select the start time for the copy throughput job.
• End Time: From the hour and minute drop-down list, select the end time for the copy throughput job.
5. On the Additional Settings tab, select the Execute all copy jobs using this task as the source of copy in parallel check box if you want to execute all the copy jobs using this task as the source of copy in parallel. If you do not select this check box, all the copy jobs run in series (one after the other).
6. Click Create Policy.

The policy is added successfully.