Steps run to extend a logical volume - assure_mimix

Steps run to extend a logical volume - assure_mimix - 6.0

Assure MIMIX for AIX Guide

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software for AIX

Version

6.0

ft:locale

en-US

Product name

Assure MIMIX for AIX

ft:title

Assure MIMIX for AIX Guide

2025

First publish date

2003

ft:lastEdition

2025-10-08

ft:lastPublication

2025-10-08T06:18:25.453000

The table below shows the order of the steps and commands that are run to extend a logical volume:

Order	Step	Command	When displayed
1.	Increase the maximum number of logical partitions on S. (S is production server, recovery server, recovery server 1, or recovery server 2)	`chlv -x <new LPs> <LV>`	If the maximum logical partitions value for the file system or logical volume will not support the new size.
2.	Extend the logical volume on the production server	`extendlv <LV name> <LP(s)>`	Always
3.	Extend the logical volume on recovery servers (Operates on all recovery servers)	`/usr/scrt/bin/extend_replica_lv -C <Context ID> -L <PVS LV>`	Always

Steps run when a configuration must be changed to increase the state map and region size

The table below shows the order of the steps and commands that are run when a configuration must be changed to increase the state map and region size. These steps are only run as a result of the Extend Logical Volume wizard. Steps 1 through 4 are run before the wizard is dismissed. The other steps will be displayed in the Configuration Window.

Order	Step	Command	When displayed
1.	Increase the maximum number of logical partitions on S. (S is production server, recovery server, recovery server 1, or recovery server 2)	`chlv -x <new LPs> <LV>`	If the maximum logical partitions value for the file system or logical volume will not support the new size.
2.	Unmount the file system on the production server.	rtumnt -C <Context ID>	If there is a mount point.
3.	Extend the logical volume on the production server	`extendlv <LV name> <LP(s)>`	If there is no mount point.
4.	Extend the file system on the production server	`chfs -a size=<new size>M <file system>`	If there is a mount point.
5.	Stop replication on the production server.	rtstop -FSC <Context ID>	Always
6.	Stop replication on the recovery server.	rtstop -FC <Context ID>	Always
7.	Stop replication on the recovery server 2.	rtstop -FC <Context ID>	If there is a recovery server 2 in this configuration.
8.	Save configuration.	-	Always
9.	Delete logical volume device special files on S. (S is production server, recovery server, recovery server 1, or recovery server 2)	scsetup -X	Always One message is displayed for each server.
10.	Delete snapshot container logical volumes on S. (S is the recovery server, recovery server 1, or recovery server 2)	scsetup -R -t jcontainer	Replication container logical volume(s) removed. One message is displayed for each server.
11.	Delete internal logical volumes.	scsetup -R -t smbitmap	Always One message is displayed for each server.
12.	Delete snapshot logical volumes on S. (S is the recovery server, recovery server 1, or recovery server 2)	scsetup -R -t pool	One message is displayed for each server.
13.	Copy configuration to S. (S is production server, recovery server, recovery server 1, or recovery server 2)	sccfgd_putcfg	Always One message is displayed for each server.
14.	Create failover context on S. (S is production server, recovery server, recovery server 1, or recovery server 2)	rtdr setup	If configuration has a failover server. One message is displayed for each server.
15.	Create containers and logical volumes on production server.	scsetup -M	Always
16.	Set all logical volumes as replicated.	scconfig -W	Always
17.	Create containers and logical volumes on S. (S is the recovery server, recovery server 1, or recovery server 2)	scsetup -M	Always One message is displayed for each server.
18.	Start replication on the recovery server 2.	rtstart -C <Context ID>	If there is a recovery server 2 in this configuration.
19.	Start replication on the production server.	rtstart -C <Context ID>	Always
20.	Start replication on the recovery server.	rtstart -C <Context ID>	Always. If there are more than one recovery servers configured, the label is: Start replication on recovery server 1.
21.	Extend replica logical volume on the recovery server.	/usr/scrt/bin/extend_replica_lv -C <Context ID> -L <PVS LV>	If there is no configured second recovery server.
22.	Extend replica logical volume on the recovery servers.	/usr/scrt/bin/extend_replica_lv -C <Context ID> -L <PVS LV>	If there are more than one recovery servers configured.