Skip to end of metadata
Go to start of metadata

Table of Contents

 Click to view the Table of Contents...

 

System Requirements

Your system must meet the following requirements:

  • Windows Version
    • Windows XP (Home or Pro) with SP2 or higher.
    • Windows Vista.
    • Windows 7.
    • Windows Server 2003 SP2.
    • Windows Server 2003 R2.
    • Windows Small Business Server 2008.
    • Windows Server 2008.
    • Windows Server 2008 R2.
    • Windows Small Business Server 2011.
    • Windows 8 and 8.1.
    • Windows Server 2012 and Server 2012 R2.
  • Hardware
    • Dual-core CPU.
    • 2GB of memory.
    • 10GB of free space on the disk where ZCB is installed.

      • Additionally, every disk to be backed up must have space for VSS snapshots. At least 10% free space is required, and 20% free space is recommended.

  • Other Requirements
    • Java 7 or higher is required.
    • The Windows locale must match that language chosen for ZCB, or a Windows language pack must be installed that matches the language chosen for ZCB.
    • The Remote Registry Service must be enabled before installation.
    • The Volume Shadow Copy Service (VSS) must be enabled. Although the Volume Shadow Service is enabled by default, it may have been turned off after Windows installation.
      • To ensure that VSS is running:
        • Right-click the My Computer icon and choose Manage from the pop up menu.
        • Expand the Services and Applications tree and locate the Volume Shadow Copy Service. If it is not started, change the General Properties to make the Startup Type Automatic.
    • ZCB must be installed and all ZCB operations must be performed as a user that has Administrator privileges.
    • ZCB depends up on the Visual C++ Redistributable. VC++ must be installed and in working order on the system.

Supported Backup Types

The following types of data can be backed up and restored by Zmanda Cloud Backup.

  • Windows NTFS files and folders
  • Windows ReFS files and folders
  • Microsoft SQL Server 2000, 2005, 2008, 2012, and 2014
  • Exchange Server 2003, 2007, 2010, and 2013
  • Microsoft SharePoint Server 2007/WSS 3, 2010, and 2013
    • Standalone and Single-Server Sharepoint Farm Configurations are supported.
    • Multi-server Sharepoint Farm Configurations are not supported.
  • Windows System State (including the registry, certificate server, and active directory information)
  • MySQL Server 5.x
  • Oracle Server 11i and 11g.
  • Hyper-V (Windows 2008 and 2012 only)
    • Server "core" installations are not supported for Windows 2008 or 2012

SQL Server, Exchange Server, SharePoint, and Hyper-V server configurations are automatically discovered by ZCB.

Getting Started

Quick Start

The Quick Start guide includes instructions on how to install and configure your first backup with ZCB. Please click Help > Getting Started within ZCB, or locate the Quick Start guide at http://help.zmanda.com. 

Installation

ZCB installation involves two steps: install the software and import the cloud certificate. Product downloads and the cloud certificate are available on the Zmanda Network Downloads screen.

If the product downloads and/or the cloud certificate are not available for download, please see Purchase & Payment Verification Errors.

Installation

ZCB uses the InstallShield installer and self-extracting .exe files for installation. After the installer is downloaded, double-click the file to begin installation. 

The amandabackup user

A new user named amandabackup is created during installation. ZCB uses amandabackup for all backup-related tasks.

For more information about amandabackup, please see What is the amandabackup user?

Import the cloud certificate

ZCB uses a cloud certificate to verify subscription status. A valid subscription is required in order to perform backups.

The cloud certificate must be downloaded from the Zmanda Network Downloads screen. Once downloaded, import the certificate into ZCB using the Cloud > Import Cloud Certificate menu option.

Command-line installation

ZCB can be installed via command line. Please see Command-line installation and configuration of ZCB.

Terminology

The following terms are used throughout this document.

Backup Types

Zmanda Cloud Backup supports the backup of many types of data, such as File System, System State, Microsoft SQL Server, and more. These are referred to as backup types

Please refer to the Supported Backup Types section for details.

Backup Sets

What to back up, when to back it up, how long to keep it, and other such configuration parameters are collectively referred to as a backup set. Each backup set has its own unique name, chosen by the user, and may only contain one backup type. 

For example, you cannot back up an Exchange database and Windows System state in the same backup set. Instead, you must create a new backup set for each type of backup.

Working with Backup Sets

Backup sets are listed along the left edge of the ZCB display. While on the Backup tab, you can create, edit, activate, deactivate, validate, delete, or clone backup sets. You can also trigger a backup to take place immediately with the Backup Now option.

All of these options are shown in a toolbar at the top of each backup set. The same operations are also available in the File menu or by right-clicking the backup set icon on the left side of the program. 

Backup Now: Use this option to begin a backup immediately, in addition to any regularly scheduled backups. 

Enable/Disable a backup set: An Enabled backup set will perform scheduled backups and be eligible for a restore operation. A Disabled backup set will not perform scheduled backups, but will be eligible for a restore. Disabled backup sets cannot use Backup Now. A Disabled backup set that is Enabled will begin backing up according to its schedules. By default a backup set is in the Enabled state.

A backup set must be saved after it is Enabled or Disabled in order for the change to take effect. 

Validate a backup set: This is a simple way to check whether the essential configuration for the backup set is correct or not. A failed validation indicates that a backup cannot be performed, and an error is returned to the user. Backup set configurations are automatically validated when the backup set is saved and before any backup run is performed. 

Delete a backup set: When the Delete Backup Set operation is chosen, ZCB will present the user with the following two options. 

Delete this backup set configuration and all associated backup data from cloud and disk.

    • Selecting this operation will remove the backup set from ZCB. All data associated with the backup set, on both the local disk and on the cloud, will be deleted. 
    • Deletion of data, especially from the cloud, can take a long time. Please be patient. 
    • A popup will appear to confirm the choice.

Just delete the configuration for this backup set from this computer, but retain the associated backup data.

    • Selecting this operation will remove the backup set from ZCB, but all data will be left intact on both local disk and the cloud.
    • A popup will appear to confirm the choice.
    • The backup set can be recovered by running a Restore Catalog operation.

Backup data that is deleted cannot be recovered.

Copy a backup set: This option will create an exact copy of the current backup set. Schedules can be carried over to the cloned backup set, or not, at the user's discretion.

The copied backup set can then be modified as necessary. Users who wish to create multiple, similar backup sets can use the clone feature to reduce setup time.

Backup Levels

Full backups, Differential backups, and Incremental backups are the three backup levels. Not all backup types will support all three backup levels. 

Full backup: This type of backup will back up all of the data associated with the backup set.

Differential backup: This type of backup will back up only the data which changed since the last successful full backup.

Incremental backup: This type of backup will back up only the data which changed since the last successful full, differential, or incremental backup.

For more information, please see What are Incremental and Differential backups?

Backup Runs

Each time a backup is performed, whether by schedule or manually, it creates a unique entry on the Report page. Each such entry is a backup run. A backup run will list details such as start time, end time, and backup size, and if successful will have an associated archive of backup data.

In most cases, backup runs can be restored, managed, and deleted independently of other backup runs. 

Other operations can also have runs. Restore runs, upload runs, and download runs are also possible.

Configure Backup Sets

Every backup set for every backup type is configured with the same basic steps. Users select what to back up, where to put the data, when to back up, and how long to keep the backups. 

Unless noted, settings for one backup set do not affect other backup sets. 

Add new backup set

Click the add new backup set button to create a new backup set at any time. Backup sets can also be added via the File menu. If there are no backup sets created, such as on a new installation, a message to create a backup set will appear in the middle of the window with an additional button. 

Default Settings

Every backup set comes with default settings that represent the best practice for the average user. The defaults may vary from one backup type to another.

The defaults are the best choice in most situations. 

What would you like to back up?

When a new backup set is created, a list of available backup types will appear. Choose the type of data you wish to back up.

Not all systems will have all backup types enabled. File System, System State, and MySQL backups are always enabled on all systems. All other backup types will be enabled if detected on the system, and disabled if not detected on the system.

The screen will change once the backup type is chosen. 

Backing up

Once a backup type is chosen, the What would you like to back up? section is replaced by a section named Backing up. Most backup types allow users to select individual items, such as files, folders or databases. A tree will appear if such granular selections are possible. Place checkmarks next to the items you wish to back up. 

For some backup types, such as System State, granular selection is not possible. A list of items to be backed up will be displayed instead.

A dropdown box above the tree shows the type of data to be backed up. Users may choose a different type of data from this menu until the backup set is saved. Once the backup set is saved, the backup type is locked and cannot be changed.

Estimate Backup Size

This button, found below the tree or list in the Backing Up section, estimates the size of a full, uncompressed backup of the data selected. It also does not take various file exclusions into account. 

Compression is enabled by default. The actual size of a backup will nearly always be smaller than the estimated size due to compression or file exclusions. 

Set your backup location

This section controls where backups are stored. It contains three options.

Backup To

Each backup run will save a backup archive to one or more locations, as determined in the Backup To section. The three options are:

Backup to Disk and Cloud: The backup archive will be saved to disk, then uploaded immediately and automatically when the backup is finished. Backup to Disk and Cloud is the default choice all Backup Types and is recommended for all users. This hybrid backup approach allows fast recovery from local disk and safeguards against disaster by storing the backups in the cloud. 

Backup To Disk: The backup archive will be saved to the chosen disk location only. An upload can be scheduled at a later time, if necessary. 

Backup to Cloud: The backup archive will be saved to the chosen cloud storage location only. Please see Info: Limitations of the Backup to Cloud operation for important information.

Disk Storage

Choose the location on disk where you wish to store your backups. This location can be a local disk, an external disk, or a network location.

The amandabackup user must have access to the selected folder. Backups to network locations may involve additional configuration to grant access to amandabackup. Please see How to use external or mapped network drives with ZCB.

ZCB also supports the use of most NAS devices as a storage destination. Please see How to use a NAS device with ZCB.

Cloud Storage Geography

CSB has data centers in both the United States and in Europe. Choose the location you wish to use.

Users may change their Cloud Storage Geography until the backup set is saved. Once the backup set is saved, the Cloud Storage Geography is locked and cannot be changed.

Edit your backup schedule

This section controls when ZCB performs a backup. The default settings are based on our average users' needs. 

Every backup level (full, differential, or incremental) requires its own schedule.

Schedule Templates

Alternative schedule templates are available in the Schedule Templates dropdown box. These allow users to quickly and easily switch between different schedule plans. 

Each backup type has its own default schedules and schedule templates.

Add Custom Schedules

Custom schedules can be created if the defaults do not exist. Select Add Custom Schedule from the Schedule Templates dropdown box. All existing schedules in the current backup set will be removed. 

The Add Schedule button to add a new schedule. Keep in mind that a separate schedule is required for each backup level. 

Schedule an Upload

The default Backup to Disk and Cloud option will upload backups immediately once they are complete. If it is necessary to upload at a later time, use the Backup to Disk option. Then create a Custom Schedule. An Upload checkbox will appear in the Edit Schedules dialogue. Place a check in the box, select a time, and save the schedule. All backups on disk for the current backup set that have not yet been uploaded will be uploaded at the time specified.

Edit Existing Schedules

Any schedule can be edited, whether it is part of a template or a custom schedule. Double-click the schedule to bring up the edit schedule dialogue. 

Delete a Schedule

Click the X icon to the right of any schedule to delete that schedule.

Retention settings

This section controls how long backups are stored on disk or cloud. Expired backups are purged within 24 hours of expiration.

Backups are only removed based on retention or by manual deletion. Every backup is added to disk or cloud without overwriting previous backups. It is thus important to set a retention policy that suits your needs while also staying within your chosen storage budget. 

ZCB allows you to specify a separate retention policy for backups stored on disk and backups stored on the cloud.

While configuring a retention policy, consider the following:

  • Importance of older backup data, to ensure that you have access to older files even if those files have been deleted or modified and are not contained in newer backup runs. Past backups also allow for recovery from viruses such as Cryptolocker, which encrypt users' data with unbreakable encryption. 
  • Free space on disk and/or cloud, to ensure that your backups do not fail due to lack of space. 

Retention Types

Users may choose between two types of retention.

Number of Cycles: This option allows users to keep a chosen number of backup cycles. A backup cycle is a full backups plus all associated incremental and differential backups. When a new full backup is completed, excess backup cycles are purged. Please see Info: Number of successful full backups to retain for more information.

Time Retained: This option allows users to keep backups for a specific period of time. Time-based retention has two special overrides to prevent deletion of backup data due to a misconfiguration of the retention policy. Both options are enabled by default, and we strongly recommend that they not be disabled.

Always Retain Last Full Backup: If this override is checked, the most recent Full Backup will not be purged even if it meets its retention period. This option ensures that you always have one Full backup to restore from.

Keep Backup if a Dependent Backup Exists: If this override is checked, a backup will not be purged if another backup depends on it. In other words, no backup in a cycle will be purged until all of the backups in that cycle are ready to be purged. This option ensures that you have all the data that is needed to perform a complete restore to any available backup point.

Special Retention Values

ZCB offers two special retention values.

Forever: Change the retention value to 0 (zero) to keep backups forever. A backup set to keep Forever will never expire. It will never be purged automatically, but it can be deleted manually. Remember that backups do not overwrite each other. Please ensure that you have ample space on disk and/or cloud if you choose to keep backups forever.

Delete After Upload: Only available for Disk backup retention, this causes the backup on disk to be deleted immediately after it is uploaded to the cloud. Only backups that have successfully uploaded will be deleted. Set your retention value to -1 to use the Delete After Upload option. 

Advanced backup settings

This section controls advanced settings.

Data Encryption

ZCB offers two different types of encryption.

Auto Encryption

CSB will automatically encrypt your backups on the cloud.

Transfer of your backup data to the cloud is secure using the Secure Sockets Layer (SSL) protocol.

The encryption itself takes place server-side on the cloud. Auto Encryption only applies to backups stored on the cloud. Local backups will not be encrypted if Auto Encryption is chosen. If encryption of locally-stored backups is required, you must use the Private Key Encryption option.

Private Key Encryption

With Private Key Encryption, users create a unique encryption key generated from a passphrase. The encryption key or passphrase is required in order to restore data.

Private Encryption Keys will encrypt your backups using AES-256 bit encryption. AES-256 bit encryption is trusted worldwide.

If Private Key Encryption is chosen, you are responsible for safe and secure storage of your encryption keys. ZCB does not store your encryption keys or passphrase anywhere. Replacement keys can be created if you remember your passphrase. Replacement keys can be used to decrypt backups.

If you lose your private encryption key and forget your passphrase, no one will be able to decrypt your encrypted backup data.

Create a new Private Encryption Key  

First, create a personal encryption key. To create the key:

  1. Click the Edit button to the right of the Advanced backup settings panel.
  2. Click Add Private Key with 256-bit encryption.
  3. A new window will appear.
  4. Enter a Key Name. This will be the name of the file stored on disk.
  5. Choose a passphrase. 
    1. The passphrase must be at least four characters in length.
  6. Confirm the passphrase.
  7. Choose a location to which your encryption key will be saved. 
    1. The key must remain in this location in order to encrypt your backups.
  8. Click OK.
  9. A new window will appear to confirm that the encryption key was created.  
  10. Click OK.
  11. Save the backup set.
  12. All future backups for this backup set, local and cloud, will be encrypted using your Private Encryption Key.
    1. Past backups, if they exist, are not retroactively encrypted.

Add an existing Private Encryption Key to a backup set

You may use an already-existing Private Encryption Key with other backup sets.

  1. Click the Edit button to the right of the Advanced backup settings panel.
  2. Click Add Private Key with 256-bit encryption.
  3. A new window will appear and ask you if you wish to use the existing key.
  4. Click Enable.
  5. Save the backup set.
  6. All future backups for this backup set, local and cloud, will be encrypted using your Private Encryption Key.
    1. Past backups, if they exist, are not retroactively encrypted.

Delete an existing Private Encryption Key

To delete an encryption key:

  1. Select any backup set for which Private Key Encryption is enabled.
  2. Click the Edit button to the right of the Advanced backup settings panel.
  3. Click Delete Private Key.
  4. A window will appear to confirm your deletion and warn that a copy of the key should be kept for decryption purposes.

Existing Private Encryption Keys cannot be modified. To change a key, first delete a key and create a new one.

Compression

Compression makes the backups smaller. A small backup can be uploaded to cloud much faster than a large one. This can help save network bandwidth and reduce the storage space required for backups. 

Compression is either ON by default, but can be turned OFF.

CSB cannot accurately predict how much any given backup set will compress. Some data, such as text documents and databases, will compress very well. Other data, like most multimedia files, does not compress well.

Bandwidth Throttling

By default, ZCB attempts to transfer data to and from the cloud at the maximum possible speed. In other words, ZCB will use all of the bandwidth it can.

Bandwidth Throttling allows users to limit the amount of bandwidth used by ZCB. Throttling can be set at a global level (affecting all backup sets), or configured for a specific backup set. 

Users may select a maximum bandwidth allotment separately for upload and for download. Also, users may choose to have throttling always apply, or to only apply at certain times.

All throttle speeds are in kilobits per second. A value of 0 means the speed is unlimited.

Throttle By Speed

The Throttle By Speed option sets a maximum bandwidth allotment that is always on. 

Throttle By Time

This option allows you to throttle only at certain times and on certain days. For example, it is possible to throttle from 8am to 5pm on every weekday. Time-based throttling is highly configurable; values can be set in 15-minute increments. 

Click the buttons for Max Upload Rates or Max Download Rates to begin configuration. A time table will appear. Select the cells from the time table shown and input the desired value in the Maximum Rate (kbps) box. Click on Apply Custom Rate to Selected Slots to apply the provided value to the selected slots. Please note that configured values take effect only for future data transfers. Any ongoing jobs will continue to use any previously configured values.

For ease of use, ZCB comes with predefined templates for time based bandwidth throttling. You can choose a template from the Choose Predefined Template dropdown. If you wish to tweak the template values, you can select the time slots as described above and configure different values.

Custom Scripts

ZCB can run batch scripts before and/or after any given backup. There are strict requirements for batch scripts used in this manner. Please see How to use batch scripts with ZCB for more details.

Email notification preferences

An email can be sent to report the status of any given operation. A SMTP server must be specified.

Click the Edit button or visit Preferences > Email to specify SMTP server information. Once configured, email notifications are enabled for all backup sets. 

By default, emails are sent only when an operation has Failed. Emails can also be sent after a Success or a Warning. 

 

Backup Details and Requirements

Every backup type has its own requirements. Application and database backups, in particular, must meet the proper requirements. Some backup types also have special configuration options.

Backup the Windows File System

Windows File System refers to files and folders stored on local, external, or network disks.

Overview

File System backups have the following properties:

  • NTFS and ReFS file systems are supported.
  • There are no restrictions on file size. 
  • Any file of any extension can be backed up. This includes virtual hard disks, such as those used for virtual machines.
  • Open, locked, and in-use files can be backed up, if files are on a local disk (including external harddrives) and the Volume Shadowcopy Service (VSS) is started.
  • Backup of mapped network drives is supported.
  • Backup of NAS devices is supported.
  • ZCB can be used to backup and restore folders that participate in DFS replication topology.

    • ZCB must be installed on the host where replicated the DFS share is configured. ZCB relies on the DFSR VSS Writer for correct functionality of backup and restore operation.

    • Backup and restore of a network shared folder which is a member of a DFS replication group is not supported.

  • Junction Point Directories in Windows Vista, Server 2008, or higher will not be backed up to ensure that backups do not include the same data multiple times.
  • ZCB will automatically exclude all files and folders contained in its own directories from File System Backups. The folder where local backups are stored will also be excluded, so that ZCB will not back up its own backups recursively.
    • Do not store files you wish to back up under any ZCB-related folder.
  • Certain system files are automatically excluded from File System backups. These files are included as part of a System State backup.

Backup Levels

File System backups support Full, Differential, and Incremental backups.

Special Options

The following special options are available for File System backups. 

Exclude Files

Files and folders can be excluded from a File System backup. Exclusions are listed below the file tree.

Click the dropdown menu to see pre-configured exclusion lists, or manually enter a list of files or folders.

Wildcards are accepted in the exclude specification. Wildcards include:

  • The asterisk ( * ), which replaces any number of characters.
  • The question mark ( ? ), which replaces a single character.

Separate exclusions with a space. 

Example 

Here is an example list of exclusions: *.pst C:\Folder\* *$Recycle* file?.txt C:\Folder\document.doc

  • The *.pst entry excludes any file with the .pst extension.
  • The C:\Folder\* entry excludes all files and folders (including subfolders) under C:\Folder\.
  • The *$Recycle* entry excludes any file or folder that contains $Recycle in the path.
  • The file?.txt entry excludes any file that has any single character between "file" and ".txt", such as file1.txt or filex.txt. File32.txt would not be excluded.
  • The C:\Folder\document.doc entry only excludes the single file at C:\Folder\document.doc. 

Requirements

The following requirements must be met for Windows File System backups to function.

  • The Volume Shadowcopy Service must be started and functional for open, locked, or in-use files to be backed up.
  • The amandabackup user must have access to the files to be backed up. 

Backup the Windows System State

Windows System State refers to a collection of several key operating system elements and their files. Backing up the Windows System State is crucial for a successful disaster recovery strategy. 

Overview

Windows System State backups have the following properties:

  • System State will contain all of the following, if they are present on the system. Components that are not installed will not be backed up. For example, if Active Directory is not installed, then Active Directory will not be included in the System State backup. 
    • Boot Files:
      • For Windows versions older than Vista: SystemDrive\NTDETECT.COMSystemDrive\ntldrSystemDrive\boot.ini (SystemDrive is usually C:).
      • On Windows Vista and newer: SystemRoot\boot directory (SystemRoot is usually C:\Windows)
    • Catalog files:SystemRoot\System32\CatRoot.
    • MachineKeys Files:SystemRoot\System32\Microsoft\Protect* and AllUsersProfile\ApplicationData\Microsoft\Crypto\RSA\MachineKeys* where ALLUSerProfile is C:\Documents and Settings\All Users.
    • Performance counters: perf*.dat and perf*.bak files in C:\windows\system32 on all Windows versions.
    • WFP files: All dll and exe files that come under Windows File Protection (WFP). Usually the dll files reside in C:\Windows\system32
    • IIS metadata file if IIS is installed (applicable to all Windows versions).
    • Certificate Database (Applicable to only Windows 2003 server that are Certificate Servers): files in C:\Windows\system32\certsrv
    • COM+ registration database.
    • Registry: System, default, SAM, Security and Software files in SystemRoot\system32\config and additional Components and Schema files in Vista.
    • Active Directory: If Active Directory is installed, backups include the database, log files, and Group Policy Objects (GPOs).
  • System State components cannot be chosen individually. System State will always back up all components currently installed on the system.
  • Files included in a System State backup are automatically excluded from File System backups. Please see Default Exclusions from File System Backups for more information. 

Backup Levels

Windows System State backups are always a full backup. Differential and incremental backups are not supported. 

Requirements

The following requirements must be met for Windows System State backups to function.

  • System State backups and Microsoft SQL Server backups should not be run simultaneously.
  • The Volume Shadowcopy Service must be started.
  • System state backups of a Windows Domain controller that holds the Active Directory Certificate Services role may encounter a "Application's Writer is Not Available" error. 

 

Backup a Microsoft SQL Server

Microsoft SQL Server is a database application. It can stand alone or be part of another application.

Overview

Microsoft SQL Server backups have the following properties:

  • Microsoft SQL Servers are automatically discovered at backup set creation.
  • Individual databases can be selected for backup.
  • Only databases are backed up. 
    • Other MSSQL files, such as installation, files are not backed up. Include these files as part of a File System backup to protect them.
  • Transaction logs are truncated during any full or incremental (log) backup. Transaction logs are not truncated during differential backups.
  • Only databases that are in the Mounted state will be backed up.
  • System databases are only backed up during full backups. They are skipped during differential and incremental (log) backups. 
  • Read-only databases are only backed up during full backups. They are skipped during differential and incremental (log) backups. 
  • Only local databases can be backed up. Backups of databases on another system are not supported.
  • New databases will be automatically detected and backed up if all databases are selected selected for backup. 
  • Databases that are removed from a Microsoft SQL Server will be automatically removed from the backup if all databases are selected for backup. 
  • Databases are not automatically added or removed from the backup if individual databases are selected. 

Recovery Models

Databases configured with the SIMPLE recovery model, FULL recovery model, and BULK recovery model are supported.

Simple Recovery Model

  • The full backup will contain .MDF, .LDF and .NDF (in case of filegroups) files in the backup image.
  • The differential backup will contain .LDF files.
  • Incremental (Log) backups will be skipped for databases using the Simple Recovery Model.

Full Recovery Model

  • The full backup will contain .MDF, .LDF and .NDF (in case of filegroups) files in the backup image.
  • The differential backup will contain the changed blocks of the .MDF database file.
  • Incremental (Log) backups will contain .TRN files (transaction logs flushed to the disk). These are transactions that have changed since the last backup of any level, be it Full, Differential, or Incremental.

Bulk Recovery Model

  • The full backup will contain .MDF, .LDF and .NDF (in case of filegroups) files in the backup image.
  • The differential backup will contain the changed blocks of the .MDF database file.
  • Incremental (Log) backups will contain .TRN files (transaction logs flushed to the disk). These are transactions that have changed since the last backup of any level, be it Full, Differential, or Incremental.

Backup Levels

Microsoft SQL Server backups support Full, Differential, and Incremental (log) backups.

Special Options

The following special options are available for Microsoft SQL Server backups. 

Allow Access

The amandabackup user must have access to the databases. The Allow Access button, located beneath the database tree, attempts to automatically add amandabackup to the proper roles. There are two possible results:

  • Access Granted: CSB was able to add amandabackup to the proper roles for all instances.
  • Access Denied: CSB was not able to add amandabackup to the proper roles for one or more instance. The amandabackup user must be added manually. Please see Allowing access to Microsoft SQL Server
    • Adding amandabackup manually does not change this result to Access Granted. The Allow Access button's only function is to try to add the user. It does not validate if amandabackup is present or not.

Requirements

The following requirements must be met for Microsoft SQL Server backups to function. Unmet requirements are the most common cause of MSSQL backup failures.

  • The amandabackup user must be added as a SQL server user with sufficient privileges. Please see Allowing access to Microsoft SQL Server.
  • The Volume Shadowcopy Service must be started. 
  • Microsoft SQL Server and Windows System State backups should not be performed simultaneously. 
  • The SQL VSS Writer Service must be running at the time of backup. CSB will attempt to start the service if it is disabled.
  • TCP/IP must be enabled for all MSSQL instances to be backed up. TCP/IP settings are controlled in the SQL Server Configuration Manager tool.
  • Transaction log-based databases such as Microsoft SQL Server, Exchange, or Sharepoint are not intended to be backed up by multiple backup applications. 

 

Icon

ZCB can perform differential backups of SQL Server 2014 databases with memory-optimized tables. However, preview builds of SQL 2014 are not optimized for differential backups.

In CTP2 (Community Technology Preview 2) or earlier, the differential backup will include all data and delta files as if it were a full backup. There will be no reduction in size; a differential is essentially the same thing as a full backup.

SQL 2014 RTM (release-to-manufacturing) is optimized so that differential backups are smaller than full backups in the expected manner.

Please see this page for more information: http://blogs.technet.com/b/dataplatforminsider/archive/2014/02/07/differential-database-backup-with-memory-optimized-tables.aspx

Icon

Microsoft Sharepoint databases can be backed up as if they were Microsoft SQL Server databases. If possible, use the Sharepoint backup type to back up Sharepoint databases.

Do not back up Microsoft Sharepoint databases in more than one backup set. The result is the same as if multiple backup applications were used. See Info: How do databases handle backups from multiple different backup applications? for more information.

 

 

 

Backup a Microsoft Exchange Server

Microsoft Exchange Server is an email-based communications server. 

Overview

Microsoft Exchange Server backups have the following properties:

  • VSS based backups of Store database files (.edb & .stm), transaction logs, and checkpoint files for all the Mounted Storage Groups are performed.
  • Mailbox Databases and Public Folder Databases can be backed up. 
  • New databases will be automatically detected and backed up if all databases are selected selected for backup. 
  • Databases that are removed from Exchange will be automatically removed from the backup if all databases are selected for backup. 
  • Databases are not automatically added or removed from the backup if individual databases are selected. 

Backup Levels

Microsoft Exchange Server backups support Full, Differential, and Incremental backups.

  • Full Backups contain the Mailbox database (.edb & .stm files), transaction logs, and checkpoint files. 
    • After a successful Full Backup, Exchange will purge all committed transaction logs. 
    • An event is logged by Exchange in the Windows Application Event Logs when transaction logs are purged. 
  • Incremental Backups contain the transaction logs only. 
    • After a successful Incremental backup, Exchange will purge all committed transaction logs. 
    • An event is logged by Exchange in the Windows Application Event Logs when transaction logs are purged. 
  • Differential Backups contain the transaction logs only. 
    • No logs are truncated or purged after a successful Differential backup.

Requirements

The following requirements must be met for Microsoft Exchange Server backups to function.

  • Backups for all versions of Exchange except Exchange 2003 have additional dependencies. 
    • Powershell 2.0 or higher must be installed on the system.
    • .NET Framework 4.0 or higher must be installed 
    • Use the Check Dependencies option in the Tools menu to verify that these are installed.
  • The Volume Shadow Copy service must be started.
  • In Windows Small Business Server 2003, the Exchange VSS Writer is disabled by default. 
    • ZCB will attempt to enable the VSS writer automatically. However, the Microsoft Exchange Information Store service must be restarted manually before backup will work.
    • The writer can be enabled manually by following these instructions in this Microsoft knowledgebase: http://support.microsoft.com/kb/838183
  • The latest Service Packs for Microsoft Exchange must be installed. 
  • Only Mounted Storage Groups are backed up. Unmounted Storage Groups are not backed up.
  • The amandabackup user must be assigned to the proper role in the Exchange Security Groups in Exchange 2007 and higher. ZCB will attempt to assign the proper role automatically.
    • These roles are:
      • For Exchange 2007: View Only Organization Management
      • For Exchange 2010 and up: Exchange View-Only Administrators
    • Please follow these steps if the amandabackup user must be added to the Exchange Security Groups manually.
      • Open "Active Directory Users and Computers"
        • For Exchange 2007: Add the amandabackup user to Microsoft Exchange Security Groups > View Only Organization Management
        • For Exchange 2010 and 2013: Add the amandabackup user to Microsoft Exchange Security Groups > Exchange View-Only Administrators
      • The Zmanda Cloud Backup Services must be restarted after amandabackup is added to the Exchange Security Groups
        • Click on Tools > Restart Services in the ZCB User Interface, or restart ZCBService and ZWCService manually from the Windows Services Panel.
  • Exchange circular logging must be disabled. Circular logging can interfere with backup operations and is not recommended in a normal production environment.
  • Transaction log-based databases such as Microsoft SQL Server, Exchange, or Sharepoint are not intended to be backed up by multiple backup applications. 

 

Backup a Microsoft SharePoint Server

Microsoft SharePoint Server is a web application framework that integrates intranet, content management, and document management. 

Overview

Microsoft SharePoint Server backups have the following properties:

  • Standalone and single-server farms are supported. Multi-server farms are not supported.
  • The following SharePoint components contained in the SQL database and application web site files are backed up, if present on the system. Individual components cannot be selected or deselected. 
    • Configuration and Admin databases
    • Content and configuration data for Web Applications (Eg: C:\Program Files\Microsoft Office Servers\14.0\Data\Office Server\Applications)
    • Any third-party databases that are registered with SharePoint
    • Shared services databases in SharePoint
    • Office Search & Help Search index files
  • Other objects, such as Site collection, Web site, List/Document library, Document library folder, Document library file, List item, and Version, are not backed up by a SharePoint backup set.
    • Files such as the SharePoint installation directory, IIS metabase information, Website application pool directory, and so on must be protected by other backup sets.
      • Files, documents, the folders that contain them, and the SharePoint installation directory itself should be backed up as part of a File System backup.
      • IIS metabase information, port configurations, host header, authentication, and other such configuration data is included as part of a System State backup.
        • Please see this blog post for more information on the relationship between SharePoint and the IIS metabase.

Backup Levels

Microsoft SharePoint Server backups support Full and Differential backups. Incremental (log) backups are not supported. 

Requirements

The following requirements must be met for Microsoft SharePoint Server backups to function.

  • The Volume Shadow Copy Service must be started. 
  • The SQL VSS Writer service must be running at the time of backup and recovery. ZCB will attempt to automatically start the SQL VSS Writer service.
  • The Windows SharePoint Services VSS Writer service will be registered and started automatically by ZCB.
  • The SharePoint VSS writer depends on other VSS writers, such as OSearch and SPSearch. These writers must be enabled and set to automatic start for Sharepoint backups to function.
    • For Sharepoint 2010
      • SPSearch4 VSS Writer 
        • Enable by starting the SharePoint Foundation Search V4 service.
      • OSearch14 VSS Writer
        • Enable by starting the SharePoint Server Search 14 service.
    • For SharePoint 2007
      • OSearch VSS Writer 
        • Enable by starting the Office SharePoint Server Search service.
      • SPSearch VSS Writer 
        • Enable by starting the Windows SharePoint Services Search service.
  • Windows SharePoint Services VSS Writer service must run under the admin app pool account, which is the Network Service account in a basic installation of Windows SharePoint Services.
  • Transaction log-based databases such as Microsoft SQL Server, Exchange, or Sharepoint are not intended to be backed up by multiple backup applications. 

Special Requirement for WSS 3.0

The default installation of Windows SharePoint Services 3 instances will use the Windows Internal Database (MICROSOFT##SSEE), which is run under the "Network Service" system account.

In such a case, the "Network Service" account must have Full Control permissions to the "misc" directory found in the folder where you installed ZCB.

By default, the misc directory is located here:

  • For Windows Server 2003: C:\Program Files\Zmanda\Zmanda Cloud Backup\misc\
  • For Windows Server 2008 and 2012: C:\ProgramData\Zmanda\Zmanda Cloud Backup(x64)\misc\

 

Icon

Microsoft Sharepoint databases can be backed up as if they were Microsoft SQL Server databases. If possible, use the Sharepoint backup type to back up Sharepoint databases.

Do not back up Microsoft Sharepoint databases in more than one backup set. The result is the same as if multiple backup applications were used. See Info: How do databases handle backups from multiple different backup applications? for more information.

Backup a MySQL Server

MySQL Server is a database application. 

Overview

MySQL Server backups have the following properties:

  • Logical backups are performed using the mysqldump utility. 
  • Individual databases within a MySQL server can be selected for backup.
  • If a single database is selected, specific tables within that database can be backed up. 
    • Create multiple MySQL backup sets if specific tables from multiple databases should be backed up. 
  • Backups can be taken of local MySQL servers or remote MySQL servers located on another machine.
  • MySQL Servers, unlike other databases, are not automatically discovered. Thus the MySQL Server backup type will always be available when creating a new backup set.

Backup Levels

MySQL Server backups are always Full backups. Differential and Incremental backups are not supported. 

Special Options

The following special options are available for MySQL Server backups. 

Discovery

MySQL Servers are not automatically discovered. Information about the server must be provided in order for a connection to be established and a backup taken.

  • MySQL User: Enter the username of a MySQL user with sufficient access to take the MySQL Server backup.
  • Password: Enter the password for the MySQL User. 
  • MySQL Server: Enter the IP address of your MySQL Server. A "localhost" value refers to the local machine. 
  • Port: Enter the port on which MySQL is listening.
  • "mysqldump" parameters: Additional parameters can be passed to the mysqldump utility. Enter them here if they are needed.
  • *Path to mysql.exe: Browse to the location where mysql.exe and mysqldump.exe are located. 

The following defaults are assumed:

  • MySQL Server: localhost
  • Port: 3306
  • "mysqldump" Parameters: --lock-all-tables

These defaults work for most MySQL instances. Two common exceptions are listed below.

  • If the MySQL instance uses a socket file for connection instead of a port, please leave the Port field blank.

  • MySQL instances that use the INNODB storage engine may find that replacing the --lock-all-tables parameter with the --single-transaction parameter can result in increased performance and lower CPU usage. 

Once configured, click the Discover button to connect to the MySQL server. A list of databases and tables will appear.

Estimate Size

The Estimate Size button is not available for MySQL backups. 

Requirements

The following requirements must be met for MySQL Server backups to function.

  • The MySQL user specified in the Discovery section must have sufficient privileges to perform backup and restore. The minimum set of privileges are:

For backup: 
LOCK TABLES, SELECT, FILE, RELOAD, SUPER, UPDATE, TRIGGER, SHOW VIEW 
For restore: 
CREATE, DROP, INDEX, SHUTDOWN, INSERT, ALTER, UPDATE, TRIGGER, SUPER, REPLICATION CLIENT, CREATE VIEW

  • MySQL client utilities (mysqldump and mysql) must be installed on the ZCB machine, and the MySQL client version must be compatible with MySQL server.

Backup an Oracle Server

An Oracle Server is a database application sold and supported by Oracle.

Overview

Oracle Server backups have the following properties:

  • The Oracle database, Control File, Server Parameter file, all table spaces, and Archived logs are backed up. 
  • All backup files & archived logs from the Flash Recovery Area are also included in the backup. 
  • The online redo logs will not be included in the backup.
  • Individual databases, log files, control files, etc cannot be selected for backup.

Backup Levels

Oracle Server backups support Full, Differential, and Incremental backups.

Requirements

The following requirements must be met for Oracle Server backups to function.

  • The Oracle VSS Writer service must be installed for the Oracle instances that need to be backed up. 
    • The Oracle VSS Writer is provided by Oracle and is not part of a default Windows server.
    • If the Oracle VSS Writer service is not installed, please refer to the Oracle documentation
  • The Oracle VSS Writer service must be started.
  • The Oracle VSS Writer service must be set to Automatic start.
  • The Volume Shadow Copy Service must be started.
  • All Oracle databases in NOARCHIVELOG mode must be Mounted and in Read-Only state. 
    • The database cannot be Open in Read Write mode. If it is, the backup will fail.
    • A backup may contain multiple databases. If one database is in Read-Only state and the others are in Read-Write state, the backup for all databases will fail.
  • Oracle databases in ARCHIVELOG mode may be Open in Read Write or in Mounted state.

Backup Hyper-V

Hyper-V is Microsoft's virtualization host. It allows users to create, run, and manage virtual machines.

Overview

Hyper-V backups have the following properties:

  • Windows "Core" Servers running Hyper-V are not supported. 
  • Individual Virtual Machines may be selected for backup.
    • The virtual hard disk files (.vhd or .vhdx) and snapshot files (.avhd or .avhdx) will be backed up for any selected virtual machine.
  • The Initial Store (InitialStore.xml) may also be selected for backup.
    • By default, this file is found in %systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\
  • VMs are backed up by one of two methods.
    • The "Child VM Snapshot" method uses the Volume Shadowcopy Service (VSS) inside a child VM. This allows the VM to be backed up without forcing it into a saved state.
      • This is the default backup method. If a Child VM Snapshot cannot be taken, a Saved State backup is taken instead.
      • Child VM Shapshot backups have additional requirements as outlined below.
    • The "Saved State" method briefly places each VM into a saved state so that a snapshot can be taken. Once the snapshot is taken, the VM is returned to its previous state. 
      • This method is used if the Child VM Snapshot method cannot be performed.
  • New VMs will be automatically detected and backed up if all VMs are selected selected for backup. 
  • VMs that are removed from Hyper-V will be automatically removed from the backup if all VMs are selected for backup. 
  • VMs are not automatically added or removed from the backup if individual VMs are selected. 

Backup Levels

Hyper-V backups are always Full backups. 

Special Options

The following special options are available for Hyper-V backups. 

Back up a running VM only if its hot backup can be performed is a special option designed to keep VMs running smoothly during backup.

If enabled, ZCB will skip backup of a running VM if a "Child VM Snapshot" backup cannot be performed.

Requirements

The following requirements must be met for Hyper-V backups to function.

  • The Hyper-V VSS Writer must be started.
  • Backups of Cluster Shared Volumes are not supported.
  • Restore of Hyper-V virtual machines and Host Configuration must be done to the same version of Windows as took the backup. 
    • For example, if the original Hyper-V backup was taken on Windows Server 2008 R2, the restore must be done to Windows Server 2008 R2.

Additional Requirements for Child VM Snapshot backups

The following requirements must be met for Child VM Snapshot backups to function.

  • Backup (volume snapshot) Integration Service must be installed and running in the child VM. 
    • The service name is "Hyper-V Volume Shadow Copy Requestor".
  • The child VM must be in the running state. VMs that are not running always use the Saved State backup method.
  • The Snapshot File Location for the VM must be located on the same volume in the host operating system as the VHD files. 
    • Example: If the VHD files are on C:\, the Snapshot File Location must be on C:\
  • All volumes in the child VM must be basic disks. Dynamic disks are not supported by the Child VM Snapshot method.
  • All disks in the child VM must use a file system that supports snapshots, such as NTFS or ReFS. 

Restore Details and Requirements

Restore Requirements

 The following requirements must be met for all restores, whether to the original machine or to an alternate machine.

  • The amandabackup user must have full access to the folder where the backups are stored. 
    • For cloud backups, this is the chosen Download Folder.
    • For local backups, this is the folder where the backups are stored on disk. 
  • Likewise, the amandabackup user must have full access to the folder(s) to which the backups are being restored.

Additional requirements for all restores to an alternate machine

Backups can be restored from one machine to another. Restores to an alternate machine are most frequently performed for testing purposes or as a part of disaster recovery scenario where the original machine is no longer accessible.

When restoring to another machine, the following steps must be performed before the restore can begin.

  • Install ZCB on the new machine.
  • Import the cloud certificate.
  • Restore Catalogs

Additional requirements for application restores

Restores to an alternate machine of applications or databases, such as Hyper-V or Microsoft SQL Server, frequently have additional requirements that must be met. Please refer to the restore section that corresponds to the application or database for more information about application restores.

Special metadata is stored for every backup run. The metadata is known as the backup catalog and includes information about when a backup was taken, what is inside the backup, what backup level it is, and much more.

When restoring to an alternate machine, the backup catalogs must be restored before the data can be restored. 

The Restore Catalog operation scans for backup runs available on disk or cloud and restores the backup catalog. This rebuilds the backup set(s) to which the backups belong and includes the backup set configuration, the Restore page, and the Report history. 

Backup catalogs can be restored from backups on disk or cloud. 

How to restore the backup catalog

Restore Catalog from Cloud

When restoring the catalog from the cloud, ZCB must search your cloud backups and download the catalog information. The actual backups themselves are not downloaded.

Only catalogs that match the criteria below will be restored. 

Cloud Location

Choose the cloud datacenter where the backups are stored. The default is "All Cloud Locations". Restricting this setting to a specific cloud location can greatly speed up the Restore Catalog process.

Host Name

This refers to the host name of the original machine that took the backups. Do not include the Windows Domain name, if  any.

  • Leave this field blank to restore backup catalogs from the current machine.
  • Enter an asterisk ( * ) to restore backup catalogs for all machines on the account.
  • Enter a specific host name to restore backup catalogs for that machine only.

Backup Set Name

This refers to the name of the Backup Set that needs to be restored.

  • Leave this field blank to restore catalogs for all backup sets.
  • Enter a backup set name to restore catalogs for that backup set only.
  • An asterisk ( * ) can be used as a wildcard if only part of the backup set name is known. 
    • For example, *exchange* would restore any backup set that contains the word "exchange". 

Restore Location

Catalog information must be downloaded to the local machine before it can be imported. Specify a directory here to use as temporary storage of this data. This data is deleted from disk at the end of the Restore Catalog process.

Restore Catalog from Local Directory

You can restore the backup catalog from backups kept on a local disk. 

Only catalogs that match the criteria below will be restored. 

Host Name

This refers to the host name of the original machine that took the backups. Do not include the Windows Domain name, if  any.

  • Leave this field blank to restore backup catalogs from the current machine.
  • Enter an asterisk ( * ) to restore backup catalogs for all machines on the account.
  • Enter a specific host name to restore backup catalogs for that machine only.

Backup Set Name

This refers to the name of the Backup Set that needs to be restored.

  • Leave this field blank to restore catalogs for all backup sets.
  • Enter a backup set name to restore catalogs for that backup set only.
  • An asterisk ( * ) can be used as a wildcard if only part of the backup set name is known. 
    • For example, *exchange* would restore any backup set that contains the word "exchange". 

Backup Data Location

This is the directory in which the local backups are stored. You must specify the exact folder in which the local backups are stored. Sub-folders will not be scanned for backups. If backups are in multiple directories, perform multiple Restore Catalog operations.

 

Every restore is configured with the same basic steps. Users choose a point in time, which data to restore, where the data is restored, and what to do if there's a conflict. 

Backups on disk will always be used for if they are available and accessible. The restore process will automatically download the backups from the cloud if the disk backups are not available. 

Choose your restore point

A list of all available backup runs for the current backup set is shown. Select one for restore. This is the restore point

The restore point can be further refined in the dropdown box below the list. This dropdown box displays all of the previous backup runs in the same cycle as the chosen restore point.

Choose All Latest to restore the latest version of data, as of the selected Restore Point, that is contained within any full, differential, or incremental backup in the backup cycle. This option eliminates the need to perform multiple restores to get the latest data. It is not necessary to restore from the full backup, and then the first incremental, and then the second incremental, and so on. When All Latest is chosen, the latest data from all backup runs is restored. All Latest is the default setting for restores.

If an individual backup is chosen instead of All Latest, only the data from the selected backup run will be restored. Data that is in other backup runs will not be restored. 

Select the data you would like to restore

Data can be selected for restore in three ways. 

Restore All

The Restore All option selects all data at the chosen Restore Point for restore. Restore All is the default selection. 

Restore Select

The Restore Select option allows users to select some data for restore instead of all data. The Restore Select button will only appear if it is supported by the current backup type. 

A file tree will be displayed for File System backups.  A list or summary will be displayed for databases, applications, and for any backup of any type that was taken before version 4.12. 

Place checkmarks next to the items that should be restored. Items that are selected will be restored. Items that are not selected will not be restored. 

The Search option allows users to search for individual files, folders, or databases. The Search button will only appear if it is supported by the current backup type.

Any item chosen in Search will be selected for restore. If it is a folder, the folder and all of its contents will be selected for restore. If it is a database or file, only that database or file will be selected for restore. 

Review your restore settings

Additional restore settings are available by clicking the Edit button.

Restore to

Most backup types allow restore to the Original Location or to an Alternate location. Some application or database restores will have different options that replace the standard Restore To options.

Restore Folder

Data will be restored to this folder, if data is restored to an alternate location.

Download Folder

When there are no backups on disk, or if the backups on disk cannot be accessed, the backup archive(s) will be downloaded from the cloud and stored in this folder. The disk(s) must have enough space to store the backup archive(s) and the data selected for restore.

Name Conflict Policy

This option controls what happens if a file already exists while a restore is in progress. There are four possible choices.

  • Overwrite Existing: The existing file will be overwritten by the file in the backup.
  • Keep Existing: The existing file will be kept. The the file from the backup will not be restored. 
  • Rename Existing: The existing file will be renamed by appending a timestamp to its file name. The restored file will be restored with its name intact.
  • Rename Restored: The restored file will be renamed by appending a timestamp to its file name. The existing file will be restored with its name intact.

Keep Downloaded Archive

Backup archives that are downloaded for restore are automatically deleted from disk when the restore is complete. Enable this option to keep the backup archive on disk. 

This option is primarily used to reduce download time if multiple restore operations must be run from the same backup. 

The backup archive is stored in the Download Folder and must be deleted manually from disk to reclaim space.

Perform archive verification

When enabled, the integrity of the backup archive will be scanned to ensure the archive is not corrupted or otherwise damaged. Archive Verification can take a very long time.

Perform archive verification if data integrity is more important than restore speed.

Run script before/after restore

Scripts can be run before or after any restore. Please see How to use batch scripts with ZCB for more information.

Encryption Options

If Private Key Encryption was used, special options will appear on the Restore page. Please refer to How to use encryption for more details on how to restore encrypted backups.

Restore Now

Click the Restore Now button to begin your restore. You will be prompted to confirm your choices.

The Monitor page will appear once the restore begins.

Restore the Windows File System

Restores of the Windows File System are among the easiest and most flexible offered by ZCB. Files can be selected individually or in groups and restored to local disks, network drives, and alternate machines with few restrictions and no additional requirements.

Functionality

ZCB will restore the chosen files to the chosen location. 

Additional Requirements

There are no additional requirements.

Restore the Windows System State

Windows System State is designed primarily for disaster recovery by restoring the registry, boot files, system files, Active Directory, and more. When used correctly in combination with a File System backup, a machine can be brought back to the exact state it was in at the time of backup.

A walkthrough of a complete system recovery, including File System and System State, can be found in Bare Metal Disaster Recovery with ZCB.

Functionality

The entire contents of the Windows System State backup will be restored. Selective restore of individual System State components is not possible.

By default, System State will restore to the Original Location and Overwrite Existing files.

Additional Requirements

System State restores have additional requirements.

  • The Windows version, including Service Packs, of the restore machine must match the original machine where the System State backup was taken. 
    • For example, if the original machine was Windows Server 2003 with Service Pack 2, the machine accepting the restore must also be Windows Server 2003 with Service Pack 2.
    • Any variation will result in failure to restore.
  • It is strongly recommended to restore System State to identical hardware as the original machine. 
    • Restore to similar hardware is usually possible, but may result in errors or failure to restore. 
    • The less similar the hardware to the original, the less likely it is that the System State restore will succeed.

System State restores to a Domain Controller with the Active Directory role can be very complex. Please refer to How to Restore System State on an Active Directory Domain Controller for full details.

Restore a Microsoft SQL Server

Microsoft SQL Server backups can be restored to the original machine or to an alternate machine.

Additional Requirements

Microsoft SQL Server restores have many additional requirements, including some requirements unique to specific Restore Locations.

Requirements for all database restores

  • Do not run backup and restore operations of a MS-SQL backup simultaneously.
  • SQL 2005 restores of system databases, such as model, master, and msdb, will fail if other applications are actively connected to the MS-SQL server. Please disable any SQL query analyzers, the SQL Management Studio, and other such programs before performing a restore of system databases.
  • The SQL Server VSS Writer service must be running at the time of backup and recovery. Microsoft recommends that the SQL VSS Writer service be automatically started. MSDE writer is not sufficient for backup and recovery.
  • The amandabackup user must have access to the SQL server. To grant access:
    • Click the "Allow Access" button on the Backup page of any Microsoft SQL backup set, or
    • Add the user in SQL server Management Studio. Click on Security > Logins > Add New Login. Add the amandabackup user account, and add it to the sysadmin server role.
  • The log-on user for the SQL Server service must have full permissions to the folder that was chosen for restore.
    • Locate this information in Services.msc. The user will be listed as the log-on user for the SQL Server service that matches the instance(s) that are to be restored.
  • System databases, such as model, master, and msdb, should be restored separately from user databases.
    • Restore system databases first.

Requirements for restore to an alternate machine

The Restore a Copy of Database to Original or New Location and Restore to a New Location and Overwrite Original Database options, discussed below, may both be used to restore to an alternate machine.

  • The SQL Server instance name must be exactly the same on the new machine as it was on the original machine. The restore will fail if the instance names do not match.
  • Restore of system databases such as master, model, and msdb require that the SQL Server version exactly match between the new machine and the original machine. The restore will fail if there is a version mismatch.
    • Example: The model database of a SQL Server 2005 database cannot be restored to anything other than a SQL 2005 instance.
  • Restore of user databases require that the SQL Server version on the new machine be the same as or higher than the original machine. 
    • Example: A user database from a SQL 2008 instance can be restored to another SQL 2008 instance or a SQL 2012 instance. It cannot be restored to a SQL 2005 instance.
  • Restore of user databases require that the new machine be running the same or higher version of Windows operating system as the original.
    • Example: A SQL 2008 instance running on Windows Server 2003 can be restored to a SQL 2008 instance running on Windows Server 2003, 2008, or 2012.
    • Example: A SQL 2008 instance running on Windows Server 2008 cannot be restored to Windows Server 2003. It can be restored to Windows Server 2012.

 

Icon

It is recommended that system databases, such as model, master, and msdb, be restored only to the original machine or an identical server. System databases contain configuration data. The Microsoft SQL Server may not start if system databases are restored to a different server.

Migration of system databases to a non-identical server requires significant database administration knowledge, as shown here.

If system databases are restored, they must be restored separately from user databases. System databases should be restored first.

Special Options

Run DBCC CHECKDB after restore

When selected, this option verifies the integrity of the database(s) after restore. It is off by default. 

Restore To

The Restore To options have been replaced for Microsoft SQL Server restores with the following

  • Original Location
  • Restore a Copy of Database to Original or New Location

  • Restore to a New Location and Overwrite Original Database

Each Restore Location may have additional requirements beyond those found above. Each Restore Location option is designed to fill a specific purpose.

Restore To: Original Location

This option will restore the selected databases to the location where it was originally located at the time of backup. There are no additional requirements.

Icon

If the database to be restored is currently attached to the SQL instance, and the current location of the database files is different from the time of backup, then ZCB will treat the current database location as the "Original" location.

Restore To: Restore a Copy of Database to Original or New Location

This method allows a user to restore the selected database with a new name to either its backup location or to a completely new location. This is similar to making a copy of the database with a new name to a new location.

Information

  • SQL recovery is performed during the restore.
  • The database file names (.ldf & .mdf) remain the same as before.

Additional Requirements

  • System databases, such as master, model, and msdb, cannot be restored using this method.
  • To restore the database to the Original location, the Path field must be blank.
  • When restoring to the Original location using this method, the Original database must be deleted or detached from SQL before the restore begins. 
    • If the Original database still exists, the restore will fail.
  • Once a user makes a selection on the Restore page, he cannot make any changes to the selection list unless he toggles between Restore Methods.

Procedure to restore a copy of a database to its original location

In the following example, we describe a database named 'Sales' that needs to be renamed as 'SalesTeam' and restored to its original location.

  1. Go to the Restore page and select 'Sales' database in the File Path view. 
    1. It is not necessary to select the database in all of the full, differential, and/or incremental backup runs. If one selects the 'Sales' database in any one backup run, ZCB will automatically select 'Sales' database from all other backup runs that are required for restore.
  2. From the 'Restore To' drop down, select 'Restore a Copy of Database to Original or New Location' option.
  3. The 'Edit Database Name & Restore Path' dialog box will appear.
    1. Specify the new name 'SalesTeam' in 'New Name' field.
    2. Keep the 'Path' field blank since we want to restore it to the same old location.
    3. Save the changes.
  4. (Optional) Select the 'Run DBCC CHECKDB' check box if you wish to verify the logical and physical integrity of all the objects in the specified database(s) after the restore completes.
  5. Click on the Restore button.
  6. A confirmation box will appear. Click OK to restore or Cancel to cancel.
  7. After restore completes, the 'SalesTeam' database will appear in the SQL Management Studio

Procedure to restore a copy of a database to a new location

In the following example, we describe how to make a copy of a database named 'Marketing' that originally exists at 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA' with a name 'MarketingTeam' that will be created at 'E:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA'.

  1. Go to the Restore page and select the 'Marketing' database in the File Path view. 
    1. It is not necessary to select the database in all of the full, differential, and/or incremental backup runs. If one selects the 'Marketing' database in any one backup run, ZCB will automatically select 'Marketing' database from all other backup runs that are required for restore.
  2. From the 'Restore To' drop down, select 'Restore a Copy of Database to Original or New Location' option.
  3. The 'Edit Database Name & Restore Path' dialog box will appear.
    1. Specify the new name 'MarketingTeam' in the 'New Name' field.
    2. Click inside the 'Path' field and choose a restore folder
    3. Save the changes.
  4. (Optional) Select the 'Run DBCC CHECKDB' check box if you wish to verify the logical and physical integrity of all the objects in the specified database(s) after the restore completes.
  5. Click on the Restore button.
  6. A confirmation box will appear. Click OK to restore or Cancel to cancel.
  7. After restore completes, both the 'Marketing' & 'MarketingTeam' databases will appear in the SQL Management Studio.

Restore To: Restore to a New Location and Overwrite Original Database

This method allows a user to move the selected database to a completely new location. The original database will be overwritten as part of restore.

Icon

This option may still be chosen if the original database is not present. The Restore to a New Location and Overwrite Original Database option will behave exactly like Restore a Copy of Database to Original or New Location in such a situation.

Information

  • SQL recovery is performed during the restore.
  • The database file names (.ldf & .mdf) remain the same as before.
  • ZCB restores the database to the 'Path' specified by the user in the 'Edit Restore Path' dialog box.
  • Details about the restore procedure are logged by the SQL Server in the Windows Event Viewer.

Additional Requirements

  • System databases like master, model, and msdb cannot be restored using this method.
  • If the selected database exists on the SQL server before the restore procedure, the database files from the original location will be deleted and restored to the new location.
  • Once a user makes a selection on the Restore page, he cannot make any changes to the selection list unless he toggles between Restore Methods.

Procedure to Restore to a New Location and Overwrite Original Database

In the following example, we describe a database 'Finance' that originally existed at 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA'.

This database needs to be moved to a new location at 'E:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA'.

  1. Go to the Restore page and select the 'Finance' database in the File Path view.
    1. It is not necessary to select the database in all of the full, differential, and/or incremental backup runs. If one selects the 'Finance' database in any one backup run, ZCB will automatically select 'Finance' database from all other backup runs that are required for the restore.
  2. From the 'Restore To' drop down, select the 'Restore to a New Location and Overwrite Original Database' option.
  3. The 'Edit Restore Path' dialog box will appear.
    1. Click inside the 'Path' field and choose a restore folder.
    2. Save the changes.
  4. (Optional) Select the 'Run DBCC CHECKDB' check box if you wish to verify the logical and physical integrity of all the objects in the specified database(s) after the restore completes.
  5. Click on the Restore button.
  6. A confirmation box will appear. Click OK to restore or Cancel to cancel.

Database ownership after restore

This section does not apply to restores to the Original Location, as database ownership will not change.

The amandabackup user is used to initiate the restore operations for Microsoft SQL Server. It will thus become the new owner of the restored databases during restores to a different computer or different instance.

This is necessary for several reasons:

  • It cannot be assumed that the user who previously owned the database exists during the restore process.
  • The user performing the restore must have the necessary permissions to apply transaction log backups to the newly restored database.
  • Likewise, the user performing the restore must have full and total access to the database, including ownership changes.

Because we require that the amandabackup user be added as a Sysadmin, we know that the amandabackup user satisfies these requirements.

After restore, any system administrator can change the database ownership to any user. Please see this Microsoft Article for more information on how to change database ownership: http://technet.microsoft.com/en-us/library/ms190909%28v=sql.105%29.aspx

Restore a Microsoft Exchange Server

Exchange databases can be restored to the same server or to an alternate server. Three types of recovery operations are allowed by Microsoft Exchange:

  • Roll-forward
  • Point in time
  • Full restore

The state of the Microsoft Exchange server when the restore is started determines what type of recovery will be available. Please see this Microsoft documentation for details on Exchange recoveries.

All Exchange versions support restores to the Original location. In addition, you can restore Exchange 2007 backups to a Recovery Storage Group and Exchange 2010 or 2013 backups to a Recovery Database.

If you wish to restore an individual mailbox or message, please refer to Recover a deleted mailbox or a mailbox item below

Additional Requirements

Microsoft Exchange Server restores have many additional requirements. Some requirements will change depending on the version of Exchange in use.

Requirements for all Exchange restores

  • The following prerequisites must be installed for all versions of Exchange, except for Exchange 2003
    • .NET 4.0 or higher
    • Powershell 2.0 or higher

Requirements for Exchange restores to an alternate machine

  • The Exchange version and service packs on the alternate machine must be the same as the original machine. 
  • Exchange must be installed and must have the same Organization and Administrative Group name as on the original server.
  • The storage groups and databases must already exist on the alternate server, and have the same names as the original storage groups or databases.
  • Because you are restoring to an alternate "recovery server" that has a different set of log files, the signatures on the log files must match. 
    • To ensure this, either rename the E0x.log file located in the Transaction log directory, or enable the Do not mount the database option while creating a Mailbox or Public folder store.
  • The Volume Shadow Copy Service must be enabled. 
    • In Windows 2003 Small Business Server edition, the Exchange Writer is disabled by default. Please follow the instructions in this Microsoft knowledgebase article to enable the Exchange Writer.
  • The Exchange VSS Writer must be stable.
    • Run the command vssadmin list writers in the Windows command prompt to check that the state of the Exchange Writer.
    • If it is not in a Stable state, restart the Microsoft Exchange Information Store Service.

Additional Requirements for selective restores in Exchange 2003 and 2007

It is possible to selectively restore individual Public Folder Databases and Mailbox Databases in Exchange 2003 and 2007, but there are further requirements that must be met.

Individual databases can be restored without these additional requirements on Exchange 2010 and higher.

  • Selective restore of Public Folder Databases and Mailbox Databases can only be performed to the Original location for Exchange 2003.
  • Selective restore to the Original Location or a Recovery Storage Group is possible for Exchange 2007.
  • The Database Files and the associated Logs must be selected on the restore page. They will be listed separately. You must select both.
  • The Delete existing transaction logs before running the restore method (discussed below) is not allowed for selective restores to the original location in Exchange 2003 or 2007.
    • No Loss Restore - Do not delete existing transaction logs restore will be performed for all selective restores, even if Delete existing transaction logs is selected.

Special Options

Restore To

Microsoft Exchange Server has special options that take the place of the common Restore Locations found for most backup types.

  • Original Location
  • Alternate Location

  • Recovery Storage Group or Recovery Database

Each Restore Location may have additional requirements beyond those found above. Each Restore Location option is designed to fill a specific purpose.

Restore To: Original Location

If chosen, this will restore the selected database(s) to their original location. Restore to the Original location is most frequently used to fix a corrupted Exchange database or resolve issues with missing or damaged transaction logs.

Additional Requirements

  • Any database that is to be restored must be in the Dismounted state.
    • For Exchange 2003 and 2007, all Mailbox Databases and Public Folder Databases within the target Storage Group must meet this requirement, even if a single database is being restored.
  • The This database can be overwritten by restore option enabled through the Exchange System Manager (Exchange 2003) or Exchange Management Console (Exchange 2007 and higher).

Restore Method

You will be presented with two options when you restore to the Original Location.

No Loss Restore - Do not delete existing transaction logs

  • The existing transaction logs will not be deleted during the restore. Once the restore is complete, Exchange will perform a roll-forward recovery if all sequential transaction logs are found.
  • Because Public Folder Databases participate in replication by design, the No Loss Restore - Do not delete existing transaction logs method is not supported for any restores that include Public Folder Databases. The Delete existing transaction logs before running the restore method must be chosen.

Delete existing transaction logs before running the restore

  • This is a "Point in time" recovery method.
  • All transaction logs that are currently present in the Log directory of the Storage Group(s), to which restored Mailbox Database(s), Public Folder Database(s), and/or Storage Group(s) belong, will be deleted at the beginning of the restore process.

Procedure to restore Exchange server data to the original location

  • Navigate to the Restore page and choose a Restore Point.
  • By default, all databases will be selected. You may individually select a Mailbox Store Database or Public Folder Database & its associated Logs from Restore Select
  • Click the Edit button next to Review your restore settings.
  • Select  "Restore to Original Location" from the Restore To dropdown menu.
  • Select" Overwrite Original" from the Name Conflict Policy dropdown menu. 
  • Choose the Restore Method you wish to use.
  • Review your selections, then click Restore to start the restore process.

Restore To: Alternate Location

When chosen, this option will restore the Exchange databases to a different Exchange server. Restore to alternate Exchange servers is usually used when the original server is no longer available.

Additional Requirements

  • All Exchange-specific requirements must be met.
  • Any database that is to be restored must be in the Dismounted state.
    • For Exchange 2003 and 2007, all Mailbox Databases and Public Folder Databases within the target Storage Group must meet this requirement, even if a single database is being restored.
  • The This database can be overwritten by restore option enabled through the Exchange System Manager (Exchange 2003) or Exchange Management Console (Exchange 2007 and higher).

Procedure to restore Exchange server data to an alternate Exchange server

  • Navigate to the Restore page and choose a Restore Point.
  • By default, all databases will be selected. You may individually select a Mailbox Store Database or Public Folder Database & its associated Logs from Restore Select
  • Click the Edit button next to Review your restore settings.
  • Select  "Restore to Alternate Exchange Server" from the Restore To dropdown menu.
  • Select" Overwrite Original" from the Name Conflict Policy dropdown menu. 
  • Review your selections, then click Restore to start the restore process.

Restore To: Recovery Storage Group or Recovery Database

Microsoft Exchange Server allows restore of Exchange Mailbox Stores to a Recovery Storage Group in Exchange 2007 and to a Recovery Database in Exchange 2010 & 2013.

Recovery Storage Groups/Databases allow users to restore the Mailbox Store to a production Exchange Server without dismounting the existing Mailbox stores.

Only Exchange 2007 and up will support Recovery Storage Groups/Databases.

Icon

It is not possible to restore a Public Folder Database to a Recovery Storage Group/Database. This functionality is not supported by Exchange. Any attempt to do so will result in a failed restore with the error "Restore could not proceed as VSS initialization failed."

Further details about the failure can be found in the Windows Application Event Logs.

Additional Requirements

All Exchange-specific requirements must be met. There are additional requirements for restores to a Recovery Storage Group/Database.

  • The Recovery Storage Group or Recovery Database must be created before the restore begins.
    • Use the Exchange Management Tool or the Exchange Management Shell to create the Recovery Storage Group/Database
  • All of the recovery databases in the Recovery Storage Group must be dismounted.
  • All of the recovery databases must have the "This database can be overwritten by restore" option enabled.
  • The Recovery Storage Group or Recovery Database folder must be empty.

If you are restoring to a Recovery Storage Group/Database on an alternate machine

  • The name of the alternate machine must exactly match the name of the original machine.
  • The recovery server must have the same Organization name, same Storage Group name, and same Mailbox Database name as the original server.

Procedure to restore Exchange server data to an alternate Exchange server

  • Navigate to the Restore page and choose a Restore Point.
  • By default, all databases will be selected. You may individually select a Mailbox Store Database or Storage Group & its associated Logs from Restore Select.
  • Click the Edit button next to Review your restore settings.
  • Select  "Restore to Recovery Database" from the Restore To dropdown menu.
    • For Exchange 2007, enter the name of the Recovery Storage Group
    • For Exchange 2010 & 2013, enter the name of the Recovery Database
  • Review your selections, then click Restore to start the restore process.

Recover a deleted mailbox or a mailbox item

ZCB does not directly support restore of individual mailboxes or messages. However, it is possible to use ZCB in conjunction with native Exchange tools to restore individual mailboxes or items.

Please refer to the following Knoweldgebase articles

Restore a Microsoft Sharepoint Server

ZCB can be used for content recovery, web application recovery, and disaster recovery of Microsoft Sharepoint. Restores can be performed to the original system or an alternate system.

Additional Requirements

There are additional requirements for all Sharepoint restores.

Requirements for all Sharepoint restore to the original machine

  • All Sharepoint databases must be in the Normal state prior to restore. 
    • State can be verified from the SQL Management Studio. The Properties menu for each database will display its current state. 
  • The following services must be started
    • Windows Sharepoint VSS Writer
    • Windows Sharepoint Services Tracing
    • The applicable OSearch and SPSearch VSS Writer services must be enabled. The name of the controlling service depends on the version of Sharepoint installed. Examples below:
      • For Sharepoint 2010
        • The SPSearch VSS Writer is controlled by the SharePoint Foundation Search V4 service
        • The OSearch VSS Writer is controlled by the SharePoint Server Search 14 service
      • For Sharepoint 2007
        • The SPSearch VSS Writer is controlled by the Windows SharePoint Services Search service
        • The OSearch VSS Writer is controlled by the Office SharePoint Server Search service

Requirements for Sharepoint restore to an alternate machine

  • The new machine must run the same version of Sharepoint, with the same Service Packs, and the same embedded SQL Server as the original machine.
  • The hostname of the new machine must be exactly the same as the original machine.
  • The instance name must exactly match the instance name from the original server.
  • Sharepoint must be installed to the same location on disk as when the backup was run.
  • All databases and log file locations must also match the original configuration.

Restore To

Sharepoint databases can be restored to their original location or to an alternate location.

Please note that ZCB does not support Roll-forward restore for Sharepoint. If a restore is targeted to the original location, any changes made to the database after the backup was taken will be lost.

Restore To: Original location

The following occurs during a restore to the Original location. 

  • The following SharePoint services are stopped before the restore begins:
    • Windows SharePoint Services Administration 
    • Windows SharePoint Services Search
    • Windows SharePoint Services Timer
    • Office SharePoint Server Search
    • IS Admin Service
  • The selected SharePoint database(s) and log files are restored to their original location. 
    • Index search files will be restored, if all databases and logs within the backup are selected for restore,
    • Individual content databases can be selected for restore, but index search files will not be restored.
  • ZCB calls the SharePoint VSS writer which automatically detaches and then reattaches each database to the farm.
  • The services which were stopped before the restore operation are restarted.

Restore To: Alternate location

No services are stopped or started before a restore to an alternate location. Nor are the databases automatically attached.

Instead, the databases and log files are simply restored to disk in the given location. Please import them manually into Sharepoint.

Restore Hyper-V

ZCB supports restore of Hyper-V hosts and hosted virtual machines to the original location or to an alternate location. Individual virtual machines may be restored.

Restored virtual machines will be automatically imported into Hyper-V in most configurations. Also, restored virtual hard disks may be attached to any existing virtual machine manually. 

Additional Requirements

Restore to the Original Location cannot overwrite an active, running VM. If such a restore is attempted, the restore will be interrupted with the following message:

  • The guest VM that you are trying to restore appears to be in a running state. It will be turned off during the restore.
    Are you sure you want to continue?

Choose "OK" to turn off the VM and continue the restore. Select "Cancel" to abort the restore process.

The above message will not appear if the name of the Virtual Machine has changed since the time the backup was taken. ZCB will proceed directly with the restore and overwrite the existing VM.

Restore a MySQL Server

MySQL databases can be restored to the original location or as a .sql file on disk that can be imported manually for restore to any compatible MySQL Server.

Additional Requirements

MySQL restores have additional requirements.

  • The MySQL user specified on the Backup page must have the following privileges in order to restore the MySQL databases:
    • CREATE, DROP, INDEX, SHUTDOWN, INSERT, ALTER, UPDATE, TRIGGER, SUPER, REPLICATION CLIENT, CREATE VIEW
  • The MySQL client utilities (mysqldump and mysql) must be installed and the MySQL client version must be compatible with MySQL server.
  • The MySQL server must be running at the time of restoration.

Restore Views

There are two ways to view databases for restore: SQL Files and Databases, each with its own benefits.

SQL Files

The SQL Files view is the default option for MySQL restores. This option is used when Restore All is selected, and is the default view shown when Restore Select is chosen.

A SQL File Restore will always include all databases that were backed up. Selective restore is not possible with the SQL Files restore view.

A SQL Files restore will create a .sql file on disk. This .sql file must be imported into any MySQL installation manually using MySQL tools or the command line. 

Databases

The Databases view allows for individual databases to be selected for restore. A Databases restore will always restore the databases to their Original location and will import the databases into MySQL automatically.

The Databases view is only visible when Restore Select is chosen.

  • Navigate to the Restore page and select a restore point.
  • Click on Restore Select
  • Change to the Databases view in the upper right.
  • Select the databases to be restored.
  • Click on Restore.

Restore an Oracle Server

Oracle databases can be restored to the original location or to an alternate location. Oracle restores can be highly technical and require access to the SQL*Plus utility that is included with the Oracle database.

Additional Requirements

Oracle restores have additional requirements:

  • SQL*Plus must be installed and accessible to the user performing the restore.
  • The Oracle VSS Writer service must be started and functional.

Recovery of ARCHIVELOG databases to the Original Location

To restore all ARCHIVELOG databases to the original location:

  • Ensure that the instance is not started.
  • Navigate to the Restore page. Select the a Restore Point.
  • Select the database files to be restored. This includes the datafiles, server parameter file, etc.
    • If the redo logs are missing, you must also select the appropriate archived redo log files.
  • Select Restore to Original Location from the dropdown menu.
    • ZCB will restore the data to the same location from where the backup was made.
  • Choose Overwrite Original as your Name Conflict Policy.
  • Click Restore to start the restore process.
  • Once the database is successfully restored, open SQL*Plus and run the below commands.

cmd> sqlplus /nolog
sql> connect sys as sysdba
sql> shutdown immediate
sql> startup mount
sql> recover database using backup controlfile until cancel;

Note: In cancel-based recovery, recovery proceeds by prompting you with the suggested filenames of archived redo log files. Recovery stops when you specify CANCEL instead of a filename, or when all redo logs have been applied to the datafiles.

  • Continue applying redo log files until the last log has been applied to the restored datafiles, then cancel recovery by executing the following command:

sql> CANCEL;

  • To finish, enter the following SQL command string

sql> alter database open resetlogs;

  • To verify that the database is in the open state (read/write mode), use the following command:

sql> select name, open_mode from v$database;

To restore a single Oracle datafile to the Original location:

Ensure that the database is either mounted or open. If the database is open, run SQL*Plus from the Command Prompt and connect to the database.

cmd> sqlplus sys as sysdba

To recover the datafile, the tablespace needs to be taken offline. Lets consider an example where the tablespace ZTEST01 needs to be restored.

sql> ALTER TABLESPACE ZTEST01 OFFLINE IMMEDIATE;

  • Navigate to the Restore page in ZCB. Select the backup run you want to restore from.
  • Select the datafile to be restored
    • Our example will use a datafile named ZTEST01.dbf.
    • If the redo logs are missing, also select the appropriate archived redo log files.
  • Select Restore to Original Location from the dropdown menu.

    • ZCB will restore the data to the same location from where the backup was made.
  • Choose Overwrite Original as your Name Conflict Policy.
  • Click on Restore.
  • Once the database is successfully restored, open the SQL*Plus and run the below commands.

cmd> sqlplus /nolog
sql> connect sys as sysdba

  • If the restored data file is older than the redo log files, then a media recovery needs to be initiated using the below command:

sql> RECOVER TABLESPACE ZTEST01;
You will see the below message
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

  • Input the appropriate log file location. Type 'AUTO' if you want Oracle to automatically find the appropriate logs and apply it.

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
Log applied.
Media recovery complete.

  • Once you have recovered all the tablespaces that you have lost, bring the offline datafile or tablespace back online using command:

sql> ALTER TABLESPACE ZTEST01 ONLINE;

To restore all ARCHIVELOG Control files:

Note: When Oracle database control files are backed up by Volume Shadow Copy Service, the backed-up files are referred to as Snapshot Control files. For example, a control file by the name of 'CONTROL01.CTL' is backed up under the name SNCF[DATABASE_SID].ORA. Let's consider an example where the database SID is ORCL. In this case the snapshot control file will have the name SNCFORCL.ORA.

  • Ensure that the database is in NOMOUNT state or can be started in NOMOUNT state by the Oracle VSS writer. You don't have to shut down the database manually.
  • Navigate to the Restore page on ZCB user interface. Select the backup run you want to restore from.
  • Select the snapshot Control File. In the above case, select 'SNCFORCL.ORA' since the SID of the database is ORCL.
  • Select Restore to Original Location from the dropdown menu.
    • ZCB will restore the data to the same location from where the backup was made.
  • Choose Overwrite Original as your Name Conflict Policy.
  • Click on Restore.

Note: ZCB automatically stops the Oracle instance while restoring and then starts it again when the restore operation is finished.

  • Make three copies of the SNCFDATABASE_SID.ORA called CONTROL01.CTL, CONTROL02.CTL, and CONTROL03.CTL.
  • Copy these three files to the control files install location. The default location is 'ORAHOME\oradata\(DATABASE_SID)\'. For the above example, copy the files to the 'C:\app\Administrator\oradata\ORCL\' directory.
  • Run sqlplus on Command Prompt Window

cmd> sqlplus sys as sysdba

  • Shut down the database and startup

sql> SHUTDOWN IMMEDIATE
sql> STARTUP MOUNT

  • Run the below command to get the database in consistent state.

sql> RECOVER database using backup controlfile until cancel;

  • Continue applying redo log files until the last log has been applied to the restored datafiles, then cancel recovery by executing the following command:

sql> CANCEL;

  • Open the database with the RESETLOGS option.

SQL> ALTER DATABASE OPEN RESETLOGS;

  • The Oracle database is now recovered. To verify that the database is in the open state (read/write mode), use the following command:

SQL> select name, open_mode from v$database;

Recovery of the server parameter file

  • Navigate to the Restore page in the ZCB. Select the backup run you want to restore.
  • Select the Server parameter file (spfile) to be restored.
    • Usually, it is named SPFILE[ORACLE_SID]".ORA .
      • For example, if the SID of the database is "ORCL", then the name of spfile will be "SPFILEORCL.ORA".
  • Select Restore to Original Location from the dropdown menu.
    • ZCB will restore the data to the same location from where the backup was made.
  • Choose Overwrite Original as your Name Conflict Policy.
  • Click on Restore.
  • Once the restore operation is done, run SQL*Plus

cmd> sqlplus sys as sysdba

  • Shutdown the database and startup again.

sql> SHUTDOWN immediate
sql> STARTUP

  • Check the database whether it's up and running

sql> SELECT name, open_mode from v$database;

Recovery of NOARCHIVELOG databases to the Original Location

To restore all NOARCHIVELOG datafiles

  • Navigate to the Restore page in the ZCB user interface. Select the backup run you want to restore from.
  • Select all the datafiles & control files. ZCB backs up one of the 3 control files i.e. CONTROL01.CTL.
  • Select Restore to Original Location from the dropdown menu.
    • ZCB will restore the data to the same location from where the backup was made.
  • Choose Overwrite Original as your Name Conflict Policy.
  • Click on Restore.
  • Make two extra copies of the CONTROL01.CTL file called CONTROL02.CTL and CONTROL03.CTL. For your information, CONTROL01.CTL file is located in the ORAHOME\ORADATA\DATABASE_SID directory.
  • To run the recovery, run sqlplus on command prompt:

cmd> sqlplus /nolog
sql> connect sys as sysdba
sql> shutdown immediate
sql> startup nomount
sql> ALTER DATABASE mount;
sql> RECOVER DATABASE;
sql> ALTER DATABASE open;

Recovery to an Alternate Location

When Restore to Alternate Location is chosen, ZCB will simply restore the selected Oracle files to disk. They must be imported manually into the Oracle database.

 

Disaster Recovery

Disaster Recovery refers to restoring the system and data in the event of a partial or complete failure of a computer.

Planning for Disaster Recovery

Disaster recovery requires that all relevant data be backed up. This usually requires several different backup sets of different backup types.

For easiest disaster recovery, simply back up everything, like so:

  • Create a File System backup set that contains all drives on the system. 
  • Create a System State backup set to get the system's registry, boot files, Active Directory, and more. 
  • Create one backup set for each database or application, such as Microsoft Exchange or Hyper-V, that is present on the system.
  • Ensure that a backup is taken of all data stored on the network, such as file shares or NAS devices.

If everything cannot be backed up for some reason, the following is the minimum required for disaster recovery:

  • A File System backup set that includes:
    • The entire system drive.
      • On most Windows system, C: is the system drive.
      • Temporary Files can be excluded.
      • Windows/system files can be excluded.
    • Database or application installation directories, if not on the system drive.
      • Any database or application that needs to be restored must have all of its files on disk backed up in addition to the databases themselves.
      • Database files, such as .mdf files for Microsoft SQL Server, that are backed up seprately as part of a Database or Application backup can be excluded.
    • User data that is not on the system drive.
  • A System State backup set.
  • A backup set for each type of Database or Application, such as Microsoft Exchange or Hyper-V.

Performing Disaster Recovery

Backups can be restored to a new machine. However, please ensure that all requirements for restore of each backup type are met before you begin.

It is recommended to use identical hardware to ensure that the System State backups restore correctly. The more dissimilar the hardware, the more likely that the System State restore will encounter problems.

The following is a high-level overview of the disaster recovery process. The details may vary based on the type of data to be restored.

  1. Install the same version of Windows as on the original system. This includes Service Packs.
    1. Ensure that the new system has the exact same hard drive partitions, Windows installation directory, and Host Name as the original server
    2. Do not place the system in a Windows Domain or Workgroup
  2. Log into the machine as an Administrator.
  3. Install ZCB and import your account's cloud certificate.
  4. Perform a Restore Catalog operation and restart ZCB when it is complete.
  5. Choose the File System backup set that contains your system drive.
  6. Go to the Restore page.
  7. Choose your restore point.
  8. Choose to restore to the Original Location and Overwrite Existing files.
  9. Begin the restore.
    1. Restore of some system files may fail because the system is in use. This is normal and should be expected. 
  10. Restore the File System backup set that houses your Application Installation Directories, if they exist and were separate from the System Drive backup set.
    1. Again, choose to restore to the Original Location with Overwrite Existing.
  11. Restore the System State backup to the Original Location with Overwrite Existing.
  12. Reboot the system after the System State restore is complete.
    1. Do not reboot until the System State restore is complete. The Windows installation may become corrupted if the system is rebooted after the File System restore is complete and before the System State restore is complete.
      1. If a reboot is performed at the wrong time, it is likely that the system will need to be formatted and the Disaster Recovery process restarted from the beginning.
  13. Once the server reboots, check to ensure that all Database servers and Applications are installed and in the running state, if they exist. Repair if necessary.
  14. Restore the Database or Application backups, if they exist. 

An example disaster recovery of files and system state can be found at Complete Disaster Recovery with ZCB.

Monitor Backups

The Monitor page displays the current status of backups, restores, uploads and downloads. The most recent operation is displayed. 

Visit the Report page for a full history and fine control over individual backup runs.

All operations can be canceled. Some can be paused and resumed, as shown on the following chart.

Operation

Cancel

Pause

Resume

Backup to Cloud

Yes

Yes

Yes

Backup to Disk

Yes

No

No

Upload to Cloud

Yes

Yes

Yes

Download

Yes

No

No

Restore

Yes

No

No

Canceling an upload will also cancel all queued uploads in the same backup set. 

When the Resume button on the Monitor page is clicked, ZCB will resume all uploads for the current backup set that are currently paused or failed. To resume one specific job, locate it on the Report page.

Upload speeds are shown on the Monitor page. The current speed and the average speed are displayed in the details column.

Reports and Backup History

The Report page displays contains the history of all operations. Backup runs and other operations can be managed from this page individually or in groups. 

Report History

A history of all operations will be displayed on the Report Page. Each row references a specific backup run or other operation and contains many details.

Each backup run will have an icon indicating its current status.

  • A green checkmark icon indicates the operation was successful.
  • A red X icon indicates the operation failed. Please see the Details column for more information.
  • A yellow warning icon indicates a warning. The operation was successful with a minor issue or failed in an expected way. Please reference the Details column for more information.
  • A grey trash can indicates that the backup was purged or deleted. The details column will contain the date the backup was deleted. 
  • Two grey vertical bars indicates that an upload is paused. It can be resumed by selecting the Resume option from the right-click menu.
  • A blue circle made of dots indicates that an operation is in progress.
  • A clock indicates that an upload is queued. Queued uploads will be uploaded in the order they were created. 

Blue info icons may appear in the Details column for any operation and can be clicked to obtain further information.

Manage Report History

You can click on any column heading to sort by that field. Columns can be dragged to display in any order.

By default, the report history is kept forever. All operations and backup runs will be displayed. Visit the Preferences > Advanced menu to change this value. 

Report Templates

ZCB allows you to customize your historical view. Click on the Define Template button, specify the template name, and choose the columns which you want to include. Click on Save Template to add this new template.

To load a specific template, you can select it from the dropdown next to the Define Template button.

Click on the Export Report button yo export your loaded template view to a Comma Separated Values (CSV) file. This file can be printed or imported into other applications to create spreadsheets and charts.

Toolbar and Right-Click Menu

Right-click any backup run or operation to get a list of tasks that can be performed. These tasks are also available in the toolbar at the top of the Report page.

Delete

This option allows you to delete data associated with backup runs and other operations. 

  • Delete Backup Data from Disk: The data will be deleted from the disk.
  • Delete Backup Data from Cloud: The data will be deleted from the cloud. Deletion of data from the cloud can take a long time. 
  • Delete Backup Run: The data will be deleted from both disk and cloud. Additionally, the backup run itself will be deleted from the Report page.

Upload

This option allows you to begin an upload of a backup on disk or resume a paused upload. 

Occasionally, a Failed upload cannot be restarted. The Upload options will be disabled if upload is not possible. If the Upload options are disabled, please begin a new backup. 

Change Retention Period

Select a backup and choose this option to change its retention period. This option only works for backups using time-based retention. 

Verify Backup Data

This option checks that all backup files are present and available. It does not check the integrity of the data. 

Select a Backup to Disk to verify a backup on disk. Select a Backup to Cloud or Upload from Disk to verify the data on the cloud.

The larger the backup, the longer verification will take. Verification of backups on the cloud can take a long time.

Verification cannot be performed for In-progress, paused, purged, or queued backups or uploads. It is also not present for Backup to Cloud operations that are Failed or Canceled. 

Information Column

The column on the right side of the Report page includes additional information about the currently-selected backup run. 

The Show Contents of Backup Run button, when clicked, will load a list of everything inside the selected backup run. The larger the backup, the longer it takes for the list to appear.

The list is paginated. Use the selector below the list to change to a different page.

Click the Prepare to Restore button to be taken to the Restore page. Only the chosen backup run will be selected for restore.

Administration

The Cloud, Tools, and Preferences menus are found at the top of the screen. Each contains additional options to help administrate backups. 

Cloud Menu

The Cloud Menu contains options related directly to the cloud storage associated with your account.

Import Cloud Certificate

Use this option to import a cloud certificate at any time. 

Check Cloud Connection

This option performs a quick test to see if the system is able to connect to the cloud. 

Manage Amazon S3 Storage

This heading applies to ZCB with Amazon S3 Storage only. Other versions of the product will not display these options. 

Purchase Cloud Subscription or Manage Cloud Subscription: Opens a browser window that connects you to Zmanda Network and the Amazon S3 portal. Your Zmanda Network account information and Amazon account information are required to access the information.

Cloud Billing: This takes the user to the web site that provides detailed billing information for the current month as well as the prior month. Amazon account information is required.

Tools Menu

The Tools Menu contains tools related to ZCB operation that do not fit anywhere else.

Restart Background Service

This tool restarts the two background services: ZCB Service and ZWC Service. These services must be restarted after certain advanced configuration changes, particularly those done in the Preferences > Advanced menu. 

Restore Catalog

ZCB stores special "metadata" for every backup run. This metadata is known as the Backup Catalog, which is used so that ZCB knows when a backup was taken, what's inside each backup, in which order incremental backups should be restored, and more. A restore cannot proceed without the catalog information.

This tool is the first step when restoring to a new machine. Please see Restore Catalog for more information. 

Move Local Backups

This tool moves backups on disk to a different location on disk. Please see How to move local backups to a new folder for more information.

Check Dependencies

Exchange backups have additional dependencies above and beyond those required for standard ZCB operation. This tool checks if those dependencies are installed. It also displays the version of the Java Runtime Environment installed on the system.

Preferences Menu

The Preferences Menu allows users to set various global settings. Any value that is set in the Preferences menu will apply for all backup sets. If a value is set globally in the Preferences menu and set in a backup set, the backup set value will be used. 

Bandwidth Management

This option allows users to limit the amount of bandwidth used by ZCB for all backup sets..

The value chosen here is not divided among backup sets. It will apply to each backup set separately. For example, each backup set will have a limit of 500kbps if a value of 500kbps is chosen in Bandwidth Management.

Email

Notifications can be sent on Success or Failure of any given operation as described in the Configure Backup Sets section of the User Guide.

A SMTP server must be specified in order to receive notifications. The following information must be provided by the user:

  • From: Please specify the email address that will be in the From field of each email notification. Be sure to whitelist this address so the notifications are not flagged as spam or junk.
  • To: Input the email addresses to which the notifications will be sent. Separate multiple email addresses with a "," (comma) character.
  • Outgoing SMTP Server: This is the IP address or hostname of the outgoing SMTP server.
  • Port: This is the SMTP server port.
  • Security: Choose the type of security used for the email notifications. 
    • The proper value must be chosen, and the SMTP server must support the chosen value.
    • For example, if you are using Exchange server, please enable Require TLS encryption option on the Exchange server. To configure Transport Layer Security Encryption for clients, please see this Microsoft KB article.
  • Username: This is the email address/username which is to be used to log into the mail server.
  • Password: This is the password for the above email address/username.
  • Authenticate: Enable if the SMTP server requires authentication. Disable if it does not.

Use the Send Test Mail button to send a test mail. Review the SMTP server information provided or the settings on the SMTP server itself if the test fails. 

The Notification Preferences option allows users to choose if notifications will be sent on Failure, on Success, or both. 

Advanced

The Advanced menu contains a variety of optional, advanced features.

Data Transfer and Networking

Proxy Servers: A proxy server can be used for data transfer to and from the cloud. 

  • Proxy Host: Enter the proxy server's host address.
  • Proxy Port: Enter the port used for access to the proxy server.

Please see How to configure ZCB to work with authenticated proxy servers if your proxy server requires authentication.

Ports: Ports 10080 and 10081 are used internally for transfer of data during backup or restore. These ports can be changed if necessary. These ports have nothing to do with firewall configuration, and do not need to be opened in a firewall.

  • Backup Port: Enter the port used to transfer data during a backup.
  • Restore Port: Enter the port used to transfer data during a restore.

The background services must be restarted if the ports are changed. Click Tools > Restart Background Service to restart the services. 

Threads: Multiple connections are opened with the cloud servers during upload or download of data. Each such connection is called a "thread". Increasing the number of threads can increase data transfer speed on some networks. However, using more threads than necessary can cause slower data transfer.

The default number of threads is 3 and the maximum number is 10

  • Max. Download Threads: Use this setting to change the number of threads used by ZCB when downloading data from the cloud.
  • Max. Upload Threads: Use this setting to change the number of threads used by ZCB when uploading data to the cloud.

Any change to the number of threads will not affect any data transfers currently in progress.

Retention Policy Enforcement

Retention policies are checked once per day. Those that have expired are purged.

  • Purge old backup data every day at: Retention policies will be checked at the time specified here.

The Report page shows old backups, even those that have been purged.

  • Keep expired backup run reports for: Set the length of time ZCB will display reports of old backup runs. Only backup runs that have expired or failed will be removed. Active backups will not be removed. 

General

Several folders are used by the program. You can change the locations of these folders.

  • Temporary Directory: Temporary files created during backups are stored in this directory. This folder must be on a local drive. 
    • The background services must be restarted to change the Temporary Directory. Click Tools > Restart Background Service after changes are saved. 
  • Backup Directory: Backups are saved to this directory in a folder with the name of the backup set by default.
    • Changes made to the Backup Directory setting will only apply to new backup sets. It will not change the location for existing backup sets.

    • Please refer to How to move local backups to a new folder if local backups must be moved to a new location.
  • Download Directory: During a restore, backup archives are saved to this directory by default.
  • Restore Directory: When restoring to an alternate location, files are saved to this directory by default.

RRS Storage

This option applies to Zmanda Cloud Backup with Amazon S3 only. It will not appear in other versions of the product.

By default, ZCB uses Amazon S3 RRS storage. Users can opt-in to more costly standard S3 storage. Please see How to switch to Standard Amazon S3 storage from Amazon S3 Reduced Redundancy Storage (RRS) for more information.

amandabackup user

A user named amandabackup is created during installation. ZCB stores the password chosen for amandabackup.

If this password changes in Windows, it must be updated manually in ZCB. Click the Update Password button to update the stored password for the amandabackup user. 

Please see Update amandabackup password for more information.

Language

ZCB is available in ten different languages:

  • English
  • German
  • Japanese
  • Simplified Chinese
  • Traditional Chinese
  • Korean
  • Thai
  • Italian
  • Portuguese
  • Spanish

The chosen language should always match the language used for Windows on the system. File names that contain characters cannot be backed up unless Windows includes those characters. For example, ZCB, even if it is set to Japanese language, cannot back up files that contain Japanese characters unless Windows is running in Japanese.

Help and Support

Need help? Have questions? Don't worry! We have several self-help options and a support team.

Self-Help

The Help Center at http://help.zmanda.com

There is a wealth of information at your disposal in the Help Center! All of our documentation is contained within, and is frequently updated.

If you hit a snag during setup, check your User's Guide for requirements. Your system may be missing some critical component. 

If you get an error, search for it in the Knowledgebase. Articles are added and updated frequently.

The Forums at http://forums.zmanda.com

Find fellow Zmanda customers and our own staff members on our forums.

Support

Open a Support Ticket from http://network.zmanda.com

Log in to http://network.zmanda.com and visit the Support tab! Opening a support ticket is the easiest, fastest way to get help from our support staff.

You may also click on Help > Contact Support within ZCB itself.

Collect Log Files

The support staff or forums members may request logs from your system. Please see Collecting ZCB logs for troubleshooting