Sponsored Content
Operating Systems AIX DR using a mksysb image on disk. Post 302949249 by rbatte1 on Wednesday 8th of July 2015 12:37:10 PM
Old 07-08-2015
I suppose it goes back to "When you try to boot what will you see?" If you are using a partitioned server or a whole physical server it should not matter either way. If you can get the console opened and then power on/activate you would (if there are no usable boot devices) drop into the SMS menus. You can then probe to see what devices are visible. You can force this by pressing the appropriate key at the right time during the start-up. Do you know how to do that?

I suppose one question to ask is "Do you have a mirrored pair of disks for your root volume group?" which should give you some resilience. If you don't know, then the output from the following would be useful:-
Code:
lsvg -p rootvg
lsvg -l rootvg
lscfg -vl hdisk0
bootlist -om normal

As has been commented, you really need to force the mksysb off the server you may need to recover such that you can boot from it, so tape, DVD or NIM server (yes, I know you haven't got NIM) because then you can select that device from the SMS menus to boot from and (hopefully) it will all recover.


If you have other volume groups, then we can work on how to save the structure and/or contents. If you have Networker backing up data over the network Smilie, then you will probably just want the structure so you can recover that then restore your data.

The output from:-
Code:
lsvg
lsvg | grep -v rootvg | while read vg
do
  lsvg -p $vg
  lsvg -l $vg
done

.... will help us plan. The best place to store the structure information is somewhere in the root volume group so that it is recovered from a mksysb when you really need it.

if you can elaborate on what you have then I'm sure we can help. It would also be useful to know if the recovery would be to the same/similar server or if there are going to be differences, e.g. do you have LVM mirrored disks and the recovery server has hardware mirrors so you only have half the storage etc.

Don't worry if you don't have all the answers yet. We can work on them later.


Kind regards,
Robin
 

10 More Discussions You Might Find Interesting

1. AIX

mksysb and boot.image

hello i saved my system this morning, mksysb tape, and i have the message: "boot.image exceeded the size....." i have not the end because the message is disappeared. where can i find the mksysb message in a log ? the message is scary ? thank you (6 Replies)
Discussion started by: pascalbout
6 Replies

2. Filesystems, Disks and Memory

Disk image !!

Hi all, I have a SCSI hard disk drive (2GB) I'm installing on it solaris 5 and some other applications on a sun sparc workstation, I made an image file of this H.D using Norton Ghost 6, then I restored this image file on another H.D.D (4GB), I tried to boot the sun sparc workstation with this new... (0 Replies)
Discussion started by: wesweshahaha
0 Replies

3. Solaris

How to create a disk image

I have a whole bunch of solaris machines. How do i create an image so i dont have to keep doing a reload and. In the pC world we have ghost what about the solaris world? (3 Replies)
Discussion started by: frankkahle
3 Replies

4. AIX

How do I create a bootable mksysb image file

I have several systems which require software maintenance several times a year. After the software maintenance, it is required that we make two system tapes for DR purposes. The creation of these system tapes takes anywhere from 1-1.5 hours because of the performance of the tape drives. What I... (7 Replies)
Discussion started by: acascianelli
7 Replies

5. Linux

disk image

when i made image of my fedora9 disk it had 18 GB. my new drive has 60GB. How can i expand the installed image to fit the entire new disk?. (2 Replies)
Discussion started by: ZG9
2 Replies

6. AIX

mksysb file image

Hello, I have an mksysb image in my disk, created like: # mksysb -i /mnt/backup/lpar2.image I want to know if this image could be copied to a tape and make it a boot image. Thanks Enzote (3 Replies)
Discussion started by: enzote
3 Replies

7. AIX

check whether a mksysb image is bootable or not?

Hi, Can any one please tell me the method to check whether a mksysb image which is in the server is bootable or not. :confused: Thanks in advance, Anoop (1 Reply)
Discussion started by: anoopraok
1 Replies

8. AIX

bootable mksysb image on

i have been given a bootable cd/dvd, that i install a ibm aix 185 workstation with, i want to make a nim mksysb resource from that, the following is a listing for the root file structure of the cd/dvd, seems someone took a mksysb of a built ibm aix machine and did mkcd -L -S -I and setup the... (2 Replies)
Discussion started by: asyed123
2 Replies

9. AIX

Restore mksysb image on cloned LPAR

Hi Folks, How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0) Let me know. Thank a lot. (1 Reply)
Discussion started by: snchaudhari2
1 Replies

10. UNIX for Advanced & Expert Users

Installation through mksysb image backup

Hi Experts, I am very new to AIX, I have a mksysb image in one of my aix server (V6), I would like to install this mksysb image on newly lpar. Is it possible without tape and NIM? Advice would be appreciated. Regards, Rockie (11 Replies)
Discussion started by: aix.rockie
11 Replies
vxrootmir(1M)															     vxrootmir(1M)

NAME
vxrootmir - create a mirror of a Veritas Volume Manager root disk SYNOPSIS
/etc/vx/bin/vxrootmir [-g diskgroup] [-t tasktag] [-p Pool_1,Pool_2,...] [[-v] [-b] [-R] root_mirror] DESCRIPTION
The vxrootmir command creates mirrors of all of the volumes on a Veritas Volume Manager (VxVM) rootable boot disk, and makes the new disk bootable. A disk to be used as a mirror can be specified either by its VM disk name (disk media name) or by its device name (disk access name). If a disk media name is specified, it is validated to make sure that it exists and that it has been properly initialized. This validation includes making sure that the private region is at the same location and has the same length as the private region on the primary root disk, and that the sum of the lengths of all of the subdisks located on the primary root disk will fit within the available space in the public region of the specified disk. If a disk access name is specified, it is validated to make sure it exists and is not in use, and that the total length of all the subdisks on the primary root disk will fit within the public region. The disk is then initialized to contain a private region with the same offset and length as the private region on the primary root disk. A new disk media name is assigned to the disk formed from the prefix rootdisk followed by the next available number (for example, rootdisk02, rootdisk03, and so on). All volumes that have a subdisk on the primary VxVM root disk are mirrored on the specified disk. When the root volume (rootvol) is mir- rored, the vxassist command executes vxbootsetup to set up the new disk as a boot disk. The -p option allows you to mirror the volumes on the root disk as stripe columns across several disks. The argument to this option is a list of disks that are to be used for the stripe column mirrors. If not enough disks are specified, vxrootmir prints a message to the standard error output, including information on how many disks are required, and then exits. When initialized for VxVM use, these stripe column disks are named with the prefix rootaux followed by the next available number (for example, rootaux01, rootaux02, and so on). OPTIONS
-b If the system was booted from the VxVM root disk that is being mirrored, this option uses the setboot command to set the alter- nate boot disk to the specified mirror. If the system was booted from another root disk (such as an LVM root disk), an alternate root disk is not set. If the -v option is also specified, information is displayed on the current setboot settings, and on whether the alternate boot disk is set to the specified mirror. -g diskgroup Specifies the boot disk group. -p Pool_1,Pool_2,... Specifies the disks that are to be used for stripe column targets when mirroring the VxVM root disk. The disks can be specified either as disk access names, or as disk media names if they have previously been initialized for use with VxVM. If specified as disk access names, the disks are checked for existence, correct size, and availability for use. -R Indicates that only the volumes required to boot successfully from the new mirror are to be mirrored. -t tasktag Marks any tasks that are registered to track the progress of an operation with the tag tasktag. This option is passed to vxas- sist when mirroring volumes, so any child tasks are also tagged with tasktag. -v Displays verbose output including timestamps for operations in progress. This option is useful as mirroring large volumes can take a long time. ARGUMENTS
daname Specifies the disk to be used as a mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as a mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxrootmir command being invoked in its simpliest form: /etc/vx/bin/vxrootmir c5t1d0 The next example shows how to use the -R option with vxrootmir. # /etc/vx/bin/vxrootmir -v -b -R c5t10d0 vxrootmir: 10:10: Gathering information on the current VxVM root configuration vxrootmir: 10:10: Checking specified disk(s) for usability vxrootmir: 10:10: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 10:10: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 10:10: Mirroring only volumes required for root mirror boot vxrootmir: 10:10: Mirroring volume standvol vxrootmir: 10:11: Mirroring volume swapvol vxrootmir: 10:18: Mirroring volume rootvol vxrootmir: 10:20: Current setboot values: vxrootmir: 10:20: Primary: 0/4/0/1.11.0 vxrootmir: 10:20: Alternate: 0/4/0/1.13.0 vxrootmir: 10:20: Making c5t10d0 (0/4/0/1.10.0) the alternate boot disk vxrootmir: 10:20: Disk c5t10d0 is now a mirrored root disk The final example shows how to specify a list of disks for use as stripe column mirrors: # /etc/vx/bin/vxrootmir -v -p c5t11d0,c5t12d0,c5t13d0 c5t10d0 vxrootmir: 12:11: Gathering information on the current VxVM root configuration vxrootmir: 12:11: Checking specified disk(s) for usability vxrootmir: 12:11: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 12:11: Preparing disk c5t11d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t11d0 to rootdg as DM rootstpm01 vxrootmir: 12:11: Preparing disk c5t12d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t12d0 to rootdg as DM rootstpm02 vxrootmir: 12:11: Preparing disk c5t13d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t13d0 to rootdg as DM rootstpm03 vxrootmir: 12:11: Mirroring all volumes on root disk vxrootmir: 12:11: Mirroring volume standvol vxrootmir: 12:12: Mirroring volume swapvol vxrootmir: 12:19: Mirroring volume rootvol vxrootmir: 12:21: Mirroring volume optvol vxrootmir: 12:24: Mirroring volume usrvol vxrootmir: 12:27: Mirroring volume homevol vxrootmir: 12:28: Mirroring volume tmpvol vxrootmir: 12:28: Mirroring volume varvol vxrootmir: 12:36: Disk c5t10d0 is now a mirrored root disk NOTES
If the vxrootmir command aborts for any reason, or if you interrupt the command during execution, an attempt is made to clean up the VxVM objects that had been generated up to the time of the abort or interruption. All mirror plexes that had already been added, or that were in the process of being added when the interruption occurred, are removed. All Data Media (DM) objects that were created are also removed. If a plex or a DM object cannot be removed, an explanatory message is displayed. SEE ALSO
setboot(1M), vxassist(1M), vxbootsetup(1M), vxintro(1M), vxmirror(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxrootmir(1M)
All times are GMT -4. The time now is 06:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy