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

databases. If the system database to be backed up is specified as the destination, when the system
database is restored from the secondary volume, the SQL Server error log files are also restored.
As a result, the contents of the error log files return to the state they were before the backup, and
consequently the error log information generated after the backup will be lost.
• Store tempdb on a different volume from the one used to store a user database to be backed up.
If the same volume is used, tempdb remains online and is overwritten with data restored from the
secondary volume when restoring from the user database only. This causes SQL Server to go into
an invalid state. To recover SQL Server from this state, it must be restarted to recreate tempdb.
After restarting SQL Server, move tempdb to a volume separate from the user database and attempt
the restore again.
• A backed-up database cannot be restored if the SQL Server versions do not match. For example,
a database backed up from a database server running SQL Server 2005 cannot be restored to
a database server running SQL Server 2008.
• In a cluster environment, install an SQL Server instance as a failover cluster.
The following points must be considered if you are using SQL Server 2005 or SQL Server 2008:
• Databases that use the snapshot function cannot be backed up and restored by Replication Man-
ager. If configured to back up a database snapshot, the backup will fail. When backing up an
entire instance, first remove any database snapshots.
• The service broker becomes disabled when databases are restored using Replication Manager.
To enable the service broker, execute the following SQL statement after restoration:
ALTER DATABASE [database name database-name] SET ENABLE_BROKER
• When using Replication Manager to manage replicas of databases using a database mirroring
function, run the operation on a principal server.
• To restore a database using a database that uses the mirroring function, disable the mirroring
function for the database.
• To restore system databases (master, model, and msdb) together with a database that uses the
database mirroring function, disable the mirroring function for the database using it, restore the
system databases, and then restore the database that uses the mirroring function.
Allocating files that comprise a database
Do not place database files to be backed up in the same volume as files that will not be backed up.
Allocating metafiles
A metafile is a file SQL Server outputs during backup processing. Metafiles store information about
database composition and are therefore used in restoration processing. For this reason, when backup
data is backed up to tape, the metafile must also be backed up to the tape.
If you have specified a VDI metafile storage directory, when backup data of the secondary volume
is backed up to tape, the metafile must also be backed up to the tape (this is not necessary if the
metafile is stored in the same directory as the database file).
When you back up to tape, use FTP or a similar method to transfer the metafile created in the metafile
storage directory in the database server to the backup server. Transfer the file in the directory using
the same name as in the metafile storage directory in the backup server and allocate the same drive
characters.
Metafile allocation on the database server and the backup server is shown in the following figure.
Managing application replicas 372