Revolving around the core of technology
|Subject:||File Interruption Scenarios|
|Creation date:||8/5/15 7:29 AM|
|Last modified on:||8/5/15 7:32 AM|
When transferring large files to the Server, it may take many hours to complete the job depending on the size of the full data set, as well as the speed of the network between the Client and the Server. Here are some scenarios in which a backup is interrupted, and how it affects the overall job.
This can occur if the Client machine crashes or if the plug is pulled and the machine shuts down completely.
There is a 5-hour timeout period on the Server, which means that if the Client computer is sleeping for more than 5 hours, then the backup job will be considered terminated. The next backup will have to start from the beginning. (NOTE: This is also the case if the network somehow crashes, and it is unable to establish a connection to the server within 5 hours.)
You also want to consider whether the file exists on the server or not:
When a brand new file is being sent to the server, Syncrify creates an MD5 signature on both ends. If the transfer is interrupted, Syncrify will try to match the MD5 signatures for each file, and it will then continue the backup from where it left off.
If the interruption occurs on a file that already exists on the Server, Syncrify will try to match up the MD5 signatures, however if they do not match, the file will have to be transferred in its entirety.
These conditions are very similar to a complete Client machine shutdown. (See the 5-hour Timeout Period in the above section.)
If the Client is sleeping for only a short period of time and the reconnection is made quickly, then every process involved in the backup job will be paused and the job will resume from where it left off.
Do you have a helpful tip related to this document that you'd like to share with other users?