A Generic Enabler for a specific hardware device is implemented through scripts
for snapping, unsnapping, and recovering. You provide these scripts based on your
snap type and your environment. (The template scripts for
Hitachi ShadowImage and
HP EVA are provided for reference
purposes.) The following sections describe the Recovery Director configuration procedure
for these two snap environments.
"I have a Hitachi HDS subsystem as my storage array and ShadowImage
or TrueCopy as the snapshot engine. I know the Quick Recovery Agent does not have
an integrated enabler for HDS. How can I integrate the QR Agent’s replication and
backup solution with the Hitachi system?"
When implementing Hitachi HDS through the Generic Enabler feature, two scenarios
must be considered:
Remote Scenario: The hardware snapshot will be created and mounted
on a remote host, and backed up from that remote host. The mounted snapshot
will also be recorded as a QR volume. In this scenario, recovery is accomplished
either by using the QR Copyback feature or by calling the recovery script that
launches the HDS copyback command.
Local Scenario: The hardware snapshot will be created and mounted
on the primary host itself. The mounted snapshot will be recorded as a QR volume.
In this scenario, QR quick recovery is available.
In the following implementation example, we describe the operation steps of the
Remote Scenario.
Three scripts should be created for the remote scenario: snap, unsnap,
and copyback. (If it were a local scenario, you would create a recovery
script rather than a copyback script.)
The snap script launches the pair-create process to make the snap
pair and populate the CommServe database to create the QR volume entry.
The unsnap script deletes the pair.
The copyback script launches the reverse pair-create process to
restore data from SVOL to PVOL. (The recovery script would unmount the
PVOLs and SVOLs and swap the drive letters between PVOL and SVOL.)
3.
Create a Generic Enabler QR Policy.
In the QR Policy
screen, select Generic snapshot as the Snapshot Engine Type.
Note
QR Volume Creation is automatically disabled (grayed out) when you
choose Generic snapshot.
4.
Create a Workflow using the Workflow Wizard.
Select QR Copy and ProxyHost File System Backup (or
Image Level ProxyHost Backup) as the Workflow operations.
Select Generic snapshot as the Snap Engine.
Specify the source volume (PVOL) and the destination volume (SVOL).
5.
In the next Workflow Wizard screen, all existing Generic-Enabler-based
QR Policies will be displayed.
Select the correct one and continue.
6.
In the QR Agent Subclient Properties screen, a new Generic Snap Scripts
tab will be enabled. This tab is only enabled when a Generic-Enabler-based
QR Policy is associated.
Specify the snap script in Create Script Pathname.
Specify the unsnap script in Delete Script Pathname.
Specify the copyback script in Recovery Script Pathname.
Select an Execution Host -- where these scripts are located
and executed.
7.
Complete the rest of the Workflow configuration.
8.
During QR volume creation, the snap script is launched by the Generic
Enabler to create the hardware snapshots, mount the snapshots, and update
the CommServe database as if the snapshots were created by the QR Copy Manager.
If any applications reside on the PVOLs, you can include the application
quiesce/unquiesce operations as part of the snap script.
9.
To recover the data:
Because we mounted the SVOLs (Business Continuance Volumes (BCVs))
on a remote machine (remote scenario), the data on the SVOLs (BCVs)
can be copied back to the PVOLs (source volumes) through either the
QR Agent’s built-in
Copyback
feature (LAN-based copy manager) or through the hardware-based recovery.
(The copyback script -- see
Template Scripts for Hitachi
HDS -- should have been specified in “Recovery Script Pathname.”).
Hardware-based recovery is recommended because it is faster and it is
LAN-free.
Here are two other recovery possibilities:
If the SVOLs (BCVs) are mounted on the same machine (local scenario),
Quick Recovery can be used. In this case the recovery script (see
Template Scripts for Hitachi
HDS) should have been specified on the Recovery Script Pathname.
Recover from the point-in-time backup. Since each version of the
snapshot has been backed up, they can be restored to anywhere, including
the source volume(s).
"I have HP StorageWorks as my storage array and Business Copy as the snapshot
engine. I know the Quick Recovery Agent does not have an integrated enabler for
the HP EVA. How can I integrate the QR Agent’s replication and backup solution with
the HP system?"
The configuration procedures for HP EVA implementation with Recovery Director
is almost the same as that of the
Hitachi HDS. (See
Template Scripts for HP EVA.)
When implementing HP EVA Business Copy through the Generic Enabler, the
QR Copyback feature will not work with the Business Copy snapshot because
the snapshot always "locks" the source volume.
The HP EVA does not have reserve restore functionality.
The system allows you to create a QR policy in the CommCell Console from the QR
Policies level.
To
create a QR policy:
From the CommCell Browser, right-click the QR Policies icon, and
then click Create New QR Policy from the short-cut
menu.
Type the policy name (Up to 32 characters).
Select the Snapshot Engine Type from the dropdown menu.
If you are creating snapshot scripts using the Generic Enabler feature, select
Generic snapshot as your Snapshot Engine Type.
Depending on the Snapshot Engine you select, some
options may not be available for configuration.
Select the Retention Policy by checking Infinite (default), or by entering
the number of hours/days/weeks.
Select the Enable QR Volume Creation check box to activate the Copy
Manager and Scratch Pool menus.
This option is automatically disabled if you selected
Generic snapshot as your Snapshot Engine Type in Step 3.
Select the Copy Manager from the list of available Copy Managers
that currently exist for this QR Volume.
(Refer to
LAN Copy Manager.)
Select the Scratch Pool from the list of available scratch pools
that currently exist for this QR Volume.
If this QR Policy will be used to create
Recovery Points,
select Enable Recovery Points, and specify the maximum number of
Recovery Points that will be retained, up to a maximum of 32.
When you select Enable Recovery Points, you are prompted to
enter a location for the cache partition for the snapshots of the QR
Volume. This location cannot be on the QR Volume.
When you are satisfied with the QR Policy's configuration, click
OK. The new QR Policy appears in the CommCell Browser.
Do not configure the content of a subclient while the parent node or any
sibling subclient has a data protection or archive operation currently running
on it.
Exchange Mailbox iDataAgents
and Exchange Mailbox/Public Folder Archiver Agents: If you change the contents of the default
backup set or archive set then the auto-discover feature will
be disabled. If you disable the auto-discovery feature, newly created mailboxes
will not be backed up/archived unless they are manually discovered and assigned
to a subclient.
NAS NDMP iDataAgents: You must
ensure there is no overlap in content between all subclients. Overlap in subclient
content will result in loss of data. An existing subclient's contents are not
automatically changed when another subclient is added with overlapping contents.
SharePoint Server iDataAgent:
The Site Content Database, the Site Collection Database, the Site Database,
and the Site Index for the virtual server must all be assigned to the same subclient.
QR Agent: Follow these guidelines when adding a volume to a QR Agent subclient:
The volume must correspond to a physical disk or RAID array.
A volume created by volume management software other than VxVM is not
valid subclient content.
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.
We recommend that you do not re-configure the content of a default subclient because this would disable its capability to serve as "catch-all" entity for client data.
As a result, the likelihood that some data will not get backed up or scanned for
archiving would increase.
From the CommCell Browser, right-click the subclient for which you want
to configure content, click All Tasks (if applicable) and then click
Properties.
Follow the procedure below that is applicable for your agent:
For File System, Active Directory, File Archiver,
Exchange Public Folder iDataAgents, NDS,
and SharePoint Server
iDataAgents click the
Subclient Properties
(Content) tab and configure content for the subclient as described below
for your agent:
For File System, Active Directory, File Archiver,
NDS, and SharePoint Server iDataAgents:
Type the full path of the data that you want to include as subclient
content in the Enter New Content field, then click Add.
Optionally, click Browse to enter the content. When browsing content while configuring SharePoint subclients,
you can add content via multiple selections with the CTRL or SHIFT
keys. For Windows, when
specifying a UNC Path, click As User, and enter the user account
information for the domain user with permissions for that path. For
NetWare/DNS, see the Notes section below for content
path examples. For Unix File Systems, you can enter the mount point
of an NFS-mounted file system, see the Notes section
below for examples.
For Exchange Public Folder iDataAgents:
Click Browse, select folders to include as content, then click
Add.
For the Unix File System iDataAgents,
to facilitate the management of resource fork data in Apple
double-encoded Macintosh files, click EnableApple Double Support.
For the Unix File System iDataAgents,
to view the actual data path for any symbolic link in the subclient content, click
Expand symbolic links of subclient content and then click
Discover.
For NAS NDMP iDataAgents,
configure the Backup Content Path field(s) as described below,
then click Add:
Click the drop-down list arrow to display the root volumes on the file server. To change the
root volume, click one in the list. If you want to refine the content path
further, use the space to the right of (or below) the root volume list to enter
additional path information. Note the following:
For NetApp, the root volume is the mount path of each volume.
Example: for volume FS1 the root volume will
be /vol/FS1.
For EMC Celerra, the root volume is the mount point created for a
volume.
Example: for volume FS1 with mount point
/FS1 the root volume will be
/FS1.
For Hitachi, no root volumes are shown in the drop down list. Type the
full path of the root volume.
Example: for volume FS1 with mount point
/mnt/FS1 the root volume will be
/mnt/FS1.
For BlueArc, the root volume is a combination of a descriptor of the
path and the volume name.
Example: for volume FS1 with a mount point
of / the root volume will be
/__VOLUME__/FS1.
Optionally, for NetApp NAS NDMP, click Browse
to enter the content.
For DB2, DB2 DPF, Exchange Database, Novell GroupWise, SharePoint Server,
SQL Server Database, Sybase, and MySQL iDataAgents,
click the Subclient
Properties (Content) tab and configure content for the subclient as
described below for your agent:
For the DB2 iDataAgent,
specify whether you want to include the entire database or a subset
of this data as content for the subclient. For the DB2 DPF
iDataAgent, specify whether you want to include all the
affected database partitions or a subset
of this data as content for the subclient.
For Exchange and GroupWise iDataAgents:
Click Configure. From the
Add/Modify
Subclients dialog box click the subclient entry for the database
element/Storage Group that you want to add to the new subclient and
select the name of the destination subclient from the list that appears.
Alternatively, you can select and assign a range of databases/storage
groups using the Change all selected databases/storage groups to
list. Note that you must have at least one database element/Storage
Group assigned to this subclient in order to save the configuration.
A database/Storage Group that is not configured for a subclient does
not appear in the list. This can be the case if the subclient containing
the database/Storage Group was deleted. If this happens, click Discover
to display all databases/Storage Groups.
For the Informix iDataAgent,
click the Subclient
Properties (Content) tab and define the contents of the subclient. Specifically,
establish the backup mode for the data to be backed up, set the backup level,
and decide whether to back up the emergency boot file and/or the ONCONFIG
file.
For the Oracle, SAP for Oracle, or Oracle RAC iDataAgent,
click the Subclient
Properties (Content) tab and define the contents of the subclient. To
configure this subclient for specialized types of backups, follow the appropriate
procedure below:
For SAN iDataAgents, click
the Subclient
Properties (Content) tab and configure content for the subclient as
described below for your agent:
Image Level on Unix
iDataAgent: Click Add.
From the
Add Content Path
dialog
box, select the volume(s) that you want to back up (use CTRL + click
to select multiple volumes). Click OK. The
selected volumes are added to the Contents of subclient list.
These volumes are automatically configured to be CXBF devices.
Alternatively, use
Volume
Explorer per specific scenarios to configure CXBF devices.
To
configure an unmounted block device or raw device as content, first
use
Volume
Explorer to configure the device as a CXBF device. Then select
the configured CXBF device as subclient content. You can ignore the
warning that is displayed.
Image Level and Image Level ProxyHost on Windows
iDataAgents: Click Add.
Then in the Add Content dialog box, type the full path of the
volume or mount point that you want to include as subclient content,
then click Add. Optionally, click Browse to select the
content. Click OK. The volume or mount point is added to the
Contents of subclient list. Add additional content by repeating
this step.
ProxyHost iDataAgent:
Select a backup host from the Backup Host list. This is the computer
to which the BCV is connected. Click Add. In the Content
field of the
Add/Edit Content for Subclient dialog box, type the primary host
path of the content that you want to back up, or click Browse
to find and select this data. In the Backup Host BCV Path field
of the
Add/Edit Content for Subclient dialog box, type the path through
which the backup host accesses this data on the BCV, or click Browse
to find and select this path. Click OK. The primary host data
path and corresponding backup host BCV path are added as a single entry
in the Contents of subclient list. To add additional entries,
repeat these steps. Refer to Notes
below for more information.
Click Add Volume. From the
Adding
Volume dialog box, select volume(s) that you want to add to the
subclient content (use CTRL + click to select multiple volumes). You can add/edit
additional advanced options for the selected volume by select
Advanced on the
Adding
Volume dialog box. Click OK.
Click Add
App to select an application and associated volumes. Click OK.
Any instances you intend to protect and recover with the QR Agent
must be configured in the QR Agent properties
Authentication
tab. They will not appear in the
Add App
dialog box if they are not configured. Only volumes containing datafiles
and archive log files will be detected by Add App. Volumes containing
control files and redo log files will not be detected.
For a clustered Exchange Server, if you are not using VSS to perform
an online quiesce, sufficient permissions are required in order to be able to
perform an offline quiesce; in such cases, ensure that the User Name
specified has Exchange Administrator rights.
Content examples for NetWare are OU=prospects.O=engineering.[Root],
(for NDS content), and SYS:\public (for File System content).
Content examples for adding an NFS-mounted file system to subclient content
of a Unix File System iDataAgent:
/mountpointA to include the entire file system at mountpointA
/mountpointA/projects for only the projects directory
within the file system at mountpointA.
Informix subclients include one or more dbspaces. As databases are added
to the dbspaces, the subclients are updated automatically.
Exchange Mailbox iDataAgents
and Exchange Mailbox/Public Folder Archiver Agents: Initially, all unconfigured mailboxes
are assigned to the default subclient. You can create a new subclient and reassign
mailboxes to this new subclient (within the same backup set/archive set).
Once assigned, the mailboxes become part of the content of the new subclient.
SharePoint Server iDataAgent:
Initially, all unconfigured data types are assigned to the default subclient.
You can create a new subclient and reassign data types to this new subclient.
Once assigned, they become part of the content of the new subclient.
ProxyHost
iDataAgent: The primary host data path is backed up by the
subclient and is the path through which the backup host accesses this data on
the BCV. A primary host path and its corresponding backup host path are listed
in the following format:
<primary_host_path> --> <backup_host_path>
For example, assume that you want to back up the D:\data directory
from your primary host and D:\ is mirrored by a BCV, which is mapped
to the backup host as F:\. Consequently, the path to this data on the
backup host is F:\data. When you add this directory to a subclient, it
is listed in the Contents of subclient pane as D:\data --> F:\data.
The primary host path in the Content field is
used for browse and restore purposes. However, it is the data in the
Backup Host BCV Path which is actually backed up. If these two
paths do not accurately correspond, the path that appears when data
is browsed for restore does not accurately reflect the data that will
be restored. In the example given above, assume that D:\data
is entered in the Content field, while F:\data1 is accidentally
entered in the Backup Host BCV Path. If you browse and select
D:\data to be restored, it is actually D:\data1 that is
restored. (Remember, F:\Data1 is the path on the backup host
that corresponds to D:\data1 on the primary host.)
Do not create a subclient while the parent node or any sibling subclient
has a data protection or archive operation currently running on it.
In cases where a new subclient is created with the same name as a deleted
subclient, the system will append a Unix time stamp to the deleted subclient's
name in data protection job history reports and views to distinguish the two
subclients. For example, subclientname_1104257351.
Informix iDataAgents: If you
will be using the Informix ONBAR utility to create backup and restore scripts,
you need not create subclients. Otherwise, if you will be using the CommCell
Console to back up and restore Informix database objects (subsets/dbspaces),
then you will need to create a subclient.
ProxyHost
iDataAgents: If you are using a BCV, you must prepare a batch
file or a shell script file on the backup host containing commands to synchronize
and split the BCV. The Resource Pack includes information on configurations
for these batch files or shell scripts, as well as examples that apply to specific
applications and hardware (e.g., Exchange databases in an EMC Symmetrix environment).
See Resource
Pack for more information on the Resource Pack.
The ProxyHost
iDataAgent also requires
that you set permissions for the batch/shell script file on the backup host.
SQL Server Database iDataAgents:
When running on Windows Server 2003 and VSS is enabled, the New Subclient
command is not available.
PostgreSQL
iDataAgents: Once you configure the PostgreSQL instance, the
system automatically generates the default backup sets and default
subclients. However, you can use the CommCell Console to create user-defined
subclients for dump backup sets to distribute some of the database content.
You cannot create user-defined subclients for FS backup sets.
From the CommCell Browser, right-click the node (agent/backup set/archive
set/instance) for which you want to create a new subclient, click All Tasks
(if applicable), and then simply click New Subclient for most agents.
For the SQL Server iDataAgent,
expand New Subclient and click either Database to include
individual databases or File/File Group to include database
elements.
Click the General
tab or General
(Quick Recovery Agent) tab of the Subclient Properties dialog box and type the name (up to 32
characters) of the subclient that you want to create.
For supported agents identified in
Support Information -
Snapshot Engines, you can select a
QSnap option to snap data and
then perform a data protection operation on the data.
For Image Level on Unix and Image Level ProxyHost on Unix, use the
Incremental Support Using field to configure either a CXBF
subclient or a checksum subclient and to enable incremental support for
either subclient type.
For QR Agents, you must also select a QR Policy from the QR Policy
list.
Select other options from the General tab as appropriate for the agent.
Click the Content or Databases tab of the Subclient Properties
dialog box and Configure Subclient Content
as appropriate for your agent.
For all agents (except QR), click the
Storage Device (Data
Storage Policy) tab of the Subclient Properties dialog box, then select
a data storage policy to associate with this subclient from the storage policy
list.
For the DB2 and DB2 DPF iDataAgents, you
can also change the number of data backup streams. For the DB2 DPF
iDataAgent, the default
stream threshold should be equal to the total number of database
partitions for the subclient.
For SQL Server iDataAgents,
you can also click the
Storage Device (Log
Storage Policy) tab of the Subclient Properties dialog box, then select
a log storage policy to associate with this subclient from the storage policy
list and select the number of backup streams for transaction log backup
jobs.
For 1-Touch for Unix, it is strongly recommended that the storage
policy that you select for the subclient configured for 1-Touch use a
MediaAgent on a different computer. If you do this, and if the system
crashes, the media will not have to be exported to another MediaAgent in
order to recover the system.
For Migration Archiver Agents, click the Archiving Rules or
Rules tab of the Subclient Properties dialog box and configure archiving rules
as appropriate for your agent. In order to perform rules-based migration
archiving operations, the Disable All Rules checkbox must be cleared.
If the File Archiver for Windows supports Data Classification, several
filter-like configuration fields are defined as archiving rules and are
available from the
Subclient
Properties (Rules) tab. If you want to define
content and archiving rules based on file attributes other than volumes,
size, and modified time (i.e., if you want to customize your rules), click
the Advanced
tab and configure as appropriate. Also, stub management options can be
configured from the
Stub Rule
tab. See
Configure
Archiving Rules - File Archiver Agents for
step-by-step instructions.
For ProxyHost and Image Level ProxyHost iDataAgents, click the
Pre/Post Process
tab of the Subclient Properties dialog box. In the PreScan field, type
the path to the batch file/shell script file that contains those commands that
are to run before each backup of the subclient, or click Browse to
locate and select this file. For ProxyHost and Image Level ProxyHost, the
file must reside on the backup host or primary host.
View or change the user group security associations for this
subclient from the
Security tab.
Determine location from where archive logs will be backed up or
deleted from the
Log
Destinations tab.
Click OK to save the subclient configuration. For QR Agents, this
procedure is now complete. For all other agents, continue on to the next step.
The
Backup Schedule dialog box advises you to schedule data protection operations for your
new subclient. It is recommended you elect to set a schedule now. You can also
associate this subclient with an All Agent Types schedule policy (which is automatically
created by the system, or can be a user defined Data Protection schedule policy).
If you have already associated a schedule policy at a previous level (Backup
Set/Instance, Agent, Client, or Client Computer Group) the schedules defined
in the Schedule Policy will be automatically applied to the new subclient.
See Schedule Policy
for more information.
If you want to associate this subclient with an All Agent Types schedule
policy, click Associate with Generic Schedule Policy, and then select
that schedule policy from the drop-down list box. Click OK.
If you want to associate this subclient with a specific schedule
policy, click Associate to schedule policy, and then select the
schedule policy from the drop-down list box. Click OK.
If you have selected to define a schedule for this subclient:
Click Schedule.
From the Backup/Archive
Options dialog box, select the type of data protection operation
that you want to schedule.
If you want to set Advanced Backup/Archive Options, click
Advanced.
After selecting the data protection type and any advanced options,
click OK. The Schedule Details dialog box appears.
From the
Schedule Details
tab, select the scheduling options that you want to apply, then click
OK.
If you don't want to create a data protection schedule at this time,
click Do Not Schedule, and then click OK.
This task is now complete.
Copy Back a QR Volume
To
copy back a QR Volume:
From the CommCell Browser, right-click the QR Agent whose volumes
(including Recovery Points and snapshots) you want to browse,
click All Tasks, and
then click Browse from the short-cut menu.
From the Browse QR
Volumes window,
right-click the
volume (or Recovery Point or snapshot) that you want to copy back, and
then click Copyback to open the
Select Volumes for Copyback dialog box. (If
you want to copy back multiple QR Volumes, highlight all of the volumes you
want to copy back by control-clicking the QR Volumes.)
From the Select
Volumes for Copyback
dialog box, assign a destination volume to each QR Volume you want to copy back.
The destination volume must be larger than the QR Volume.
To assign a destination volume, click on the QR Volume, and then click the
Set Destination button to open the
Select
Destination for Copyback
dialog box.
From the list of volumes in the
Select Destination for Copyback dialog box, select the volume that is to be the
copyback destination. (You can see a list of volumes on a different host by
selecting a different computer in the dropdown Host: list.) Click the
volume you want as the copyback destination and click Select.
Repeat steps 4 and 5 for any QR Volumes that do not have a destination
volume for copyback in the
Select
Destination for Copyback dialog box.
Ensure that all volumes you want to copy back are checked in the Selectcolumn.
Click OK to copy back the volumes. The system displays a progress
bar and copies back the volumes. You can track the progress of the recover
operation from the Job Controller window.
To
create a QR policy: