< Previous | Next > | |
Product: Volume Manager Manual Pages for Storage Foundation | |
Manual: Maintenance Commands (1m) |
vxrvgNAMEvxrvg - perform VERITAS Volume Manager operations on RVGs SYNOPSISvxrvg [-f] [-g diskgroup] -c checkpoint checkdelete rvg vxrvg [-f] [-g diskgroup] checkend rvg vxrvg [-f] [-g diskgroup] -c checkpoint checkstart rvg vxrvg [-g diskgroup] cplist rvg vxrvg [-g diskgroup] {-F [-r]|-M|-N} makeprimary rvg [rlink] vxrvg [-g diskgroup] makesecondary rvg [rlink] vxrvg [-f] [-g diskgroup] recover rvg vxrvg [-g diskgroup] resync rvg vxrvg [-g diskgroup] [-f] [-p] [-P prefix | -a] snapback rvg vxrvg [-g diskgroup] [-P prefix] [-o keepcache] snapdestroy rvg vxrvg [-g diskgroup] snapprint rvg vxrvg [-g diskgroup] [-P prefix] snaprefresh rvg vxrvg [-g diskgroup] [-f] [-P prefix] snaprestore rvg vxrvg [-g diskgroup] [-P prefix] [-F | -S] snapshot rvg [instantfull=volume_list] [instantso=volume_list] [plexbreakoff=volume_list] [exclude=volume_list] [plexprefix=plex_prefix] [cache=cachename | cachesize=size] [syncing={yes|no}] [comment="comment"] vxrvg [-f] [-g diskgroup] start rvg vxrvg [-f] [-g diskgroup] stop rvg vxrvg [-1] [-g diskgroup] getdatavols rvg vxrvg [-1] [-g diskgroup] getrlinks rvg vxrvg [-g diskgroup] [-z] [-i interval] [-t timestamp_freq] [-C count] stats rvg DESCRIPTIONThe vxrvg utility performs VERITAS Volume Manager (VxVM) operations on replicated volume groups (RVGs) that consist of VxVM Intelligent Service Provisioning (ISP) volumes or traditional VxVM (non-ISP) volumes. vxrvg is specific to VERITAS Volume Replicator (VVR), which requires a valid license. The first operand is a keyword that determines the specific operation to perform. Each operation can be applied to only one diskgroup at a time. The rvg operand is used to determine a default local disk group, according to the standard disk group selection rules described in vxdg(1M). A local disk group can be specified using the -g diskgroup option. KEYWORDSDeletes the specified Primary checkpoint. The required -c option specifies the checkpoint string that is marked in the SRL volume, and which needs to be deleted. After using the Primary checkpoints to synchronize the Secondary, they can be deleted by using the vxrvg -c checkpoint checkdelete rvg command. Marks the storage replicator log (SRL) volume associated with the specified RVG, rvg. Use this command only after you have finished copying all of the data volume data to a secondary site (see vxrvg checkstart). Marks the SRL volume associated with the specified RVG, rvg. Any writes to any of the data volumes subsequent to the checkstart are logged in the SRL volume until a subsequent vxrvg checkend is executed. The required -c option specifies a checkpoint string which is associated with the start and end marks in the SRL volume. Use this command before copying all of the data volume data to the secondary sites. The checkstart/checkend marks indicate the series of updates which the secondary must receive for it to become consistent. The secondary is inconsistent while these updates are in the process of being transmitted to it. This means that the secondary is not a valid candidate for a primary migration during this period. Displays information about all existing checkpoints that are associated with the specified RVG, rvg, including their name, size, and percentage of SRL used. If SRL usage reaches 100%, the checkpoint overflows and becomes unusable, as indicated by the output message "<Checkpoint overflowed>." Note that only primary checkpoints (created using vxrvg -c checkpoint checkstart on the primary) are associated with an RVG. Secondary checkpoints (created using vxrlink -c checkpoint pause on the secondary) are associated with the RLINK, and can be listed using vxrlink cplist. Converts a secondary RVG, rvg, to a primary RVG. In the event that the primary site fails, this command can be used to perform a failover using the -F or -N options. For a planned migration, the -M (migrate) option should be used. One of the options -F, -M, or -N must be specified with this command. The -r option may be specified with the -F option to perform an automatic resync of the RVG after a failover. Converts a primary RVG, rvg, to a secondary RVG. Note that all applications must be shut down and all data volumes must be closed. Recovers the specified RVG, rvg, after rebooting the system. Starts replay of a DCM that is active due to SRL overflow or failback logging. Replay occurs for all RLINKs on which the dcm_logging flag is set. If any of these RLINKs are disconnected or paused, resynchronization is delayed until this condition clears. Detaching a disconnected or paused RLINK clears the dcm_logging flag, and allows resynchronization to proceed on any remaining RLINKs. Reattaches snapshot volumes to their original volumes in the specified RVG, rvg. This operation is similar to the vxassist snapback command for traditional (third-mirror breakoff) snapshots, and to the vxsnap reattach command for full-sized instant snapshots. Note When performing a snapback operation on plex-breakoff snapshots, the vxrvg snapback command reattaches the plexes in the SNAPDONE state if the plexes were added using the vxsnap addmir command. Otherwise, it reattaches the plexes in the ACTIVE state. To reattach snapshot volumes, specify either the -P prefix option to reattach the set of snapshot volumes (one for each volume in the RVG) that has the specified prefix, or the -a option to reattach all snapshot volumes (multiple snapshot volumes for each volume in an RVG). Otherwise, vxrvg returns an error. If only one set of snapshots exists for the volumes in the RVG, neither option need be specified. Note If an RVG consists solely of VxVM ISP volumes, the -f (force) option must be specified when reattaching snapshot plexes. Otherwise, the operation fails and an error is returned. Snapshot volumes are usually reattached in a serial manner (one after another), which can take a long time if the snapshot volumes are large. The -p option can be used to reattach snapshots volumes in parallel. This is faster that reattaching them serially. Note The snapback operation can only be used with regular plex-breakoff snapshots, full-sized instant snapshots, and instant plex-breakoff snapshots. It cannot be used with space-optimized instant snapshots. Destroys (completely deletes) snapshot volumes. By default, this command deletes any cache object (used by space-optimized instant snapshots) together with the instant snapshots that have the specified prefix. To preserve a shared cache object, specify the -o keepcache option. Note The cache object is not destroyed if any other space-optimized instant snapshots are configured on it. Displays information on the relationships between the data volumes of an RVG and any corresponding snapshots. Refreshes existing snapshot volumes from all volumes in the specified RVG. This creates new point-in-time images for the snapshots, and the snapshots are immediately available for use with their new contents. The -P option can be used to restrict the refresh operation to snapshot volume names that begin with the specified prefix. Note Any applications that are running on the snapshot volumes must be closed before using this command. Restores the contents of all data volumes in the specified RVG from the corresponding snapshot volumes. The volume is immediately available with its restored contents. The -P option can be used to restrict the restore operation to snapshot volume names that begin with the specified prefix. Note The RVG must be stopped before proceeding with the restore operation. This command restores data on the Primary as well as on the Secondary host. When this command is used to restore the data on the Primary RVG volumes, it deletes all existing checkpoints. On the Primary, if the RLINKs are active and the volumes do not have DCM logs, the restore operation succeeds only if the -f (force) option is also specified. This detaches the Primary RLINK. On the Secondary, this command can be used only if the RLINKs are detached, or if the attached RLINKs are in the fail state. When the restore operation is in progress, the RVG is put into DCM logging mode. The changes that are applied to the volume on the Primary, as part of the restore operation, are not replicated on the Secondary until the vxrvg resync command is run. Note This operation can only be used with instant snapshots. Creates snapshot volumes for all volumes in the specified RVG, rvg. This operation is similar to the vxassist snapshot command for traditional (third-mirror breakoff) snapshots, and to the vxsnap make command for instant snapshots. The traditional snapshot operation takes an attached temporary mirror, and creates a new volume with the broken-off mirror as its plex. The vxassist snapstart command is normally used to create the snapshot plex. Instant snapshot operations create full-sized or space-optimized instant snapshots. Full-sized instant snapshots may be created by plex breakoff, or by using a volume that you created earlier. Note If the RVG consists of VxVM ISP volumes, you can create only full-sized or space-optimized instant snapshots. Full-sized instant snapshot volumes should be created using a naming convention such as prefix-data_volume_name. If you do not specify a prefix, the naming convention is SNAP-data_volume_name. Note Make sure that the original volumes and any required snapshot volumes (for full-sized instant snapshots that are created in this way) have been prepared before creating instant snapshots. For more information, see the vxsnap(1M) manual page. If volumes are not prepared in advance, the default behavior of the snapshot operation is to create traditional snapshots. For plex-breakoff snapshots, the plexprefix attribute can be used to specify the specific plexes that are to be used as snapshot plexes. If this is done, plexes should be created using a naming convention such as plex_prefix-data_volume_name. If the plexprefix attribute is not specified, a plex in the SNAPDONE state is chosen for the snapshot operation. Note When creating instant plex-breakoff snapshots, it is recommended that the vxsnap addmir command is used to add the plexes. For more information on creating the mirrored plexes, see the vxsnap(1M) manual page. You can use the -P option to specify the prefix that is used for the creation of snapshot volumes. For example, a data volume named hr_dv01 might have snapshot volumes named june-hr_dv01, july-hr_dv01 and so on. For space-optimized instant snapshots, a common (shared) cache object can be created before creating the snapshots. Alternatively, a separate cache object can be created for each snapshot by specifying the cachesize attribute to the vxrvg snapshot command. This attribute cannot be used with an RVG that consists solely of VxVM ISP volumes. Note The second method creates a cache object for the snapshots that cannot be preserved by specifying the -o keepcache option to the snapdestroy operation. When creating instant snapshots the following attributes may be specified to the vxrvg snapshot operation: Specifies the name of a cache object (created in advance) that can be shared between several space-optimized instant snapshots. The snapshots are created on this cache object. This attribute can only be specified when creating instant space-optimized snapshots using the -S option or the instantso attribute. This attribute cannot be specified in conjunction with cachesize. Specifies the size of the cache object that is to be used by a space-optimized instant snapshot. This attribute creates a separate cache object with a cache volume of the specified size for each space-optimized snapshot. This attribute can only be specified when creating instant space-optimized snapshots using the -S option or the instantso attribute. This attribute cannot be specified in conjunction with cache. If an RVG consists solely of VxVM ISP volumes, you cannot use this attribute to create the cache object. Instead you must set up the cache object before creating the snapshots. Associates a description (having a maximum length of 40 characters) with the snapshot volume. Specifies a comma separated list of volumes for which no snapshots are to be created. Specifies a comma-separated list of volumes for which full-sized instant snapshots are to be created. This attribute cannot be used with the -F option. Specifies a comma-separated list of volumes for which space-optimized instant snapshots are to be created. This attribute cannot be used with the -S option. Specifies a comma-separated list of volumes for which full-sized plex-breakoff instant snapshots are to be created. Specifies a prefix for the plexes that are to be used for creating the plex-breakoff snapshots as defined by plexbreakoff. The -F and -S options may not be specified with this attribute. Specifies whether the snapshot volumes for full-sized instant snapshots must be synchronized. If set to yes (the default), the volumes are synchronized in the background. The synchronization can be stopped or started as required. This attribute is not valid for space-optimized instant snapshots. Starts the specified RVG, rvg. This enables I/O accesses to the associated data volumes. The data and SRL volumes must be ACTIVE. The RVG is set to the ACTIVE state. Stops the specified RVG, rvg. This disables I/O accesses to the associated data volumes. The RVG is set to the CLEAN state. Displays names of all data volumes that are associated with the specified RVG, rvg. Displays names of all rlinks that are associated with the specified RVG, rvg. Displays application statistics for the given RVG, rvg. This is only valid on the primary. The -i interval option allows the stats command to be executed at the given interval. The -t timestamp_freq option displays the system date at the given frequency. The -C count option displays the stats the specified number of times. The -z option resets the stats for the given RVG. The values displayed are: Number of times that the application attempted to read from a data block that was currently being written to. Maximum number of threads writing at any point in time. Average number of threads performing writes. Maximum write size (in 1024-byte blocks) observed on any data volume in the RVG. Average write size reported in 1024-byte blocks. OPTIONSDisplays the output in one column. This option can only be used with either the getdatavols or getrlinks keywords. Specifies that the snapback operation is to reattach all snapshot volumes that are associated with volumes in the specified RVG. Required with the checkstart and checkdelete keywords. The checkpoint string is associated with the checkstart and checkend marks in the SRL volume (see vxrvg checkstart). It can be printed with vxprint -l rvg, but is overwritten in the RVG record by a subsequent vxrvg checkstart command (although it persists in the SRL volume until entries written to the SRL volume eventually wrap around and overwrite it). For the checkstart, checkdelete, checkend, recover, start and stop keywords, this option forces the operation to be performed even if the RVG is in use by another utility. For the checkdelete keyword, this option allows a checkpoint to be deleted even if the checkend operation has not finished. For the start keyword, this option allows an RVG to be started in PASSTHRU mode. For the stop keyword, this option allows an RVG to be stopped even if it is open or mounted. For the snaprestore keyword, this option forces the operation to be performed when the RLINKs are active, but have not been enabled for DCM logging. For the snapback keyword, this option allows snapshot plexes to be reattached in the case when an RVG consists solely of VxVM ISP volumes. When specified with the makeprimary operation, enables failback logging during a failover. When specified with the snapshot operation, full-sized instant snapshots are created. Specifies the local diskgroup for the operation either by name or by disk group ID (see vxdg(1M) for more information on disk groups). Executes the stats command every interval seconds. With the stats command, displays the system date every timestamp_freq seconds. Executes the stats command count times. Used with the stats command to reset the stats for a given RVG. Performs a controlled migration from a secondary RVG to a primary RVG. This option is only used with the makeprimary keyword. Disables failback logging when performing a failover. This option is only used with the makeprimary keyword. Preserves the cache object when used with the snapdestroy keyword. Allows the snapback operation to reattach snapshots to their original volumes in parallel. With the snapshot operation, assigns names to created snapshot volumes with the format prefix-volume_name, where volume_name is the name of the original volume. With the snapback operation, reattaches only those snapshot volumes that have names beginning with the specified prefix. Uses vxrvg resync to perform an automatic resynchronization of the RVG after a failover. This option may only be specified with the -F option to the makeprimary keyword. When specified with the snapshot operation, space-optimized instant snapshots are created. EXIT CODESThe vxrvg 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. SEE ALSOvxassist (1M), vxdg (1M), vxedit (1M), vxintro (1M), vxmake (1M), vxprint (1M), vxrlink (1M), vxsnap (1M), vxvol (1M) |
^ Return to Top | < Previous | Next > |
Product: Volume Manager Manual Pages for Storage Foundation | |
Manual: Maintenance Commands (1m) | |
VERITAS Software Corporation
www.veritas.com |