Image of AIX image and clone learning Notes

I am very entangled in the cloning and mirroring technologies of the aix system. I have read many documents and summarized them. Please criticize and correct them. Image: The same data as the source data, and synchronously update and clone the source data: copy the source data at a certain time point, the same data volume and source data snapshot: the source data at a certain time point, refers... information & n is very entangled in the cloning and mirroring technologies of the aix system. I have read many documents and summarized them. Please criticize and correct them.
Image: same data as source data, and synchronously updated with source data
Clone: copy source data at a certain time point. The data volume and source data are the same.
Snapshot: the source data at a certain point in time. it is a pointer (not mentioned here)
I. image technology
It is generally used for system Backup. I think it is like raid1, mainly at the system level.
Steps:
The general steps are: add a new hard disk, scan the device, check whether the device is normal, add a pvid, add a volume group, perform mirror, add boot information to the new hard disk, and reset the boot sequence.
1. lsp view physical volumes. This is because no new hardware is found. we will start scanning the device.
Cfgmgr-v
2. after the new hardware is found, we need to look at the properties of the physical volume.
Lsdev-Cc disk
The new physical volume does not have the pvid.
3. add a pvid.
Chdev-l hdiskn-a pv = yes
N in hdiskn represents a variable, which represents the new disk label.
You can also use chdev-l hdisk1-a pv = clear to delete the pvid.
4. join the volume Group
Extendvg rootvg hdiskn // if there is data in hdiskn while doing extend, there will be no content in hdiskn
This is also the premise that two disks are used for mirror, because all the disks used for mirroring must be in the same volume group.
5. create mirror
Mirrorvg-c 2 rootvg
There are only two scenarios for mirror: two or three disks for mirroring. If there are two, we can also do this directly:
Mirrorvg rootvg because it is two by default, it is not necessary to specify the source and target disks. However, if three disks are used as images, you must specify the source and target disks.
Mirrorvg-c 3 rootvg hdisk0 hdisk1
6. verify that mirror is created successfully.
Lsvg-l rootvg
View the pps ing between pps and pvs. indicates no success, indicates successful dual-disk image, indicates successful 3 disk image.
You can also use lsvg rootvg to check the content of QUORUM.
QUORUM: 1 indicates no,
QUORUM: 2 indicates yes.
7. provide new boot information for the new disk
View the current boot sequence
Bootlist-m normal-o
Add boot information to hdiskn
Bosboot-ad/dev/hdiskn
Reset the boot sequence to give hdiskn the highest priority. The system cannot be started.
Bootlist-m normal hdiskn hdisk0 cdrom
8. restart the system
Shutdown-Fr
Undo mirror
1. remove the mirror of rootvg.
Unmirrorvg rootvg hdiskn
2. remove the hdiskn boot information
Chpv-c hdisk1
3. reset the startup sequence
Bootlist-m normal hdisk0
Lab:
# Lspv
# Chdev-l hdisk1-a pv = clear
# Chdev-l hdisk1-a pv = yes
# Lspv
# Extendvg rootvg hdisk1
// If hdisk1 has data in extend, the data in hdisk1 will be gone.
Old hdisk1 disk above
The following hdisk1 is a new disk.
# Extendvg rootvg hdisk1
# Mirrorvg-m rootvg hdisk1 or smitty mirrorvg select background mode
# Bosboot-ad/dev/hdisk1
# Bootlislt-m normal hdisk0 hdisk1 cd0 which is in front of the device, first boot from the device
# Shutdown-Fr
Check whether it is mirror,
# Lsvg-l rootvg
Note: LPx2 = PP indicates an image, LP = PP indicates that no image is made, and LPx3 = PP indicates that there are two images. LPx2 = PP refers to a copy of LP data, which corresponds to two copies of PP data. There are two physical copies.
 
You can also modify the startup list.
# Bootlislt-mnormal hdisk1 hdisk0 cd0 let hdisk1 boot the system and check the scsi ID
# Lsvg rootvg
Description: AIX: rootvg image. Enable both hard disks. Benefits: when the hard disk is hard to be started, you can use another hard disk to start the machine.
Note:
Chdev-l hdisk1-a pv = yes
It is safe. if it fails to run, it will certainly fail to be created because mkvg is called.
Postscript: remove image
# Unmirrorvg rootvg hdisk1 // remove the mirror of rootvg
# Chpv-c hdisk1 // remove the hdisk1 boot information
# Reducevg rootvg hdisk1 // delete hdisk1 from rootvg
# Rmdev-dl hdisk1 // delete a hardware device (add-R to force the device to be deleted)
# Bootlist-m normal hdisk0

From wolf