HP StorageWorks P9000 Replication Manager Software 7.1.1 CLI User Guide (TB584-96032, September 2011)
• The database cannot be restored to SQL Servers with the version different from the one at backup.
For example, a database backed up with SQL Server 2005 cannot be restored to 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:
• In Application Agent, a backup or restoration cannot be performed for database snapshots. If you
want to back up all the instances, delete the database snapshot. If you include the database
snapshot in the backup target, the backup will fail.
• The service broker becomes disabled for databases that are restored by using the drmsqlrestore
command. To enable the service broker, execute the following SQL statement after restoration:
ALTER DATABASE [database name database-name] SET ENABLE_BROKER
• If any of the following commands is executed on a database where the database mirroring function
is used, execute the command on the principal server:
drmsqlbackup, drmsqllogbackup, drmsqldisplay -refresh
• If a database that uses the database mirroring function is to be restored, release the database
mirroring setting before restoring the database.
• If the system databases (master, model, and msdb) are to be restored in addition to a database
that uses the database mirroring function, release the mirroring setting on the database that is to
be restored, restore the system databases, and then restore the database that uses the database
mirroring function.
• If you use any of the following commands to delete backup information, the VDI metafile that was
created when the backup was performed will also be deleted. Before deleting the backup inform-
ation, back up the exported backup information and the VDI metafile.
• drmresync
• drmappcat -delete
• EX_DRM_RESYNC
• For SQL Server 2005, the database configuration files of the resource and master databases are
stored in the same location. Application Agent does not show information about freezing and
backup processing for the resource database. The database configuration file of the resource
database is backed up and restored along with the database configuration file of the master
database when the system database is backed up and restored.
Allocating files that comprise a database
Allocate the database file backed up by Application Agent to a volume separate from files not to be
backed up.
Application Agent can back up only the database configuration files (the *.mdf and *.ndf data
files and the *.ldf transaction log file) and metafiles. Metafiles are generated when the backup
command is executed.
For database configuration files that are not subject to backup and for general files, no freezing
processing is executed. Therefore, if the primary volume contains a file that is not subject to the freezing
processing, pair partitions will be duplicated during file writing, resulting in loss of database integrity.
Allocate only the database configuration files subject to the freezing processing in the primary volume.
Allocation of database configuration files is shown in the figure below.
Application Agent CLI User Guide 79