crm_verify(8) [suse man page]

CRM_VERIFY(8)							  [FIXME: manual]						     CRM_VERIFY(8)

NAME

       crm_verify - check the CIB for consistency

SYNOPSIS

	   crm_verify [-V] -x file

	   crm_verify [-V] -X string

	   crm_verify [-V] -L|-p

	   crm_verify [-?]

DESCRIPTION

       crm_verify checks the configuration database (CIB) for consistency and other problems. It can be used to check a file containing the
       configuration or can it can connect to a running cluster. It reports two classes of problems, errors and warnings. Errors must be fixed
       before Heartbeat can work properly. However, it is left up to the administrator to decide if the warnings should also be fixed.

       crm_verify assists in creating new or modified configurations. You can take a local copy of a CIB in the running cluster, edit it, validate
       it using crm_verify, then put the new configuration into effect using cibadmin.

OPTIONS

       --help, -h
	   Print a help message.

       --verbose, -V
	   Turn on debug information.

	       Note
	       Increase the level of verbosity by providing additional instances.

       --live-check, -L
	   Connect to the running cluster and check the CIB.

       --crm_xml string, -X string
	   Check the configuration in the supplied string. Pass complete CIBs only.

       --xml-file file, -x file
	   Check the configuration in the named file.

       --xml-pipe, -p
	   Use the configuration piped in via stdin. Pass complete CIBs only.

EXAMPLES

       Check the consistency of the configuration in the running cluster and produce verbose output:

	       crm_verify -VL

       Check the consistency of the configuration in a given file and produce verbose output:

	       crm_verify -Vx file1

       Pipe a configuration into crm_verify and produce verbose output:

	       cat file1.xml | crm_verify -Vp

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

SEE ALSO

       ???

AUTHOR

       crm_verify was written by Andrew Beekhof.

[FIXME: source] 						    07/05/2010							     CRM_VERIFY(8)

PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME

       Pacemaker - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_shadow (query|command) [modifiers]

DESCRIPTION

       crm_shadow - Perform configuration changes in a sandbox before updating the live cluster.

       Sets  up an environment in which configuration tools (cibadmin, crm_resource, etc) work offline instead of against a live cluster, allowing
       changes to be previewed and tested for side-effects.

OPTIONS

       -?, --help
	      This text

       -$, --version
	      Version information

       -V, --verbose
	      Increase debug output

   Queries:
       -w, --which
	      Indicate the active shadow copy

       -p, --display
	      Display the contents of the active shadow copy

       -E, --edit
	      Edit the contents of the active shadow copy with your favorite $EDITOR

       -d, --diff
	      Display the changes in the active shadow copy

       -F, --file
	      Display the location of the active shadow copy file

   Commands:
       -c, --create=value
	      Create the named shadow copy of the active cluster configuration

       -e, --create-empty=value
	      Create the named shadow copy with an empty cluster configuration

       -C, --commit=value
	      Upload the contents of the named shadow copy to the cluster

       -D, --delete=value
	      Delete the contents of the named shadow copy

       -r, --reset=value
	      Recreate the named shadow copy from the active cluster configuration

       -s, --switch=value
	      (Advanced) Switch to the named shadow copy

   Additional Options:
       -f, --force
	      (Advanced) Force the action to be performed

       -b, --batch
	      (Advanced) Don't spawn a new shell

       -a, --all
	      (Advanced) Upload the entire CIB, including status, with --commit

EXAMPLES

       Create a blank shadow configuration:

	      # crm_shadow --create-empty myShadow

       Create a shadow configuration from the running cluster:

	      # crm_shadow --create myShadow

       Display the current shadow configuration:

	      # crm_shadow --display

       Discard the current shadow configuration (named myShadow):

	      # crm_shadow --delete myShadow

       Upload the current shadow configuration (named myShadow) to the running cluster:

	      # crm_shadow --commit myShadow

AUTHOR

       Written by Andrew Beekhof

REPORTING BUGS

       Report bugs to pacemaker@oss.clusterlabs.org

Pacemaker 1.1.10-29.el7 					     June 2014							      PACEMAKER(8)