HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses - Manual (Page 7)

•
Adding the database 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 43) .
•
Using the same version of HP 3PAR InForm OS, HP 3PAR VSS Provider, and HP 3PAR Recovery
Manager for SQL Software on all backup and productions systems
•
Installing the same version of the InForm CLI software on both the backup and production
systems
•
Using the SQLServerWriter service
•
Exporting volumes to a host must be in the form of base volumes; exporting snapshot volumes
is not supported.
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.1
•
HP 3PAR Recovery Manager Software for SQL Server 4.3
•
HP 3PAR Storage System 2.3.1 or higher
Features Supported
•
Windows Enterprise Server
For detailed OS version support, see the HP 3PAR InForm OS Configuration Matrix.
•
Microsoft SQL Server
For detailed SQL server version support, see the HP 3PAR InForm OS Configuration Matrix.
•
Volume Shadow Copy Service Full backup type
•
Virtual copy creation using HP 3PAR VSS Provider Software for Microsoft Windows
•
Scheduling and management of automated tasks
•
Mount virtual copies locally or remotely
•
Mount virtual copies in read/write mode
•
Unmount virtual copies
•
Delete virtual copies
•
Environment Report
•
File Copy restore
•
Database-level file restore in “No Recovery” mode
•
Selective restore of databases from a instance level virtual copy
•
Automate the Point of failure restoration process
Running Recovery Manager on a Japanese OS 7