ltdbtool(1) [centos man page]

LTDBTOOL(1)						   CTDB - clustered TDB database					       LTDBTOOL(1)

NAME

       ltdbtool - manipulate CTDB's local TDB files

SYNOPSIS

       ltdbtool [OPTION...] {COMMAND} [COMMAND-ARGS]

DESCRIPTION

       ltdbtool is a utility to manipulate CTDB's local TDB databases (LTDBs) without connecting to a CTDB daemon.

       It can be used to:

       o   dump the contents of a LTDB, optionally printing the CTDB record header information,

       o   convert between an LTDB and a non-clustered tdb by adding or removing CTDB headers and

       o   convert between 64 and 32 bit LTDBs where the CTDB record headers differ by 4 bytes of padding.

OPTIONS

       -e
	   Dump empty records. These are normally excluded.

       -p
	   Dump with header information, similar to "ctdb catdb".

       -s {0 | 32 | 64}
	   Specify how to determine the CTDB record header size for the input database:

	   0
	       no CTDB header

	   32
	       CTDB header size of a 32 bit system (20 bytes)

	   64
	       CTDB header size of a 64 bit system (24 bytes)

	   The default is 32 or 64 depending on the system architecture.

       -o {0 | 32 | 64}
	   Specify how to determine the CTDB record header size for the output database, see -s.

       -S SIZE
	   Explicitly specify the CTDB record header SIZE of the input database in bytes.

       -O SIZE
	   Explicitly specify the CTDB record header SIZE for the output database in bytes.

       -h
	   Print help text.

COMMANDS

       help
	   Print help text.

       dump IDB
	   Dump the contents of an LTDB input file IDB to standard output in a human-readable format.

       convert IDB ODB
	   Copy an LTDB input file IDB to output file ODB, optionally adding or removing CTDB headers.

EXAMPLES

       Print a local tdb in "tdbdump" style:

		 ltdbtool dump idmap2.tdb.0

       Print a local tdb with header information similar to "ctdb catdb":

		 ltdbtool dump -p idmap2.tdb.0

       Strip the CTDB headers from records:

		 ltdbtool convert -o0 idmap2.tdb.0 idmap.tdb

       Strip 64 bit CTDB headers from records, running on i386:

		 ltdbtool convert -s64 -o0 idmap2.tdb.0 idmap.tdb

       Strip the CTDB headers from records by piping through tdbrestore:

		 ltdbtool dump idmap2.tdb.0 | tdbrestore idmap.tdb

       Convert a local tdb from a 64 bit system for usage on a 32 bit system:

		 ltdbtool convert -s64 -o32 idmap2.tdb.0 idmap2.tdb.1

       Add a default header:

		 ltdbtool convert -s0 idmap.tdb idmap2.tdb.0

SEE ALSO

       ctdb(1), tdbdump(1), tdbrestore(1), ctdb(7), http://ctdb.samba.org/

AUTHOR

       This documentation was written by Gregor Beck

COPYRIGHT

       Copyright (C) 2011 Gregor Beck, Michael Adam

       This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
       the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

       This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with this program; if not, see http://www.gnu.org/licenses.

ctdb								    11/27/2013							       LTDBTOOL(1)

OCF_HEARTBEAT_CTDB(7)						OCF resource agents					     OCF_HEARTBEAT_CTDB(7)

NAME

       ocf_heartbeat_CTDB - CTDB Resource Agent

SYNOPSIS

       CTDB [start | stop | monitor | meta-data | validate-all]

DESCRIPTION

       This resource agent manages CTDB, allowing one to use Clustered Samba in a Linux-HA/Pacemaker cluster. You need a shared filesystem (e.g.
       OCFS2) on which the CTDB lock will be stored. Create /etc/ctdb/nodes containing a list of private IP addresses of each node in the cluster,
       then configure this RA as a clone. To have CTDB manage Samba, set ctdb_manages_samba="yes". Note that this option will be deprecated in
       future, in favour of configuring a separate Samba resource.

       For more information see http://linux-ha.org/wiki/CTDB_(resource_agent)

SUPPORTED PARAMETERS

       ctdb_recovery_lock
	   The location of a shared lock file, common across all nodes. This must be on shared storage, e.g.: /shared-fs/samba/ctdb.lock

	   (unique, required, string, no default)

       ctdb_manages_samba
	   Should CTDB manage starting/stopping the Samba service for you? This will be deprecated in future, in favor of configuring a separate
	   Samba resource.

	   (optional, boolean, default no)

       ctdb_manages_winbind
	   Should CTDB manage starting/stopping the Winbind service for you? This will be deprecated in future, in favor of configuring a separate
	   Winbind resource.

	   (optional, boolean, default no)

       ctdb_service_smb
	   Name of smb init script. Only necessary if CTDB is managing Samba directly. Will usually be auto-detected.

	   (optional, string, no default)

       ctdb_service_nmb
	   Name of nmb init script. Only necessary if CTDB is managing Samba directly. Will usually be auto-detected.

	   (optional, string, no default)

       ctdb_service_winbind
	   Name of winbind init script. Only necessary if CTDB is managing Winbind directly. Will usually be auto-detected.

	   (optional, string, no default)

       ctdb_samba_skip_share_check
	   If there are very many shares it may not be feasible to check that all of them are available during each monitoring interval. In that
	   case this check can be disabled.

	   (optional, boolean, default yes)

       ctdb_monitor_free_memory
	   If the amount of free memory drops below this value the node will become unhealthy and ctdb and all managed services will be shutdown.
	   Once this occurs, the administrator needs to find the reason for the OOM situation, rectify it and restart ctdb with "service ctdb
	   start".

	   (optional, integer, default 100)

       ctdb_start_as_disabled
	   When set to yes, the CTDB node will start in DISABLED mode and not host any public ip addresses.

	   (optional, boolean, default no)

       ctdb_config_dir
	   The directory containing various CTDB configuration files. The "nodes" and "notify.sh" scripts are expected to be in this directory, as
	   is the "events.d" subdirectory.

	   (optional, string, default "/etc/ctdb")

       ctdb_binary
	   Full path to the CTDB binary.

	   (optional, string, default "/usr/bin/ctdb")

       ctdbd_binary
	   Full path to the CTDB cluster daemon binary.

	   (optional, string, default "/usr/sbin/ctdbd")

       ctdb_socket
	   Full path to the domain socket that ctdbd will create, used for local clients to attach and communicate with the ctdb daemon.

	   (unique, optional, string, default "/var/lib/ctdb/ctdb.socket")

       ctdb_dbdir
	   The directory to put the local CTDB database files in. Persistent database files will be put in ctdb_dbdir/persistent.

	   (unique, optional, string, default "/var/lib/ctdb")

       ctdb_logfile
	   Full path to log file. To log to syslog instead, use the value "syslog".

	   (optional, string, default "/var/log/ctdb/log.ctdb")

       ctdb_debuglevel
	   What debug level to run at (0-10). Higher means more verbose.

	   (optional, integer, default 2)

       smb_conf
	   Path to default samba config file. Only necessary if CTDB is managing Samba.

	   (optional, string, default "/etc/samba/smb.conf")

       smb_private_dir
	   The directory for smbd to use for storing such files as smbpasswd and secrets.tdb. Old versions of CTBD (prior to 1.0.50) required this
	   to be on shared storage. This parameter should not be set for current versions of CTDB, and only remains in the RA for backwards
	   compatibility.

	   (unique, optional, string, no default)

       smb_passdb_backend
	   Which backend to use for storing user and possibly group information. Only necessary if CTDB is managing Samba.

	   (optional, string, default "tdbsam")

       smb_idmap_backend
	   Which backend to use for SID/uid/gid mapping. Only necessary if CTDB is managing Samba.

	   (optional, string, default "tdb2")

       smb_fileid_algorithm
	   Which fileid:algorithm to use with vfs_fileid. The correct value depends on which clustered filesystem is in use, e.g.: for OCFS2, this
	   should be set to "fsid". Only necessary if CTDB is managing Samba.

	   (optional, string, no default)

SUPPORTED ACTIONS

       This resource agent supports the following actions (operations):

       start
	   Starts the resource. Suggested minimum timeout: 90.

       stop
	   Stops the resource. Suggested minimum timeout: 100.

       monitor
	   Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10.

       meta-data
	   Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

       validate-all
	   Performs a validation of the resource configuration. Suggested minimum timeout: 30.

EXAMPLE

       The following is an example configuration for a CTDB resource using the crm(8) shell:

	   primitive p_CTDB ocf:heartbeat:CTDB 
	     params 
	       ctdb_recovery_lock=string 
	     op monitor timeout="20" interval="10" depth="0"

SEE ALSO

       http://www.linux-ha.org/wiki/CTDB_(resource_agent)

AUTHOR

       Linux-HA contributors (see the resource agent source for information about individual authors)

resource-agents UNKNOWN 					    06/09/2014						     OCF_HEARTBEAT_CTDB(7)