The Silent Cubes long-term storage system is not able to verify copy operations to the Head Unit. To detect faulty copy operations and prevent incorrectly or incompletely stored data, we strongly recommend that you use software such as Robocopy, which can take on this task.
The minimum age setting, which can be configured for each volume (minimum 20 seconds, maximum 300 years), allows you to give the verification process an appropriate time window. Depending on your software, choose a sufficiently high minimum age.
Important notes on using Robocopy in Windows environments: When the Optimizations for Robocopy function, which can be configured separately for each volume, is active, the system ignores files with the following modification time when archiving to the Silent Cubes:
1 January 1980 00:00:00 GMT to 2 January 1980 00:00:00 GMT.
Robocopy classifies files with a modification time within this time window as not yet complete. Accordingly, the Head Unit does not pass these files on to the storage units. They remain pending and can be deleted or overwritten again if necessary.
In the event of a failed copy operation with Robocopy, incompletely transferred files can therefore be identified by a modification time that falls within the specified time window. The reasons for a failed copy operation can be varied:
-
Network interruption
-
Weak network (timeout)
-
Missing parameters in the copy process with Robocopy that would have enabled the copy process to resume (parameter /Z)
By choosing suitable parameters, Robocopy can either overwrite or delete files marked as incomplete in this way during a renewed copy attempt, before they are permanently stored in the Silent Cubes.
You can find more information about Robocopy and its parameters on the Internet at http://en.wikipedia.org/wiki/Robocopy