HP P9000 Replication Manager Software 7.4.1-00 Release Notes (TB584-96068, April 2013)

XP P9000 RAID Manager installation path for database servers and backup servers
If XP P9000 RAID Manager is installed on a non-system drive, you must change the INSTALL_PATH
parameter in the XP P9000 RAID Manager linkage definition file (DEFAULT.dat) or change the XP
P9000 RAID Manager Installation Path setting in the Application Agent Settings window.
In addition, if you execute a VSS backup or manage a replica of Exchange Server, you must set the
system environment variable VSHTCRMENVF on the backup server. For details, see the explanation
about the settings necessary for using VSS in the HP XP P9000 Replication Manager Software
Application Agent CLI User Guide.
Editing the journal option settings
If the version of Device Manager installed at a remote site is 7.2.0 to earlier than 7.3.1, editing the
journal option settings of an HP XP P9500 Storage journal group generates the following error
messages:
An attempt to perform journal pool processing has failed. [KAVN00589-E]
An attempt to call the Device Manager server function has failed. (Device
Manager server’s error code: KAIC05000, Device Manager server’s error
message: An unidentified error has occurred.) [RPM-01004]
To edit the journal option settings, upgrade the Device Manager installed at a remote site to 7.3.1 or
later.
Using the GetTasks command
When the GetTasks command displays the task information on copy groups defined by device
groups, a hyphen (-) is displayed in Host (Primary).
Backup and restore management in a SQL Server 2012 AlwaysOn Availability
Group configuration
Functional overview
Replication Manager Application Agent 7.4.0 and 7.4.1 support operations to back up, restore, and
recover SQL Server databases in configurations using SQL Server AlwaysOn Availability Groups, by
using the Application Agent CLI. Note, however, that only operations to back up and restore user
databases on an active node in an AlwaysOn Availability Groups configuration are supported. The
following operations are not supported in an AlwaysOn Availability Groups configuration: 1) backup
and restoration of system databases and 2) backup and restoration of user databases on a passive
node. The descriptions in this section assume that the primary database server is the active node.
This section describes the procedure for steps 1 through 3 to create a SQL Server 2012 AlwaysOn
Availability Group configuration.
1. Build a database on the secondary database server by using a backup.
This step includes the procedure for using a backup of the primary database server to build a
database on the secondary database server, which is required for an AlwaysOn Availability
Groups configuration.
2. Back up and restore the user database on the active node.
This step includes the procedure for normal backup and restoration operations by using Application
Agent, between the primary database server in the AlwaysOn Availability Groups configuration
and a backup server.
3. Build a database on the secondary server by using a backup.
This step includes the procedure for using a backup of the primary database server to build a
database on the secondary server. The secondary server can be used as, for example, the primary
database server in another AlwaysOn Availability Groups system.
8 Backup and restore management in a SQL Server 2012 AlwaysOn Availability Group configuration