HP Serveur lame HP ProLiant BL465c Gen8 - Manual (Page 278)

Precautions when restoring a database
• When you attempt to restore an SQL Server system database (master, model, msdb, or distribution),
the SQL Server service to be restored needs to be stopped to recover the system database. The
database to be restored cannot be accessed temporarily.
• During restoration of the SQL Server system databases (master, model, and msdb), do not connect
to the SQL Server. If you connect to a database that is being restored, checking of the process
status is repeated by the number of times specified in the parameter (number of retries and retry
interval for checking the process status) of the Application Agent configuration definition file
(
init.conf ). In this case, if the user is disconnected during repeated checks of the process status,
restoration will resume.
• When performing a restoration, if the name of the drive that makes up the SQL Server database
is different from the backed up name, restoration terminates with an error. Before performing
restoration, with the
drmsqlcat command or SQL Server Enterprise Manager, check the corres-
ponding drive name of the restoration destination.
• When you specify the -nochk_host option to perform restoration on a different host from that
where the data was backed up from, make sure that backup data is restored on the appropriate
host, because a validity check of the host names in the backup catalog is not performed during
the restoration.
• When restoring an SQL Server database whose name has been changed, be sure to first detach
the target SQL Server database to be restored. If you restore the SQL Server database without
detaching, the command will not terminate properly, and you might no longer be able to use the
SQL Server database after it has been restored.
• After a database is restored, the owner of the database is changed to the user who performed
the restoration. To change the owner, use SQL Server Enterprise Manager to attach the database
again, or use the
sp_changedbowner system stored procedure.
• When you perform restore operations using a template catalog, execute the drmsqlrestore
command with the -template option.
• For non-cluster configurations, before performing restoration, make sure that the files and directories
on the primary volume are not being used by other applications, as Application Agent mounts
and unmounts the primary volume during restoration processing. If a file or directory on the primary
volume is being used by another application, cache synchronization during unmount processing
will fail, and restoration processing will terminate in an error.
In particular, keep the following in mind:
• When using the command prompt to move a drive to the primary volume, be sure to close the
command prompt window, as if you move a drive to a volume other than the primary volume,
an error will occur during the unmount operation.
• If a location within a drive of the primary volume is open in Explorer, either move the mount
point of the drive to one other than the primary volume, or close Explorer.
• If a location within a drive of the primary volume is open from an external computer, terminate
the open application.
• The primary volume may be opened by a service or resident process-monitoring program. In
this case, be sure to terminate any such monitoring programs.
• Before performing restoration, check that all applications accessing the database to be restored
are terminated. This includes SQL Server's high-order applications. For example, an SQL Server
component such as Reporting Services is also a high-order application of SQL Server. Therefore,
you must make sure that such SQL Server components are terminated before you start the restoration.
If any applications connected to the database are running, roll-forward attempts after metafile
application will fail, and restoration cannot be performed correctly.
Operation for SQL Server databases 278