Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3376
  • Last Modified:

Mirroring rootvg - risks if any and tips

I would like to mirror an existing rootvg in a 4.3.2 box which currently has a single physical volume.  I have some spare drives to add and create the new volume group to mirror with.  

Since the system has ran for a few years - I would assume that mirroring would replicate all of its data to the mirrored volume group safely..?

Any tips or recommendations with rootvg mirroring would be appreciated.
  • 3
  • 3
1 Solution
Mirroring is a stand feature of AIX and it is no risk. Last month I mirrored 8 volume groups to migrate data from HDS 9200 to HDS 9570 and the process was very smooth.

Procedure to mirror rootvg and assume the new mirror pv is hdisk1 and your rootvg  has only  hdisk0 is the current boot disk.
The size of hdisk1 must be equal to or bigger than hdisk1.

1. extendvg rootvg hdisk1
2. mirrorvg rootvg
3. lsvg -l rootvg
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
hd5                 boot       1     2     2    closed/syncd  N/A
paging01            paging     10    20    2    open/syncd    N/A
hd8                 jfslog     1     2     2    open/syncd    N/A
hd4                 jfs        2     4     2    open/syncd    /

Note : the number of PPs of each filesystem is double the number of LPs. If not, the LV has one copy.
4. bosboot –a –d /dev/hdisk1  (write the bootstrap record)
5. bootlist -m normal -r  (display the current bootlist)
6. bootlist -m normal hdisk0 hdisk1
7. bootlist -m normal -r  (double checkt hdisk1 is added to bootlist)

Step 4 to 7 is optionlal but usually most system programmers writes the bootstrap record and hdisk1 to bootlist and it is the purpose of mirror rootvg.

nsomeAuthor Commented:
Thanks cpc2004.  I speculate that the mirror volume group within smitty would perform the same tricks (i.e. extend rootvg hdisk1?)

In the event of a failure of one of the disks within a mirrored rootvg, what would be the impact on the system?  Ideally the system would continue functioning within its hdisk0 of the mirror while the replacement drive is loaded and mirrored again (correct?)

I need to setup a DR procedure in the event a disk goes for a mirrored rootvg configuration.

Again, much thanks.
Yes, you can use smit to do the rootvg mirroring. I use AIX command as it is more easy for you to understand as I don't have to capture the screen.

If a mirrored volume is scratch, it has no impact to AIX. However you must have a monitoring tools or a cron job to check the status of the rootvg mirroring and errpt entry relating to rootvg mirroring is broken. Hence you can call IBM CE replace the faulty hdisk. Usually IBM CE will unmirror the rootvg, reducevg and remdev the faulty hdisk.  Replace the faulty hdisk. Issue cfgmgr to add the new hdisk. Repeat the procedure of the previous post to mirror the rootvg.
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

nsomeAuthor Commented:
nsomeAuthor Commented:
One more question cpc2004

In a mirrored rootvg configuration, is management of data I/O to all pv's associated with the rootvg mirror transparent to the OS kernel and its activities?  In a failure of one PV, data is only written to the good PV - thus not affecting in any way the instance of the OS?

Yes, this is the purpose of mirrored disk. One mirrored PV failure does not affect the data integrity of the the mirrored disk.

quick comment, check that your volume group QUORUM is set to off, since AIX uses it to define whether to vary on or not a volume group based on the number of surving hdisks, since the initial disk in a volume group has 2 votes and the next have only 1 if the first disk fails AIX will decide the QUORUM limit was not met and it will not be able to vary the volume group... u do this using ....

chvg -Q n

I would not recommend mirroring the paging space, unless you want to prevent the system from crashing if one of the disks fails. the problem with this is that mirroring the paging will hit you very hard if your server starts paging, if you can afford a reboot, that would be the way to go.

Also, make sure you dont define your primary dump device on the same disk as the secondary (and do not mirror such devices) I believe that AIX still uses /dev/hd6 as the default dump device, but not 100% sure since we seldom do installs from scratch anymore. you can verify which devices are defined as dump devices using the following command..

/htdocs/esv# sysdumpdev -l           <- small L
primary              /dev/hd7
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON

on this particular system the primary dump device is hd7 and there is no secondary dumpdevice, but this is not a production server, we do not mirror paging space on some servers and we make sure that the lv's associated as dump devices are not mirrored, since the failing componet might be the LVM manager which would be in charge or capturing the dump to disk since a mirrrored device is involved.


Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now