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
  • Selecting components
  • VSS Mode​
  • Backing up Oracle Database
  • Backing up MS SQL Database​

Was this helpful?

Export as PDF
  1. Guide
  2. Protected Items

Application-Aware Writer

What is the Application-Aware Writer?

Imagine taking a snapshot of your entire server at a specific point in time. That's what a regular backup does. But what if you only want to back up the critical data of a specific program? That's where the Application-Aware Writer comes in.

It leverages a technology called VSS (Volume Shadow Copy Service) built into Windows Server. VSS works with certain software programs to ensure their files are in a consistent state during a backup. This allows Zmanda Pro to capture only the essential data used by that program, for a more focused and efficient backup.

Benefits of Application-Aware Backups:

  • Targeted Protection: Back up only the crucial data of specific applications, like databases or email servers.

  • Reduced Backup Time: By focusing on specific data, backups can be completed faster compared to full server backups.

  • Improved Recovery: In case of software failure, you can restore just the application data, minimizing downtime.

Examples of Supported Applications:

  • Oracle Database

  • Microsoft SQL Server

  • Microsoft Exchange Server

  • Microsoft SharePoint

  • Many other applications with built-in VSS Writers

Important Considerations:

  • Potential Cost: Using the Application-Aware Writer might incur additional charges depending on your Zmanda Pro plan.

  • Not for Everything: This method is ideal for specific software with VSS Writers. Regular file backups are still recommended for general server data.

  • Focus on Application Data: This Protected Item type is designed for backing up specific applications. If you want to back up regular files and folders with a VSS snapshot, use the "Files and Folders" Protected Item type with the "take filesystem snapshot" option enabled.

Selecting components

  1. In Zmanda Pro, during backup configuration, select the "Application-Aware Writer" option.

  2. Clicking the "Edit" button ( pencil icon) will display a list of VSS Writers installed on your server. These represent the applications Zmanda Pro can back up using this method.

Choosing What to Backup:

  • Full Application Backup: You can select the top checkbox next to the VSS Writer name. This includes all data managed by that application in the backup.

  • Granular Selection: For applications that allow it, you can choose specific components to back up. For example, with the Microsoft SQL Server VSS Writer, you can select individual databases instead of the entire server.

Understanding Non-Selectable Components:

  • Some VSS Writers might have certain components pre-configured as non-selectable. These will appear as greyed-out options without checkboxes in Zmanda Pro.

VSS Mode​

Zmanda Pro offers various VSS backup modes for Application-Aware Writer backups. These modes determine how the application's data is captured in the backup. However, the specific behavior of each mode depends on the individual VSS Writer for the application you're backing up.

Here's a breakdown of the common modes:

  • VSS Full: Creates a complete backup of the application data, including all files and configurations. This is the most comprehensive option but also requires the most storage space.

  • VSS Copy: Similar to Full, it captures a complete copy of the application data. However, the VSS Writer might behave differently regarding log files. Some might copy and retain them, while others might copy and then remove them (similar to SQL Server truncating logs).

  • VSS Incremental: Captures only the changes made to the application data since the last backup (either Full or Incremental). This can save storage space but requires keeping all previous backups for complete restoration.

  • VSS Differential: Creates a backup containing only the changes since the last Full backup. It's more space-efficient than Full backups but requires both the Full backup and the Differential backup for restoration.

Choosing the Right Mode:

  • Limited Information: Unfortunately, Zmanda Pro cannot definitively explain each mode's behavior due to variations between VSS Writers.

  • Refer to Application Documentation: For a clear understanding of how these modes function for your specific application, consult the documentation for its VSS Writer.

  • Recommendation: Zmanda Pro recommends setting the backup mode to match your existing regular backup jobs. Typically, these are either Full or Copy backups. This ensures consistency in your overall backup strategy.

Important Note:

If you choose a mode not supported by the VSS Writer for your application, Zmanda Pro will default to the Full backup mode to ensure a complete capture.

Backing up Oracle Database

Zmanda Pro utilizes the built-in Oracle VSS Writer for application-aware backups of your Oracle Database. This VSS Writer is generally available with Oracle Database 11g and later versions (including 12c and 18c). For Oracle Database versions 10g or 9i, you might need to install a separate, newer version of the Oracle VSS Writer.

Important Note:

  • SYSDBA Privileges: The Oracle VSS Writer requires SYSDBA permissions to access the database for backups. Your database administrator will ensure this access is granted.

  • Deduplication and Storage Efficiency: Our service can perform deduplication on Full or Copy backups created at the VSS component level. This helps optimize storage usage even with incremental backups.

How to Back Up Your Oracle Database?

  1. Log in to the web-based interface provided by our service. Your administrator will grant you the appropriate permissions.

  2. During the backup configuration process, choose the "Application-Aware Writer" option.

  3. A list of available VSS Writers will appear. Select "Oracle VSS Writer - ORCL" to initiate an Oracle database backup.

  4. Depending on your needs, you can choose to back up the entire database or select specific parts like individual tablespaces.

  5. Our service offers various backup modes, including Full, Copy, Incremental, and Differential. Choose your backup mode

  6. Once you've selected your options, initiate the backup process. Our service will handle capturing the chosen Oracle Database data using the Oracle VSS Writer.

Understanding Backup Modes:

  • Full Backup: Creates a complete copy of your entire Oracle Database, including all data files and configuration settings. This offers the most comprehensive protection but requires the most storage space.

  • Copy Backup: Similar to Full Backup, it captures a complete copy of your database. However, the handling of log files might differ slightly. It's recommended to consult your Oracle Database documentation for specifics.

  • Incremental Backup: Captures only the changes made to your Oracle Database since the last backup (either Full or Incremental). This can save storage space but requires keeping all previous backups for complete restoration.

  • Differential Backup: Creates a backup containing only the changes since the last Full backup. It's more space-efficient than Full backups but necessitates both the Full and Differential backups for restoration.

Backing up MS SQL Database​

Understanding Backup Modes:

  • Full Backup: Creates a complete copy of your entire SQL Server database, including all data files and configuration settings. This offers the most comprehensive protection but requires the most storage space.

  • Copy Backup: Similar to Full Backup, it captures a complete copy of your database. However, the handling of transaction logs might differ slightly. It's recommended to consult your SQL Server documentation for specifics.

  • Incremental Backup: Captures only the changes made to your SQL Server database since the last backup (either Full or Incremental). This can save storage space but requires keeping all previous backups for complete restoration.

  • Differential Backup: Creates a backup containing only the changes since the last Full backup. It's more space-efficient than Full backups but necessitates both the Full and Differential backups for restoration.

Important Notes:

  • VSS Writer Requirements: The Microsoft SQL Server VSS Writer might require specific permissions to access the database for backups. Your database administrator can ensure this access is granted.

  • Deduplication and Storage Efficiency: Our service can perform deduplication on Full or Copy backups created at the VSS component level. This helps optimize storage usage even with incremental backups.

  • Refer to Microsoft's Documentation: For a clear understanding of how these VSS Writer modes function specifically with your SQL Server version, consult the documentation provided by Microsoft.

PreviousWindows Server System StateNextDisk Image

Last updated 1 month ago

Was this helpful?

Refer to Oracle's Documentation: For a clear understanding of how these VSS Writer modes function specifically with your Oracle Database version, consult the .

documentation by Oracle