Mount status of secondary volumes, P9000 raid manager configuration definition files, Multi-target or cascade configurations – HP XP Racks User Manual

Page 374: Cluster configurations (sql server), Recovery model (sql server), Copy groups and applications, Copy groups and backup catalogs

Advertising
background image

Data files to be stored on a particular disk drive must belong to the same instance. Data files from
different instances must not be stored on the same disk drive.

Mount status of secondary volumes

Unmount all secondary volumes before performing a backup or restore to a database server. Failing
to do so may cause unpredictable results.

P9000 RAID Manager configuration definition files

For replica management, the configuration definition (HORCM) files of a linked P9000 RAID Manager
instance must be located in the Windows directory (

%windir%

).

Multi-target or cascade configurations

If a volume is used to configure more than one copy pair (for multi-target or cascade configurations),
the configurations for the volume need to be defined using the same instance number.

Cluster configurations (SQL Server)

The following considerations apply to cluster configurations:

If a database server is in a cluster configuration, specify a shared disk for the following:
• VDI metafile directory
• UNDO file directory

Add the shared disk indicated above to the cluster group defining the instance.

To create both Exchange and SQL Server cluster configurations on the same physical node, the
host IDs, application types, and virtual hosts must be specified correctly. Even if SQL Server inform-
ation is incorrectly specified for Exchange, or Exchange information is incorrectly specified for
SQL Server, an error might not be displayed. If the configuration is incorrect and the system con-
tinues to be used, abnormal operations may result.

Recovery model (SQL Server)

Replication Manager only supports the database recovery models "Full" or "Bulk-logged."

Copy groups and applications

A copy group should only contain copy pairs associated with a single application. If a copy group
contains copy pairs associated with multiple applications, backup and restoration operations may
have unpredictable results.

Copy groups and backup catalogs

The backup information in the backup catalog is managed based on using the copy group as a key.
Depending on the backup method, you might not be able to perform a restore, even though the backup
data exists on the secondary volume.The following is an example of two objects (databases, storage
groups, or information stores) stored in separate volumes:

Database A (copy group:

vg01,obj01

)

Database B (copy group:

vg01,obj01

)

Use the following backup method to back up the databases:

1.

Back up database A and database B concurrently. The replica

2010/8/31 07:14:00

is created.

Managing application replicas

374

Advertising