<< Click to Display Table of Contents >> Navigation:  Using SyncBackPro > Expert Mode > Copy/Delete, VSS

 

SyncBack V12 introduced advanced Volume Shadow Copy Service (VSS) options that give greater control over the open/locked file copy process.

 

 

•Do not use unelevated volume shadow copy method if not run elevated: If you installed SyncBack as a Windows Administrator (for All Users) then the Scheduler Monitor Service will have been installed. Using that service, users running SyncBack unelevated can copy open/locked files.

 

•Use advanced Volume Shadow Copy Service: In most cases, there is no need to use this option. SyncBack can copy open/locked files without this option being enabled. This option is available for advanced users who are knowledgeable about the VSS process. When enabled, you can fine-tune the VSS options used.

 

Advanced Volume Shadow Copy Service Settings

 

•Provider: The Volume Shadow Copy Service (VSS) in Windows relies on components known as VSS Providers to create and manage shadow copies. A VSS Provider is a software or hardware module that implements the logic required to generate a consistent snapshot of a volume while it is in use. Applications and services can then read data from this snapshot, allowing open or locked files to be copied safely. Windows includes a built-in Microsoft Software VSS Provider, which is used on most systems. However, some storage solutions, such as enterprise-grade RAID controllers, SAN arrays or advanced SSDs, may install their own hardware or third-party software providers. These providers can offer enhanced performance, improved snapshot capabilities or features tailored to specific storage technologies. When configuring SyncBack, you may select which VSS Provider to use if more than one is available. In most cases, the default Microsoft Software VSS Provider is recommended, unless your storage vendor specifies otherwise.

 

•Context: A VSS Context defines the operational scope and behavior used when a shadow copy is created. It instructs Windows on the type of snapshot to produce, the environment in which it will be used, and the level of access permitted. Different contexts are designed for different scenarios, from standard system backups to specialized environments such as hypervisors, remote volumes, or application testing.The context determines factors such as whether the snapshot is persistent, temporary, transportable, or designed for software development and testing. SyncBack uses these Windows-defined contexts to request a shadow copy that matches your selected configuration. Choosing the correct context helps ensure that the snapshot is created successfully and is compatible with your backup or synchronization task. The default is Client Accessible.

 

oBackup: It is generally a non-persistent, read-only shadow copy that automatically involves VSS writers to ensure application-consistent data. The shadow copy is automatically deleted when the backup application finishes or fails.

oFile Share Backup: Used for shadow copies of data residing on Server Message Block (SMB) 3.0 file shares. Allows VSS operations to work across the network, coordinating with the remote file server's VSS components.

oNAS Rollback: Specific to Network Attached Storage (NAS) scenarios. Coordinates with NAS devices supporting the VSS for SMB File Shares protocols.

oAPP Rollback: Used for application-specific rollback scenarios. Creates a persistent shadow copy intended for long-term storage or application-level recovery. It ensures writer involvement for data consistency.

oClient Accessible: This is the default, and creates a persistent shadow copy that is read-only but accessible to end-users via the "Previous Versions" feature in Windows Explorer. This context typically uses the system software provider and is designed for user-driven file recovery rather than enterprise backup.

oClient Accessible with Writers: A variation of client accessible that forces the involvement of VSS writers during creation. Ensures application consistency for data that might be client-accessible (e.g. a simple file share hosting a small database file), which the standard client-accessible context doesn't always guarantee.

 

•Backup Type: A VSS Backup Type specifies how the system should treat the data that is being backed up through a shadow copy. It informs VSS writers and applications whether the backup is full, incremental, differential, or intended for copying without modifying any internal backup markers. Each backup type serves a different operational purpose. For example, a full backup type may direct certain applications to clear logs or update internal state information after the backup completes. A copy backup type, on the other hand, performs the backup without altering those markers. This is useful when you want to create a consistent snapshot of data without affecting the backup schedule of other software. SyncBack allows you to choose the backup type so that the shadow copy behaves in a way that matches your workflow. Selecting the correct type ensures compatibility with applications that participate in VSS operations and helps maintain stable and predictable backup behavior across your system.

 

oFull: This type backs up all selected files regardless of their backup history. Crucially, it instructs VSS writers to truncate (clear) their application transaction logs after the snapshot is successfully created and the backup is complete.

oIncremental: This type backs up only files that have changed or been added since the last full or incremental backup. It coordinates with writers to identify these specific files. The backup history for files is updated.

oDifferential: This type backs up all files that have changed or been added since the last full backup. Unlike incremental, each differential backup contains all changes since the initial full backup. The backup history for files is updated.

oLog: This is a specialized type specific to VSS, where only a writer's transaction log files are backed up. This is commonly used in databases with specific recovery models (e.g. SQL Server) to maintain a continuous point-in-time recovery capability.

oCopy: This is the default. Like a full backup, it copies all files at the time of the snapshot. However, the critical difference is that it does not update the backup history of the files and does not truncate application logs.

oOther: This type is typically used for specific, non-standard VSS operations.

 

•Bootable System State: A specialized instruction for comprehensive disaster recovery scenarios where the ability to boot the system after a restore operation is the primary objective.

 

•Include Writers: The availability of this option depends on the Context selected. For example, it is not available for Client Accessible but is for Client Accessible with Writers. This setting allows you to specify which VSS Writers must be included in the shadow copy process. If they are not, then the profile run will fail.

 

•Exclude Writers: As with Include Writers, the availability of this option depends on the Context selected. This setting allows you to specify which VSS Writers should be excluded from the shadow copy process.

 

 

 

All Content: 2BrightSparks Pte Ltd © 2003-2026