Shadow Copies are native Windows VSS snapshots. Shadow storage is the location that Windows uses to store these snapshots.
Both the Datto Windows Agent and ShadowSnap backup process use VSS snapshots and shadow storage.The amount of shadow storage space required depends on how quickly applications modify data after the backup begins, and how quickly ShadowProtect and ShadowSnap can copy the data into the backup.
If the VSS backup fails, the Datto Windows agent will use the Datto Block Device (DBD) to hold the data, whereas ShadowSnap will use ShadowProtect's STC engine.
ShadowCopy and the ShadowSnap Agent
Datto recommends that you disable the Windows Shadow copy process when using ShadowProtect because of the difference between how ShadowProtect and Microsoft interact with the shadow storage space. Microsoft will fill up the shadow storage space until it is completely full, and then destroy the oldest backup to make room for the newest backup. This can have an adverse effect on ShadowProtect, because it uses the same storage space for its backups. Once we have written the backup to the destination, the software cleans up its shadow copies.
If you cannot disable Windows Shadow Copy, Datto recommends that you set your shadow storage space to unbounded. This will allow the space to grow as necessary to accommodate ShadowSnap backups.
Working with Shadow Storage
The following commands will allow you to manage shadow copies and shadow storage from the Windows Command Prompt. You will need to launch the Command Prompt session as an administrator.
View existing shadow copies:
vssadmin list shadows
View the size of the storage:
vssadmin list shadowstorage
Change the allocated size for your shadow storage:
vssadmin resize shadowstorage /for=<ForVolumeSpec> /on=<OnVolumeSpec> [/maxsize <MaxSizeSpec>]
- If no value is specified for /maxsize, there is no limit placed on the amount of storage space that can be used.
- Microsoft TechNet: vssadmin resize shadowstorage (external link)