A command line utility that allows you to back up, restore, and reconfigure the quorum device. qrmutil is located in $SYBASE/$SYBASE_ASE/bin.
--additional_run_parameters=parameter_list
--buildquorum=[force]--cluster_take_over
--config_file=file_name
--diag={all | boot | toc | nodes | locks | config | cms}
--display={boot | nodes | heartbeat | master | cluster |
instance | config | state}
--drop_cluster=[force]
--drop_instance=instance_name
--errorlog=file_name
--extract_config=file_name
-h, --help
-F, --cluster_input=file_name
--fence_capable=device_path
-s, --instance=instance_name
--instance_node=node_name
--interfaces_dir=path_to_interfaces_file
--max_instances=number_of_instances
--master_dev=master_device
--primary_address=interconnect_address
--primary_port=port_number
--primary_protocol=protocol
-Q, --quorum_dev=quorum_device
--register_node=node_name
--secondary_address=interconnect_address
--secondary_port=port_number
--secondary_protocol=protocol
--traceflags=traceflag_list
--unregister_node=node_name
--verify_node=node_name
-v, --version]
--additional_run_parameters=parameter_list – parameters that unified agent uses to start the dataserver. Unlike other settings, dataserver does not read the additional run parameters. They are read by the unified agent and passed to the dataserver command line. If you include the --instance parameter, the additional run parameters apply to the specified instance. Otherwise, the additional run parameters apply cluster-wide.
--buildquorum[=force] – builds a new quorum device. Use =force to overwrite an exiting file or an existing quorum device on a raw partition. You must include the --cluster_input parameter with --buildquorum.
--config_file=config_file_name – if used with -instance, sets this path to the Adaptive Server configuration file for the specified instance. If -instance is not included, sets the path to the cluster-wide configuration file.
--diag={all | boot | toc | nodes | locks | config | cms} – for internal use only.
--display={boot | nodes | heartbeat | master | cluster | instance | config | state} – displays the current state of cluster or instance:
boot – displays the startup information for the cluster, including the version of the quorum device, any trace flags issued at startup, the boot id of the cluster, and any messages displayed at startup.
nodes – displays the registered management nodes.
heartbeat – displays heartbeat information for all nodes in the cluster.
master – displays master device information.
cluster – displays the cluster configuration.
instance – displays the instance configuration. You must include --instance=instance_name with this parameter.
config – displays configuration for the cluster and for all instances in the cluster.
state – displays the current state for the cluster and for all instances in the cluster.
--drop_cluster=[force] – drops a cluster and removes the quorum device. Use =force to force the drop if the quorum indicates the cluster is running.
WARNING! --drop_cluster removes the cluster.
--drop_instance=instance_name – Sybase internal use only.
WARNING! Use the sybcluster utility to drop an instance from the cluster.
--errorlog=log_file_name – full path to the error log for the specified instance. You must include the -instance_name parameter. Takes effect at next restart of the instance.
--extract_config=file_name – extracts the configuration area of the quorum device to the specified file.
-h | --help – qrmutil displays its full syntax.
-F | cluster_input=file_name – loads the cluster configuration from the specified cluster input file.
--fence_capable=device_path – tests if specified device can be fenced. Returns either “Device is fence capable” or “Device is not fence capable”.
-instance=instance_name – applies qrmutil parameters to a specified instance.
--interfaces_dir=interfaces_path – the path to a dirctory that contains a file named interfaces. If this parameter is used with --instance, it sets the path to the interfaces file for the specified instance. If --instance is not included, sets the path to the cluster-wide interfaces file.
--max_instances=number_of _instances – sets the maximum number of instances for the cluster configuration.
--master_dev=master_device_name – changes the master device the cluster uses.
--primary_address=inteconnect_address – changes the primary interconnect address for a given instance.
--primary_port=port_number – changes the starting port number for the primary interconnect for a given instance.
--primary_protocol=protocol – changes the protocol used for the primary cluster interconnect.
-Q | --quorum_dev=quoum_path – specifies the full path to the quorum device.
--register_node=node_name – registers a node for quorum management.
--secondary_address=inteconnect_address – changes the secondary interconnect address for a given instance.
--secondary_port=port_number – changes the starting port number for the secondary interconnect for a given instance.
--secondary_protocol=protocol – changes the protocol used for the secondary cluster interconnect.
--traceflags=trace_flag, trace_flag – changes the cluster-wide or the instance-specific trace flags for startup. If you do not include a list of trace flags, qrmutil clears the trace flags for the cluster instance.
--unregister_node=node_name – unregisters a node for quorum management.
--verify_node=node_name – indicates that the specified node is registered on the quorum device.
-v | --version – displays the version information for the qrmutil utility.
Example 1 This example changes the path to the error log to /sybase/opt/cluster/ASE-15_0/ase1.log:
qrmutil --quorum_dev=/dev/raw/raw101 --instance=ase1 --errorlog=/sybase/cluster/ASE-15_0/ASE-15_0/ase1.log
Example 2 This example registers the node “blade5” for mycluster:
qrmutil --quorum_dev=/dev/raw/raw101 --register_node=blade5
Example 3 This example creates a new quorum device for the cluster “mycluster”:
qrmutil --quorum_dev=/dev/raw/raw101 --cluster_input=/sybase/cluster/ase1.inp -buildquorum
Example 4 This example backs up the quorum device to /sybase/cluster_bak/quorum.bak:
qrmutil --quorum_dev=/dev/raw/raw101 --extract_config=/sybase/cluster_bak/quorum.bak
Example 5 This example restores the quorum device from the backup created in /sybase/cluster_bak/quorum.bak:
qrmutil --quorum_dev=/dev/raw/raw101 --cluster_input=/sybase/cluster_bak/quorum.bak --buildquorum=force
Example 6 This example displays the cluster configuration stored on the quorum device:
qrmutil --quorum_dev=/dev/raw/raw101 --display=config
Example 7 This example tests whether the named device can be fenced:
qrmutil --quorum_dev=/dev/raw/raw101 --fence_capable=/dev/raw/raw106
qrmutil is primarily a diagnostic utility. Sybase recommends using sybcluster to make configuration changes to the cluster.
You can pass up to 20 commands to qrmutil. However, you can specify the --instance= parameter only once.
If you specify --buildquorum, the quorum is built and qrmutil exits without running any commands other than --cluster_input.
qrmutil exits after it executes the --drop_cluster parameter.
This is an example of using multiple commands:
qrmutil --quorum_dev=/dev/raw/raw101 --display=cluster --register_node=blade1 --unregister_node=blade2 --verify_node=blade3
