C event messages – HP 3PAR Application Software Suite for Microsoft SQL Licenses User Manual
Page 79
C Event Messages
This appendix provides information for the event messages generated by HP 3PAR Recovery
Manager Software for Microsoft SQL Server.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages
Description/Action
Event Message
Event ID
Some of the target volumes are not HP 3PAR virtual volumes.
All of the drives need to be HP 3PAR drives.
•
Verify that all database and log destinations belong to an
HP 3PAR Storage System.
RMS5312: ERROR: Some of your volumes
are either non-3PAR volumes or
unsupported types of disk drives.
5312
The Remote Copy volume group is not configured for the
specified SQL database or instance.
RMS5313: ERROR: Couldn't find the
Remote Copy group for the specified
volume.
5313
•
Check the Remote Copy configuration and HP 3PAR Storage
System setup.
•
Consult the HP 3PAR InForm OS CLI Administrator's Manual
or the HP 3PAR InForm Management Console Help for details
on setting up and checking Remote Copy functionality.
To create a virtual copy of a SQL database or instance, the
virtual volumes configured to store SQL database and log files
RMS5314: ERROR: The number of virtual
volumes used to create the virtual copy
5314
must match the virtual volumes configured in the Remote Copy
volume group.
does not match the number of virtual
volumes in the Remote Copy group.
•
Check the Remote Copy configuration and HP 3PAR Storage
System setup.
•
Consult the HP 3PAR InForm OS CLI Administrator's Manual
or the HP 3PAR InForm Management Console Help for details
on setting up and checking Remote Copy functionality.
The repository might be out of sync.
•
Run rmsql analyze to list the out-of-sync entries.
RMS5319: ERROR: The virtual copy was
not found in the repository.
5319
To use an alternate (non-default) mount point directory in the
RMSql mount
command, you must first create the mount point
directory.
RMS5321: ERROR: The specified mount
directory does not exist.
5321
•
Verify that the mount point directory exists.
•
Alternatively, do not specify a mount directory. If an alternate
directory is not specified, Recovery Manager uses the default
mount directory.
79