LogoLogo
EBR DocsHelp
Zmanda Pro
Zmanda Pro
  • Welcome to the Zmanda Pro Documentation
  • Overview and Concepts​
  • Best Practices
  • Start Here
    • Initial Security Setup
    • Step 1: Adding a User
    • Step 2: Client Download and Installation
    • Step 3: Client Login
    • Step 4: Adding a New Storage Vault
    • Step 5: Adding a New Protected Item
    • Step 6: Initiating a Backup
    • Step 7: Checking Backup Job Status
    • Step 8: Restore Data
  • Guide
    • Zmanda Pro Server Deployment (On-prem)
      • Zmanda Pro Self-Hosted Deployment
        • Self-Hosted Online Server
        • Self-Hosted Online Server Setup
        • Self-Hosted Offline Server
        • Self-Hosted Offline Server Setup
        • Storage Manager Service
        • Storage Manager Service Setup
        • Zmanda Pro Client Setup
        • Disaster Recovery Plan: Self-Hosted Server
        • Disaster Recovery Plan: Self-Hosted Server Recovery Workflow
        • Admin Password Reset
        • Custom Certificates Upload
    • Zmanda Pro Usage
    • Zmanda Pro Client Installation
      • Zmanda Pro user configuration
      • Storage configuration
    • Restarting at boot ​(Linux)
    • Protected Items
      • Files and Folders
      • MySQL
        • Xtrabackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MySQLDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • MariaDB
        • MariaBackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MariaDBDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • Microsoft Office 365
      • Postgres
      • Program Output
      • Microsoft Hyper-V
      • Microsoft SQL Server
      • MongoDB
      • Windows Server System State
      • Application-Aware Writer
      • Disk Image
      • VMware vSphere
        • Configuration
        • Backup
        • Restore
        • Troubleshooting
      • MariaDB
        • Backup & Restore MariaDB with a staging path
        • Backup & Restore MariaDB without a staging path using Streaming
      • Oracle RMAN
        • Configuration
        • Backup
        • Restore
        • Perform a Full Database Backup with Oracle RMAN
        • Perform a database backup using a Custom Oracle RMAN Script
        • Restore an Oracle RMAN backup using Backup Manager
        • Recover an Oracle database after restoring from Zmanda Pro Backup Manager
        • Troubleshooting Oracle RMAN backups with Backup Manager
    • Configure SSO
    • Configure & Apply Policies
    • Configure Email Reporting
    • Backup Manager
      • Login
    • Automation Tools
      • Bulk Operations with ZPAT
        • Bulk addition of policies
        • Bulk onboarding of devices
        • Bulk deletion of users
        • Bulk Rename of Devices
        • Bulk Restore
        • Bulk addition of protected items
        • Bulk administration of client devices with Ansible
      • Disaster Recovery Plan: Zmanda Pro Clients
    • Encryption & Key Management
    • Zmanda Pro Job Statuses
    • Disk Image Walkthrough
      • Create & Use Recovery Media
    • Common Problems & Solutions
    • Troubleshooting
    • VMware to Hyper-V Migration
      • Configuration
      • Backup
      • Restore to Hyper-V
Powered by GitBook
LogoLogo

Quick Links

  • Amanda Community Wiki
  • Amanda Community Downloads
  • Share Feedback

About

  • About Us
  • Customer Testimonials

Terms

  • Terms of Use
  • Privacy Policy

Contact Info

  • Denver, CO, USA
  • 888-496-2632 (US)
  • 408-732-3208 (INT)

2025 © Zmanda, A BETSOL Company

On this page

Was this helpful?

Export as PDF
  1. Guide
  2. Protected Items

Windows Server System State

PreviousMongoDBNextApplication-Aware Writer

Last updated 1 year ago

Was this helpful?

A System State backup captures essential data for your server, including:

  • Active Directory: Stores user accounts, groups, and permissions.

  • Boot files: Files required to start your server.

  • COM+ registration: Information for programs that use Microsoft's Component Object Model.

  • System Registry: A database storing server settings.

Having a System State backup allows you to restore your server to a previous working state in case of hardware failure, software corruption, or accidental data deletion.

Zmanda Pro supports System State backup on specific versions of Windows Server with the "Server Backup Role" enabled.

Verify the following before moving forward:

  • Local storage: Zmanda Pro requires a designated local storage space to temporarily store data during the backup process. This space, called the spool directory, has specific requirements:

    • Bare root drive: The drive letter representing the storage location shouldn't be associated with any folders or files.

    • Supports VSS: The storage drive must work with Microsoft's Volume Shadow Copy Service (VSS), which allows backups without interrupting server operations.

    • Minimum 10GB free space: Ensure the storage location has enough space to hold the temporary backup data.

    • Windows Server 2008/2008 R2: Avoid using system or critical volumes for the spool directory on these server versions. If necessary, refer to Microsoft KB944530 for a workaround using the registry.

    • Fixed drive appearance: Regardless of whether it's physically internal or external, the storage drive must appear as fixed (non-removable) to the Windows Server.

    • Removable drive workaround: If using a removable drive, create a shared folder on it and use the folder's UNC path (Universal Naming Convention) as the spool directory.

For detailed information on System State backups in Windows Server, refer to the following Microsoft resources:

  • Backing Up System State Data:

  • Wbadmin:

Restoring a System State Backup

After creating a System State backup with Zmanda Pro, you can use the wbadmin start systemstaterecovery command to recover the data onto a functioning Windows Server.

Alternative Backup Method

Zmanda Pro also offers an alternative backup method for System State – using the "Application-Aware Writer" Protected Item type. This method provides similar results to the standard method with some key differences:

  • No spool space required: This method doesn't require a designated storage space for temporary data during backup.

  • No .vhd file: The backed-up files aren't consolidated into a single .vhd file format.

  • Potential deduplication benefits: This method might offer better data deduplication during backup, reducing storage requirements.

  • Bootloader file exclusion: However, this method might not capture bootloader files, which are crucial for server startup.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc938537(v=technet.10)?redirectedfrom=MSDN
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc742124(v=ws.11)?redirectedfrom=MSDN