Best Practices ¶
General guide ¶
- Keep your Server up to date with your release stream (Quarterly or Voyager). Update customer devices silently via the Bulk Update feature in ‘Accounts’.
- Ensure that the Server Self-Backup is enabled, and saved to a safe location.
- Consider separate Storage Vaults for different devices, unless there is a significant amount of shared data.
- Stagger the schedules of backups into the same Storage Vault to avoid lock issues. Lock issues are rare, unless a device unexpectedly stops or pauses during the final phase of the retention pass. This is when the software obtains brief, exclusive access to the Vault, applies snapshot Retention Rules, and deletes old, or unreferenced data.
- Multiple, simultaneous backups into the same Vault are usually not a problem, and it offers benefits such as deduplication. Some devices which are shutdown frequently, such as laptops, can cause some issues. Consider separate Vaults for these. Contact Comet for more specific recommendations.
- Instead of backing up network-shares, consider installing the client software directly onto the device where the original data is stored. The backup will then be for a local path, and usually without issue.
- Where there are issues with the MS proprietary Windows Server System State and Windows System Backup backup types, consider using the Disk Image backup type instead. Disk Image was specifically designed to overcome issues with these types, and has much greater functionality, as well as scope for future enhancement.
- Ensure that the Comet Server and customer devices have synced time-zones, or you may get a series of log messages showing missed backups, followed or preceded by successful backups. Watch for clock-drift. Comet allows up to 10 minutes difference before logging separate events.
- Ensure that customer devices are always ‘Online’ with respect to the Comet Server, and have sufficient resources available to be able to complete the backups in the expected time-frame.