The following table shows subclient creation and configuration details
specific to
the Quick Recovery Agent.
Agent
Type of Data
Default Subclient created during install of the Agent
Supports Default Subclient
Supports User Defined Subclient
Contents of the default subclient when user-defined subclient is present
Other Types of subclients supported by the Agent
Notes
QR Agent
volume level data
No
No
Yes
N/A
None
None
There are several reasons to distribute the storage content across multiple subclients:
To ensure that all volumes in the subclient are snapped and copied at the
same point-in-time. This is important to preserve the consistency of
application objects that may span volumes (e.g., SQL Databases or Exchange
Storage Groups).
To schedule subclient operations (e.g. QR Volume Creation/Update) at
different times.
To run jobs on multiple subclients in parallel.
To associate subclients with different QR Policies.
For administrative convenience.
Note that you cannot run multiple, concurrent jobs on the same subclient.
Distribute the content to multiple subclients to achieve greater parallelism.
QR Agent subclients may have overlapping content. In this scenario, the user creates a
QR Volume of the source data at an early point-in-time to one destination
volume, while another QR Volume is incrementally updated to a second destination
volume. Each of these operations is managed through its own subclient configured
with the source volume as content.
When subclients have the same source volume as content, only one subclient is
allowed to create incremental updates. Other subclients must select the
Disable
incremental update of QR Volumes option during subclient creation.
When subclients have overlapping content, they must use the same
snapshot engine. If the QR policies associated with the subclients are
configured to use different snap engines, they must be reconfigured to use the
same snap engine.
Once installed, the agent is configured and is therefore able to manage the
data or volumes on the client computer. However, you can change certain aspects
of the subclient configuration to manage the data in the
manner that best suits your needs.
You can view or change the
subclient configuration from the Subclient Properties dialog
box. The following information can be configured.
You can enable or disable all operations for this CommCell object and all
objects below it. For more information, see
Activity Control.
Content/Databases
You can define the content of the
subclient. Most agents include a configure button that displays a dialog where
you can add or modify the data included as subclient content. For step-by-step
instructions, see
Configure Subclient Content.
Overlapping Subclient Content
To configure subclients for overlapping content, select the Disable Incremental update of QR Volumes field. For more information, see
Overlapping Content.
Pre/Post Processes
You can add, modify or view Pre/Post
processes for the subclient. These are batch files or shell scripts that you can
run before or after certain job phases. For more information, see
Pre/Post Processes.
QR Policy Association
You can associate a QR Policy to the subclient for QR volume creation operations. For more information, see
QR Policies.
Software Compression
You can specify whether software compression is enabled or disabled for the subclient when the selected QR Policy is configured to use a LAN copy manager. For more information, see
Data Compression.
You can rename a subclient. For step-by-step instructions, see
Rename a Subclient.
Generic Snap Scripts
This tab is enabled if you had chosen Generic snapshot as your Snapshot
Engine Type when you created the QR Policy for the subclient. In this tab, specify the path names for the snap, unsnap, and recovery (or copyback) scripts,
and select the host for the scripts.
User Accounts
You can define an account with permissions to execute Pre/Post commands for
the agent's archive, backup, or volume creation jobs.
See Quick Recovery Agents:Other User Accounts in User Accounts and Passwords for more
information.
If you add content to a subclient that has already been scheduled and has
been performing QR Volume creation and/or updates, the new content will not
be included in the current schedule(s). Delete the schedule and create a new
schedule to ensure that the new contents are included.
If a subclient contains multiple volumes, the volumes will be snapped
and copied sequentially; however, if you have sufficient hardware resources
for simultaneous copies, you can schedule multiple subclients to be copied
at the same time. Therefore, in some cases, it may be possible to accelerate your QR
Volume creation by splitting a single subclient containing multiple volumes
into smaller subclients containing a single volume. Note that application
volumes should never be split into multiple subclients; use caution when
configuring your subclients for optimal performance.
The volume must correspond to a physical disk or RAID array.
Subclients may have overlapping content; however, if two or more subclients overlap, they all must use the same snapshot engine. If the QR policies associated with the subclients are configured to use different snap engines, they must be reconfigured to use the same snap engine in this scenario.
If you are creating a subclient that will use Generic Enabler snapshot
scripts, see Generic
Enablers.
You cannot modify subclient content if an incremental backup
schedule exists. Modifying subclient content includes adding or deleting a
volume from the subclient or changing the subclient's QR policy. These tasks
are not allowed if an incremental backup is scheduled or active.
SQL volumes will not be added to subclient contents if any databases are
in the suspect or loading state, in which case they may not be
discovered by the Quick Recovery Agent. Use the SQL Enterprise Manager to change the
mode of the database(s).
QR does not support data protection for applications and application
data residing on the C: drive.
If you are creating a subclient that will use a QR™ Policy with QSnap as the
snapshot enabler and Recovery Points enabled, you must specify a cache volume
(unless a cache volume had been specified in Client Properties/Advanced). The
cache volume specified during Quick Recovery® Agent subclient creation will be used as the cache
volume for all snapshots (source and destination) and for all Agents for that
particular machine.
When configuring a subclient to contain a slice 0 volume, the
destination volume must also be a slice 0 volume. To specify the slice 0
volume to be used as the destination volume, manually select the destination
volume in the QR
Volume Creation Advanced Options dialog box.
If the slice 0 partition is empty, and if the disk is allocated space from
slice 1 onwards, then slice 1 will be considered as slice 0 by the agent.
Therefore, from whatever slice partition you start to allocate space on the disk,
that particular slice will be considered as slice 0.
A volume created by volume management software other than VxVM is not valid
subclient content.