HP XP P9000 Replication Manager Software 7.4.
© Copyright 2013 Hewlett-Packard Development Company, L.P.
Version 7.4.1-00 Description This is the initial release of HP XP P9000 Replication Manager Software Edition 7.4.1. For details, see “Enhancements” (page 3). For previous behaviors resolved in this release, see “Fixes” (page 4). Update recommendation Routine Superseded version 7.4.
• Replication Manager can now manage copy pair configurations for which virtual IDs are set and change copy pair statuses for the following storage system: ◦ • • HP XP P9500 Storage Replication Manager now supports the following operating systems on a management server: ◦ Windows Server 2012, no SP (x64) ◦ Red Hat Enterprise Linux 6.3 (x86/x64) Replication Manager now supports Firefox ESR 17 on the following operating systems: ◦ Red Hat Enterprise Linux 5.3 (x86)-5.
Important considerations Replacing secondary volumes of Continuous Access Synchronous or Continuous Access Journal in a 3DC multi-target configuration (open systems) To replace all the secondary volumes included in a Continuous Access Synchronous or XP P9000/XP Continuous Access Journal copy pair, launch the Pair Configuration Wizard more than once to replace the secondary volumes using the following procedure: 1.
1. 2. Multiple tasks for the same copy pair are executed simultaneously. The tasks include a task that changes the copy pair status.2 Recovery procedure For tasks that froze in the Executing status: • Restart the XP P9000 Command View AE Suite Common Component service to reset the tasks to the Failure status. • Execute tasks again that you need to complete so that they are not executed simultaneously.
Managing application replicas If the following tasks are scheduled, n/a is displayed in the Execution Type column of the Tasks list: • A task that creates a replica of an application database. • A task that restores a replica of an application database. Creating a 4x4 Continuous Access Journal copy group for a mainframe system When creating a 4x4 Continuous Access Journal copy group for a mainframe system, in certain configurations there are conditions for the specifiable EXCTG ID.
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.
Requirements To use the Application Agent CLI in an SQL Server AlwaysOn Availability Groups configuration, you must fulfill the requirements described in the Application Agent CLI manual in addition to the following requirements. • The version of Application Agent is 7.3.0-00 or later. • The database software is SQL Server 2012. • The version of the operating system on each server is within the range supported by Application Agent.
After executing the drmsqllogbackup command, be sure to avoid updating the user database that was backed up. 4. Export the backup information to a temporary file. Information about backup operations from primary volumes to secondary volumes must be copied to the secondary database server. On the primary database server, execute the drmdbexport command to export information about backup operations to a temporary file. In this example, the name of the temporary file is C:\temp\EX-FILE1.drm.
When this command is executed, the drmsqlrecovertool dialog box appears. Click Add, and then select all transaction log backup files. Then, for Recovery Mode, select Loading, and for Roll Forward, select Yes. 11. Use SQL Server Management Studio to set up an AlwaysOn Availability Groups configuration consisting of the primary and secondary database servers. Back up and restore the user database on the active node This section describes the procedure for backing up and restoring a user database.
2. 3. 4. If the user database of the secondary server (USER_A) is attached, detach it. Prepare • Stop the instance of the SQL Server. • Unmount the file system of the secondary volume. • Take the secondary volume disk offline. Refresh the dictionary map file on the primary database server. PROMPT > drmsqldisplay -refresh PROMPT > 5. Back up the user database to the secondary volume. Back up the user database on the primary database server.
10. Import the temporary file transferred from the primary database server into the backup catalog of the secondary server. Import the temporary file transferred from the primary database server (C:\temp\EX-FILE1.drm) into the backup catalog of the secondary server. To import the temporary file, on the secondary server, execute the drmdbimport command. PROMPT > drmdbimport -f C:\temp\EX-FILE1.drm PROMPT > 11. Verify that the file has been imported. Verify that the import operation has finished normally.
Installation instructions For installation information, see the following manual sections: Component Manual Management server HP XP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Management client HP XP P9000 Replication Manager Software Configuration Guide Application Agent HP XP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Compatibility/interoperability No issues.
Tiered Storage Manager Software 7.4.1-00 • HP XP P9000 Tiered Storage Manager Software CLI Reference Guide (TB585-96029) Version 7.4.1-00 • HP XP P9000 Tiered Storage Manager Software Release Notes (TB585-96030) Version 7.4.
