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

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.
PROMPT > drmdbexport 0000000001 -f C:\temp\EX-FILE1.drm
PROMPT >
5. Transfer data to the secondary database server.
Using a method of your choice, transfer the following files to the secondary database 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
database server.
6. Start an instance of SQL Server on the secondary database server.
• Bring the secondary volume disk online.
• Mount the file system of the secondary volume.
• Start an instance of SQL Server.
7. Import the temporary file transferred from the primary database server into the backup catalog
of the secondary database server.
Import the temporary file transferred from the primary database server (C:\temp\EX-FILE1.drm)
into the backup catalog of the secondary database server. To import the temporary file, on the
secondary database server, execute the drmdbimport command.
PROMPT > drmdbimport -f C:\temp\EX-FILE1.drm
PROMPT >
8. Verify that the file has been imported.
Verify that the import operation has finished normally. To do so, on the secondary database
server, execute the drmsqlcat command.
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. Doing so changes the status of the final user database to
RESTORING.
PROMPT > drmsqlrecovertool instA
PROMPT >
10 Backup and restore management in a SQL Server 2012 AlwaysOn Availability Group configuration