HP P9000 Replication Manager Software 7.4.0-00 Configuration Guide (TB584-96058, December 2012)

4. Start Exchange System Manager and view the properties of the storage group to be recovered.
Check the location of the transaction logs as well as the initial characters of the log file. The initial
characters are E0n, where n is from 0 to 3.
5. Of the transaction log files in the storage group to be recovered, move those not matching the
description in step 4 to a new folder.
6. From the Exchange System Manager, mount the information store to be recovered.
7. Check that the information store is mounted, and then delete the transaction log files moved in
step 5.
Restoring a replica fails with event ID 454
If you have applied Exchange Server 2003 Service Pack 1 to a database server and end up with a
mixture of transaction logs from before and after the service pack installation, a restore operation on
the data may fail. In such a case, an event log with an event ID of 454 will be output. Follow this
procedure for the restore:
1. Execute the following command for each of the *.edb and *.stm files to be restored, and
record the leftmost numeric values displayed for Last Consistent:
Exchange-installation-folder\bin\eseutil /mh file-name-for-restoration
2. The minimum value among these recorded values is the Last Consistent log number. Move
any transaction log with a number smaller than this value to a different folder. For example, when
the Last Consistent log number is 1ab, the transaction log files E0x00001.log through
E0x001aa.log would be moved.
3. Using Exchange System Manager, mount all information stores for the storage groups to be
restored.
Creating a replica fails with error message RPM-10006
If different logical volumes are mounted at mount points in a hierarchical relationship, such as M:\
and M:\MNT, any mount points that hold a lower-level directory mount point (in this case, M:\) cannot
be specified for backup. If specified, the backup will fail, and an error message (RPM-10006 and
RPM-20062) will be output.
If this happens, only the lowest-level mount point can be specified for backup, so if you want to specify
multiple mount points for backup (including directory mount points), create a configuration in which
there is no hierarchal relationship between the mount points.
Creating a replica fails with event IDs 17, 1 and 10010
If a backup operation fails, the status of the Windows Logical Disk Manager Administrative service
will remain stopped, and event logs that have event IDs 17, 1, and 10010 will be output.The backup
attempt fails because the Logical Disk Manager Administrative service hangs up. If this happens,
restart the backup server. After the restart, check the effect of the operation on the backup server.
Disk status remains online after replica operation is complete
In Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 environments, the
disk status of secondary volumes on the backup server change to Offline after a backup operation
is performed. However, note that if the operation fails, the status of the secondary volumes on the
Troubleshooting134