Advanced - VMware SnapProtect™ Backup

Table of contents

Managing Snapshots

List Snapshots

Mount Snapshots

Delete Snapshots

Revert Virtual Machine from a Snapshot

Configuring User Accounts

Virtual Center Credentials

Permissions for Custom User Accounts

Configuring Auto-Discovery by Datastore Affinity of Virtual Machines

Configuring Subclients through the Command Line

Truncating SQL Database Logs

Verify SnapProtect Backups

Choosing Restore Types

Restore to a Different ESX server

Restoring Files and Folders

Restore Files from a Snapshot (Live Browse)

Restore Data from a Backup Copy

Data Aging for SnapProtect Snapshots

Retention by Number of Jobs

Options not supported for VMware

Using a Separate ESX Server for a Backup Copy

Configuring a Subclient to Use a Separate Proxy Client

Specifying Secondary ESX Server for Backup Copy Operations

Restoring Virtual Machines from a Snapshot Mounted on the Secondary ESX Server

Disabling VMware Quiesce

Pre/Post Processing using VMware Tools

Additional Options

Managing Snapshots

The snapshots of the data created by the SnapProtect backup are also available for various other operations like list, mount, unmount, or delete.

List Snapshots

The browse operation provides the capability to see the snapshots created for an agent, job, or a snapshot copy. The list of the snapshots displayed is corresponding to the entity selected for the browse operation, for e.g., browsing the snapshots for an agent will display all the snapshots created for the selected agent. You can view volume or disk related information for the snapshots. Follow the steps given below to browse snapshots.
  1. From the CommCell Browser, navigate to Client Computers | Virtual Server | <Instance>.
  2. Right-click <backup set> and click All Tasks | List Snaps.
  1. The Snaps created during SnapProtect operation dialog box displays a list of all the snapshots created for the selected subclient. It also displays important information about each snapshot, including the source month path, snap mount path, the storage array, and the source client.

    Click the Disk View tab to display the snapshot name, e.g. SP_2_79_1286222629.

 

Mount Snapshots

You can mount any available snapshot to access the data included in the snapshot. It is recommended that you select the option to protect a snapshot when it is mounted, as this will ensure that the changes made to the snapshot when it is mounted are not retained when you unmount the snapshot and the snapshot is usable for data protection operations. Follow the steps given below to mount snapshots:

If the niSCSIEnable registry key is configured, SnapProtect backup will always try to mount using iSCSI method. If this key is not configured, SnapProtect backup will try to mount using the FC method first.
  1. From the CommCell Browser, navigate to Client Computers | Virtual Server | <Instance>.
  2. Right-click <backup set> and click All Tasks | List Snaps.
  3. From the Snaps created during SnapProtect operation dialog box, right-click the snapshot that you wish to mount and select Mount.

    You can also open the Snaps created during SnapProtect operation dialog box by right clicking the snapshot copy in a storage policy. However, if you open the dialog box by this method, you can only view the list of snapshots and cannot mount the snapshots.
  1. From the Mount Path dialog box, you can select a different ESX server for mounting the snap by choosing the Select ESX server for snap mount option.
  2. Select the appropriate ESX server from the Browse for ESX Server dialog box. 
  1. Click OK to close the Browse for ESX Server dialog box.
  2. Click OK to close the Subclient Properties dialog box.

Unmount Snapshots

Follow the steps given below to Unmount Snapshots:

  1. From the CommCell Browser, navigate to Client Computers | Virtual Server | <Instance>.
  2. Right-click <backup set> and click All Tasks | List Snaps.
  1. Right-click the snapshot you wish to unmount and click Unmount.
  2. Click Yes when prompted if you want to continue.
If the snapshot does not get unmounted, select the Force Unmount option to mark the snapshot as unmounted.

Snap Mount to a different ESX server

While performing mount operations you can use a temporary ESX server to reduce the load on the production server.
  1. From the CommCell Console, right-click the subclient for which you wish to perform a SnapProtect backup and click Properties.
  2. Click the SnapProtect Operations tab.
  3. Select the SnapProtect option to enable SnapProtect backup for the selected subclient.
  4. You can select a different ESX server for mounting the snap by choosing the Select ESX server for snap mount option.
  5. Select the appropriate ESX server from the Browse for ESX Server dialog box. 
  6. Click OK to close the Browse for ESX Server dialog box.
  7. Click OK to close the Subclient Properties dialog box.
By default the snapshot will be exposed to the first Host Bus Adapter (HBA) on the ESX Server. If you want to expose the snapshot to a specific HBA, configure the sPortInfo registry key.

Delete Snapshots

Snapshots can either be deleted using job-based pruning or from the list of displayed snapshots when browsing snapshots. Data Aging can also be used to define the retention rules and pruning of snapshots. Follow the steps given below to delete snapshots:

  • Manual deletion of snapshots is not recommended. When a snapshot is deleted, it is no longer possible to perform data recovery operations from the snapshot copy. However, if a backup copy was created from the snapshot, data recovery operations can be performed from the backup copy.
  • Ensure that the snapshot to be deleted is not mounted.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>.
  2. Right-click the subclient and click List Snaps.
  1. Right-click the snapshot you wish to delete.
    Ensure all snapshots with the same Job ID are selected for a successful deletion operation.
  2. Click Delete.
  3. Enter the confirmation text string, erase snapshots.
  4. Click OK.

Revert Virtual Machine from a Snapshot

You can use the revert operation to bring the data back to the point-in-time when the snapshot was taken. This operation overwrites any modifications to the data since the time when the snapshot was created.

Revert operations for a virtual machine are supported on NetApp File Servers but not from SnapVault or SnapMirror snapshots. Other file servers are not supported. To perform a revert operation, the SnapRestore license is required on the NetApp file server.

Before performing revert operation, ensure that all the disks reside on the NFS data store. If the data does not reside on the NFS data store, you cannot perform the revert operation.

It is recommended to verify the contents of the backup and ensure that you want to perform a revert operation as it is an irreversible operation.
  1. From the CommCell Browser, navigate to Client Computers | Virtual Server | <Instance>
  2.  Right-click <backup set> and click All Tasks | Browse Backup Data.
  3. From the Browse Options dialog box, select Container Restore and click OK.
  4. Select the virtual machine that you want to revert and click Recover All Selected.
  5. From the Restore Options dialog box, click Advanced.
  6. Select the Use hardware revert capability if available option.
  7. Click OK to confirm the revert operation.
  8. Click OK from the Advanced Restore Options dialog box.
  9. Click OK to start the revert.
For NetApp NFS configurations:
  • This operation reverts all data on the file server volume, not just the data that is associated with the snapshot.
  • A volume revert deletes all snapshots that were created after the snapshot to which you are reverting.
  • If you perform a volume revert on the source for a SnapVault/SnapMirror copy, and the snapshot to which you are reverting was created before the most recent snap moved to the SnapVault/SnapMirror copy, then the SnapVault/SnapMirror copy operation no longer works.
     

Configuring User Accounts

The Virtual Server iDataAgent requires user accounts that have sufficient privileges for the software to:

An administrative account configured with the VCB Role and the following additional privileges can be used:

User-defined roles can also be created provided the above-mentioned privileges are included in those roles.

The following sections provide the steps necessary to configure user accounts for Virtual Centers and ESX Servers.

Virtual Center Credentials

  1. Navigate to Client Computers | <Client> | Virtual Server.
  2. Right-click the instance and click Properties.
  3. In the VMware | vCenter area, click the Change button.
  4. Enter the username and password.

    The password must not contain single-quote (') or double-quote (") characters.

  5. Click OK to save your changes.
  6. Click OK.

Permissions for Custom User Accounts

You can create a separate account for backup and restore operations. When you are create a user account, following system privileges are automatically added to account:

Category Available Permissions
System Anonymous

Read

View

Ensure that the following permissions are assigned to the user account:

Backup Permission Requirements

Category Available Permissions
Datastore Allocate space

Browse datastore

Configure datastore

Low level file operations

Remove datastore

Rename datastore

Update virtual machine files
Global Disable methods

Enable methods

Licenses
Host - Configuration Advanced settings

Connection

Storage partition configuration

System Management
Virtual machine - Configuration Add existing disk

Add new disk

Add or remove device

Change resource

Disk change tracking

Disk lease

Remove disk

Settings
Virtual machine - Provisioning Allow read-only disk access

Allow virtual machine download

Clone virtual machine
Virtual machine - Snapshot Management ("Virtual machine - State" in vSphere 4.1) Create snapshot

Remove Snapshot

Restore Permission Requirements

Category Available Permissions
Datastore Allocate space

Browse datastore

Configure datastore

Remove datastore

Rename datastore

Update virtual machine files
Host - Configuration Advanced settings

Connection

Storage partition configuration

System Management
Network Assign network
Resource Assign vApp to resource pool

Assign virtual machine to resource pool
Virtual machine - Configuration Add existing disk

Add new disk

Add or rRemove device

Advanced

Change CPU count

Change resource

Disk change tracking

Disk lease

Host USB device

Memory

Modify device settings

Raw device

Reload from path

Remove disk

Rename

Reset guest information

Settings

Swapfile placement

Upgrade virtual machine compatibility ("Upgrade virtual hardware " in vSphere 4.1")
Virtual machine - Interaction Power Off

Power On
Virtual machine - Inventory Create new

Register

Remove

Unregister
Virtual machine - Provisioning Allow disk access

Allow read-only disk access

Allow virtual machine download

Mark as template (to restore VM template)
Virtual machine - Snapshot Management ("Virtual machine - State" in vSphere 4.1) Create snapshot

Remove Snapshot

Revert to snapshot

Configuring Auto-Discovery by Datastore Affinity of Virtual Machines

It is recommended to configure automatic discovery of virtual machines by data store affinity if you have a large VMware environment with many virtual machines, ESX servers and datastores.

When configured, new virtual machines found in the datastore are automatically assigned to the desired subclient and backed up when backup operations on the subclient are performed.

  1. From the CommCell Browser, right-click the backup set for which you want to discover guest hosts and then click Properties.
  2. Select Rule-Based Discovery.
  3. Click Discover By drop-down box and select DataStore Affinity.
  4. Click Configure.
  5. From the Datastore Configuration for Auto Discover dialog box, click Discover Data Stores.
  6. From the Auto Discover Data Stores dialog box, locate the datastores you wish to configure for auto discovery and select the subclient you wish to associate each with.

    To exclude a select number of datastores from being backed up, choose the Do Not Backup option in the Subclient column.

  7. Click OK to save your changes.
  8. Click OK from the Datastore Configuration for Auto Discover dialog box.

Configuring Subclients through the Command Line

Use the following steps to configure a subclient with SnapProtect properties:

  1. Download the update_subclient_add_template.xml file and save it on the computer from where the command will be executed.
  2. Select the operation that you want to run from the sections below, and execute the command from the <Software_Installation_Directory>/Base folder after substituting the parameter values.

    Set Backup Type

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -backupType xxxxx

    Use Proxy to perform SnapProtect backups

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -useProxy/clientName xxxxx

    Set the Transport Mode for VMware

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -transportModeForVMWare xxxxx

    Set the Proxy for the ESX Host

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -isSnapBackupEnabled true -proxyESXHost xxxxx

    Enable Application aware Backups and Truncate Exchange Database Logs

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -isSnapBackupEnabled true -backupForGranularRecovery true -truncateExDBLogs true

    Use Separate Proxy for Snap to Tape Operation

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -isSnapBackupEnabled true -useSeparateProxyForSnapToTape true -separateProxyForSnapToTape/clientName xxxxx

    Set the Storage Array Type

    qoperation execute -af update_subclient_add_template.xml -appName 'Virtual Server' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -isSnapBackupEnabled true -snapShotEngineName 'xxxxx'

Available Parameters for Subclients

The following table describes the parameters used in the above sections.

Parameter Description of Parameter values
clientName Name of the client computer.
backupsetname Name of the backup set. If the backup set name is not specified in the command query, the default backup set is used by default.
appName Name of the application. In this case it would be 'Virtual Server'.
subclientname Name of the subclient.
backupType Option to set the backup level at which the SnapProtect backup should run. Valid values are:
  • FILE_LEVEL
  • VOLUME_LEVEL
  • DISK_LEVEL
useProxy/clientName Name of the client computer that will behave as the proxy. This is useful when you want a different computer to perform the backups.
transportModeForVMWare Option to set the transport mode of your environment. Valid values are:
  • AUTO, to allow the software to automatically set the transport mode based on your setup.
  • SAN
  • HOT_ADD
  • NAS
  • NBD_SSL
  • NBD
isSnapBackupEnabled Option to enable the SnapProtect configuration on the subclient.

Valid values are true/false.
backupForGranularRecovery Option to enable the application aware backup operation to allow granular recovery of files. Valid values are true/false.

When this option is set to true, you can also truncate the Exchange Database logs using the truncateExDBLogs parameter. Valid values for this parameter are true/false.
useSeparateProxyForSnapToTape Option to enable the use of a proxy computer to perform SnapProtect operations in a different Virtual Server client. Valid values are true/false.

When this option is set to true, you also need to specify proxy computer using the separateProxyForSnapToTape/clientName parameter.
snapShotEngineName Name of the storage array to be configured with the subclient. Valid values are:
  The name of the storage array should match with the name displayed in the Available Snap Engine list in the subclient properties.
  • Data Replicator
  • 3PAR Clone
  • 3PAR Snap
  • Dell Compellent Snap
  • Dell Equallogic Clone
  • Dell Equallogic Snap
  • EMC Celerra
  • EMC CLARiiON SnapView Clone
  • EMC CLARiiON SnapView Snap
  • EMC TimeFinder BCV
  • EMC TimeFinder Clone
  • EMC TimeFinder Snap
  • EMC CLARiiON SnapView Snap
  • Fujitsu ETERNUS DX Clone
  • Fujitsu ETERNUS DX Snap
  • HDS Copy on Write Snapshot
  • HDS Shadow Image
  • HP EVA Clone
  • HP EVA Snapshot
  • IBM XIV Snap
  • IBM SVC FlashCopy
  • IBM SVC Space-efficient FlashCopy
  • LSI Snapshot
  • LSI Volume Copy
  • NetApp
  • Nimble Storage CS-Series Snap

Truncating SQL Database Logs

When you are using Virtual Server iDataAgent to create the snapshot of a SQL server, you can truncate the SQL server database logs before creating the snapshot. Follow the steps given below to truncate the SQL server database logs:

  1. Install the Microsoft SQL Server iDataAgent for restore only on the virtual machine which has the SQL server. For more information, refer to Installing Restore Only Agents.

    Once you install the agent, the CvSQLBackupUtility will be available in the <Base> folder under <Installation Directory> on the virtual machine. This utility will be used to truncate the SQL server database logs.

  2. Create batch file with name <post-thaw-script.bat > and type the following command in the batch file.  as below

    CvSQLBackupUtility.exe -server <SQL Server> -database <databasename> -op <operation>

    This command will execute the SQL command to truncate logs.

    For example:

    <Install Directory>\Base\CvSQLBackupUtility.exe" -server VSA_SQL2 -database ReportServer -op truncatelog

  3. Create directory backupScripts.d under C:\Program Files\VMware\VMware Tools and copy the above batch file to this location.

    The post-thaw-script location varies based on ESX versions For more information refer to http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006671.

    When you perform the SnapProtect backup of the SQL server, the batch file will be executed while creating the snapshot and the SQL database logs will be truncated.

Verify Snapprotect Backups

You can verify a backup to ensure that you can restore the virtual machine.

The recovery verification recreates the virtual machine to ensure backed up application and data are available as expected.

  

Mount the snapshot

  1. From the CommCell Browser, right-click the subclient that contains the virtual machine backup that you want to verify, click All Tasks | List Snaps.
  2. Right-click the snapshot that you wish to verify and select Mount.
  3. From the Mount Path dialog box, click the Select ESX server for snap mount option.
  4. Select an ESX server from the Browse for ESX Server dialog box.

    As this ESX server will be used to create the virtual machine, it is recommended that you select a non-production server.

  5. Click OK.

Browse the data

  1. From the CommCell Browser, right-click the subclient that contains the backup that you want to verify and click All Tasks | Individual files/folders.
  2. Click OK.

BROWSE NEW DATASTORE AND REGISTER THE VIRTUAL MACHINE

  1. From the VI client, ensure that the new virtual machine from the backup is registered. The virtual machine name will be in the [OriginalVMName]_[BackupJobID]_GX_BACKUP format.

    If the virtual machine is not registered, follow the steps given below to browse the new datastore that is created and register the virtual machine.

  1. Click the virtual machine you want to register and click the Summary tab to see the datastore name.
  2. Click the ESX server you selected in Step 4, and click the Storage option.
  3. Identify the new datastore created after mounting the snapshot and register the virtual machine. The new datastore will have the following name:

    [OriginalDatastoreName]_GX_BACKUP_[BackupJobID]

  4. Specify a name for the virtual machine.

Verify the data using VI client

  1. Right-click the virtual machine and select Edit Settings. Click Network adapters.
  2. Clear the Connect at power on checkbox in the Virtual Machine Properties dialog box for all the available network adapters.
  3. Click OK.
  4. Turn on the virtual machine.
  5. Click the Summary tab and select the I moved it option.
  6. Login to the virtual machine and verify the applications and data.
  7. After verification is complete, power off the virtual machine.
  8. Right-click the virtual machine and select the Remove from inventory option.

unmount the snapshot

  1. From the CommCell Browser, right-click the entity that contains the snapshots you want to browse, click All Tasks | List Snaps.
  2. Right-click the snapshot that you wish to unmount and select Unmount.

Choosing Restore Types

When restoring VMware data, it is important to consider the backup level that was originally performed. The following table illustrates the types of restores available for each backup level:

Backup Level

Restore Level from Snap

Restore from Tape

Notes
Disk-Level Disk-Level (as virtual machine)

Disk Level (as VMDK file)

 Disk-Level (as virtual machine)

Disk Level (as VMDK file)

  
Disk-Level with Enable Granular Recovery enabled Disk-Level (as virtual machine)

Disk-Level (as VMDK file)

Volume-Level (as physical volume)

Volume-Level (as VHD)

Volume-Level (as VMDK)

File-Level

 Disk-Level (as virtual machine)

Disk-Level (as VMDK file)

File-Level

 

  
Volume-Level Disk-Level (as virtual machine)

Disk Level (as VMDK file)

 Volume-Level (as physical volume)

Volume-Level (as VHD)

Volume-Level (as VMDK)

 Supported only with volumes formatted with the NTFS file system.
Volume-Level with Enable Granular Recovery enabled Disk-Level (as virtual machine)

Disk-Level (as VMDK file)

Volume-Level (as physical volume)

Volume-Level (as VHD)

Volume-Level (as VMDK)

File-Level

 Volume-Level (as physical volume)

Volume-Level (as VHD)

Volume-Level (as VMDK)

File-Level

 Supported only on Windows-based VMware virtual servers formatted with the NTFS file system.
File-Level File-Level

Disk-Level (as virtual machine)

Disk-Level (as VMDK file)

Volume-Level (as physical volume)

Volume-Level (as VHD)

Volume-Level (as VMDK)

 File-Level For file level restores, select Enable Granular Recovery option.

Restore to a Different ESX server

You can override the default restore selection by choosing a different Virtual Centre or ESX Server to restore, by following the steps given below:
  1. From the CommCell Console, right-click the Subclient and select Browse Backup Data.
  2. Click OK and select the virtual machine under the backupset. Its entire contents will be automatically selected in the right pane. Click Recover All Selected.
  3. Click Advanced from the Restore Options dialog box.
  4. Select the ESX Browse tab.
  5. The Default Selection has the IP address of the ESX Server pre-populated.
  6. Select Override Default Selection to locate a different destination.
  7. Enter appropriate credentials to logon to the server using Configure Password button.
  8. Click Browse VirtualCentre/ESX Servers for destination to provide the ESX Server path to which the virtual machine will be restored.
  9. Select the appropriate ESX server. 
  10. Click OK to close the Browse for ESX Server dialog box.
  11. Click OK to close the Advanced Restore Options dialog box.

Restoring Files and Folders

To restore files and folders to a Windows client, the client must have one of the following components installed:
  • Windows File System iDataAgent
  • Restore Only Agent for Windows File System.

Consider that the following before restoring files and folders from a virtual machine:

  • The virtual machine has the MBR partition. If the virtual machine has GPT partition, you can restore files from a backup copy. For more information, refer to Restore Data from a Backup Copy.
  • You must perform the backup using the VMware Storage API method. For more information, refer to Configuring Backups for vSphere VADP Environments.
  • You cannot restore any archived files and folders.
  • It is recommended to perform the file-level restores from disk or volume-level backups only when you are restoring small files. For example, restoring a 2GB file from a disk-level backup is not recommended.

You can restore files from NTFS file systems with the following limitations:

  • The formatted cluster size (allocation unit) must be 1024 or greater.
  • You cannot restore any archived files and folders.
  • You cannot restore any file that has zero bytes, symbolic links, or hard links associated with it.
  • You cannot restore files that have been dehydrated by Windows 2012 dedup.
  • You cannot restore files from volumes created on Windows Storage Spaces.

If you cannot restore a file, you can restore the complete virtual machine or the disk that contains the file.

When restoring a file or folder on a virtual machine, the Enable Granular Recovery must have been selected when the backup was performed.

  1. From the CommCell Console, perform a Browse and Restore operation.
  2. In the Browse Options window, click Individual files/folders.
  3. Click OK.
  4. In the Browse window, click a file or folder in the right pane, and then click Recover All Selected.
  5. From the General tab, specify a Staging Path. This is the destination path to which the file will be restored.
  6. Click OK.
  The Preserve Source Path/Remove Source Path feature is supported for File level restores from File level backup jobs. It is not relevant for Volume Level and Disk Level backups and restores.

Restore Files from a Snapshot (Live Browse)

You can restore files and folders from a snapshot when a backup is performed without enabling the Enable Granular Recovery advanced backup option.

Before performing the browse and restore from a snapshot, note the following:

  • This feature is available for Windows-based VMware virtual machines but not available for any other operating system.
  • This feature is available for the MBR partition. If the virtual machine has GPT partition, you can restore files from a backup copy. For more information, refer to Restore Data from a Backup Copy.
  • You must perform the backup using the VMware Storage API method. For more information, refer to Configuring Backups for vSphere VADP Environments.

Follow the steps given below to perform the browse and restore from a snapshot:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Virtual Server | <Instance>.
  2. Right-click the subclient that contains the data that you want to restore and click Browse Backup Data.
  3. In the Browse Options window, click Individual files/folders.
  4. Click OK.
  5. Select the virtual machine that contains the files that you wish to restore.

    Depending on the hardware configuration, it may take some time to mount the snapshot on the ESX server before displaying the files and folders.

  6. In the Browse window, right-click a file or folder in the right pane and click Recover All Selected.
  7. From the General tab, specify a Staging Path. This is the destination path to which the file will be restored.
  8. Click OK.

Restore Data from a Backup Copy

You can perform a restore from the backup copy by setting the appropriate copy precedence number.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>.
  2. Right-click the entity that contains the snapshots you want to restore, and point to All Tasks | Browse Backup Data.
  3. Click OK.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  5. From the Restore Options for All Selected Items window, click Advanced.
  6. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  7. In the Copy Precedence box, type the copy precedence number for the backup copy.

 8.   Click OK.

 9.   Click OK to close the Restore Options dialog box and start the restore job.

Data Aging for SnapProtect Snapshots

The following procedures describe the available retention configurations for snapshots. For movement to media retention, refer to Data Aging - Getting Started.

Retention by Number of Jobs

By default, snapshots are pruned based on the number of retention days and cycles specified in the storage policy. You can configure your snapshot copy to retain a defined number of SnapProtect backup jobs. When the total number of jobs goes above the specified retention number, the remaining jobs will be pruned. This configuration is recommended for File System and File System like Agents. This feature is supported for SnapProtect operations performed using the NetApp storage array.

The NetApp Snap Management license is required for retaining snaps by number of jobs.

1.
  • From the CommCell Console, navigate to Policies | Storage Policies | <Storage Policy>.
  • Right-click the primary snapshot copy and click Properties.
2.
  • Click the Retention tab.
  • Click Retain Snaps by Number of Jobs.
  • Click OK to the warning dialog box.
  • Specify the number of jobs to be retained for the primary copy.
  • Click OK.

 

Options not supported for VMware

The following options are not supported for SnapProtect backup for Virtual Server iDataAgent - VMware:

Using a Separate ESX Server for a Backup Copy

The backup copy is an additional standby copy of data. It can be created during the SnapProtect backup or at a later time. You can use a separate proxy client and ESX Server to create a backup copy. If you want to reduce the time required for mounting the snapshot,  you must use a local Proxy client and ESX server for backup copy operations.

The backup copy can be an inline backup copy, offline backup copy or netapp’s vault or mirror copies.

For example: The default proxy client and ESX Server is in location A and you want to use the backup copy of the data from location B. In such scenario, you can use an ESX server in location B for creating backup copy and then restore virtual machines from the backup copy.

Configuring a Subclient to Use a Separate Proxy Client

Follow the steps given below to use a separate proxy for creating the backup copy:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Virtual Server | <Instance>.
  2. Right-click the subclient and select Properties.
  3. Click the SnapProtect Operations tab.

    The Proxy ESX Server section will display the Primary proxy client and Primary ESX Server.

  4. Click Use Separate Proxy for Snap To Tape check box.
  5. Select a Proxy client from the Proxy list.
  6. Click OK.

    The selected Proxy client will be treated as a secondary proxy client. It will be used to perform the Inline Backup copy, Offline Backup copy, NetApp Vault or NetApp Mirror operations.

    You can use the default ESX Server to create backup copy or you can specify a secondary ESX Server for the backup copy.

Specifying Secondary ESX Server for Backup Copy Operations

Follow the steps given below to specify a secondary ESX Server. The snapshots will be mounted to the specified ESX proxy and not to the Primary proxy.

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right click the Secondary Proxy client and click Properties.
  3. Click the Registry Key Settings tab.
  4. Click Add.
  1. In the Name box, type sProxyESX.
  2. In the Location list, type HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance<xxx>\
  3. In the Type list, select REG_SZ.
  4. In the Value field, type the Host name or IP address of the secondary ESX Server.
  5. Click OK.

 

Restoring Virtual Machines from a Snapshot Mounted on the Secondary ESX Server

Follow the steps given below to perform the browse and restore from a snapshot mounted on the alternate ESX Server:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Virtual Server | <Instance>.
  2. Right-click the subclient that contains the data that you want to restore and click Browse Backup Data.
  3. Select the Type of Intended Restore.

    If you haven't selected the Enable Granular Recovery option while performing the backup, select the secondary proxy in the Use MediaAgent list.

  4. Click Advanced.
  5. Select the Browse from copy precedence check box.
  6. Enter the Copy Precedence of the snapshot copy.

    You can find out the copy precedence of the snapshot copy from the Copy Precedence tab of the Storage Policy Properties dialog box.

  7. Click OK.
  8. Click OK.

    The data from the snapshot mounted on the secondary ESX server will be displayed.

  1. Select the virtual machine that you want to restore and Click Recover All Selected.
  2. From the General tab, click Advanced.
  3. Click the Data Path tab.
  4. Select the secondary proxy client from the Use Proxy list.
  5. Click OK.

The secondary ESX server will be used to restore the virtual machine.

Disabling VMware Quiesce

Quiescing indicates pausing or altering the state of running processes on a computer, particularly those that might modify information stored on disk during a backup, to guarantee a consistent and usable backup.

For windows Microsoft VSS inside the guest will be used to quiesce the file system and applications. This ensures that the data consistency of the file system and all VSS supported applications. By default VMware will engage all of the VSS writers that are configured inside the guest. If it is necessary to exclude a writer please refer to http://kb.vmware.com/kb/1031200

For Linux, the vmsync driver will be used to quiesce the file system and applications.  This is included with VMware tools. The vmsync driver ensures that the file system is in a consistent state prior to the vmware snapshot being created. The vmsync driver is only supported with vSphere 5.0 and above.

Consider the following before enabling or disabling the quiescing during the backup:

You can disable quiescing to reduce the backup time. If you disable quiescing, you can perform backup of the virtual machines which has .vmdks with same name.

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right click the Proxy client and click Properties.
  3. Click the Registry Key Settings tab.
  4. Click Add.
  1. In the Name box, type VwSkipQuiesceVM.
  2. In the Location list, type HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance<xxx>\
  3. In the Type list, select REG_DWORD.
  4. In the Value field, type 1.
  5. Click OK.

 

Pre/Post Processing using VMware Tools

You can use the VMware tools to perform the any operations before or after the backup. For example: A virtual machine hosts a oracle database and you want to enable the Hot backup of the database before performing the backup, you can run a script using the VMware Tools.

For more information about running scripts on Windows virtual machines, refer to http://kb.vmware.com/kb/1006671

On the Linux virtual machines, the script /usr/sbin/pre-freeze-script will be executed when the software snapshot is created and /user/sbin/post-freeze-script will be executed when the software snapshot is removed. Ensure that these scripts are executable by the VMware tools user.

The following scripts are available to perform the Pre/Post processes using VMware tools:

Operation

Procedure

Scripts
The scripts can be used to take snapshot of a VM with DB2 Application. This script allows VMWARE to suspend I/O updates to DB2 database till VMWARE LINUX guest snap shot is completed.
  1. On a Linux virtual machine, copy the pre-freeze-script and post-thaw-script to /usr/bin directory.
  2. Copy write_suspend and write_resume scripts to a location where DB2 database can execute it. (Preferably to a directory under DB2 home)
 pre-freeze-script.sh

post-thaw-script.sh

write_resume.sh

write_suspend.sh
The scripts can be used to take snapshot of a VM with MAXDB Application. This script allows VMWARE to suspend I/O updates to MAXDB database till VMWARE LINUX guest snap shot is completed.
  1. On a Linux virtual machine, copy the pre-freeze-script and post-thaw-script to /usr/bin directory.
  2. Copy suspend_logwriter and resume_logwriter scripts to a location where MAXDB database can execute it. (Preferably to a directory under MAXDB home)
 pre-freeze-script.sh

post-thaw-script.sh

resume_logwriter.sh

suspend_logwriter.sh

 
The scripts can be used to take snapshot of a VM with Oracle Application. This script allows VMWARE to suspend I/O updates to Oracle database till VMWARE LINUX guest snap shot is completed.
  1. On a Linux virtual machine, copy the pre-freeze-script and post-thaw-script to /usr/bin directory.
  2. Copy pre-freeze-script.sql and post-thaw-script.sql scripts to a location where Oracle database can execute it. (Preferably to a directory under Oracle home)

    These scripts change the entire database to backup  mode.

    If the virtual machine has Oracle iDataAgent installed on it, you can also use the consistent-archivelog-backup.rman script as a sample to run archivelog backup. This will get a consistent snap and also all the latest archived logs and current control file.

 pre-freeze-script.sh

post-thaw-script.sh

pre-freeze-script.sql

post-thaw-script.sql

consistent-archivelog-backup.rman
The scripts can be used to take snapshot of a VM with Sybase Application. This script allows VMWARE to suspend I/O updates to Sybase database till VMWARE LINUX guest snap shot is completed.
  1. On a Linux virtual machine, copy the pre-freeze-script and post-thaw-script to /usr/bin directory.
  2. Copy pre-freeze-script.sql and post-thaw-script.sql scripts to a location where Sybase database can execute it. (Preferably to a directory under Sybase home)

    These scripts execute sybase quiesce commands which will stop updates to databases.

 pre-freeze-script.sh

post-thaw-script.sh

pre-freeze-script.sql

post-thaw-script.sql

Additional Options

Several additional options are available to further refine your backup and restore operations. The following table describes the additional options:

Option Description Related topics
Job Results Directory Ensure that the full path name for the Job Results Directory, combined with the VMDK file name, is no greater than 255 characters in length.
  1. From the CommCell Browser, right-click the icon of the client computer whose job results path you want to change, then click Properties.
  2. From the Job Configuration tab of the Client Computer Properties dialog box, click User Name/Password to establish or change the Impersonate User account to access the Job Results Directory. Click OK once you have administered the account.
  3. From the Job Configuration tab, type a new job results path in the Job results path field.
    You can also click Browse to browse to a new job results path from the Browse for Job Result Path dialog box. Click OK.
  4. Click OK to save your changes.
 Refer to Job Management.
Pre/Post Commands The Pre/Post commands for SnapProtect backup can either be executed on the proxy or the source computer. You can use the Pre/Post Process tab of the Subclient Properties dialog box to select where you wish to execute the Pre/Post commands. SnapProtect backup supports Pre/Post commands for the agents that support it.
Use of Pre/Post Snap commands is not supported when using Data Replicator as the storage array.
 For more information on using the Pre/Post commands, see Pre/Post Processes.
View Snapshot Details You can view the details of a snapshot for an agent, job, or a snapshot copy. When you right-click any of these entities, you will be able to browse all the snapshots corresponding to the selected entity.
  1. From the CommCell Browser, right-click the entity that contains the snapshots you want to browse, and click All Tasks | List Snaps.
  2. The Snaps created during SnapProtect operation dialog box displays a list of all the snapshots created for the selected entity and displays important information about each snapshot, including the source mount path, snap mount path, the storage array, and the source client.
  3. Right-click the snapshot and click Details to view the snapshot properties.
  
Select a Job for Backup Copy You can select a specific job for creating backup copy. Once selected, the Move Snap to Tape field for the specific job will be changed to Picked (i.e., the next backup copy operation will move this job to media).
  1. Right-click a storage policy containing SnapProtect backup jobs, and then click View Jobs.
  2. Right-click the job and then click Pick for Backup Copy.
  
Disable a Job for Backup Copy You can prevent a job from being moved to media. You can apply this option to those jobs that were previously selected for moving to media. On selecting this option, the Move Snap to Tape field for the specific job will be changed to Not Picked (i.e., the next backup copy operation will not move this job to media).
  1. Right-click a storage policy containing SnapProtect backup jobs and then click View Jobs.
  2. Right-click the job and then click Do not Backup Copy.
  
Offline Snap Copy Job Summary Report Offline Snap Copy Job Summary Report provides job summary details of backup copy jobs for moving snapshots to media. See Backup Copy Job Summary Report for more details
Find Use Find to search and locate files or folders from a SnapProtect backup. If you want to restore a specific file or folder from a backup set or subclient, you can search the file or folder in the backup set or subclient.

Before searching the subclient, ensure that all the files and folders in the subclient are included in the index. The files and folders are included in the index when you perform the File Level backup or Enable Granular Recovery before performing the Volume Level or Disk Level backup.

See Finding and Restoring for more details.

Back to Top