Table of ContentsLibraryView in Frames

What restarts and retries are

In SnapMirror, a retry is an automatic attempt to start the transfer process after an interruption, whether or not any data was successfully transferred. A restart is the resumption of a previous transfer process from a restart checkpoint.

SnapMirror sets a restart checkpoint every 5 minutes during a transfer. SnapMirror restarts the previous transfer where it left off, if the following conditions are met:
  • A restart checkpoint exists.
  • All Snapshot copies being transferred still exist.
  • The value for the restart mode in the /etc/snapmirror.conf file is set to always or is not set, and the next scheduled update has not arrived.

If the conditions are not met, SnapMirror creates a new Snapshot copy and starts a new transfer.

If a scheduled transfer fails (for example, due to network failure), SnapMirror automatically retries the transfer the next minute. If a transfer fails due to an error that renders it unfit for a retry (for example, in case of user abort), or if the source denied the transfer for any reason, the transfer is not retried the next minute. In such cases, an update is always attempted according to the schedule specified in the snapmirror.conf file.

Note: If a user-initiated, manual update fails, the update is not tried automatically and the user is informed. The user needs to reissue the command if an update is required.

After a reboot, SnapMirror does not automatically retry a transfer that was interrupted; however, the next scheduled or manual transfer restarts it at that restart checkpoint, if the checkpoint is still valid.

An initial transfer can be restarted but will not be retried automatically. To restart an initial transfer, enter the snapmirror initialize command again. Scheduled incremental updates automatically retry the transfer.