Open a command line as Administrator by browsing to C:\Windows\System32. In order to configure the shadow copy storage location for each volume, the following steps can be taken:ġ. If this is not possible, specifying a separate drive that contains the paging file is typically still better than storing the shadow copy on the drive being backed up. The ideal situation would be to have a separate drive dedicated to shadow copies that is not being backed up and is also not the drive containing the paging file.
For desktop versions of Windows (Windows 7, 8, 8.1, 10), the shadow copies of a volume are written to the volume itself and this cannot be altered. Note: This functionality is only available on Server editions of Microsoft Windows and is not available on desktop versions of the operating system. The shadow copy storage location of each volume on a Windows server can be configured to use a different NTFS volume. This can result in very high I/O or low disk space problems during the backup of a volume since the drive is experiencing load from the backup reading files, load and disk space usage from VSS reading from and writing to the shadow copy, and load and disk space usage from any other applications on the system using that same volume. Causeīy default, Microsoft Volume Shadow Copy Services (VSS) is configured to write the shadow copies of a volume to a folder on the volume itself during a backup job. Backup jobs fail due to Microsoft Volume Shadow Copy Service (VSS or snapshot) related errors indicating either a lack of disk space or I/O that is too high to maintain the shadow copies.