T.R | Title | User | Personal Name | Date | Lines |
---|
724.1 | cluxfer does manual failover | DECWET::CAPPELLOF | My other brain is a polymer | Wed Apr 02 1997 12:47 | 9 |
| In one of the releases of Digital Clusters, we added the "cluxfer"
command to initiate manual failover. Look in the release notes for
documentation. Syntax is:
cluxfer GroupName NodeName
where "GroupName" is the name of the group you want to failover, and
"NodeName" is the name of the node where you want the group to come
online.
|
724.2 | cluxfer.exe | MSE1::MASTRANGELO | | Wed Apr 02 1997 12:52 | 17 |
|
I'm pretty sure that the cluxfer.exe utility comes with SP1 for V1 but
I'm not certain. Look in the \Digital\Clusters directory on one of
the machines and you should see cluxfer.exe in there. If its not there
you can get it if you install SP2 (or upgrade to V1.1).
This is from the release notes.
2.12.1 Cluxfer Utility for Manual Failover from Batch File
---------------------------------------------------------
The new cluxfer command line utility lets you start a manual
failover of a cluster failover group from within a batch file
or from an application. With this utility, you can transfer a
cluster failover group to a specific cluster node. See
Appendix A of the Administrator's Guide for details.
|
724.3 | IF EXISTS THEN FAILOVER | NETRIX::"[email protected]" | Tsvika Lavie | Sun Apr 06 1997 04:29 | 14 |
|
Hello,
Thanks for your help I'm going to use it.
Regarding to the Scripting questions, is there a way to check within the
script if the drive is "mounted" by one of the cluster members, before it
tries to failover it to the second member of the Cluster.
Thanks again,
Tsvika Lavie
[Posted by WWW Notes gateway]
|
724.4 | test disk access | DECWET::LEES | Will, NTSG DECwest, Seattle | Mon Apr 07 1997 15:28 | 4 |
| If a disk device is not online on a system, uncached reads or writes will
return ERROR_NOT_READY.
|