This article describes the Datto Windows Agent.
Requirements for your target server and your network:
- Gigabit connections from the Datto to all relevant network infrastructure (Check switch ports, try to have the Datto appliance on a gigabit switch whenever possible)
- Supported operating systems:
- Windows XP Service Pack 3
- Windows Server 2003 Service Pack 2
- Windows Vista and higher, latest Service Packs recommended
- 10% of the volume must be free at time of install, so we may create a file in the root of the volume to handle block transport during transfers.
- If a volume is selected for backup, 10% of the volume free space is required on that volume (up to 10 GB). If the volume is large enough that 10 GB represents less than 10% of the total disk space, the percentage of the disk that represents 10 GB is required. This is a common requirement among backup agents so that the agent has sufficient space to track and block-transfer changes for subsequent backups
- Recommended at least 1GB of RAM free for install and backups to run
- NTFS filesystems (ReFS is not currently supported)
- Firewall rules:
- The protected machine must have Internet access for the initial installation of the Datto Windows Agent.
- From protected machine to Datto appliance: Port 3260 (for iSCSI), 3262 (for Mercury), UDP 139, and TCP 25568.
- The Datto Windows Agent uses Mercury as its primary transport method; however, if this fails, backups are intended to fall back to iSCSI.
- From Datto appliance to internet: ports 22, 80, 123, 443 outbound to at minimum the addresses specified in this article: Datto IP Ranges.
- You may need additional addresses for the continuity of off-site syncing. See Datto Networking Requirements for local and offsite networking requirements and best practices for Datto appliances.
- Verify that no other backup software is installed on the machine.
After you have checked the server, go to download.datto.com and click the Windows button under Backup Agent Download. You must have internet access during the install and the initial start so that the agent can retrieve certificates. Once you have installed the agent, you may pair the agent to the Datto device and begin configurations.
Note that if your machine will not have regular internet access, you will have to manually check for updates to upgrade to newer versions.
However, you must reboot the system before you can load the backup driver, which is necessary to begin running backups.
When you install the Datto Windows Agent, it creates a DattoCTRL file and a DattoSNAP file on the protected server, in the root directory of each protected volume. You may need to select the Show hidden files and folders in Windows to see them.
DattoCTRL can be between 5 GB to 10 GB in size. It is the file that the backup agent uses to assist with block transfers from Windows to the Datto appliance.
DattoSNAP is the file that the Datto Windows Agent writes the changed block information to, so that it knows what it need to move during each backup.
Setting Schedules / Initial Configurations
Items to consider when configuring the Datto Windows Agent:
- Before setting a backup schedule, discuss with your client how far back you would ever need to go to retrieve data. Set the expectations with them and provide a schedule accordingly. Set the local data retention policies based on these conversations and expectations. Remember that long-running retention policies will require more disk space, and should be considered when sizing an appliance.
- Consider the server’s application: while a file server may need to be backed up during business hours as files are in constant change, a terminal server that simply houses configurations may not require as many backups per day as there is little to no change provided. Backups are just like any other service on a server, they consume resources and take disk input / output. Consider this while setting a schedule.
- The size of your server's backups can grow if you use Distributed File System (DFS) in your environment. See How Distributed File System (DFS) Interacts with the Datto Solution for more information.
- Before you take the first backup, make sure that any volumes that you do not want to be backed up are excluded from the advanced options tab. Remember that any additional drive that is attached to the machine may attempt to be backed up (USB drive, additional storage drive, etc.)
The Datto Windows Agent does not have a GUI. Follow these steps to verify that the installation was successful:
- Make sure the production machine has been rebooted following the installation of the Datto Windows Agent.
- Check Programs and Features to ensure that Datto Windows Agent is listed as an installed program.
- Make sure that both essential services are present Datto Backup Agent Service and DattoProvider.
- Attempt to pair the protected system via the web UI of your Datto appliance, and start a backup for it. Both processes should complete successfully.
The Datto Windows Agent automatically updates itself when a new version becomes available, except when the release includes a driver update. Because a driver update requires an update of the host system, you will need to download and install these versions manually. You can download the latest releases of the Datto Windows Agent at the Datto Download Page.
The current release of the Datto Windows Agent is 18.104.22.168. You can check the protected machine's agent version from the Protect tab of your Datto appliance's GUI.
Install of the Datto Agent Service Failed. Uninstall and run the install again
This error message can be caused by missing Windows updates. To resolve this error, make sure that the following Windows updates are installed on the protected system:
9. Visual C++ Redistributable for Visual Studio 2015
After installing any missing updates, re-run the Datto Windows Agent installer.
Install of the Datto Provider Failed. Uninstall and run the install again.
This error message can be caused if the Distributed Transaction Coordinator service is in an unusable state. To troubleshoot this issue:
1. Check the Windows Event Logs for the Complus error shown in Figure 1.
2. Using the Services control panel (services.msc), make sure that the Distributed Transaction Coordinator service is running. If it is not running, start it. If it is running, restart it.