This process includes instructions for network setup, checking the health of the machine to be protected, and obtaining and installing the agent software.
See the article Datto Networking Requirements to ensure that your target machine can connect to Datto's infrastructure.
- Ensure the health of your hardware. This includes checking the status of RAIDs and hard drives. Make any necessary repairs before deploying the Datto backup agent. Failure to complete this step may result in backing up corrupted systems.
- We recommend that you run defragmentation before deployment of a Datto backup agent. You may run defragmentation software after deployment, but keep in mind that defragmentation programs rearrange data on a block level and will result in large incremental backups.
- For Windows systems, remove any other backup software with a high-level uninstaller that removes registry keys, dll files, and stray folders. These components will conflict with both the ShadowSnap and Datto Windows backup agents. To complete the uninstall process, reboot the machine.
Obtaining Agent Software
Download the Windows agent software from download.datto.com. After installing, you must reboot Windows.
Install the Linux agent software by following the instructions at Installing The Datto Linux Agent.
Additional Considerations for Windows Machines
Depending on the core functions of the target machine, consider the following items:
- SQL: If you are running SQL Maintenance jobs, set it up to back up to a separate partition to be excluded from being backed up to the Datto appliance. Otherwise, your device will quickly fill up.
- Exchange: Since VSS backups truncate logs upon completion, we recommend that you disable circular logging. Make sure that the VSS writers for Exchange are enabled. Disable any autoarchiving tools, as they will cause larger incremental backups.
- DFS: Distributed file systems on servers that stage and replicate files and folders to other places may cause large incremental backups. By default, DFS should not cause large changes as long as the transfers occur as expected and the VSS writer that maintains them remains stable.
- Hypervisors: We recommend that you isolate datastores on a separate partition and that the non-datastore volumes be backed up by the ShadowSnap agent. Back up any severs that reside on the datastore individually to allow for granular recovery and restoration options.
- Clustering: ShadowSnap does not officially support backups of high-availability clusters due to the way that disks are created and maintained within the clusters.