Event Messages

This appendix provides information on the event messages generated by RMC-S.

Table 3: RMC-S Server Event Messages

Event ID

Event Message

Description/Action

5312

RMS5312: ERROR: Some of the volumes are either non3PAR volumes or unsupported types of disk drives.

Some target volumes are not HPE 3PAR, HPE Primera virtual volumes. All drives must be HPE 3PAR drives.

  • Verify that all database and log destinations belong to an HPE 3PAR, HPE Primera Storage System.

5313

RMS5313: ERROR: Could not find the Remote Copy group for the specified volume.

The Remote Copy volume group is not configured for the specified SQL database or instance.

  • Check the Remote Copy configuration and HPE 3PAR, HPE Primera Storage System setup.

  • Consult the HPE 3PAR InForm OS CLI Administrator' Manual or the HPE 3PAR, HPE Primera Management Console Help for details on setting up and checking Remote Copy functionality.

5319

RMS5319: ERROR: The snapshot was not found in the repository.

The repository might be out of sync. To list the out-of-sync entries, run HpRmCli Sql analyze.

5321

RMS5321: ERROR: The specified mount directory does not exist.

To use an alternative (non-default) mount point directory in the HpRmCli Sql mount command, you must first create the mount point directory.

  • Verify that the mount point directory exists.

  • Alternatively, do not specify a mount directory. If an alternative directory is not specified, RMC-S uses the default mount directory.

5325

RMS5325: ERROR: The snapshot time stamp does not exist for the snapshotset ID.

When you created the snapshot, RMC-S could not store the snapshot time stamp in the repository for the specified snapshotset ID.

  • Wait a few minutes and then retry the operation.

5326

RMS5326: ERROR: Volume Restore failed.

A failure occurred when restoring data using the volume restore feature. The failure might leave the HPE 3PAR, HPE Primera Storage System in an inconsistent state. If the VLUNs are missing, ensure that they are recreated.

5327

RMS5327: ERROR: One or more of your volumes are on dynamic disks. Dynamic disks are not supported.

Some of the database or log files are stored on volumes created on dynamic disks. Ensure that the database and log files reside on volumes created on basic disks.

5328

RMS5328: ERROR: One or more of your databases are on the system volume. You cannot create Virtual Copies of system volumes.

Some of the database or log files are stored on the system volume.

  • Ensure that the database and log files are on HPE 3PAR, HPE Primera virtual volumes.

5329

RMS5329: ERROR: The destination file exists. Specify a different restore location and try the operation again.

Performing a restore from backup does not overwrite an existing copy of the same file. Verify that the specified restore folder is empty and try the operation again.

5332

RMS5332: ERROR: Could not find the SQL Writer. Either the Writer is not installed or is not running.

SqlServerWriter was not found on the SQL Server.

  • Run the vssadmin list writers command and verify that SqlServerWriter is listed.

  • Ensure that the SQL Writer service is in the Running state.

5333

RMS5333: ERROR: Remote Copy groups are not configured. A Remote Copy group must be present to perform this operation.

There are no Remote Copy volume groups configured on the HPE 3PAR, HPE Primera storage systems. Ensure that the Remote Copy volume group is configured before you create a remote snapshot.

  • Check the Remote Copy configuration and HPE 3PAR, HPE Primera Storage System setup.

  • Consult the HPE 3PAR InForm OS CLI Administrator'Manual or the HPE 3PAR, HPE Primera Management Console Help for details on setting up and checking Remote Copy functionality.

5335

RMS5335: ERROR: Mount point drive letter is already in use.

The specified mount point drive letter is already in use. Be sure to specify an unused drive letter as a mount point when you enter the HpRmCli Sql mount command.

5336

RMS5336: ERROR: Mount point directory is not a valid directory.

The specified mount point is not a directory. Be sure to specify a valid directory as a mount point when you enter the HpRmCli Sql mount command.

5337

RMS5337: ERROR: Mount point directory is not empty.

The mount point directory specified already contains files. Be sure to specify a valid directory as a mount point when you enter the HpRmCli Sql mount command.

5354

RMS5354: ERROR: The SQL database was not found in the SQL Writer database list.

SqlServerWriter could not find the specified database in its list of databases supported for backup.

  • Verify that the database is online and attached.

  • Ensure that the database is not a snapshot/mirrored database.

  • If you are performing an SQL instance level Snapshot, ensure that all the databases and SQL instance volumes are from the same HPE 3PAR, HPE Primera.

5356

RMS5356: ERROR: The expiration time is out of range (0h - 336h).

The expiration time for a snapshot must be a value between 0 and 43,800 hours (or between 0 and 1825 days).

  • Try again, using a value within the range allowed.

5367

RMS5367: ERROR: Unknown error encountered. See the logs for more information.

An unexpected error occurred.

  • For more details, check the logs in the RMC-S installation folder and the event logs.

5379

RMS5379: ERROR: Failed to mount snapshot. Check the application and system event logs for the most recent error.

RMC-S failed to mount the snapshot.

  • Check the application and system event logs for the most recent error messages.

5380

RMS5380: ERROR: Failed to create snapshot. Check the application and system event logs on the SQL Server for the most recent error.

RMC-S failed to create the snapshot.

  • Check the application and system event logs on the SQL Server for the most recent error messages.

5387

RMS5387: ERROR: Failed to set the disk in maintenance mode because the disk is offline.

Could not set the disk in maintenance mode because the disk is offline. Ensure that the disk to be restored is online before you run the volume restore operation.

5388

RMS5388: ERROR: Failed to set the disk in maintenance mode.

Could not set the disk in maintenance mode.

  • Ensure that the disk is online and can be put in maintenance mode.

  • Troubleshoot using the cluster command:

    cluster res <resource-name> /maint:on