本文件已封存並已停止維護。

Staggering Synchronization Start Times

更新日期: 2010年4月

適用於: System Center Data Protection Manager 2010

You can specify the starting time, in minutes after the hour, of synchronization jobs for each protection group. Staggered starting times minimize the network impact of running multiple large protection jobs simultaneously.

To determine whether staggering the start times of synchronization jobs is appropriate for your needs, first gather information about scheduled protection jobs in DPM Administrator Console:

  • In the Monitoring task area, on the Jobs tab, review jobs that are scheduled for times when the DPM server experiences large disk queues.

  • In the Protection task area, review details for protection groups to determine the size and frequency of protection jobs.

Offsetting synchronization start times can also be used to optimize secondary protection of another DPM server. Secondary protection is when a DPM server protects the database and replicas of another DPM server, referred to as the primary DPM server. You can offset the synchronization of the primary DPM server to the secondary DPM server to occur after the data sources are synchronized to the primary DPM server.

To stagger synchronization start times

  1. In DPM Administrator Console, click Protection on the navigation bar.

  2. In the display area, select a protection group.

  3. In the Actions pane, click Optimize performance.

  4. On the Network tab, select the hours and minutes to offset the start of the synchronization job in the Offset <time> start time by field.

    The maximum allowed value for offset is the same as the synchronization frequency.

  5. To apply your changes, click OK.

    Changing the start time offsets recovery points for files by the equivalent amount of time.

You can choose between two modes of synchronization: at regular intervals or just before a recovery point is created.

Synchronization at regular intervals distributes the load on the network throughout the day. In the case of synchronization just before a recovery point is created, the network traffic is potentially greater at the time of synchronization, but data is not sent throughout the day.

If an organization has limited network bandwidth between the protected computer and the DPM server and this limited bandwidth is also expected to be shared by normal corporate usage, consider using synchronization only before recovery point and schedule it during off-peak hours.

Although the impact on network traffic and performance is important, you must also consider how the choice of synchronization mode affects your ability to recover data. If you synchronize only once a day, the maximum loss window is 24 hours. However, if you choose to synchronize every hour, your maximum loss window is 1 hour.

另請參閱

顯示: