Advanced Configuration - Image Level iDataAgent

  • This product is deprecated for AIX and Linux. New installations of the Image Level Agent are no longer supported in V10, but the agent will continue to function normally. Upgrade to the latest service pack in V10 is supported. You cannot use your installed version of the Image Level Agent to perform backups in the next version of SnapProtect.
  • This functionality is now available using Block-Level Backup. We recommend that you begin backing up data by using the block-level backup method instead of using the Image Level Agent as soon as you are able to. No new license is required for Block-Level Backup. For instructions on transitioning to block-level backups, see Transitioning from Image Level Agent to Block-Level Backups.

See Deprecated Features, Products, and Platforms for comprehensive information on deprecated products.

Table of Contents

Understanding the CommCell Console

The Image Level iDataAgent uses the following logical entities to manage backup and restore operations from the CommCell Console.

Client

The computer in which the iDataAgent is installed and contains the data to be secured.

Agent

Software module that facilitates backup and restore operations.

Subclient

Defines the data to be backed up.

QSnap Service

The QSnap® Service is a software-based snapshot implementation that integrates with other Agents, providing all of the components necessary for basic snapshot functionality without requiring specialized hardware. The QSnap product is an installable, licensed software module. In this release, the QSnap service will still be automatically installed with CDR but will not be used as the default snap engine. QSnap® Services will be used as the source snapshot on Windows 2000 and Windows XP. It will not be used for creating Recovery Points, even with the aforementioned operations systems.

On Unix platforms, the driver name is Unix QSnap. You will often see "CXBF" in references to the Unix QSnap driver. For example, a CXBF device is a volume or partition that is monitored by the CXBF block-filter driver.

The QSnap service provides the following functionality:

  • Data Replication Agents

    QSnap functionality is automatically installed with the ContinuousDataReplicator agent. In addition to providing volume-level snapshot functionality, the QSnap driver has an integrated block-filter driver that monitors changes to a volume over time. For any volume-level agent, the bitmaps help ensure that the next data protection operation can be an incremental backup instead of a full backup.

  • Unix File System iDataAgent

    QSnap services can be used with the Unix File System iDataAgent. When QSnap is installed and enabled for use with this Agent, the snapshot functionality of QSnap is used to snap and then back up locked and/or open files.

  • Windows File System iDataAgent

    QSnap services can be used with the Windows File System iDataAgent. When QSnap is installed and enabled for use with this Agent, the snapshot functionality of QSnap is used to snap and then back up locked and/or open files.

  • Backup & Recovery Agents

    QSnap services is automatically installed with the following Backup & Recovery iDataAgents: Image Level.

Managing Subclients

Image Level backups are either CXBF (QSnap) backups or non-CXBF (Checksum) backups.

Creating a Subclient for CXBF backups

To run a CXBF backup, QSnap must be installed on the client and you must configure a CXBF subclient. When you add a volume to a subclient content, it is automatically configured as a CXBF device.

On a Unix platform, a CXBF device is a volume or partition that is monitored by the CXBF block-filter driver. Consider the following when configuring a CXBF device:

  • CXBF devices should not be configured on Operating System file systems.
  • CXBF devices can only be configured on quiescent file systems (i.e. unmountable or not busy).

Use the following steps to create a subclient for performing CXBF backups:

  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click <Image Level >, point to All Tasks, and then click New Subclient.
  3. In the Subclient Name box, type a name.

  1. Click the Content tab.
  2. Click Add, select the volume that you want to backup. Select multiple volumes by holding down the Ctrl Key. Click OK.

    Alternatively, you can click Volume Explorer to select the content.

  3. Click the Storage Device tab.
  4. In the Storage Policy box, select a storage policy.
  5. Click OK.

Creating a Subclient for Non-CXBF (Checksum) Backups

To run a non-CXBF (Checksum) backup, you must configure a non-CXBF (Checksum) subclient and also provide a supported snapshot. If a snapshot of a volume already exists, you can directly perform backup and recovery operations on that existing snapshot resulting in better performance and lower storage requirements.

The VSS software provider takes a snapshot of the source volume, database or file, which is then used to create backups. The Image Level On Windows iDataAgent is integrated with the VSS Enabler to conduct backup operations using a VSS software provider. Microsoft Volume Shadow Service is the default, and only supported VSS software provider.

VSS can be enabled for backups of local volumes in both clustered and non-clustered environments. VSS can be enabled only on the NTFS volumes and not on the FAT or FAT32 volumes.

VSS is supported on all the Windows operating systems listed in the System Requirements, except Windows 2000. You cannot enable VSS on Windows 2000.

Use the following steps to create a subclient for non-CXBF backups:

  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click <Image Level >, point to All Tasks, and then click New Subclient.
  3. In the Subclient Name box, type a name..
  4. Click Checksum.
  5. Click the Content tab.
  6. Click Add, select the volume that you want to backup. Select multiple volumes by holding down the Ctrl Key. Click OK.

    Alternatively, you can click Browse or Volume Explorer to select the content.

  7. Click the Storage Device tab.
  8. In the Storage Policy box, select a storage policy.
  9. Click OK.

Configuring Backups Using Volume Explorer

Volume Explorer maintains a database of the disk volumes attached to each MediaAgent and Image Level on Unix iDataAgent, including unique identifying information (WWN/LUN) for each volume.

This information can be used to determine when a single physical volume is mapped to different drive letters or paths on multiple hosts. The system can also look up this information during backup and restore operations, eliminating the need for tedious manual entry of WWNs and LUNs for each subclient or restore job.

For Unix clients, hosts with Image Level on Unix iDataAgent and the CXBF driver installed will appear in Volume Explorer. For AIX, Solaris and Linux, Volume Explorer will detect only the volumes on disks that have been partitioned, or have had a partition table created on them.

For Windows, Volume Explorer detects volumes that are formatted and contain a file system. Raw volumes are not supported.

Use the following steps to configure backups using volume explorer:

  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click <Image Level >, point to All Tasks, and then click New Subclient.
  3. In the Subclient Name box, type a name.
  4. Click the Content tab.
  5. Click Volume Explorer to select the content.
  6. Click the Storage Device tab.
  7. In the Storage Policy box, select a storage policy.
  8. Click OK.

Configuring Application Backups for Oracle

To be able to back up Oracle instances with the Image Level iDataAgent, the Oracle data files and Oracle archive logs must reside on two separate volumes. In addition, the Oracle installation binaries, control file, and online redo logs must reside in volumes other than the data files volume and the archive logs volume. During an Oracle backup, each Image Level subclient is expected to quiesce only one instance at a time. Pre/Post process commands are required to quiesce and unquiesce the Oracle instance during the backup.

A single Image Level iData Agent's subclient can backup a single Oracle instance, a separate subclient must be created to backup each Oracle instance. Use the following steps to create a subclient to backup an Oracle instance:

  1. Copy and rename the PreOraScan.bat and PostOraScan.bat sample files before customizing them for a given Oracle instance (e.g., copy PreOraScan.bat to PreOraScan_<instancename>.bat and copy PostOraScan.bat to PostOraScan_<instancename>.bat).

    The readily provided scripts are samples only and must be customized to quiesce and unquiesce the Oracle instances that you are backing up. Edit the scripts to have the following variables set properly: ORACLE_HOME, ORACLE_SID, GALAXY_BASE, SQL_CONNECT, GALAXY_SQL_TEMP_DIR.

    The PreOraScan.bat and PostOraScan.bat files are commented with instructions about setting each of these values for your environment.

    For non-CXBF Image Level subclients on Unix, you must provide the appropriate PreScan scripts to run the snap and mount operations. You must also provide the appropriate PostBackup scripts to run the un-mount and un-snap operations.

    Example of a PreScan script:

    [d#!/bin/sh
    lvcreate --size 100m --snapshot --name TestLv01_snap /dev/testvg/TestLv01
    mount /dev/testvg/TestLv01_snap /vol1
    lvcreate --size 100m --snapshot --name TestLv02_snap /dev/testvg/TestLv02
    mount /dev/testvg/TestLv02_snap /vol2
    exit 0

    Example of a PostBackup script:

    [d#!/bin/sh
    umount /vol1
    lvremove -f /dev/testvg/TestLv01_snap
    umount /vol2
    lvremove -f /dev/testvg/TestLv02_snap
    exit 0

  2. From the CommCell Browser, navigate to Client Computers | <Client>.
  3. Right-click Image Level, point to All Tasks, and then click New Subclient.
  4. In the Subclient Name box, type a name.
  5. Click the Content tab.
  6. Click Add, select the volume that you want to backup. Select multiple volumes by holding down the Ctrl Key.

    Alternatively, you can click Volume Explorer to select the content.

  1. Click the Pre/Post Process tab.
  2. In the PreScan process box, type the full path of the process that you want to execute during PreScan phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
  3. In the PostScan process box, type the full path of the process that you want to execute during PostScan phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
  4. In the PostBackup process box, type the full path of the process that you want to execute during PostBackup phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
  5. Click OK.
  6. For subclients on Windows platforms, Run As displays Not Selected.

    If you want to change the account that has permission to run these commands, click Change.

    • In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter the user name and password. click OK.
    • If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.
  7. Click OK.
  8. Click the Storage Device tab.
  9. In the Storage Policy box, select a storage policy.
  10. Click OK.

  1. From the CommCell Browser, right click the <Subclient> for which the pre/post processes are set and then click Backup.
  2. Select Full as backup type and Immediate to run the job immediately.
  3. Click OK.

    You can track the progress of the job from the Job Controller or Event Viewer window.  When the backup has completed, the Job Controller displays Completed.

  4. Verify that the PreScan and PostScan phases succeeded. The CVVIOrascan.log will be created in the log file directory, which contains logs of snapping the Oracle archive log volume.

To verify the Oracle database is really quiesced:

In the admin bdump directory of the Oracle instance, open the alert<instancename>.log to verify that the Oracle instance was properly quiesced and unquiesced. This log file records all the activities of the Oracle instance.

Enabling QSnap for Snapshot Creation

QSnap can be used with the Image Level iDataAgent to ensure that consistent backups can be taken from the active live system with point-in-time snapshots created. All the components necessary for basic Image Level iDataAgent functionality are available without requiring specialized hardware.

On Windows, QSnap snaps the data to be backed up to free space on the source volume or another specified volume. On Unix, QSnap copies modified data on the cache partition during the snap window. The cache partition cannot be on the same volume.

Use the following steps to use QSnap for snapshot creation:

  1. From the CommCell Console, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name box, type nOverrideVSSSnapSelection.

    The Category and Type fields are populated automatically.

  6. In the Value field, type 1.
  7. Click OK.

    For Windows 2000, irrespective of the presence of the key, snap would always be through QSnap because VSS is not available on Windows 2000.

SAN and Volume Level Agents on Windows

Change the QSnap Bitmap Location Using Qsnp2Config Tool

The bitmap location is specified during the installation of QSnap functionality. Only NTFS volumes are supported for the bitmap location. For cluster installation, the default location for storing bitmaps is the corresponding shared volume but in case of an upgrade the shared location selected prior to upgrade will be the default location for the bitmaps. You can change the bitmap location using the Qsnp2Config tool.

Use the following procedure to change the location of the QSnap bitmaps. Prior to changing the bitmap location, consider the following:

  • The bitmap location must be an NTFS volume.
  • Directory Path Mount points are not supported.
  • For standard configurations the volume you select must be a local drive. Do not select any fibre channel attached devices, external SCSI devices, or other external hard disks.
  • For cluster configurations, the volume you select must be a shared volume of the same Cluster Group and all volumes on the Cluster Group must use this shared volume for the bitmap file storage.
  • A reboot may be required for the changes to take place.
  • In some instances, changing the location of the bitmaps may force a full backup job. This will happen if the Bitmap Init value is set 1, if the Bitmap Init value remains 0, then a full backup will not be forced.
To change the location of Block Filter (BF) Parameters of an individual volume:
  1. From the \Base directory, launch the Qsnp2Config tool, which will display the DEFAULT Parameters configured during install.
  2. Click on the Configure Block Filter on Volumes button.

  1. In the Enter a Volume field, enter the volume you desire to change (for e.g., l:) and click the Select button, which will display the current settings for the volume.
  2. Click Deactivate BF. In the Bitmap Volume field, enter the volume where you want to store the bitmap for the selected volume (for e.g., l:).
  3. Click the Activate BF button.
  4. Repeat this process for each volume on which you are going to change the bitmap location.
  5. Click Close to close the Configure BlockFilter Volume dialog box.
  6. Click the Exit button to close the Qsnp2Config dialog box.

To change the location of Block Filter (BF) Parameters of all volumes:
  1. From the \Base directory, launch the Qsnp2Config tool, , which will display the DEFAULT Parameters configured during install.
  2. Click Update BF Params, enter the new bitmap location (for e.g., l:) in the Default Volume to keep Bitmap Files field and click Update.
  3. Click OK.
  4. Click the Exit button to close the Qsnp2Config dialog box.

Change the Extent Size for Backup Applications

Use the following procedure to change the backup extent size.

This procedure will require a reboot.

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Update BF Params, enter the desired value in Extent size in Bytes for Backup Applications and click OK to continue.
  3. Click OK. The new extent size settings will take effect after a reboot.

Change the Extent Size for Replication Applications

Use the following procedure to change the replica extent size.

This procedure will require a reboot.

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Update BF Params, enter the desired value in Extent size in Bytes for Replication Applications and click OK to continue.
  3. Click OK. The new extent size settings will take effect after a reboot.

Enable Persistence on Volumes

By default, persistence is enabled on all volumes. If required, you can also enable persistence on volumes with the Qsnp2Config tool.

Use the following procedure to enable QSnap bitmap persistence on a volume or volumes.

Disabling persistence does not require a reboot and does not force your next job to be a full.

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Configure Volumes, then enter or Select the volume for which you want to enable QSnap bitmap persistence.
  3. Click Enable Persistence. The Persistence Enabled value should be set to 1.
  4. Repeat this process for each volume on which you are enabling persistence.
  5. Click the Exit button to complete volume configuration.

Disable Persistence on Volumes

Use the following procedure to disable QSnap bitmap persistence on a volume or volumes:

Disabling persistence does not require a reboot and does not force your next job to be a full.

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Configure Volumes, then enter or Select the volume for which you want to disable QSnap bitmap persistence.
  3. Click Disable Persistence. The Persistence Enabled value should be set to 0.
  4. Repeat this process for each volume on which you are disabling persistence.
  5. Click the Exit button to complete volume configuration.

Enable Persistence on Cluster Volumes

Once you have installed QSnap, use the following procedure to set persistence and configure QSnap on a cluster:

  1. From the Cluster Administrator software, take the GxClusPlugin service resource offline.
  2. Configure additional setting on both physical nodes using the following steps:
    • From the CommCell Browser, navigate to Client Computers.
    • Right-click the <Client>, and then click Properties.
    • Click Advanced and then click Additional Settings tab.
    • Click Add.
    • In the Name box, type ClusterBFMode.

      The Category and Type fields are populated automatically.

    • In the Value field, type 2.
    • Click OK

  3. Configure your volumes:
    • From the \Base directory, launch the QST2 Tool. This executable can be run from either physical node.
    • Activate the block-filter driver on the volume.
    • Enable Persistence.
    • Set the Bitmap Init Value to 0.
    • Specify the volume to keep the bitmap. Ensure the volume you specify here is a shared volume.
  4. From the Cluster Administrator software, bring the GxClusPlugin service resource back online.
  5. Initiate a failover by moving the group to the other physical node.
  6. The cluster volumes you configured on the original node need to be configured on the current node as well. Once configured on both nodes, you will not need to configure them again. Configure your volumes by repeating Steps 1 - 4 above.

QSnap is now configured for your cluster.

Disable Persistence on Cluster Volumes

Use the following procedure to disable persistence on a cluster:

  1. From the Cluster Administrator software, take the GxCVD and GxEvMgrc service resources offline.
  2. Add any additional physical disk resources that you want to protect as dependencies to CVD (the physical disk resource that QSnap was installed on for the virtual node is listed as a dependency by default).
  3. Configure additional setting on both physical nodes using the following steps:
    • From the CommCell Browser, navigate to Client Computers.
    • Right-click the <Client>, and then click Properties.
    • Click Advanced and then click Additional Settings tab.
    • Click Add.
    • In the Name box, type ClusterBFMode.

      The Category and Type fields are populated automatically.

    • In the Value field, type 1.
    • Click OK

  4. Configure your volumes:
    • From the \Base directory, launch the Qsnp2Config tool. This executable can be run from either physical node.
    • Click Configure Volumes, enter or Select the volume for which you want to disable QSnap bitmap persistence.
    • Click Deactivate BF to deactivate the block-filter driver on the volume.
    • Set the Persistence Enabled value to 0.
    • Set the Bitmap Init Value to 0.
    • Set the Bitmap Volume to your desired location for storing the bitmap file. The volume is required to be a local volume.
    • Click Reactivate BF to reactivate the block-filter driver.
    • Repeat this process for all of the shared volumes you would like to protect on with QSnap on your cluster.
  5. From the Cluster Administrator software, bring the GxCVD and GxEvMgrc service resources back online.
  6. Initiate a failover by moving the group to the other physical node.
  7. The cluster volumes you configured on the original node need to be configured on the current node as well. Once configured on both nodes, you will not need to configure them again. Configure your volumes:
    • Click Configure Volumes, enter or Select the volume for which you want to disable QSnap bitmap persistence.
    • Click Deactivate BF to deactivate the block-filter driver on the volume.
    • Set the Persistence Enabled value to 0.
    • Set the Bitmap Init Value to 0.
    • Set the Bitmap Volume to your desired location for storing the bitmap file. The volume is required to be a local volume.
    • Click Reactivate BF to reactivate the block-filter driver.
    • Repeat this process for all of the shared volumes you would like to protect on with QSnap on your cluster.

Persistence is now disabled on your cluster.

Enable and Disable QSnap Block-Filter Driver on Specific Volumes

Through the use of a block-filter driver, the QSnap software creates bitmaps to track the block-level changes to a volume over time. These bitmaps are stored in memory and later written to disk. The bitmaps help ensure that the next data protection operation can be an incremental backup instead of a full backup. Unlike the COW cache, which is created and used only when creating snapshots, bitmaps are always maintained for devices monitored by the block-filter driver.

When the QSnap software is installed, its block-filter is activated for all volumes by default. The block-filter may be active on volumes you do not want it to be active on — as may be the case after upgrading QSnap. You can manually activate/deactivate the QSnap block-filter driver on specific volumes, using:

  • Qsnp2Config Tool
  • QST2 Tool
  • the BFActivateAll additional setting - An alternative method to enable or disable the block filter of all volumes on the client computer:
    1. From the CommCell Browser, navigate to Client Computers.
    2. Right-click the <Client>, and then click Properties.
    3. Click Advanced and then click Additional Settings tab.
    4. Click Add.
    5. In the Name box, type BFActivateAll.

      The Category and Type fields are populated automatically.

    6. In the Value field, type 1.
    7. Click OK.

Bitmaps and Changed Blocks

After the first full backup, you can update the backup incrementally so that only the changed blocks on the source volume are backed up or copied. In order to keep track of the changes, the QSnap program creates a bitmap that records the changed blocks for each source volume.

If the system cannot verify the integrity of a bitmap, it will force the next backup to be a full backup, which may be undesirable in the following situations:

  • moving very large amounts of data
  • moving data across a slow LAN or WAN
  • (for the Quick Recovery® Agent) recreating off-site QR™ recovery volumes

Use the following procedure to manually deactivate the QSnap block-filter driver functionality on specific volumes:

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. To de-activate the block-filter driver on the volumes you do not want to be monitored:
    • Click Configure Volumes, then enter or select the volume for which you want to disable the block-filter driver.
    • Click Deactivate BF.
    • Repeat this process for each volume on which you are disabling the block-filter driver.
    • Click OK to continue.
  3. Click the Exit button to close the Qsnp2Config tool.

Change the Write Inactivity Period (WIP)

Use the following procedure to change the write inactivity period (WIP). Use caution when changing this value. If the default value of 3 seconds is not sufficient (for example, due to slow disk performance), try small, incremental increases in the value (e.g., increase the value to 5 seconds).

This procedure will require a reboot.

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Update Snap Params, then enter the new Write Inactivity before Snap (Seconds) value and click OK to continue.
  3. Click the Exit button to close the Qsnp2Config tool.

Enable SAN Environment

Enabling the SAN Environment allows you to continue incremental operations after a device (SAN-attached disk) has been reconnected. This option is enabled by default. Disabling feature this will force a full QR Volume creation in cases where a disconnected device has been reconnected.

Use the following procedure to enable SAN environment support, allowing you to perform incremental backups after a SAN device has lost connectivity:

  1. From the \Base directory, launch the Qsnp2Config tool.
  2. Click Update BF Params, then change the Enable SAN Environment value to 1 and click OK to continue.
  3. Click the Exit button to close the Qsnp2Config tool.

QST2 Tool for Windows

The QST2 tool is used primarily for testing and troubleshooting the QSnap driver. The tool allows you to directly access and use the QSnap driver through command line calls. The QST2 tool is located in the \Base directory and has both snapshot and bitmap file commands.

  • Some features of this tool should not be used without instruction from a support specialist and have been marked DO NOT USE.
  • This tool provides some options that are better performed using the CommCell Console or Qsnp2Config. If there is another, preferred method to perform a task, it is noted in the description.

Use the following steps to access snapshot commands:

  1. Launch the QST2 tool from the command line by navigating to the \Base directory and entering:

    qst2 x:

    Where x is the drive letter for the volume containing the snapshot(s) with which you intend to work.

  2. Enter 1 to access the snapshot options.
  3. Select one of the following:
    • Get Device Snap Info - measures the amount of data that has been cached on the current snap. Multiply the FSSectorSize by the TotalCachedSectors to calculate the Bytes of data have been cached. This will only return data if a QSnap snapshot already exists on the volume specified when starting the QST2 tool.
    • Activate Snap - creates a snapshot of the current specified volume. Note that you must specify a cache partition using options 8 or 13 before attempting to activate.
    • Deactivate Snap - deactivates an activated snapshot of the current specified volume.
    • Expose Snap as Mount Point - mounts an activated snap to a drive letter.
    • Remove Exposed Snap Mount Point - unmounts a snapshot that you had previously mounted.
    • Test Driver Control Object - DO NOT USE.
    • Test IOCTL to QSnap - DO NOT USE.
    • Freeze Snap - DO NOT USE.
    • Get Cached Extents - DO NOT USE.
    • Get Snap Volume Device ID - displays the Snap Volume Device ID for a snapshot. If you are performing a function that requires the ID, and you do not know the snapshot ID, use this option to get the information.
    • Add NTFS Cache Partition to QSnap Driver - specifies an NTFS volume as the preferred cache volume for snapshots.
  4. When you are finished working with your snapshots, enter 0 to return to the main menu and then enter 0 again to exit the program.

Use the following steps to access bitmap commands:

  1. Launch the QST2 tool from the command line by navigating to the \Base directory and entering:

    qst2 x:

    Where x is the drive letter for the volume containing the bitmaps with which you intend to work.

  2. Enter 2 to access the bitmap options.
  3. Select one of the following:
    • Get info - displays the information that the QSnap driver has regarding bitmaps for your volume.
    • Activate Block Filter - this should be performed from the Qsnp2Config and should only be done during specific configuration procedures or for troubleshooting purposes.
    • Deactivate Block Filter - this should be performed from the Qsnp2Config and should only be done during specific configuration procedures or for troubleshooting purposes.
    • Set Bitmap - DO NOT USE.
    • Clear Bitmap - resets the current bitmap information to zero. In a production environment this will cause the next data protection operations to be a Full Backup. It is not recommended to use this option.
    • Get Bitmap - prints out the bitmap information to a file. The file will show you which areas of the bitmap are dirty (contain blocks with modified information).

      Select 0 for Image Incremental bitmaps, 1 for Image Differential bitmaps, or 2 for QR Incremental update bitmaps. To write the data to a file, type the file name and path, when prompted to Press S to dump bitmap on screen.
    • Get and Merge Bitmap - DO NOT USE.
    • Enable Persistence - this should be done from the Qsnp2Config. See Enable Persistence on a Volume and Enable Persistence on Cluster Volumes for more information.
    • Disable Persistence - this should be done from the Qsnp2Config. See Disable Persistence on Volumes and Disable Persistence on Cluster Volumes for more information.
  4. When you are finished working with your bitmaps, enter 0 to return to the main menu and then enter 0 again to exit the program.

Mount the COW Cache Partition

The QSnap creates a copy-on-write (COW) cache, to which it copies blocks that are being overwritten on the source volume during a snapshot creation. This preserves the original data, ensuring an accurate snapshot for data protection and recovery operations.

The COW cache contains only copies of blocks that have been overwritten. Any new data that is written to free space on a source volume is not cached. It is important to ensure there is enough space for the cached blocks.

When installing the CXBF block filter driver, you will be asked to specify a mount point for the copy-on-write cache. Use the example below to mount the partition. When you have selected an appropriate volume, mount it to the previously specified mount point using a command similar to the following:

mount /dev/cxbf/dsk/c1t1d1s1 /<mount_point>

Where <mount_point> is the mount point you specified during the installation of the CXBF driver.

  • You will be unable to unmount this partition during any job that uses the COW Cache. If you need to change the partition that is mounted to the COW Cache mount point, you must wait for the job(s) to complete.

Configuring a CXBF Device Using Volume Explorer

On a Unix platform, a CXBF device is a volume or partition that is monitored by the CXBF block-filter driver. After installing the software, you must create CXBF devices for the volumes you want to back up.

Consider the following when configuring a CXBF device:

  • CXBF devices should not be configured on Operating System file systems.
  • CXBF devices can only be configured on quiescent file systems (i.e. unmountable or not busy).

Use the following steps to create a CXBF device using Volume Explorer:

  1. From the CommCell Console, navigate to Tools | Control Panel.
  2. Double click Volume Explorer.

    Alternatively, you can access Volume Explorer from the Content tab in Subclient Properties.

  3. From the Hosts pane, select the host connected to the volume you want to configure.
  4. Right-click the desired volume in the Volumes pane, and then select Configure CXBF device.
  5. Click Configure.

Test a CXBF Device

Use this procedure to test a CXBF device to see if the driver has successfully attached.

To test the CXBF device:

  1. Log on to the client computer as root.
  2. Depending on your operating system, type one of the following commands:

    For AIX:

    lsdev | grep cxbf

    For Linux:

     lsmod | grep cxbf

    For Solaris:

     modinfo | grep cxbf

  3. If the CXBF driver was attached successfully the command will return the unique identifier of the driver. For example:

    For AIX:

    cxbf0 Available N/A

    For Linux:

    cxbf 132200 2

    For Solaris:

    236 781f8000 c13d 234 1 cxbf (cxbf 0.1)

  4. In the event that the driver did not attach successfully, do the following:

    For AIX:

    • Execute the rmdev -dl cxbf0 command
    • Execute the mkdev -c cxbf -s lvdd -t cxbf command
    • Run the lsdev | grep cxbf command again to ensure that the driver is attached

    For Linux:

    • Execute the rmmod cxbf command
    • Execute the insmod /lib/modules/2.6.18-92.el5/extra/cxbf.ko command
    • Run the lsmod | grep cxbf command again to ensure that the driver is attached

    For Solaris:

    • Execute the rem_drv cxbf command
    • Execute the add_drv cxbf command
    • Run the modinfo | grep cxbf command again to ensure that the driver is attached

Use a Disk That Has Been Newly Added to a Client

When new disks are added to a client, and have been labeled, verify that they can be seen. (If not, edit the sd.conf file as shown below.) Then, use Volume Explorer to detect the newly added disks and create cxbf devices on all the volumes of the newly added disk(s).

To edit the sd.conf file:

  1. Log on to the client computer as root.
  2. Navigate to the /kernel/drv/ directory.
  3. Edit the file as vi sd.conf. The file will need to be modified if the target is beyond 15 and LUN is greater than 7. The following is an example of the sd.conf file:

    name="sd" class="scsi" target=0 lun=0 to target=15 lun=7

    You will need to add more entries if required by your hardware configuration.

    The maximum range of target is 0-255 and for each target LUN the range is 0-255.

    It is strongly recommended that you do not edit the file unless required.

  4. See Configure a CXBF Devices in Volume Explorer to configure the volume.

Change a Disk Label

When the disk label has changed, for example, after changing sizes of the partitions/slices, the following procedure needs to be followed to see the new CXBF devices with the correct/updated sizes.

To update the CXBF devices:

  1. Unmount, deconfigure, and delete the CXBF devices related to that disk, using Volume Explorer.
  2. Change the disk label.
  3. Detect, configure, and mount the devices using Volume Explorer.

Use a Newly Configured CXBF Device

RAW Devices (for Oracle Volumes Only)

For the Quick Recovery Agent and Image Level iDataAgents, if the Oracle instance has data files residing on a raw partition, soft links need to be re-established after creating the raw CXBF devices.

For example, if an Oracle volume is linked as:  data1.dbf -> dev/rdsk/c1t1d1s1

To create the links:

  1. Shut down the Oracle database.
  2. Remove the link:

    rm data1.dbf

  3. After installing the CXBF driver, re-establish the link:

    ln -s /dev/cxbf/rdsk/c1t1d1s1

  4. Ensure the permissions for the devices are set to the Oracle user and Oracle group:

    chown Oracle:dba /dev/cxbf/rdsk/c1t1d1s1

  5. Start the Oracle database.

File System (for Oracle Volumes Only)

If the selected disk contains an existing file system that is mounted, then the disk will need to be unmounted and mounted on the CXBF device. (All data will be preserved.) For example, if two Oracle volumes were mounted as:

/dev/dsk/c1t1d1s1 /ora_data
/dev/dsk/c2t1d1s1 /ora_logs

To mount them as CXBF devices:

  1. Shut down the Oracle database.
  2. Unmount the volumes:

    umount /ora_data
    umount /ora_logs

  3. Configure the volumes as CXBF devices using Volume Explorer.
  4. After installing the CXBF driver, mount the same volumes as CXBF devices using Volume Explorer:

    mount /dev/cxbf/dsk/c1t1d1s1 /ora_data
    mount /dev/cxbf/dsk/c2t1d1s1 /ora_logs

    After mounting volumes as CXBF devices, do not also mount them as ordinary Solaris devices using the dev/dsk path; this might cause a system panic.

  5. Give ownership of the devices to Oracle:

    chown Oracle:dba /ora_data
    chown Oracle:dba /dev/cxbf/dsk/c1t1d1s1
    chown Oracle:dba /ora_logs
    chown Oracle:dba /dev/cxbf/dsk/c2t1d1s1

  6. Start the Oracle database.

Edit the Mapping File for RAW Devices (for Oracle Volumes Only)

Oracle uses an environment variable called DBCA_RAW_CONFIG, and mapping file that tells the Oracle database application where to create data files, redo files and control files. DBCA_RAW_CONFIG is the variable indicating path of mapping file.

The mapping file must be modified to point to the CXBF devices created for the RAW devices.

To edit the mapping file:

  1. Open the mapping file.
  2. Replace the RAW devices with the appropriate CXBF devices. For example:

    System=/dev/rdsk/c1t0d2s1

    Change to:

    System=/dev/cxbf/rdsk/c1t0d2s1

  3. Ensure the permissions for the devices are set to the Oracle user and Oracle group:

    chown Oracle:dba /dev/cxbf/rdsk/c1t1d1s1

    chmod 600 /dev/cxbf/rdsk/c1t0d2s1

  4. Start the Oracle database.

CVSnap Tool for UNIX

Display All CXBF Devices

You can use the CVSnap Tool to display all CXBF devices using the following steps:

  1. From the command line, type one of the following, depending on your operating system, and press Enter:

    For Solaris:

     /usr/sbin/cvsnap

    For AIX:

    /sbin/cvsnap

    For Linux:

     /sbin/cvsnap

  2. At the cvsnap> prompt, type show (on Solaris) or show_filters (on AIX or Linux) and press Enter.

    Sample output:

    No of bf devices 7
    c1t0d26s0
    c1t0d26s1
    c1t0d26s3
    c1t0d26s4
    c1t0d26s5
    c1t0d26s6
    c1t0d26s7

  3. To exit, at the cvsnap> prompt, type quit and press Enter.

Display All Snapshots

You can use the CVSnap Tool to display all snapshots on the computer using the following steps:

  1. From the command line, type one of the following, depending on your operating system, and press Enter:

    For Solaris:

     /usr/sbin/cvsnap

    For AIX:

    /sbin/cvsnap

    For Linux:

     /sbin/cvsnap

  2. At the cvsnap> prompt, type show_snaps press Enter.
  3. To exit, at the cvsnap> prompt, type quit and press Enter.

Get CXBF Device Information

You can use the CVSnap Tool to obtain CXBF device information using the following steps:

  1. From the command line, type one of the following, depending on your operating system, and press Enter:

    For Solaris:

     /usr/sbin/cvsnap

    For AIX:

    /sbin/cvsnap

    For Linux:

     /sbin/cvsnap

  2. At the cvsnap> prompt, type one of the following, depending on your operating system, and press Enter:

    getinfo device=<deviceID>

    getinfo minor=<minor number for device>

    getinfo bfminor=<bfminor number for device>

  3. To exit, at the cvsnap> prompt, type quit and press Enter.

Stop and Delete a CXBF Device on AIX

You can use the CVSnap Tool to stop and delete a CXBF filter using the following steps:

After you defunc and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required.

  1. From the command line, type the following command and press Enter.

    /sbin/cvsnap

  2. At the cvsnap> prompt, type show_filters and press Enter.

    All the available CXBF filters will be displayed and from this list you can get the filter number which is the number appended with CXBF.

    For example:

    cvsnap>show_filters

    Sample output:

    /dev/cxbf/cxbf1/blk
    /dev/cxbf/cxbf3/blk
    /dev/cxbf/cxbf4/blk

    Here, there are three filters with filter numbers 1,3, and 4.

  3. At the cvsnap> prompt, type stop_filter minor=<filter_minor_number> and press Enter.

    For example:

    stop_filter minor=1

    Sample output:

    Stopping CXBF node over:
    minor=1

  4. At the cvsnap> prompt, type delete_filter_minor=0 and press Enter.
  5. To exit, at the cvsnap> prompt, type quit and press Enter.
  6. Next, the cxbf-bootscript1.rc and cxbf-bootscript2.rc files in /sbin need to be edited. These files are based on CXBF devices present, and are automatically generated every time a new CXBF device is detected. Edit these two files to remove the entries corresponding to the device you just deleted.
  7. Verify that the device you just deleted no longer appears, using the procedure detailed in Display All CXBF Devices.

Stop and Delete a CXBF Device on Linux

You can use the CVSnap Tool to stop and delete a CXBF filter using the following steps:

After you defunc and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required.

  1. From the command line, type the following command and press Enter.

    /sbin/cvsnap

  2. At the cvsnap> prompt, type show_filters and press Enter.

    All the available CXBF filters will be displayed and from this list you can get the filter number which is the number appended with CXBF.

    For example:

    cvsnap>show_filters

    Sample output:

    /dev/cxbf/cxbf0
    /dev/cxbf/cxbf1

    Here, there are two filters with filter numbers 0 and 1.

  3. At the cvsnap> prompt, type stop bfminor=<filter_number> and press Enter.

    For example:

    stop bfminor=0

    Sample output:

    Stopping CXBF node:
    minor=0

  4. At the cvsnap> prompt, type delete bfminor=0 and press Enter.
  5. To exit, at the cvsnap> prompt, type quit and press Enter.
  6. Next, the cxbf-bootscript1.rc and cxbf-bootscript2.rc files in /sbin need to be edited. These files are based on CXBF devices present, and are automatically generated every time a new CXBF device is detected. Edit these two files to remove the entries corresponding to the device you just deleted.
  7. Verify that the device you just deleted no longer appears, using the procedure detailed in Display All CXBF Devices.

Defunc and Delete a CXBF Device on Solaris

You can use the CVSnap Tool to defunc and delete a CXBF filter using the following steps:

After you defunc and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required.

  1. From the command line, type the following command and press Enter.

    /usr/sbin/cvsnap

  2. At the cvsnap> prompt, type defunc device=<deviceID> and press Enter.

    For example:

    defunc device=c1t0d6s0

    Sample output:

    defunc device=c1t0d6s0
    device c1t0d6s0 marked defunct.

  3. At the cvsnap> prompt, type delete device=c1t0d6s0 and press Enter.
  4. To exit, at the cvsnap> prompt, type quit and press Enter.
  5. Next, the cxbf-bootscript1.rc and cxbf-bootscript2.rc files in /usr/sbin need to be edited. These files are based on CXBF devices present, and are automatically generated every time a new CXBF device is detected. Edit these two files to remove the entries corresponding to the device you just deleted.
  6. Verify that the device you just deleted no longer appears, using the procedure detailed in Display All CXBF Devices.

Configuring Number of Snap Retries

By default, the number of snapshot retries is set to 3 for image level backups. You can increase the number of snap retries using the following steps:

  1. From the CommCell Console, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name box, type nSnapRetry.

    The Category and Type fields are populated automatically.

  6. In the Value field, type <Value>.

    For example, 5.

  7. Click OK.

Configuring Extent Size

The Image Level iDataAgent backs up extents on the source drive. The extent size is initially set to 512KB for Windows. For Unix, the default extent size is 2MB (the Unix GUI will display 4096 because 4096 x 512 bytes equals 2MB).

Use the following steps to change the extent size:

  1. From the CommCell Console, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name box, type BackupExtSize.

    The Category and Type fields are populated automatically.

  6. In the Value field, type 1024.
  7. Click OK.

To improve the backup performance further, the extent size can be configured to be larger than 4GB. Use the following steps:

  1. From the CommCell Console, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name box, type BackupExtSizeHigh.

    The Category and Type fields are populated automatically.

  6. In the Value field, type 4194304.
  7. Click OK.

Configuring Multiple Streams for Backups

Multi-Streaming employs multiple data streams per subclient for backup operations. This enables the subclient's contents to be distributed to all the streams, transmitting them in parallel to the storage media. Hence a subclient whose data is secured using three data streams, utilizes more of the available network resources, and can complete in as little as one third the time that the same data would require using a single stream.

Note that, you do not have to enable multi-streaming if you have multiple mount points pointing to the same physical drive.

For Unix, multiple streams are supported for CXBF backups. Follow the steps given below to configure multi-streaming:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Image Level>.
  2. Right-click the <Subclient>, and then click Properties.
  3. In the Number of Data Readers box type or select the number of data streams.
  4. Select the Allow multiple data readers within a drive or mount point checkbox.
  5. Click the Storage Device tab.
  6. In the Storage Policy list, click a storage policy name.
  7. Click OK.

The number of streams configured in the Storage Policy should be equal to, or greater than the specified Number of Data Readers .

Configuring Pre and Post Processing for Backups

Setting Up Pre and Post Processes

You can add and modify Pre/Post processes for a subclient. These are batch files or shell scripts that you can run before or after certain job phases. For example, you can use an echo command to check the level of a backup. Similarly, you can include a case statement within a script to run specific operations based on the level of the backup job.

A Save As Script file can also be run as a pre/post process, if you include the absolute path of the associated input file in the script file.

See Pre and Post Processes - Commands and Arguments for information on additional arguments that the CommServe sends to the Pre and Post processes.

Use the following steps to set up pre/post processes:
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Image Level>.
  2. Right-click the <Subclient>, and then click Properties.
  3. Click the Pre/Post Process tab.
  4. Click the Browse button to select the process you want to set up.
  5. Click OK.

Setting Up Post Processes to Run during Failures

You can add and modify post processes for a subclient. For example, you can use run specific operations in the event of a job failure.

Use the following steps to set up post processes to run during job failures:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Image Level>.
  2. Right-click the <Subclient>, and then click Properties.
  3. Click the Pre/Post Process tab.
  4. Select  the Run Post Scan Process for all attempts check box.
  5. Select the Run Post Backup Process for all attempts check box.
  6. Click OK.

Disabling Raw Device Backups

Raw device backups are enabled by default on AIX clients. However, you can disable raw device backups and allow block device based backups using the following steps:

  1. From the CommCell Console, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name box, type sSnapUseBlkDevice.

    The Category and Type fields are populated automatically.

  6. In the Value field, type Y.
  7. Click OK.

Enabling Optimized Scan for Metadata Collection on AIX Clients

Metadata contains information such as the directory structure and file attributes. Metadata collection at the file level during backups is necessary to perform file level restores. Metadata collection performance can be enhanced using Optimized Scan. When Optimized Scan is used for metadata collection, ACLs will not be available for restore.

Create a CXBF Image Level subclient before you enable Optimized Scan. See Creating a Subclient for CXBF backups.

  1. Ensure that the Optimized Scan database is located on a non Optimized Scan monitored volume and a non CXBF monitored volume.
  2. At the Unix prompt on the client computer, type the command to define the location of the Optimized Scan database after navigating to the /opt/snapprotect/Base location:

    DcClient -edit DB_FOLDER <dbpath>

    The <dbpath> must exist prior to running the command.

  3. Use the following steps to start monitoring the CXBF mount point:
    • From the CommCell Browser, navigate to Client Computers | <Client> | File System | <Backup Set>.
    • Right-click the  <Backup Set>, point to All Tasks and then click New Subclient.
    • In the Subclient Name box, type a name.
    • Click the Storage Device tab.
    • In the Storage Policy list, click a storage policy name.
    • Click the Content tab.
    • Click Add.
    • Select the <Mount Path> of the CXBF mount point you want to add to the monitoring list and click Add.
    • Click Close.
    • Right-click the <Subclient>, and then click Properties.
    • On the Subclient Properties of <Subclient> dialog box, click the Advanced Options tab.
    • Click Optimized Scan.
    • Click OK.

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. On the Client Computer Properties for <Client> dialog box, click Advanced.
  4. On the Advanced Client Properties dialog box, click the Additional Settings tab.
  5. Click Add.
  6. On the Add Additional Settings on Unix Client dialog box, perform the following:
    1. In the Name box, type sUseDCForMetaData. The Category and Type details will be automatically populated.

      Alternatively, you can click Lookup and search for the additional setting using the Find box.

  7. Click OK.

Deconfiguring a CXBF Device from Using Optimized Scan

Follow these steps to deconfigure a CXBF device from using Optimized Scan.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | <Backup Set>.
  2. Right-click the <Subclient> on which Optimized Scan is enabled, and then select Properties.
  3. On the Subclient Properties of <Subclient> dialog box, click the Advanced Options tab.
  4. Click Recursive Scan.
  5. Click OK.

Uninstalling the CXBF Driver If Optimized Scan Is Enabled on a CXBF Volume

Follow these steps to disable Optimized Scan on all the subclients that have CXBF configured volumes as content.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | <Backup Set>.
  2. Right-click the <Subclient> on which Optimized Scan is enabled,  and then select Properties.
  3. On the Subclient Properties of <Subclient> dialog box, click the Advanced Options tab.
  4. Click Recursive Scan.
  5. Click OK.

    Prior to uninstalling the CXBF driver make sure that Optimized Scan monitoring is stopped on all the CXBF volumes.

Modifying an Agent or Subclient

The following table describes the properties that can configured from the agent, backup set and subclient levels.

Option Description Related Topics
Change Storage Policies You can modify the storage policies in any of the following situations:
  • To include a different media for the backup operation.
  • To use a storage policy with a different retention criteria.

You can change the storage policies from the subclient level.

  1. From the CommCell Browser, right-click the <Subclient>.
  2. Click Properties.
  3. Click Storage Device.
  4. Select the Storage policy from the drop-down menu.
  5. Click OK.
Refer to Storage Policies.
Data Transfer Options You can efficiently configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following:
  • Enable or disable Data Compression either on the client or the MediaAgent.
  • Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

You can configure the data transfer options.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Image Level.
  2. Right-click the <Subclient>, and then click Properties.
  1. Click the Storage Device tab.
  2. Click the Data Transfer Option tab.
  3. Choose the appropriate software compression option for this subclient.
  4. Select the Throttle Network Bandwidth check box, and set the required bandwidth.
  5. Click OK.
Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | Image Level.
  2. Right-click the <Subclient>, and then click Properties.
  1. Click the Storage Device tab.
  2. In the Storage Policy list, click a storage policy name.
  3. Click Data Paths.
 
Configure Activity Control You can enable backup and restore operations from the agent and subclient level. However, you can enable restore operations only from the agent level.
  1. From the CommCell Browser, navigate to Client Computers | <Client>
  2. Right-click the <Client> or <Subclient> in the right pane, and then click Properties.
  3. Click the Activity Control tab and select or clear option(s) as desired.
  4. Click OK.
Refer to Activity Control.
Enable and Disable Data Encryption When you configure encryption at the client level, it is configured automatically for all the subclients associated with all the agents installed on that client. If you want to disable or change the encryption at the subclient level, follow the steps given below:
  1. From the CommCell browser, right-click the <Subclient>.
  2. Click Properties.
  3. Click Encryption.
  4. Select the desired encryption.
  5. Click OK.
Refer to Data Encryption.
View Software Version and Installed Updates The Version tab, at the Agent level displays the software version and post-release service packs and updates installed for the component.
  1. From the CommCell Browser, right-click Image Level.
  2. Click Properties.
  3. Click Version.
  4. Click OK.
 
CommCell Configuration Report The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, subclients, and storage policies within the CommCell based on the selected filter criteria.
  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Configuration.

    The Report Selection dialog box appears.

  3. Click Run.
Refer to CommCell Configuration.

Deleting an Agent or a Subclient

The following sections describe the steps involved in deleting an agent or a subclient.

When you delete a subclient, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes.

Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.

Deleting an Agent

You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

  • You cannot delete an agent while operations for that agent are running.
  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click the <Agent>, and then click Delete.
  3. A confirmation message is displayed with the following message:

    This operation will permanently delete the data backed up from this level and it cannot be restored.

  4. Click OK to continue with the deletion operation or click No to abort the deletion.

Deleting a Subclient

Consider the following before deleting a subclient:

  • You cannot delete a default subclient.
  • Schedules associated with the subclient are also automatically deleted.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>.
  2. Right-click the <Subclient> that you want to delete, and then click Delete.
  3. A confirmation message is displayed, asking if you want to delete the subclient.

    Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.