Event Messages

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

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

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

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

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

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

To use an alternate (nondefault) 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 alternate directory is not specified, RMC-S uses the default mount directory.

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.

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

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.

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

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

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.

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.

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

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

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

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.

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.

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.

NetBackup installation information could not be retrieved from the registry.

• Verify that NetBackup is properly installed and that you have access to the registry entry.

• Use Add/Remove Programs to confirm that NetBackup is installed.

Unable to open or create the NetBackup include file for the specified policy. You can run only one backup job per policy at a time on a NetBackup client. Ensure that no other HpRmCli Sql backup command with same policy is running. Wait for the prior backup command to complete and try again.

The NetBackup restore failed.

• On the NetBackup server, check the application event log and NetBackup logs.

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.

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.

The NetBackup backup process has failed.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

An unexpected error occurred.

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

The policy was not found in the NetBackup database.

• Verify that the policy is valid.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

The schedule was not found in the NetBackup database.

• Verify that the policy is valid.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

RMC-S could not connect to the NetBackup server.

• Ensure that you can connect to the NetBackup master server.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

The backup cannot be created because no storage units are available.

• Ensure that the storage units are configured and available for use.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

The process cannot continue because the policy is not a valid client type.

• Ensure that the policy is a valid client type.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

The NetBackup server is not allowing this operation.

• Wait some time and try the operation again.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

RMC-S cannot locate the client in the policy specified.

• Verify that the client is correctly configured for the specified policy.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

To create backups, the policy used to create the backup must be active.

• Verify that the specified policy is active.

• For more details, check the application event log and NetBackup logs on the NetBackup server.

RMC-S failed to mount the snapshot.

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

RMC-S failed to create the snapshot.

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

The Data Protector installation information could not be retrieved from the registry.

• Verify that Data Protectoris properly installed and that you have access to the registry entry.

• Use Add/Remove Programs to confirm that Data Protector is installed.

The specified data list could not be found or access was denied.

• Ensure that the correct name is specified for the datalist.

• Ensure that the SYSTEM account has permission to run backup processes from the specified client.

• Use the Data Protector Manager GUI to configure client permissions.

Data Protector failed to execute the specified command. For more details, check the Data Protector logs on the Data Protector Cell Manager server.

The Data Protector Session ID to restore was not found for the time stamp specified. Ensure that the backup time stamp does not belong to another backup vendor (for instance, NetBackup).

The NetBackup policy to restore was not found for the time stamp specified. Ensure that the backup time stamp does not belong to another backup vendor (for instance, Data Protector).

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.