Cloning Performance

In general, a volume write that occurs as part of a backup operation and a volume write that occurs as part of a cloning operation proceed at the same speed. However, if a clone operation is automatically requested as part of a scheduled backup, you may experience a performance degradation in other scheduled backups that follow. Backup generally attempts to complete one group's scheduled backup before a scheduled backup is initiated for another group. However, Backup considers that a group backup is finished when the backup operations are complete, not when any automatic cloning is complete. Therefore, if another group starts its backup while the previous group's clone operation is underway, you may experience contention for nsrmmd resources or specific volumes. To avoid this problem, you may decide to refrain from automatic cloning and instead initiate a single clone operation by passing a set of ssids to nsrclone as part of a job that runs at a nonpeak time after all backups are complete.