unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Page:
Section:
Apropos / Subsearch:
optional field



volmigrate(8)							volmigrate(8)



NAME

  volmigrate, volunmigrate - Moves AdvFS domain	storage	from physical storage
  to LSM volumes (volmigrate) or from LSM volumes to physical storage (volun-
  migrate)

SYNOPSIS

  /usr/sbin/volmigrate [-g diskgroup] [-f] [-n]	[-m count] [-s count] [-l
  sectors] [-N volume_name] [-d] domain_name disk_media_name...

  /usr/sbin/volunmigrate [-f] [-n] [-d]	domain_name disk_partition...

OPTIONS

  -g diskgroup
      Used with	volmigrate only. Specifies the disk group in which to create
      the LSM volume for the domain.


				       Note

	 When migrating	the cluster_root domain, the resulting LSM volume
	 must belong to	the rootdg disk	group. The command fails if you
	 specify another disk group for	this volume.

      Use the -g option	to avoid confusion between disks with the same disk
      media name in more than one disk group; for example, if both the rootdg
      and dg1 disk groups contain disks	named disk01 and disk02. If you	want
      to specify the disks belonging to	the dg1	disk group, use	-g dg1.

      If every disk group contains uniquely named disks, the -g	diskgroup
      option is	not necessary.

  -f  When used	with volmigrate, permits migration to an LSM volume that pro-
      vides less than the recommended amount of	room for file system over-
      head, which is the size of the in-use area of the	domain plus 10%.
      (Does not	permit migration to an LSM volume smaller than the in-use
      area of the domain.)

      When used	with volunmigrate, permits migration of	a domain from an LSM
      volume to	physical storage that provides less than the recommended
      amount of	room for file system overhead, which is	the size of the	in-
      use area of the domain plus 10%. (Does not permit	migration to storage
      providing	less space than	the in-use area	of the domain, which would
      result in	data loss.)

  -n  Does not reverse any changes made	if an error occurs.

  -m count
      Used with	volmigrate only. Specifies the number of mirrors to create
      for the volume. The number count must be greater than 1.

      For all volumes with more	than one mirror, except	for the	cluster_root
      domain volume, a Dirty Region Log	(DRL) is enabled.

  -s count
      Used with	volmigrate only. Specifies the number of columns to stripe
      the volume across. The number count must be greater than 1.

  -l sectors
      Used with	volmigrate only. Specifies the size of the volume in sectors.
      Default is the size of domain.

      Use the -l option	to create a volume larger or smaller than the default
      size, which is the size of the domain. If	the domain is larger than the
      amount of	space currently	in use,	you can	create the volume sized	to
      encompass	only the in-use	area plus 10% extra room for file system
      overhead (recommended). You must use the -f option with the -l option
      to create	a volume that is less than 10% larger than the in-use area.
      You cannot create	a volume smaller than the in-use area of the current
      domain even with the -f option, as that would result in data loss.

  -N volume_name
      Used with	volmigrate only. Specifies the name of the volume. Default is
      the domain name with the suffix vol.  For	the cluster_root domain, the
      default volume name is cluster_rootvol. If you assign a different	name,
      there cannot be another volume with that name.

  -d  For internal use only. Executes the command in debug mode.

OPERANDS

  domain_name
	  Specifies the	AdvFS file domain to move into or remove from an LSM
	  volume.  The domain must be mounted.

  disk_media_name
	  Used with volmigrate only. Specifies the LSM disk, by	disk media
	  name,	to use in creating the LSM volume.

  disk_partition
	  Used with volunmigrate only. Specifies the disk partition that the
	  domain will occupy after the migration. The disk partition cannot
	  be under LSM control.

DESCRIPTION

  The volmigrate and volunmigrate commands are available on both standalone
  systems and clusters.

  LSM must be installed	and running on the system or cluster, the domain to
  be migrated or unmigrated must be mounted, and there must be sufficient
  disks	in the target disk group to create the volume for the domain. You
  must be superuser to run these commands.

    +  The volmigrate command modifies an AdvFS	domain,	including
       cluster_root on a cluster but excluding the boot	partitions on stan-
       dalone systems or cluster members, to use LSM volumes for its storage.
       This permits you	to use the LSM storage management capabilities,	such
       as mirroring, on	the volume.

    +  The volunmigrate	command	moves an AdvFS domain from an LSM volume to
       physical	storage	and removes the	LSM volume.  This command operates on
       any AdvFS domain	that is	comprised solely of LSM	volumes.




				     Note

       The volmigrate and volunmigrate commands	run in verbose mode by
       default.	These commands are scripts that	invoke other commands and
       display the called command and the input	parameters passed to it	by
       volmigrate or volunmigrate.  If errors occur, the command that
       experienced the error displays its own error messages or	codes.

       One of the commands that	volmigrate invokes is volassist. Because of
       this, you can use attribute assignment in the form attr=value, instead
       of the options listed previously. The assignable	attributes and values
       are the same as those supported for volassist. The syntax for volmi-
       grate when using	attribute assignment is	as follows:

       /usr/sbin/volmigrate [-g	diskgroup] [-f]	[-n] [-N volume_name]
       domain_name disk_media_name... [attr=value]

       See volassist(8)	for more information.

  With volmigrate, you must specify one	or more	LSM disks, by their disk
  media	names, to create the LSM volume	for the	domain.	 (See volprint(8) or
  voldisk(8) for more information on choosing LSM disks	for this operation.)
  The data from	the domain is moved to the LSM volume, and the original
  storage is removed from the domain and left unused. This occurs while	the
  system or cluster is running and does	not require you	to unmount the
  filesets or reboot the system	or cluster.

  With volunmigrate, you must specify one or more physical disks or disk par-
  titions for the domain to use	after the migration. The data from the domain
  is moved to physical storage.	The LSM	volume is removed from the domain,
  then removed completely after	the data is migrated. This occurs while	the
  system or cluster is running and does	not require you	to unmount the
  filesets or reboot the system	or cluster.

  The size of the partition or partitions you specify determines the size of
  the domain; the domain will use all the space	indicated. This	might be more
  than necessary. Use the LSM volprint command to display the size of the
  volume and choose one	or more	disk partitions	to accommodate the domain.

  The disk partition or	partitions specified must be large enough to hold the
  domain and allow for file system overhead of at least	10%. The volunmigrate
  command checks that the disk partition specified is large enough to meet
  this requirement. To use a partition that provides less than 10% extra
  space, use the -f option. The	operation fails	if the partition is not	large
  enough to accommodate	the current domain; that is, if	the migration would
  result in loss of data.

RESTRICTIONS

  The following	restrictions apply to volmigrate:

    +  The domain must consist of physical disks to use	the volmigrate com-
       mand; it	cannot contain LSM volumes.

    +  When migrating the cluster_root domain, the LSM volume must be created
       in the rootdg disk group.  Therefore, all the disk media	names you
       specify for this	domain must be in the rootdg disk group. The volmi-
       grate command checks that the disks belong to the rootdg	disk group
       and returns an error if they do not.

       In addition, the	LSM disk or disks for the cluster_root volume must be
       simple or sliced	disks (must contain an LSM private region).

    +  For any cluster domain, the disks should	be on a	shared bus so that
       cluster members have access to the disks	regardless of whether an
       individual cluster member is up or down.	(If a clusterwide file system
       were on a member's private bus and if that member crashed, the remain-
       ing cluster members would not have access to that file system.)

       The volmigrate command checks that the disks are	accessible by all
       cluster members.	If this	condition is not met, volmigrate returns an
       error.

       For example, disk dsk0 is on a private bus on one node in the cluster,
       while disk dsk16	is on a	private	bus on another node in the cluster.
       Both disks are accessible only when both	nodes are running. This	is
       not recommended,	as it creates an unbootable cluster_root domain.
	    # volmigrate -m 2 cluster_root dsk0	dsk16
	    volmigrate:	disks need to be accessible locally from at least one
	    cluster member



  The following	restrictions apply to volunmigrate:

    +  In a cluster, the partitions you	specify	for the	domain to occupy
       after removal from the LSM volume should	be on a	shared bus so that
       cluster members have access to the partitions regardless	of whether an
       individual cluster member is up or down.	(If a clusterwide file system
       were on a member's private bus and if that member crashed, the remain-
       ing cluster members would not have access to that file system.)

       The volunmigrate	command	checks that the	specified partition meets
       this requirement. If this condition is not met, volunmigrate returns
       an error.

       For example, disk dsk0 is on a private bus on one node in the cluster,
       while dsk16 is on a private bus on another node in the cluster. Both
       disks are accessible only when both nodes are running. This is not
       recommended, because it creates an unbootable cluster_root domain.
	    # volunmigrate cluster_root	dsk0g dsk16g
	    volunmigrate: disks	need to	be accessible locally from at least one
	    cluster member



EXAMPLES

    +  To migrate the cluster_root domain to an	LSM volume with	two mirrors,
       each of which is	striped	over four columns, enter:
	    # volmigrate -m 2 -s 4 cluster_root	dsk2 dsk4 dsk6 dsk8 dsk10 dsk12	dsk14 dsk16

    +  To migrate the tdmn domain to an	LSM volume named temp_vol with two
       mirrors,	enter:
	    # volmigrate -m 2 -N temp_vol tdmn dsk4 dsk8

    +  To migrate the cluster_root domain from an LSM volume to	physical
       storage,	enter:
	    # volunmigrate cluster_root	dsk5g dsk8g



FILES

  /usr/sbin/volmigrate,	/usr/sbin/volunmigrate
      Specifies	the command path.







SEE ALSO

  Commands: hwmgr(8), volassist(8), voldisk(8),	volencap(8), volprint(8)


  Cluster Administration, Cluster Installation,	Logical	Storage	Manager