Frequently Asked Questions

Product Information & Technical Details

What is Volume Shadow Copy Service (VSS) and how does it relate to Windows backups on EC2?

Volume Shadow Copy Service (VSS) is a Windows service that enables the creation of consistent "shadow copies" of volumes, even when they are in use. VSS is essential for application-consistent backups on Windows servers, including those running on AWS EC2. It coordinates between applications (writers), backup software (requestors), and storage providers to ensure data consistency. N2WS supports VSS through a lightweight backup agent installed on Windows instances, enabling consistent backups for applications like SQL Server, Exchange, and SharePoint. Note: VSS is specific to Windows environments; for Linux, alternative methods are required.

How does N2WS support VSS-based backups for Windows servers on AWS EC2?

N2WS enables VSS-based, application-consistent backups for Windows servers on AWS EC2 by providing a thin backup agent that installs in seconds on the Windows instance. This agent interacts with VSS to ensure that backups are consistent for supported applications and system components. The process is automated and does not require manual intervention. Note: VSS-based backups are only available for Windows workloads; for other operating systems, different backup methods are needed.

What types of applications are supported by VSS for consistent backups?

VSS supports consistent backups for all Microsoft applications that integrate with it, including Exchange, SQL Server, SharePoint, Active Directory, Windows Registry, and the file system. Some non-Microsoft applications, such as Oracle, also support VSS. N2WS leverages VSS to ensure backups of these applications are application-consistent. Note: Applications must have a VSS writer to participate in consistent backups; unsupported applications may not achieve application consistency.

What are the main components of VSS and how do they interact during a backup?

VSS consists of three main components: requestors (backup applications like N2WS), writers (applications that ensure data consistency, e.g., SQL Server writer), and providers (components that create and maintain shadow copies). During a backup, the requestor initiates the process, writers ensure data is in a consistent state, and providers create the shadow copy. If any writer fails or times out, the backup fails. Note: Proper configuration of all components is required for successful backups.

What are the two methods for creating shadow copies in VSS?

VSS supports two methods for creating shadow copies: Clone (a complete copy of a volume, typically provided by hardware or software mirroring) and Differential (copy-on-write, where only changed data blocks are stored). The differential method is more space-efficient initially but grows as changes accumulate. Note: The method used depends on the storage provider and system configuration.

Features & Capabilities

What features does N2WS offer for backup and disaster recovery?

N2WS provides automated backup and recovery for AWS, Azure, and hybrid cloud environments, near-instant recovery, immutable backups, cost optimization (up to 92% reduction in long-term backup costs), compliance and security tools, multi-cloud management, and granular restore capabilities. It also supports VSS for application-consistent Windows backups on EC2. Note: Some advanced features may require specific configurations or licensing; consult documentation for details.

Does N2WS support integration with other tools and APIs?

Yes, N2WS supports integration with third-party monitoring tools, identity providers, and compliance reporting solutions like Datadog, Splunk, and Bocada. It also offers a RESTful API for automation and integration, with documentation available at N2WS RESTful API documentation and a Quick Start and User Guide. Note: Integration capabilities may require additional setup or technical expertise.

What technical documentation is available for N2WS users?

N2WS provides comprehensive technical documentation, including a user guide (User Guide), release notes (Release Documentation), RESTful API docs, upgrade guides, and troubleshooting resources. These resources cover deployment, configuration, upgrades, and best practices. Note: Some documentation may require registration or support access.

Security & Compliance

What security and compliance certifications does N2WS have?

N2WS is independently certified to ISO/IEC 27001:2022 and is SOC compliant by inheritance through AWS and Azure. It also supports FedRAMP, ITAR, and CJIS compliance when deployed in AWS GovCloud. For a copy of the ISO certificate, contact customer.success@n2ws.com. Note: Some compliance features depend on the underlying cloud provider's certifications.

How does N2WS ensure data security and compliance for backups?

N2WS provides immutable, air-gapped backups, multi-factor authentication, end-to-end encryption (TLS/HTTPS), and customizable compliance reporting. It runs directly inside your cloud environment, inheriting AWS and Azure security features, and does not access or transfer your data outside your control. Automated compliance reports help with audits for HIPAA, SOC 2, and GDPR. Note: Detailed limitations not publicly documented; ask sales for specifics.

Use Cases & Benefits

Who can benefit from using N2WS for backup and disaster recovery?

N2WS is designed for cloud directors, IT managers, and managed service providers (MSPs) in enterprises, public sector, retail, education, transportation, nonprofits, healthcare, finance, and IT/software industries. Customers include Johnson & Johnson, Dyson, Skechers, City of Oakland, and Deutsche Bahn. Note: Best fit for organizations using AWS or Azure; teams with on-premises-only environments may need alternative solutions.

What core problems does N2WS solve for its customers?

N2WS addresses high disaster recovery costs (up to 92% storage savings), downtime and data loss (near-instant recovery), ransomware threats (immutable backups), manual backup inefficiencies (automation), compliance challenges (automated reporting), multi-cloud complexity (unified console), scalability for large data volumes, and long-term backup costs. Note: Some advanced features may require specific cloud configurations.

Can you share specific customer success stories using N2WS?

Yes. For example, Skechers standardized backup and recovery across a multi-cloud estate, St. John's University eliminated legacy tape storage and improved recovery, DB Systel automated backup for 1,500+ volumes and 700 servers, City of Oakland protected critical AWS data, and Gett saved 50% on cloud costs. See more at N2WS case studies. Note: Results may vary based on environment and implementation.

Implementation & Support

How long does it take to implement N2WS and how easy is it to get started?

N2WS can be implemented in as little as two weeks, supported by dedicated Customer Success Managers, onboarding calls, and comprehensive documentation. Deployment options include AWS Marketplace AMI or CloudFormation templates. A 30-day free trial is available without a credit card. See the install guide for details. Note: Implementation time may vary based on environment complexity.

What feedback have customers given about the ease of use of N2WS?

Customers report that N2WS is simple to use, with quick setup and intuitive management. For example, Shane H. (MSP) says, "It's very simple to use and we are a MSP for multiple companies. Support is great and quick to respond." Julian Ware (City of Oakland) notes, "You're just clicking and going. And, to me, that's what the modern world of backup is." Note: User experience may vary based on technical background and environment.

Competition & Comparison

How does N2WS compare to AWS Backup for Windows EC2 backups?

N2WS offers features not available in AWS Backup, such as DR backups of encrypted resources, 60-second backup intervals, multi-gen file/folder level recovery, and a user-friendly RESTful API (no Lambda scripting required). AWS Backup is limited to AWS environments and lacks VSS-based application consistency for Windows workloads. Choose N2WS for advanced features and multi-cloud support; choose AWS Backup for basic AWS-only backup needs. Note: AWS Backup may be preferable for teams with minimal compliance or automation requirements.

Windows Backup on EC2: Introduction to Volume Shadow Copy Service (VSS)

Volume Shadow Copy Service, or VSS, is a Windows service that allows you to take "shadow copies" of your volumes, even when they are in use.
Share post:

When backing up Windows Servers in EC2, one would naturally want to utilize the power of EBS snapshots. While EBS snapshots are crash consistent by nature, creating an application-consistent backup typically requires the backup software to interact directly with applications, be it databases or other.  And that’s where Volume Shadow Copy Service (VSS) comes in.

Windows applications are more integrated than Unix/Linux applications

Volume Shadow Copy Service (VSS) is a backup infrastructure for Window servers. It allows applications to integrate to it on one end, and backup software and storage hardware on the other. VSS creates “shadow copies” which are consistent copies of volumes that can be stored on the file system or in specialized storage devices and repositories. Introduced in Windows server 2003, VSS is the standard way to make consistent backup of Windows servers.

All Microsoft applications, like Exchange, SQL Server and SharePoint support VSS and other Windows components make sure backup is consistent by utilizing VSS: Active Directory, Windows Registry and the file system itself. Additionally, some non-Microsoft applications, such as Oracle, support VSS as well. The three main components of VSS are requestors, writers and providers:

  • Requestors – Applications that request for a backup or “shadow copy” to be created, like backup applications.
  • Writers – Applications that write data to volumes and support backing up their persistent data using VSS. Writers include: SQL Server writer, Oracle writer, NTFS writer etc… Writers make sure shadow copies are consistent from the application’s perspective.
  • Providers – Components that know how to create and maintain shadow copies (or backups). Windows comes with a system provider capable of storing the backup data into regular Windows volumes. Storage Arrays sometimes come with hardware providers that know how to store shadow copies.
vss diagram EC2 backup EBS
image taken this page on Microsoft’s site

VSS supports two methods for shadow copies

  • Clone: A complete clone of a volume usually provided by software or hardware mirroring. Storage hardware providers typically support this type.
  • Differential:  Changed data blocks from the original volume are copied to the shadow copy, to provide a consistent image for a certain point-in-time. This method is also called “copy-on-write.” With this method, the shadow copy consists of blocks in the volumes which were changed after the shadow copy was taken. This means that the amount of data is small at the beginning and grows over time.

Writers register with the Windows infrastructure the specific volumes they write to. For instance, a database that stores data of volume D: and logs in volume E:, will notify VSS that this application writes to these volumes. When a provider asks to create a shadow copy on a certain volume or volumes (e.g. D:), the infrastructure signals all the writers writing to that volume to make sure the persistent data on the volume is consistent.

This can be done by closing transactions, flushing queues, closing files etc… Once the provider receives indications that all writers are in a consistent state, it creates the actual shadow copy. Any errors from writers result in an error.

In addition, if a writer doesn’t respond in a timely fashion, the process will time out and fail.
While the shadow copy exists, backup software can use the frozen and consistent image of the volume to copy the data out as a valid backup.

Once the backup operation completes, the requestor notifies the VSS infrastructure that backup is completed and VSS notifies all relevant writers that backup was successful. Applications can automatically perform operations depending on successful completion of backup, like logs truncation.

VSS on EC2 and EBS Volumes

When running production Windows Servers on EC2 with EBS volumes for persistent data, the power of VSS can be leveraged. It is possible to implement a general-purpose file level backup solution that supports VSS in EC2.

While such a solution will result in consistent backups, all the advantages of EBS snapshots will be missed out. To take consistent backups of Windows applications and still benefit from the powerful capabilities of EBS snapshots, such as fast incremental backup and rapid recovery, a backup solution utilizing VSS with EBS snapshots is required. Such a solution will enjoy all worlds in terms of backup and recovery times as well as consistency of Windows applications.


N2WS is an enterprise-class backup solution for EC2 based on EBS & RDS snapshots. It supports VSS using a thin backup agent that is installed in seconds on the Windows instances. Consistent backup based on VSS is supported automatically. Try it for free.

You might also like

the disaster-proof backup & DR checklist

What your backup plan is missing...

Fortify your backup plan across every critical dimension with this checklist.