Limitations
For a list of general Data Protector limitations, see the HP Data Protector product
announcements, software notes, and references.
• Maximum 512 shadow copies per volume are allowed. The number of shadow
copies per volume is limited by system resources.
• To run a VSS integration backup, the writer’s data must be on an NTFS filesystem.
For hardware providers, this is not required.
• The VSS integration backup of writers which store their data on network shared
volumes is not supported.
• 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.
• 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.
• If the backup system is in a cluster and if you select the Mount the replica
on backup system option, note that the replica disks are mounted to the active
cluster node. In the case of a backup system failover, the mounted disks are not
unmounted and moved to another node.
• During a local backup, with the option Track the replica for instant
recovery selected, and with the option Mount the replica not selected,
note the following:
• On Windows Server 2003, the created snaphots are unpresented on the
application system after the backup.
• On Windows Server 2008, the created snaphosts are only put offline after
the backup, while they stay presented on the application system.
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
Zero downtime backup integration guide 345
To Next Page
Loading...
Need help?
General