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
volrecover(8)						      System Manager's Manual						     volrecover(8)

NAME
volrecover - Performs volume recovery operations SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...] OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera- tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5 parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back- ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name, the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume. State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume. Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim- its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated relative to the given disk group. Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu- ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre- fix:options can be specified to restrict the set of commands that the -o option should be applied to. Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes) Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies to mirror resynchronization and RAID5 parity recovery DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (medianame). If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place. Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that involve unrelated disks will run in parallel. EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command: # volrecover -b medianame If you want to monitor the operations, use the command: # volrecover -v medianame SEE ALSO
volintro(8), volplex(8), volume(8) volrecover(8)
All times are GMT -4. The time now is 04:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy