Replication Manual

27
Note that failed replication runs imply that something went wrong during the replication itself.
The overall status of task is determined by periodical tests the system performs itself which
usually points to configuration problems.
The Statistics part of the report displays some useful information on the replication run:
 Start time, end time, and duration: Please note that duration is not always equal to the end
time – start time. A replication run could potentially be suspended for some time when it
runs out of the replication window.
 Number of files processed/ files size processed: The number of files (including folders) and
the total file size that has been processed. ‘Processed’ means the files and directories are
read by the Replication Client.
 Number of new/updated files transferred / new/updated file size transferred: This is the
total number of files and file size that the Replication Client has send to the Replication
Server.
The Configuration summary part of the report summarizes the configuration which was uses
in this replication run.
7. Recovering from an emergency situation
There are two ways of recovering from an emergency situation:
 Restore all data back to the original storage location
 Temporary redirect all traffic to the replication destination
7.1 Restore all data back to the original storage location
This method is the easiest, but causes the longest downtime for your services.