HP XP P9000 Command View Advanced Edition Software - Manual (Page 388)

Event source : Virtual Disk Service
Event ID : 1
Description : Unexpected error. Error code : 48F@02000018
Event type : error
Event source : Disk
Event ID : 15
Description : The Device XXXXXXXXXXXX is not the status that can be
accessed.
• The following event log may be output to the database server, the file server, or the backup server,
and can safely be ignored:
Event type : Warning
Event source : VSS
Event ID : 12333
Description : Warning of Volume Shadow Copy : The storageID that is not supported in VSS was
reported from the provider.
• After a volume is hidden and the OS disk configuration is recognized again, the error message
Device has been removed is output to the Windows event log. HP recommends that you
periodically delete the error messages in the event log.
Restoring replicas (restores)
The following precautions apply to restoring replicas:
• To restore and recover SQL Server system databases, stop the target SQL Server service. This will
make the databases being restored temporarily inaccessible. Do not connect to SQL Server when
a restore is in progress.
• To restore a renamed SQL Server database, be sure to detach the database before doing the
restoration. If you attempt to restore the database without detaching it, the restore will not execute
properly and the restored database might not be available. If this occurs, detach the database
and restore it again.
• Make sure that all databases to be restored are ready. For information on the status of a database,
see “
About SQL database and service status ” on page 412. A database with the Unconfirmed
status is automatically removed and restored. If any of the databases to be restored are not ready,
the process might fail. If this occurs, remove any databases that are not ready and re-start the
restoration.
• Quit all business programs and make sure that any applications that access the database are not
running. (The term applications implies any application that is at a higher level than SQL Server.)
Also, make sure that SQL Server components such as Reporting Services, which is also an applic-
ation at a higher level than SQL Server itself, are not running. If an application that connects to
the database is running, a roll-forward operation might fail after applying the metafiles. If this
occurs, the restoration will not be performed correctly. For example, if an application is running
that retries when an ODBC session is not established, the application will issue an ODBC session
establishment request during a roll forward (that occurs after metafiles have been applied), resulting
in a failed roll-forward operation.
• To avoid possible errors during a restore, do not connect to any database restored from a different
computer, such as an application server.
• Observe the following precautions regarding access to primary volumes:
• If the Command Prompt was used to migrate a drive to the primary volume, close the Command
Prompt window. If a drive is migrated to a volume other than the primary volume, an error will
occur when the drive is unmounted.
• If the primary volume drive is being opened from Explorer, move the mount point to a drive
other than the primary volume or exit Explorer.
Managing application replicas 388