HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses - Manual (Page 101)

After volume promote, on few occasions, the volume involved in the restore operation might not
come online.
Suggestion:
From the Disk Management utility of the server, select the volumes involved in Restore operation
and manually make them online. If the problem persists, present the LUN which was to be restored
to the same host again through HP 3PAR Management Console (MC) using a LUN ID different
from the original LUN ID.
Problem:
After Repository location change, previously scheduled tasks do not work and they do not appear
in Task Manager List.
Suggestion:
Delete those old tasks from Windows Task Scheduler. Clean up the Recovery Manager Tasks
folder and create those tasks again from the Recovery Manager.
Problem:
Point of failure (using Auto restore) fails if, earlier the virtual copy is recovered manually using
Point in time and No recovery option.
Suggestion:
Do not use any third party software or SQL management studio for backing up the transaction
logs. Doing so would result in Recovery Manager not having the Transaction log backup sequence
and this results in the failure of point-of-failure restore operation.
Problem:
If you are trying to uninstall HP 3PAR Recovery Manager for SQL , sometimes a window pops up
prompting for server reboot.
Suggestion:
It is recommended that you click Cancel button, stop the HP 3PAR Recovery Manager for SQL
service and HP 3PAR VSS Provider service and then try the uninstallation of the product again.
Problem:
If Recovery Manager for SQL server is in the workgroup and is managed by Recovery Manager
for Exchange backup server, then one click backup fails.
Suggestion:
Symantec NetBackup must be installed using custom installation option and registration of the
Symantec Netbackup service during the time of installation must be done explicitly using work
group privilege.
Problem:
You might encounter the following error in HP 3PAR Recovery Manager Software for SQL CLI or
GUI output or in the log files.
Troubleshooting 101