12-20-2008
Quote:
Originally Posted by
Padow
BTW, I've never copied from disk to tape and performed a restore. You should test a restore before relying on it for a DR.
To be honest i doubt that it will work. If the "mksysb" does not write to a tape device or a NIM server it does not include the boot code to the image as far as i know. Therefore the tape will not be bootable if you transfer it that way - the boot code would still be missing. One would have to provide this boot code via a floppy disk or CD-ROM to boot off the tape.
I'd like to second, though, what you said above: using NIM is the right way to do it.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
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. AIX
Hi,
I have a tape made with mksysb on an AIX machine that will not restore, the system is dead to the point of needing an op sys reload.
I am trying to restore some critical data files and can read the tape image with dd on another system (SCO). I have worked out the file headers enough to... (0 Replies)
Discussion started by: ovingtond
0 Replies
3. UNIX for Advanced & Expert Users
Hi, (HP-UX 11.11)
I need to create a tape image of an igniteUX image created on our igniteUX server.
That is to say. I have a "Online" image of the igniteUX of the targeted system but I now need to copy it to a useable TAPE (igniteUX) image so i can build an other server from it that is not... (3 Replies)
Discussion started by: Andrek
3 Replies
4. AIX
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. AIX
Hello Folks,Having some problems moving an old mksysb backup to a file image.data to DVD-RAM1) From mkdvd if i do a new backup it works fineBUT2) From mkdvd if I do fails:+--------------------------------------------------------------------------+| Use an existing mksysb image?... (8 Replies)
Discussion started by: filosophizer
8 Replies
6. AIX
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
7. AIX
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
8. AIX
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
9. UNIX for Advanced & Expert Users
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
10. AIX
This may be a dumb question and the more I think about it the worst it seems!!
I have inherited some standalone systems where they are using the mksysb command to create a disk file image; this image is then backed up to Networker.
My dumb question is how would we go about restoring this... (4 Replies)
Discussion started by: gz3xzf
4 Replies
LEARN ABOUT REDHAT
mkbootdisk
MKBOOTDISK(8) System Manager's Manual MKBOOTDISK(8)
NAME
mkbootdisk - creates a stand-alone boot floppy for the running system
SYNOPSIS
mkbootdisk [--version] [--noprompt] [--verbose]
[--device devicefile] [--size size]
[--kernelargs <args>] [--iso] kernel
DESCRIPTION
mkbootdisk creates a boot floppy appropriate for the running system. The boot disk is entirely self-contained, and includes an initial
ramdisk image which loads any necessary SCSI modules for the system. The created boot disk looks for the root filesystem on the device sug-
gested by /etc/fstab. The only required argument is the kernel version to put onto the boot floppy.
OPTIONS
--device devicefile
The boot image is created on devicefile. If --device is not specified, /dev/fd0 is used. If devicefile does not exist mkinitrd cre-
ates a 1.44Mb floppy image using devicefile as the filename.
--noprompt
Normally, mkbootdisk instructs the user to insert a floppy and waits for confirmation before continuing. If --noprompt is specified,
no prompt is displayed.
--verbose
Instructs mkbootdisk to talk about what it's doing as it's doing it. Normally, there is no output from mkbootdisk.
--iso Instructs mkbootdisk to make a bootable ISO image as devicefile.
--version
Displays the version of mkbootdisk and exits.
--kernelargs args
Adds args to the arguments appended on the kernel command line. If this is not specified mkbootdisk uses grubby to parse the argu-
ments for the default kernel from grub.conf, if possible.
--size size
Uses ize (in kilobytes) as the size of the image to use for the boot disk. If this is not specified, mkbootdisk will assume a stan-
dard 1.44Mb floppy device.
SEE ALSO
grubby(8) mkinitrd(1)
AUTHOR
Erik Troan <ewt@redhat.com>
4th Berkeley Distribution Tue Mar 31 1998 MKBOOTDISK(8)