Getting Started with Datto Endpoint Backup with Disaster Recovery Windows Agent
Topic
This article describes system requirements for the Datto Endpoint Backup with Disaster Recovery (formerly Endpoint Backup for Servers) Windows Agent.
Environment
-
Datto Endpoint Backup with Disaster Recovery (Windows)
Description
System requirements
OS |
Datto Endpoint Backup with Disaster Recovery supports Core, Essentials, Standard and Datacenter editions of the following operating systems:
|
Memory requirements |
|
Disk space requirements |
|
Network |
|
Anti-virus exceptions |
Create exceptions for Datto Cloud Continuity Service and the DattoProvider service: %SYSTEMDRIVE%\Program Files\Datto\Datto Cloud Continuity\DattoCloudContinuity.exe %SYSTEMDRIVE%\Program Files\Datto\Datto Cloud Continuity\DattoProvider.exe Allow the following file: %SYSTEMROOT%\system32\Drivers\DattoCbt.sys |
Other Requirements |
|
Considerations
- Cloud virtualizations have limitations with AADDS (Azure Active Directory Domain Services )
- System compression, also known as "Compact OS", is a Windows feature that allows rarely modified files to be compressed using the XPRESS or LZX compression formats and is NOT supported.
- Endpoint Backup with Disaster Recovery does not currently support systems using REFS volumes.
- Backing up external/removable drives is unsupported. See Volume Level Backup Control for Datto Endpoint Backup with Disaster Recovery for more information.
- Backup of User Profile Disks used by the Remote Desktop Service is unsupported. Remote Desktop Service (external link). These volumes should be excluded from backups.
- If you are protecting any volumes on your machine using an anti-virus software that uses VSS to allow for rollback remediation or snapshotting in the event of a security / encryption breach (like SentinelOne, for example), this will need to disabled in order for the Windows agent to properly backup these volumes.
- Storage Server operating systems are not supported at this time.
Versioning
For the latest Agent version information, see Release Notes. You can check your protected machine's installed version from the agent tray icon. The Datto Endpoint Backup Agent's latest release is always available at theDatto Download Page.
Installation
Endpoint Backup with Disaster Recovery Agent Software can be downloaded on datto's download page, full installation instructions can be found here.
Datto recommends running the following checks on the system you are protecting before installing the Endpoint Backup Agent:
chkdsk
- Run chkdsk to be sure that all RAIDs and individual disks report back as healthy. Perform necessary disk repairs before deploying any backup agent. Failure to do so may result in backing up corrupted systems and restoration failures.
Disk defragmentation
- While Datto can perform backups that are running disk defragmentation, be aware that this rearranges data at a block level, and may result in larger backups.
- Run disk defragmentation before you deploy the agent.
- VSS-aware disk defragmentation programs may allow for smaller backups but are optional.
Windows updates
- Download Windows updates, service packs, and any other Microsoft-provided updates. After installing these updates, reboot the server. When scheduling your deployment, remember that the 2nd Tuesday of every month is Microsoft's 'Patch Tuesday.'
Virus scan
- Run a virus scan before you deploy the Datto backup solution to your production machine.
Event Viewer
- Check the target's system and application logs to see if there are any VSS or hardware errors.
- Resolve any errors before attempting to install the agent.
Previously installed backup software
- Before installing the Endpoint Backup Agent, you should disable and remove all other backup software from the production machine. Depending on the software, you may need to completely uninstall it for backups to run correctly.
- When uninstalling other backup software, use a high-level program that eliminates all traces of the incompatible software, including registry keys, DLLs, and stray folders. These components can cause conflicts.
Group Policy
- To avoid issues with installing the necessary certificates, ensure that the Windows Group Policy is not set to "Allow only Enterprise Administrators"