HP XP P9000 Replication Manager 7.4.
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Version 7.4.0-00 Description This is the initial release of HP XP P9000 Replication Manager Software Edition 7.4.0. For details, see “Enhancements” (page 3). For previous behaviors resolved in this release, see “Fixes” (page 4). Update recommendation Routine Superseded version 7.3.
• Replication Manager now supports the following virtual platform on a management server and an Application Agent host: ◦ • • VMware ESXi 5.1 Replication Manager now supports Internet Explorer 10 on the following operating systems: ◦ Windows Server 2012, no SP (x64) ◦ Windows 8, no SP (x86/x64) Replication Manager now supports the following operating system on an Application Agent host: ◦ Windows Server 2012, no SP (x64) Fixes Fixes for 7.4.
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.
Performing advanced operations per copy pair When you have executed a takeover-recovery (recreate) operation to a copy group including copy pairs in simplex status per copy pair, update the storage system information after the task is complete. If you do not update the storage system information, you will be unable to perform any copy pair operation to copy pairs in simplex status in the target copy group in Change Pair Status Wizard.
• ◦ takeover-recovery (resync) ◦ takeover-recovery (recreate) Operations on the mainframe system: ◦ restore Regarding copy groups maintaining their consistency, if you use a tool other than Replication Manager to perform a swap operation or takeover (Reverse Resync) operation for either only the copy group on the open system or only the copy group on the mainframe system, you cannot use Replication Manager to manage the relevant copy group. InPrivate Browsing in Internet Explorer 9.
Using the GetCTDelta command If XP P9000 Command View AE Common Component is not installed under the installation directory of XP P9000 Command View AE suite products, set the HRPM_CLI_BASE_PATH environment variable to the Common Component installation directory before executing the GetCTDelta command.
• HP XP P9000 Command View Advanced Edition Suite Software Plug-in for Virtualization Server Provisioning User Guide (TB581-96307) Version 7.3.0-00 • HP XP P9000 Command View Advanced Edition Suite Software Mainframe Agent Installation and Configuration Guide (TB581-96078) Version 7.2.0-00 • HP XP P9000 Command View Advanced Edition Suite Release Notes (TB581-96329) Version 7.4.0-00 • HP XP P9000 Command View Advanced Edition Suite Software Mainframe Agent Release Notes (TB581-96331), Version 7.4.
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.
2. Back up the user database to a secondary volume. Back up the user database on the primary database server. On the primary database server, execute the drmsqlbackup command by using the -target option or -f option to specify the user database. PROMPT > drmsqlbackup instA -target USER_A PROMPT > When this command is executed, backup information is registered in the backup catalog of the primary database server under a new backup ID (the next sequential unused ID number).
PROMPT > drmsqlcat instA PROMPT > 9. Restore the user database on the secondary database server. To restore the user database, on the secondary database server, execute the drmsqlrestore command. When this command is executed, the status of the user database becomes RESTORING. PROMPT > drmsqlrestore 0000000001 -no_resync -nochk_host -target USER_A 10. Recover the user database. To recover the user database, on the secondary database server, execute the drmsqlrecovertool command.
PROMPT > drmsqlrecovertool instA PROMPT > 6. Use SQL Server Management Studio to rebuild the AlwaysOn Availability Group. Build a database on the secondary server by using a backup This section describes the procedure for using the database on the primary database server to build a database for the secondary server. (This procedure corresponds to step 3.) 1. Delete the secondary server from the AlwaysOn Availability Group (only if a secondary server has been registered).
8. Transfer data to the secondary server. Using a method of your choice, transfer the following files to the secondary server: • The exported temporary file • VDI metafiles • The backup files for the transaction logs In this example, the exported temporary file is now C:\temp\EX-FILE1.drm on the secondary server. 9. Start an instance of SQL Server on the secondary server. • Bring the secondary volume disk online. • Mount the file system of the secondary volume.
