backup session manager checks whether the command addresses it and if this
is the case it aborts.
3. Abort sessions (all or specific) with application identifications
omniclus -clus obvs.hermes.com -session * -abortsess
-abortid != 10
Note: On UNIX systems replace the * wildcard with '*'.
This way the user can define groups of sessions and abort only the ones that
are actually related to the application that failed over. For example a backup
session that performs a normal filesystem backup of a remote client is not aborted
because an application server switches, while the application server backup
can be aborted.
4. Temporarily disabling the Data Protector cell
The following command will inhibit backup sessions for twenty minutes:
omniclus -clus cluster.domain.com -inhibit 20
The following command will inhibit backup sessions forever:
omniclus -clus cluster.domain.com -inhibit *
Note: On UNIX systems replace the * wildcard with '*'.
The following command will re-activate backup sessions immediately:
omniclus -clus cluster.domain.com -inhibit 0
5. EMC/Symmetrix links
The following syntax will connect to specific (running) backup session managers
and inform them to left the EMC/Symmetrix links split:
omniclus -clus cluster.domain.com -session * -symlink split
Note: On UNIX systems replace the * wildcard with '*'.
The following syntax will connect to specific (running) backup session managers
and inform them to left the EMC/Symmetrix links active (established):
omniclus -clus cluster.domain.com -session * -symlink
active
Note: On UNIX systems replace the * wildcard with '*'.
SEE ALSO
omnirsh(1M)
Command line interface reference 83
To Next Page
Loading...
