HP 10400 Application Software Suite for Microsoft SQL Media LTU Recovery Manager Requirements

•Virtual copy (snapshot) space must be available on virtual volumes where the SQL Server database resides.

•To create virtual copies on the base volume, you must associate virtual copy space with the base volume itself. For more information on creating a base volume with virtual copy space, or assigning virtual copy space after the base volume is created, see the HP 3PAR InForm OS Command Line Interface Reference.

NOTE: For platform-specific release levels, refer to the latest HP 3PAR InForm OS Configuration Matrix. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate to your product page, click Support for your product, and then click Manuals.

Recovery Manager Requirements

•To create virtual copies and perform one-click backup, the Microsoft SQL Server database for which virtual copies are to be created must be online.

•One backup server is required.

•Because Recovery Manager operates through HP 3PAR VSS Software, the database must be online to perform a file copy restore at the database level. To restore a SQL database that is detached, you can either mount a previously created snapshot of this database to the production server and copy over the database files, or you can issue a volume restore at the database level. For more information about restoring volumes, see “Recovery Manager Commands” (page 42).

•Backup and production server(s) must be running the same level OS version and the same version of HP 3PAR Recovery Manager for SQL Software. Recovery Manager does not support cross-platform configurations.

•The same version of the InForm CLI must be installed on both the production and backup servers.

•The SQLServerWriter service must be running.

•Volumes exported to a host must be base volumes; you cannot export snapshot volumes.

Running Recovery Manager on a Japanese OS

CAUTION: To be fully compatible with Recovery Manager, you must use English-language naming conventions in your SQL Server setup (for example, for domain names, instance and database names, path names, and so on).

Recovery Manager does not function correctly when any language other than English is used, even for areas in which SQL Server itself supports Japanese characters.

•SQL Server OS: Windows Server 2008 R2, Japanese OS

•Microsoft SQL Server 2008 R2

•HP 3PAR VSS Provider Software 2.1.0

•HP 3PAR Recovery Manager Software for SQL Server 4.2

•HP 3PAR Storage System 2.3.1 or higher

Recovery Manager Requirements 9