Best Practices: Initial Backup
Summary
This article describes the Initial Backup Best Practices.
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, 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 your Service Provider (check in DS-User > Initial Backup > 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).
DS-System-side best practices for Initial Backup
- Whenever the file system on the Initial Backup buffer cannot be directly read by the Operating System on DS-System side (e.g. Mac DS-Client connected to a Windows DS-System ), NFS or CIFS can be used for the Initial backup import.
See Also
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.
![]() ![]() |