tableau-parm(1) [debian man page]

tableau-parm(1) 														   tableau-parm(1)

NAME

       tableau-parm - Tableau Write-blocking Bridge Query/Command Utility

SYNOPSIS

       tableau-parm [-r] device

DESCRIPTION

       tableau-parm  is  designed  to interact with write-blocking forensics bridges produced by Tableau, LLC. It can be used to query bridges for
       various bridge and device data, as well as to disable DCO regions.

OPTIONS

       tableau-parm accepts the following parameters:

       -r     Directs tableau-parm to permanently remove a DCO, if it exists.  THIS WILL MODIFY THE STATE OF THE DRIVE. USE AT YOUR OWN RISK!  (It
	      is  recommended  for forensics investigations, that a full drive image be taken before this command is run, and then again afterward
	      if a DCO was detected originally.) Note: after running this, you'll need to restart the Tableau bridge for it  to  correctly  detect
	      the changes.

       device Required	argument.  Specifies  the device file for the bridge/drive to be queried. This must be a device presenting SCSI emulation.
	      Under Linux, all USB and FireWire mass storage devices behave like SCSI devices. Once a bridge and drive are plugged in and  powered
	      on, one can generally find out what the device was dynamically mapped to by running: dmesg | tail -20

OUTPUT

       tableau-parm  generates	simple output with one data value per line, interspersed with blank lines and section headers.	This output format
       is subject to change.

EXAMPLES

       To query a bridge which is mapped to /dev/sda:

	    tableau-parm /dev/sda

       To remove a DCO from the hard drive on /dev/sda:

	    tableau-parm -r /dev/sda

BUGS

       Older versions of ATA and SATA Tableau firmwares didn't properly handle HPA and DCO on some types of drives. Be sure to upgrade your block-
       ers' firmwares using the firmware update utility, version 4.2 or later, which was released on July 5, 2007.

       This  is  not really a bug, but something to note: when a drive has both an HPA and DCO section, and the DCO is removed, the HPA is removed
       with it. This is how the bridge firmware works, and isn't something controlled by tableau-parm. Just something to be aware of.

CREDITS

       Copyright (C) 2007,2009 Timothy D. Morgan

       Copyright (C) 1999,2001,2006,2007 D. Gilbert

       tableau-parm was written by Timothy D. Morgan using portions of SCSI example code written by D. Gilbert.

       Tableau, LLC cooperated in the development of this tool by providing documentation on the proprietary SCSI interfaces and assisted in test-
       ing.  Without their help, this tool would not have been possible. Tableau, LLC does not endorse or warrant this code in any way.

LICENSE

       Please see the file "LICENSE" included with this software distribution.

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

SEE ALSO

       hdparm(1) sdparm(1)

Forensics Utilities						 30 September 2009						   tableau-parm(1)

vxdco(1M)																 vxdco(1M)

NAME

       vxdco - perform operations on DCO objects and DCO volumes

SYNOPSIS

       vxdco [-g diskgroup] att volume dco

       vxdco [-g diskgroup] attlogvol dco dco_volume

       vxdco [-g diskgroup] [-o rm] dis dco

       vxdco [-g diskgroup] [-o rm] dislogvol dco

       vxdco [-g diskgroup] -o force enable dco

DESCRIPTION

       Note: The vxdco command can only be used with version 0 DCOs and DCO volumes.  It cannot be used with version 20 DCOs and DCO volumes.

       The  vxdco  command is used to manipulate version 0 data change objects (DCO objects or DCOs) and DCO volumes that allow the use of Persis-
       tent FastResync with volumes.

       The att operation attaches a DCO object, dco, to a volume, volume.  If the DCO object has an associated DCO volume, you can use the command
       vxvol set fmr=on volume to enable Persistent FastResync on the volume after the att operation has completed.

       The  attlogvol  operation  associates a DCO volume, dco_volume, with a DCO object, dco.	If the DCO object is already attached to a volume,
       you can use the command vxvol set fmr=on volume to enable Persistent FastResync on the volume after the attlogvol operation has completed.

       The dis operation dissociates a DCO object, dco, from a volume, and disables FastResync on that volume.	If the -o rm option is	specified,
       the DCO object, the DCO volume, its plexes and associated subdisks are removed in the same operation.

       The dislogvol operation dissociates a DCO volume from a DCO object, dco, and disables FastResync on the parent volume.  If the -o rm option
       is specified, the DCO volume, its plexes and associated subdisks are removed in the same operation.

       If an error occurs while reading or writing a DCO volume, it is detached and the badlog flag is set on the DCO.	(You can use  one  of  the
       options	-a, -F or -m to vxprint to check if the badlog flag is set on a DCO.)  The -o force enable operation clears the badlog flag on the
       DCO.

       The following command sequence demonstrates how to recover the DCO volume that tracks the top-level volume vol1 in the disk group egdg:

	      vxdco -g egdg -o force enable vol1_dco
	      vxvol -g egdg stop vol1
	      vxvol -g egdg start vol1

       Here vol1_dco is the DCO associated with vol1.

       Caution: Only use the -o force enable operation if you are certain that no writes have gone to the volume since	the  error  occurred  that
       caused its DCO volume to become detached.  Otherwise, data corruption may result.

       The -g diskgroup option specifies the disk group to which the parent volume, DCO object, and DCO volume belong.

       You  can  use the make keyword to vxassist to create a volume with an attached DCO object and DCO volume.  You can also use the addlog key-
       word to vxassist to create and add a DCO object and DCO volume to an existing volume.  vxdco may then be used to dissociate  a  DCO  object
       from its parent volume, and subsequently reattach it if the DCO object and DCO volume have not been removed.

       The  vxdco  command  is	also  used  by vxassist and vxplex to handle the DCO objects and DCO volumes that are associated with volumes. The
       vxmake command is used to create DCO objects, which can be specified using output from vxprint.

       Note: When using disk group move, split and join (see vxdg(1M)) to move volumes or snapshot volumes  between  disk  groups,  take  care	to
       ensure that the DCO volumes accompany their parent volumes.

EXIT CODES

       The  vxdco  utility  exits with a non-zero status if the attempted operation fails. A non-zero exit code is not a complete indicator of the
       problems encountered, but rather denotes the first condition that prevented further execution of the utility.

       See vxintro(1M) for a list of standard exit codes.

NOTES

       When a volume is attached to a DCO as its log volume, its device nodes are deleted. If vxdco dislogvol is subsequently used  to	dissociate
       the log volume from the DCO, the device nodes are not recreated.

SEE ALSO

       vxassist(1M), vxdg(1M), vxintro(1M), vxmake(1M), vxplex(1M), vxprint(1M), vxvol(1M)

VxVM 5.0.31.1							    24 Mar 2008 							 vxdco(1M)