Policy-Based Data Replication
System Administration Manual
354
Troubleshooting Replication Failures
If a replication fails with errors, identify the source of the problem and ensure that it has been
cleared. Listed below are some possible scenarios were a replication job can fail and possible
solutions that may resolve the problem.
❑
The destination volume is offline.
In this case, bring the volume back online before the replication can continue.
❑
The destination volume was full.
In this case, clear up more space in the destination.
❑
One of the volumes involved may have been unmounted.
In this case, remount the volume before the replication can continue.
❑
SMU was rebooted while a replication job was in progress.
In this case, the replication will abort but will restart the next scheduled replication job
when comes back on line.
Note:
Without any further action upon a replication failure, the replication
will continue as expected on its next scheduled run. However, this will
recopy any changes already copied during the failed replication attempt.
Clicking the
Run Now
button will cause the failed replication to be restarted
immediately and will avoid recopying most of the data.
Start Time
Displays the date and time when the replication began.
End Time
Displays the date and time when the replication ended.
Duration
Displays the time taken to complete the replication.
Server/EVS
Displays the EVS on which the Source and Destination File System reside.
Bytes Transferred
Displays the volume of data in Bytes that were replicated.
Содержание Titan SiliconServer
Страница 1: ...Titan SiliconServer System Administration Manual ...
Страница 12: ...Table of Contents xii Titan SiliconServer ...
Страница 308: ...File Services 296 Titan SiliconServer 4 Click OK To access available iSCSI Targets 1 Click on the Available Targets tab ...
Страница 411: ...Status Monitoring 399 Titan SiliconServer 3 Click details ...