Best practices for initial backup
When running initial backups, consider the following:
• The path specified must accommodate the size of the incoming data.
• The file system on the initial backup buffer must be able to handle the size of the incoming files.
• When running several initial backups at the same time, make sure the device where initial buffer is located can handle the I/O load. If too many initial backup processes are sending data to the same path at the same time, the sessions may stop and the related errors will be reported.
• All initial backup sets written to the same initial backup path must be completed before the physical media is sent to the service provider (in DS-User, on the Initial Backup menu, click Status).
• Always check the DS-Client activity log and the event viewer at the end of every initial backup session to ensure that no errors are reported.
• If the initial backup session is interrupted, it can be resumed but you must synchronize the backup set (Right-click the backup set > Synchronize: Normal). To resume, start another backup session. The other option is to reset the backup set as Incomplete, then re-run the initial backup from the beginning (DS-User > Initial Backup > Status).
• If the file system on the initial backup buffer cannot be directly read by the operating system on DS-System side (like a Mac DS-Client connected to a Windows DS-System), NFS or CIFS can be used for the initial backup import.