HP Application Recovery Manager software A.06.10 Administrator's guide (March 2008)

correct or if the SMI–S provider is currently operational. It just compares the saved
data against the actual setup. This may provide misleading results, if the CV EVA or
CV EVA SMI-S environment is not operating properly. If you use the results for an
actual cleanup, verify the configuration first. The option checks also the entries which
should be purged.
To check SMISDB for consistency, use the omnidbsmis command. See the
omnidbsmis man page for command syntax.
Purging SMISDB
During purge (normally started at the beginning of the backup session for the selected
backup specification), SMI-S Agent attempts to delete storage volumes marked for
purging. You can also run SMISDB purge manually using the omnidbsmis command.
See the omnidbsmis man page for more information.
Deleting replicas on the disk array and SMISDB Entries
Using the omnidbsmis command, you can delete:
• A specific backup session (a replica version), identified by the session ID, and
information about it.
• Backup sessions based on a specific backup specification (a replica set), identified
by the backup specification name, and information about them.
See the omnidbsmis man page for command syntax and examples.
IMPORTANT:
If the —reference option is specified, the command does not remove the target volumes
that constitute a replica; it removes the entries that describe the session. Consequently,
you cannot perform instant recovery from such a replica because the session information
has been removed. If this option is not specified, the command removes also the target
volumes on the disk array.
Excluding or including sessions from use
After a backup session, you can leave the replica mounted on the backup system for
other purposes than backup (replica set rotation) and instant recovery. For example,
you can use such replica for backup to tape with third–party backup software,
database replication and similar.
Administrator's guide 27