HP Data Protector 6.2 software integration with HP 3PAR Storage System

25
Figure 23: Content of virtual copy is available on the application system.
Microsoft SQL backup
Microsoft SQL Server provides support for creating snapshots from SQL Server data using VSS by
providing SQL writer. Starting with MS SQL version 2005, SQL writer is included in the MS SQL
installation. To check if the writer is properly installed and if it is in the proper, stable state, execute
following command on the server where MS SQL Server is running:
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool(C) Copyright
2001-2005 Microsoft Corp.
......
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {f6f07c24-a3be-44dd-b311-48020f20a512}
State: [1] Stable
Last error: No error
......
C:\>
To perform a backup of Microsoft SQL Server data, it is required that the MS Volume Shadow Copy
Integration component is installed on the server where the SQL Server is running as well as on the
backup server. It is not possible to run a transaction log backup using MS Volume Shadow Copy
Integration. Only full backups are possible. These backups, even though they do the backup of
transaction logs, do not truncate them. To be able to perform a backup of transaction logs, Data
Protector MS SQL Integration component must be installed on the server where MS SQL Server is
running. This integration uses Microsoft Virtual Disk Interface (VDI) to run block-level backup of
transaction logs. For information on how to configure backup of MS SQL transaction logs, refer to the
Integration Guide for Microsoft Application listed in the For more information section.
Before running backup, ensure that both data and log files are stored on the 3PAR Storage System
disks.