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

• ASCII characters
• Multi-byte characters (one character must be expressed using 1- or 2-byte characters)
However, do not use the following characters:\ / : , ; * ? < > | “
• Do not use names in the following form for database data files:
META_database-ID.dmp
Where database-ID is a 10-digit number.
• In a cluster environment, specify a user on each node for the owner of a database subject to
backup. Local users with the same user name and password on different nodes are not considered
to be the same user. Therefore, use a domain user account that is common to all nodes. If a failover
is performed to a node where the database-owner user does not exist, the backup fails because
the database owner is unknown.
• If the system databases ( master , model , and msdb ) are to be backed up, specify, as the output
destination for SQL Server error log files, a volume different than the one that contains the system
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.
• 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.
• In SQL Server 2005, the database configuration file of the resource database is stored in the same
location as the master database. Replication Manager does not quiesce the backup target or
display backup information because the resource database is a read-only database. But when a
replica of a system database is created or restored, a replica of the database configuration file
is created or restored along with the master database.
Unsupported functions
The following functions are not supported for SQL Server 2008:
Managing application replicas 394