HP Data Protector A.06.00 additional writers and HP StorageWorks Disk Array XP support for Microsoft Volume Shadow Copy Service integration

• The Data Protector Microsoft VSS integration does not provide any restore method
for writers requesting a custom restore method. These writers are by default not
presented by Data Protector.
If a writer specifies a custom restore method, it is only possible to restore the
writer's data as plain files using the Data Protector functionality. You can perform
the custom restore manually. Refer to the writers documentation for additional
information on the restore methods.
• Microsoft Exchange Server 2007 Standby Continuous Replication (SCR) is not
supported
• Preview is not possible for VSS backup and restore sessions.
• VSS backups with hardware provider are only supported for volumes on disk
arrays. This is also valid for system disks. Instant recovery of system disks backups
is not possible.
Enterprise Virtual Array hardware provider limitations
• With the EVA provider, if there are too many, for example more than four, source
volumes selected for backup, the creation of snapshots may take too long and
VSS may fail the snapshots creation process. It is strongly recommended not to
specify too many objects in a backup specification, since they might reside on
more than four source volumes. For example, a Microsoft Exchange Server storage
group should not reside on more than four source volumes, and only one storage
group should be selected for backup if the storage group occupies four source
volumes. The same limitation also applies to Microsoft SQL Server databases.
Disk Array XP hardware provider limitations
• If the Disk Array XP VSS hardware provider is in the VSS compliant mode, and
there is a high read-write load the disk array, the replica creation may take a
long time. Consequently, the backup session may fail.
By default, Data Protector waits for a maximum of 45 minutes (2700 seconds)
for mirrors to become synchronized. If synchronization is not completed when
the waiting period expires, Data Protector aborts the backup session.
You can increase the waiting period duration by setting the
OB2VSS_WAIT_TIMEOUT omnirc variable. The variable value determines the
period (in seconds) for which the Data Protector agent waits for mirrors that are
created in one session to become fully synchronized. If the
OB2VSS_WAIT_TIMEOUT variable is set to more than 2 hours (7200 seconds),
you should additionally increase the value of the global variable SmIdleTimeout
past the value of OB2VSS_WAIT_TIMEOUT. The value of SmIdleTimeout
should be specified in minutes, rather than seconds.
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service74