HP XP7 Replication Manager Configuration Guide (TK981-96012, May 2014)

Restoring a replica with roll-forward fails with error message RPM-11510
When restoring a replica with the roll-forward option, if the storage group to recover has more than
1,008 transaction log files, the restore and roll-forward will complete, but the information store will
not be mounted and the message RPM-11510 is output. Follow this procedure to complete the mount
operation:
1. Start the event viewer for the operating system on the database server.
2. Confirm that the error log with the event source MSExchangeIS and the Event ID 9518 are
recorded. Open the properties for the error log, and confirm that the description field reads
Error 0xfffffd9a has occurred. If this event is recorded in the log, skip to step 4.
3. If the error log in step 2 is not recorded, confirm that an information log with event source ESE,
event ID is 302, and the description field reads Database engine normally completed
the recovery steps. Also check that this log is followed immediately by an information log
with event source ESE, event ID 101, and the description Database engine is stopped.
NOTE:
If you do not find either of the error logs described in steps 2 and 3, do not continue this
procedure.
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.
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 hierarchical 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 Windows log entries with 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.
Troubleshooting134