Best practices: Initial backup
Creation Date: December 04, 2007
Revision Date: December 04, 2007
Product: DS-Client
Summary
This article describes the best practices for the initial backup of data.
See Also:
DS-Client-side best practices for Initial Backup
When running initial backups the following aspects need to be taken into account:
• 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 (e.g. FAT32 has a 4GB file size limitation).
• When running several initial backups at the same time, ensure 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 might 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 your service provider (to verify, 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 (in the Backup Sets tab, select the backup set, and then on the Sets menu, point to Backup Sets, and then click Synchronize). To resume, start another backup session. The other option is to reset the backup set as “Incomplete” (on the Initial Backup menu, click Status, select the backup set and then click Mark Incomplete), then re-run the Initial Backup from the beginning.