volmigrate, volunmigrate - Moves AdvFS domain storage from
physical storage to LSM volumes (volmigrate) or from LSM
volumes to physical storage (volunmigrate)
/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...
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 distinguish 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, the
default behavior is to assume the rootdg disk
group. Use -g dg1 to specify the disks belonging to
the dg1 disk group.
If every disk group contains uniquely named disks,
the -g diskgroup option is not necessary. Permits
the migration of a domain to a volume (with volmigrate)
or from a volume to physical storage (with
volunmigrate) 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 an LSM volume
or to physical storage that is smaller than the
in-use area of the domain.) Does not reverse any
changes made if an error occurs. 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. Used with volmigrate only.
Specifies the number of columns to stripe the volume
across. The number count must be greater than
1. 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. 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. For
internal use only. Executes the command in debug
mode.
Specifies the AdvFS file domain to move into or remove
from an LSM volume. All filesets within the domain must
be mounted. Used with volmigrate only. Specifies the LSM
disk, by disk media name, to use in creating the LSM volume.
Used with volunmigrate only. Specifies the disk partition
that the domain will occupy after the migration.
The disk partition cannot be under LSM control.
The volmigrate and volunmigrate commands are available on
both standalone systems and clusters. The volmigrate command
moves an AdvFS domain from physical storage to an LSM
volume and leaves the original storage unused. This permits
you to use the LSM storage management capabilities,
such as mirroring, on the volume. In a cluster, you can
migrate any domain including the cluster_root domain but
not the boot partitions on cluster members (rootmemberID_domain#root).
On a standalone system, you can
migrate any domain except the root_domain. (To place the
root domain under LSM control, use the volencap command.)
The volunmigrate command moves an AdvFS domain from an LSM
volume or volumes to physical storage and removes the LSM
volume or volumes. This command operates on any AdvFS
domain that uses only LSM volumes for its storage.
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.
Volmigrate [Toc] [Back]
With volmigrate, you must specify one or more LSM simple
or sliced disks, by their disk media names, to create the
LSM volume for the domain. The disks must already belong
to the disk group in which you intend to migrate the
domain. If two or more disk groups contain disks with the
same disk media names, use the -g diskgroup option to
indicate the correct disk group. (See volprint(8) or voldisk(8) for more information on choosing LSM disks for this
operation.)
The volmigrate command creates the volume with the specified
properties, moves the data from the domain to the LSM
volume, and removes the original storage from the domain.
The original storage is left unused. Migration occurs
while the system or cluster is running and does not
require you to unmount the filesets or reboot the system
or cluster.
One of the commands that volmigrate invokes is volassist.
Therefore, you can use the same attribute assignments (in
the form attr=value) with volmigrate as you can for volassist,
instead of using the options for volmigrate.
The syntax for using attribute assignment with volmigrate
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.
Volunmigrate [Toc] [Back]
With volunmigrate, you must specify one or more physical
disks or disk partitions, which cannot be under LSM control,
for the domain to use after the migration. The volunmigrate
command moves the data from the domain to the
physical storage, removes the LSM volume or volumes from
the domain, then destroys the volume or volumes 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 volunmigrate command does not permit
migrating a domain to storage that does not provide at
least as much space as the in-use portion of the domain;
that is, if the migration would result in loss of data.
For all domains except cluster_root, when you migrate the
domain to a mirrored volume, LSM adds a dirty-region log
(DRL) plex by default. LSM places the DRL on one of the
disks you specify for the migration, which is not an optimal
configuration. Ideally, the DRL plex should not share
a disk with the volume data. To correct this, after the
migration, you can add a new DRL plex to the volume, specifying
a different disk, and remove the original DRL plex.
The volmigrate and volunmigrate commands use the AdvFS
addvol and rmvol commands which are available only with
the AdvFS Utilities license.
LSM must be installed and running on the system or cluster,
all the filesets within the domain to be migrated or
unmigrated must be mounted, and there must be sufficient
simple or sliced disks in the target disk group to create
the volume for the domain. You must be superuser to run
these commands.
The following restrictions apply to volmigrate: You cannot
migrate the root_domain on a standalone system, or the
member boot partitions in a cluster (rootmemberID_domain#root).
The domain must consist of physical
disks to use the volmigrate command; it cannot contain LSM
volumes. You must specify LSM simple or sliced disks
(must contain an LSM private region). The command fails if
you specify a nopriv disk. 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 belong to the rootdg disk
group. The volmigrate command checks for this and returns
an error if they do not. For any cluster domain, the
disks you specify for the migration should be on a shared
bus so that cluster members have access to the domain
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 remaining
cluster members would not have access to that file system.)
The volmigrate command checks that the disks are
accessible by all cluster members, and returns an error if
they are not.
For example, in the following command, 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
domain 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
remaining cluster members would not have access to that
file system.) The volunmigrate command checks that the
specified partition meets this requirement, and returns an
error if it does not.
For example, in the following command, 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
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 To
migrate the cluster_var domain from an LSM volume to physical
storage (dsk6h) that provides only 5% more space than
the volume size, enter: # volunmigrate -f cluster_var
dsk6h
Specifies the command path.
Commands: hwmgr(8), volassist(8), voldisk(8), volencap(8),
volprint(8)
Cluster Installation, Logical Storage Manager
volmigrate(8)
[ Back ] |
