This restoration process is very useful to restore the server from mksysb backup file, instead of using NIM resources like mksysb and spot.
By using alt_disk_mksysb command we can restore the system backup on separate disk without down the server. No downtime required. This is a online activity.
Minimum downtime required to reboot the server.
Steps are
1. Remove the old_rootvg image, if exists
# alt_rootvg_op -X old_rootvg
Note that the -X flag only removes the volume group place holder for the altinst_rootvg or old_rootvg.
2. To install mksysb image on hdisk1 .It will take few minutes to complete the installation wait until it is completed.
# alt_disk_mksysb -m /mksysb_images/my_mksysb -d hdisk1
alt_disk_mksysb flags
-d target_disk(s) – The disk or disks you want to clone to.
-m Specifies the location of the mksysb that you want to clone. The value for device can be: Tape / CD device OR path name of mksysb image in a file system.
3. Once completed above command, Verify bootable image is created on hdisk1 or not . For hdisk1 it has to show YES.
# ipl_varyon -i
4. If you got the downtime reboot the server with hdisk1(altinst_rootvg)
# bootlist -m normal -o
# bootlist -m normal hdisk1 hdisk0
# shutdown -Fr
Note :
If your rootvg was mirrored to hdisk0 & hdisk1 on the source system when you created the mksysb, and you want to alt_clone to a single disk, (hdisk2 on the target system, for example) using a customized image.data file located under /home/image.data, you would run the following:
# alt_disk_mksysb -m /usr/sys/inst.images/mksysb_filename -i /home/image.data -d hdisk2
-i image_data – image.data file to use instead of the default image.data file from mksysb image. The image.data file name must be a full path name (for example, /tmp/my_image.data).
For example if you have a customized image.data file. A common use of a custom image.data file would be to break the mirrors on the rootvg so you can install a mksysb backup with a mirrored rootvg environment to one disk
By using alt_disk_mksysb command we can restore the system backup on separate disk without down the server. No downtime required. This is a online activity.
Minimum downtime required to reboot the server.
Steps are
1. Remove the old_rootvg image, if exists
# alt_rootvg_op -X old_rootvg
Note that the -X flag only removes the volume group place holder for the altinst_rootvg or old_rootvg.
2. To install mksysb image on hdisk1 .It will take few minutes to complete the installation wait until it is completed.
# alt_disk_mksysb -m /mksysb_images/my_mksysb -d hdisk1
alt_disk_mksysb flags
-d target_disk(s) – The disk or disks you want to clone to.
-m Specifies the location of the mksysb that you want to clone. The value for device can be: Tape / CD device OR path name of mksysb image in a file system.
3. Once completed above command, Verify bootable image is created on hdisk1 or not . For hdisk1 it has to show YES.
# ipl_varyon -i
4. If you got the downtime reboot the server with hdisk1(altinst_rootvg)
# bootlist -m normal -o
# bootlist -m normal hdisk1 hdisk0
# shutdown -Fr
Note :
If your rootvg was mirrored to hdisk0 & hdisk1 on the source system when you created the mksysb, and you want to alt_clone to a single disk, (hdisk2 on the target system, for example) using a customized image.data file located under /home/image.data, you would run the following:
# alt_disk_mksysb -m /usr/sys/inst.images/mksysb_filename -i /home/image.data -d hdisk2
-i image_data – image.data file to use instead of the default image.data file from mksysb image. The image.data file name must be a full path name (for example, /tmp/my_image.data).
For example if you have a customized image.data file. A common use of a custom image.data file would be to break the mirrors on the rootvg so you can install a mksysb backup with a mirrored rootvg environment to one disk