Top
PRIMECLUSTER  Installation and Administration Guide4.3

J.1.16 RMS console message

Details on incompatibilities

Because of the change mentioned in "J.1.2 hvswitch command", hvswitch -f outputs different console message from that of previous versions.

Changes

Before upgrading [PRIMECLUSTER 4.2A00]

The use of the -f (force) flag could cause your data to be corrupted and could cause your node to be killed. Do not continue if the result of this forced command is not clear.


The use of force flag of hvswitch overrides the RMS internal security mechanism. In particular RMS does no longer prevent resources, which have been marked as "ClusterExclusive", from coming Online on more than one host in the cluster. It is recommended to double check the state of all affected resources before continuing.

Do you wish to proceed? (default: no) [yes, no]:

After upgrading [PRIMECLUSTER 4.3A20]

The use of the -f (force) flag could cause your data to be corrupted and could cause your node to be killed. Do not continue if the result of this forced command is not clear.

The use of force flag of hvswitch overrides the RMS internal security mechanism. In particular RMS does no longer prevent resources, which have been marked as "ClusterExclusive", from coming Online on more than one host in the cluster. It is recommended to double check the state of all affected resources before continuing.

IMPORTANT: This command may kill nodes on which RMS is not running in order to reduce the risk of data corruption!

Ensure that RMS is running on all other nodes. Or shut down OS of the node on which RMS is not running.

Do you wish to proceed ? (default: no) [yes, no]:

Note

None.