Use the Verify and Synchronize task
to validate the cluster configuration, reconfiguration, or changes
and commit them to the cluster by updating all nodes with the same
view of the configuration.
Verify and synchronize your cluster configuration after changes
are made within a cluster. Those changes include, for example, changes
to the hardware operating system, node configuration, or cluster configuration.
Attention: Synchronizing a cluster might delete or
alter information in the cluster. Save a snapshot of the cluster before
you synchronize changes.
Fields
- Action to perform
- Provides a list of options for verifying and synchronizing a cluster.
- Verify only
- Runs only the verification process. When this option is selected,
only the Force synchronization if verification fails option
is disabled.
- Synchronize only
- Runs only the synchronization process. When this option is selected,
all of the other options are disabled.
- Verify and Synchronize
- Runs the verification and synchronization processes. When this
option is selected, all of the other options are enabled. If the verification
process completes successfully, by default, the synchronization process
runs. You can use the Force synchronization if verification fails with
the Verify and Synchronize option.
- Verify
- Provides a list of verification options.
Note: If you changed the
operating system configuration on one or more of the nodes in your
configuration, select the Entire configuration option.
- Entire configuration
- By default, runs a complete check of the topology and resources
of a configuration.
- Unsynchronized changes only
- Runs verification checks on only the changes which have taken
place in the ODM files since the time of the last verification operation.
- Correct errors found during verification
- Select an option for correcting verification errors.
- No
- By default, verification errors are reported but are not corrected.
- Yes
- Prompts you to correct common configuration issues before starting
cluster services.
- Force synchronization if verification fails
- Select Yes or No from the menu.
- No
- By default, if the verification process returns errors, the synchronization
process does not run.
- Yes
- Forces a synchronization process regardless of the results of
the verification process.
Attention: This option is
not recommended. If you must use this option, ensure that you understand
the effects of these cluster configuration changes.
- Log file to store verification output
- Specifies the log file name that is used for storing the verification
output. By default, the output is stored in the clutils.log file.
- Terminate verification after this many errors
- Sets a limit for the number of errors that can occur before the
program ends. The default is 10. You can change this value by entering
a new value ranging from 0 to x, where x is a whole
number.
- Verification methods to run
- Provides a list of verification options to run.
- Pre-installed only
- By default, runs only preinstalled verification methods.
- Custom only
- Runs only the custom verification methods.
- Pre-installed and custom
- Runs both the preinstalled and custom verification methods.
- Custom verification methods
- Select one or more custom verification methods. By default, none
are selected.