Deleting Backup Sessions; Enabling And Disabling Replicas; Changes In The Environment - HP Data Protector A.06.11 Integration Manual

Deleting backup sessions

Using the omnidbvss command, you can delete:
• A specific instant recovery-enabled backup session (a replica version), identified
by the session ID, from the non-persistent part of the VSSDB and disk array, or
only from the VSSDB.
• All instant recovery-enabled backup sessions based on a specific backup
specification (a replica set) from the non-persistent part of the VSSDB and disk
array, or only from the VSSDB.
• A specific backup session, identified by the session ID, from the persistent part
of the VSSDB.
• All backup sessions based on a specific backup specification or that were created
before a specified date from the persistent part of the VSSDB.
See the omnidbvss man page for the command syntax and examples.

Enabling and disabling replicas

Using the omnidbvss command, you can present and mount (enable) on a backup
system and unmount and unpresent (disable) from a backup system the replicas from:
• All instant recovery-enabled sessions.
• A specific instant recovery-enabled session, identified by the session ID.
• All instant recovery-enabled sessions based on a specific backup specification.

Changes in the environment

During a VSS instant recovery sessions or the VSSDB maintenance sessions using the
omnidbvss command (remove, disable, enable), the state of target volumes in a
replica is checked prior to restore, remove, disable, and enable operations. Before
restore, the state of the source volumes on the application system is also checked. If
the check finds any changes that have not been tracked in the VSSDB, the session
is aborted, notifying you about the specific changes. This check can be disabled by
setting the OB2VSS_IGNORE_BACKUP_DISK_CHANGES and
OB2VSS_IGNORE_SOURCE_DISK_CHANGES omnirc variables to 1.
During VSS backup session, a replica is created and left on a disk array until the
specified number of replicas rotated is reached. After that, the next replica to be
created replaces the oldest replica in the set. If the oldest replica in the set cannot
be replaced because you have manually (not using Data Protector) unpresented the
replica from the backup system and presented it on some other system, the backup
Zero downtime backup integration guide 341