Editing or deleting a data copy schedule for SnapMirror transfers

You can edit or delete data copy schedules that are used for SnapMirror baseline copy, update, and resynchronization operations, if you have other DR schedules configured or modified that require the transition data copy schedule to be modified.

Before you begin

The project must be in the preparation, data copy, or apply configuration (precutover) phase.

About this task

Procedure

  1. From the Dashboard, select a project, and then click Configure Schedule.
    All the existing schedules for the project are displayed.

    You can also edit or delete schedules from the Configure Schedule option.

  2. Edit or delete a schedule:
    If you want to... Then...
    Edit an existing schedule
    1. Click .

      The Modify Schedule dialog box is displayed.

      Note: You can edit the schedule and SnapMirror parameters for the data copy operations.
    2. Make the required changes, and then click Save.
    Delete a schedule
    1. Click .

      The schedule is deleted from the pane.

      Note: At least one schedule is required for data transfers. Therefore, you should not delete all of the schedules.

Example

The following example illustrates how the throttle limit is applied when there are active SnapMirror transfers in the project.

Schedule Number of volumes and data copy state Maximum number of concurrent SnapMirror transfers Throttle limit Throttle used by each transfer
Before modifying Five volumes waiting for baseline Five 500 MBps 100 MBps
After modifying
  • For two volumes, baseline is in progress using 100 MBps throttle
  • For three volumes, baseline is completed and are waiting for updates
Five 250 MBps
  • Two volumes that are in baseline continue to use the 100 MBps throttle
  • Three volumes for which the baseline is completed use the modified 50 MBps throttle for the updates

When the baseline copy for the two volumes is completed, the new throttle limit of 50 MBps is used for these volume SnapMirror relationships while scheduling the next data copy operations.