This article describes the installation and software upgrade process for the ShadowSnap agent.
- Potential Conflicts and Incompatibilities
- Server State Checklist
- Server Tuning
- Pre-Deployment Requirements
- Updating the ShadowSnap Agent
- Additional Resources
Datto's ShadowSnap Backup Agent protects local physical and virtual Windows machines in conjunction with Datto's business continuity appliances: SIRIS and ALTO.
The ShadowSnap solution has two components: ShadowSnap and ShadowProtect. Datto's web interface requires both of these components.
There is no ShadowSnap interface on the locally protected machine; however the ShadowProtect program is available from the Start menu of a protected system with the full ShadowSnap package installed. After installation, both components are listed in the Add/Remove Programs control panel.
The current version of ShadowSnap is version 3.4.3. It works in conjunction with ShadowProtect MSP version 5.0.1.
1.1. ShadowProtect - Backup Software
ShadowProtect is a requester of Microsoft's Volume Shadow Service (VSS). The VSS writers act as the primary backup engine and deliver Application-aware backup images. In case of failures in specific VSS providers, ShadowProtect also has a fallback: StorageCraft Shadow Copy Provider. This service only requests the most important VSS writers to deliver a crash-consistent backup.
1.2. ShadowSnap - Remote Agent
ShadowProtect, as managed by the ShadowSnap remote agent, is a volume based backup solution: It backs up entire partitions, not individual files and folders. If there is data that you do not want to back up, relocate it to a separate partition, and exclude it from backup images.
As the ShadowSnap solution is a volume based backup provider, any block level change on the protected agent is accounted for in backup. This includes other backups, certain maintenance tasks, or failures that interfere with the file system. ShadowSnap can only back up volumes that are recognized by the Windows operating system as local, stable volumes. ShadowSnap / ShadowProtect cannot back up mapped network drives.
If you have an application that does not have its own VSS writer to properly freeze/thaw the application's database in the event of a VSS-aware backup, we recommend that you configure that software to use its own backup service.
- Backup software is like anti-virus software: Having more than one in place is problematic as they will conflict. Disable or remove all other backup software. When removing, use a high level uninstaller that removes all traces of the program after deployment, including registry keys, dlls, and stray folders. These components can cause conflicts.
- Acronis usually prevents installation of the ShadowSnap agent. For any machine that previously had Acronis, follow the steps in this article: Removing Acronis.
- Datto does not endorse or support backing up laptops with the ShadowSnap software due to their mobile nature; laptops must be inside the LAN and not on a wireless network to perform backups in a timely manner. Attempts to do so are at your own discretion.
- There is a known issue with the Synaptics Touchpad Driver and the VirtualBox Guest Additions software.
- Older versions of the driver can cause a BSOD of the laptop itself.
- Synaptics Touchpad Driver Version 18.104.22.168 - 9/15/11 is compatible.
- Subsequent versions are able to accept the ShadowSnap installer.
3. Server State Checklist
Follow these tips to get your server in shape for smooth backups:
- Hardware health: Run chkdsk to be sure that all RAIDs and individual disks report back as healthy. Run any necessary disk repairs before the deployment of any backup agent. Failure to do so may result in backing up corrupted systems and may result in restoration failures.
- Disk defragmentation: While we can support backups that are running disk defragmentation, be aware that this rearranges data at a block level, and larger backups will consequently result. Run a disk defragmentation before deployment of the agent. VSS-aware disk defragmentation programs may allow for smaller backups, but this would be left to your own discretion.
- 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 ShadowSnap agent.
- 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.
- SQL: Check for SQL maintenance jobs that may be taking place, as they are a separate backup solution and may cause conflicts. To avoid very large incremental backups, Datto recommends to have SQL maintenance jobs saved to a partition that is unprotected by the Datto. If the Datto is set to protect the volume that has the SQL maintenance jobs saved, the local Datto may fill up, causing it to not sync to the Cloud properly. Best Practices for SQL servers can be found here.
- Exchange: Since Exchange Servers are essentially database servers with mail stores in EDB (Exchange Database Format), Datto recommends the same process for maintenance jobs that would be had with SQL as well as Exchange (see above SQL recommendation). Make sure that the Exchange writers are enabled on your operating system. Also, check for additional archiving tools such as auto-archiving that may cause larger incremental changes.
- For Exchange 2010 and 2013, Datto recommends that you enable circular logging.
- For earlier versions, VSS backups will truncate logs upon completion and circular logging can be disabled.
- DFS: Distributed file systems on servers that stage and replicate files and folders to other places may also account for larger backups. Consider the role of DFS before deployment, and consider that it may take larger backups if the files are staged at a particular time. DFS shouldn't cause large changes, as long as the transfers are occurring as expected and the VSS writer that maintains them remains stable. See How Distributed File System (DFS) Interacts with the Datto Solution for more information.
- Hypervisors: Datto recommend that hypervisors have their datastores isolated on a separate partition, and that the non-datastore volumes be backed up by the ShadowSnap agent. Servers that reside on the datastore should be backed up individually to allow for more granular recovery and restore efforts. Best practices for backing up hypervisors can be found here.
- Clustering: ShadowSnap does not support backing up Hyper-V hosts that are members of a failover cluster due to an incompatibility between the ShadowSnap software and Cluster Shared Volumes (CSVs). In addition, ShadowSnap does not support backing up any other OS that has access to a CSV. However, we are able to support backing up a guest VM running on a Hyper-V failover cluster as long as the guest OS itself does not access a CSV.
- Proxies: ShadowSnap and ShadowProtect do not support the use of proxy servers on the network. Agents check in to StorageCraft to verify their license monthly.
Here is another excellent resource from Datto's partners at StorageCraft: StorageCraft Server Tuning Guide
Many of these settings can significantly improve the reliability of the backups, especially any network latency issues or disk input / output issues. Since these steps involve manipulating the registry, take a backup of the registry before making any changes.
The following are 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)
- Firewall rules:
- From protected machine to Datto appliance: TCP 3260 (iSCSI port), UDP 139, and TCP 25566 (Live when the StorageCraft Raw Agent service is enabled and running, check with netstat).
- From Datto appliance to internet: 22, 80, 123, 443 outbound to at minimum the addresses specified in this article: Datto IP Ranges.
- Additional addresses may need to be needed for the continuity of off-site syncing, articles on additional IP ranges can be found on the knowledge base under Datto IP Ranges.
- Verify that no other backup software is installed on the machine, especially other versions of ShadowProtect, as Datto's software requires the MSP version of ShadowProtect.
- Be sure that anti-virus is temporarily disabled for deployment. After installation, you will need to configure your anti-virus to ignore the StorageCraft folder.
- StorageCraft provides a downloadable tool to analyze a system for ShadowProtect compatibility, which is available here.
- To ensure successful backups, a minimum of 20% free space per protected volume, and 1 GB of RAM, need to be available on the production machine. If resources fall below these thresholds, backups will fail.
0 – 70%
Utilization is good.
71 – 80%
Utilization is outside optimal limits. Monitor the volume growth and look at cleaning up unnecessary files and moving non-essential data to other storage.
81 – 100%
Volume is becoming critical. Snapshots will start to fail, disk queue lengths will increase. Create space.
Figure 1 illustrates the data flow for the ShadowSnap Agent.
1. After the server has been checked, you can run the installer. Go to download.datto.com and click the ShadowSnap button under Backup Agent Download. When the installer finishes downloading, run the executable with Administrator privileges. Running the installer without elevated privileges may result in the installer exiting with the error "ShadowProtect installation failed."
2. Click Next to start the ShadowSnap Setup.
3. Select the destination folder for the installer, and click Next.
4. Click Install.
5. The ShadowSnap installer will also install VirtualBox Guest Additions.
6. Click Next once the installer has completed.
7. Click Close (either restart immediately or later). Backups will not function until the system has been rebooted.
8. You are now able to pair the protected machine with the SIRIS device and proceed to start backups. Don't forget to configure your backup settings. If you receive an integrity check error, proceed to this article.
6.1. Setting Schedules / Initial Configurations
Here are some items to consider when configuring ShadowProtect:
- Consider your client’s needs, and discuss this with them before providing the schedule: how far would you need to feasibly go back 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.
- 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.)
6.2 Verify Installation
Follow these steps to verify that the installation was successful:
- Make sure that all 3 essential services are present and running: ShadowProtect Service, StorageCraft Raw Agent, and StorageCraft Shadow Copy Provider.
- A Quick test of the services would be to restart from services.msc and see if they stop and start cleanly.
- Open up the ShadowProtect software on the device. The lower left tab should show an active license.
- Check out the agents tab after pairing the agent to the device, the agent should populate as ready to accept a backup.
The ShadowSnap Agent does not automatically update itself when a new version becomes available. You will need to download and install these versions manually. You can download the latest releases of the ShadowSnap agent at the Datto Download Page.
To ensure reliability of your backups, Datto recommends installing ShadowSnap updates as they become available.
You can check the protected machine's agent version from the Protect tab of your Datto appliance's GUI.