Sponsored Content
Full Discussion: Mkdvd mksysb
Operating Systems AIX Mkdvd mksysb Post 303037406 by RecoveryOne on Wednesday 31st of July 2019 03:41:28 PM
Old 07-31-2019
filosophizer,
It appears to me that you are calling mkdvd, and not the mksysb function directly. From the limited output of your session it looks like a smitty mkdvd instead of a smitty mksysb.
By calling mkdvd, the system will split the backup data into ISO's that can be set bootable and burnt, but you may end up with more than one volume.
By calling mksysb, the system will write one giant file, not set it bootable. You should be able to use mkdvd/mkcd and pass said file to it to make bootable images if required. Be warned, it will split the mksysb into as many volumes as it needs to.

So, single ISO image will require you to prune down your rootvg so all the data fits into one DVD. I try to keep my rootvg's just that, but in cases where others have invaded my space, booting at 15G mksysb from a nim server isn't a problem Smilie

If you have a nim server, I highly recommend checking this script out. Script to Automate System Backups Over the Network Using NIM

Ok, now errors. If you are running this in console it should tell you:
From my system:
Code:
Creating information file (/image.data) for rootvg...
Creating list of files to back up.
Backing up 102671 files..............................
58809 of 102671 files (57%)..............................
83152 of 102671 files (80%)......backup: 0511-449 An error occurred accessing ./home/tsminst1/srvmon/srvmon_10min_done.txt: A file or directory in the path name does not exist.
backup: 0511-449 An error occurred accessing ./home/tsminst1/srvmon/srvmon_20min_done.txt: A file or directory in the path name does not exist.
0512-003 mksysb may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.

Also if running from smit, the smit.log should contain the info. By default, the smit.log should be found in the root filesystem.

If you are calling the mksysb/mkdvd from a script, you will need to capture errors and log them.

Hope this helps!

Last edited by RecoveryOne; 07-31-2019 at 04:47 PM..
 

10 More Discussions You Might Find Interesting

1. AIX

mksysb...

Hi friends.. My one problem is not resolved yet I have another. I am planning to take an OS backup of my p550 using "mksysb". Now i am confussed. suppose I give the command to take the backup into a tape drive and my backup size exceeds the tape capacity.. what will happen? will it ask for... (2 Replies)
Discussion started by: balaji_prk
2 Replies

2. AIX

mksysb

I dont have either a tape drive or a DVD Writer attached to the AIX box. Can you let me know the possibilities of making an mksysb in a bootable media? This is required as we have a requirement to upgrade the OS. (2 Replies)
Discussion started by: chrisanto_2000
2 Replies

3. AIX

mksysb

Hello everyone I have two questions. I would like to hear your opinions, your tips. I have several box with aix 5.3. the rootvg in each box has mirror. but I have a cron that makes a mksysb every week. Do you think that it the best to have a mksysb of rootvg if I have a mirror on this... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

4. AIX

Help with mksysb

Hi All, Working on AIX 4.2 system. On this server there is no tape drive or a DVD Writer attached to the AIX box. I was able to do mksysb, but I got warning message saying it will not be bootable. On the new system, I did install 5.3 and now I need to restore this mksysb image from the... (5 Replies)
Discussion started by: samnyc
5 Replies

5. AIX

mkdvd mkcd mksysb from file fails

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

Mksysb mkdvd rootvg > 6gb

Hello, Just wondering if I don't have tape drive or NIM server then what are the possible ways to make mksysb ? My DVD-RAM has only 4GB capacity where as my rootvg is more than 6GB anythoughts ? POSTSCRIPT: SEE HERE FOR THE SOLUTION:... (1 Reply)
Discussion started by: filosophizer
1 Replies

7. AIX

savevg - mksysb

Hello, I use commands savevg & mksysb to do backups on an AIX server. Frequently, I have a return code 3. I would know why, but after searches, I did'nt find. If somebody know ... Tell me. Thanks. emetra (2 Replies)
Discussion started by: emetra
2 Replies

8. AIX

Using mkdvd to create bootable mksysb on dvd reports success but nothing on dvd?

Hello, Running AIX 7.1 7100-00-03-1115, trying to make a mksysb image to a dvd drive using mkdvd. My final command looks like this.. mkdvd -e -V rootvg -R -C /usr1/AIXADMIN/mkcd/cd_fs -I /usr1/AIXADMIN/mkcd/cd_images -M /usr1/AIXADMIN/mkcd/mksysbimage -d /dev/cd0 -Y When i run this... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

9. AIX

Mkcd and mkdvd errors

Hi all, i use both mkcd and mkdvd for making bootable images of aix 5.3 servers i have. They have dvd reader but no writer. I have the following questions/errors: 1. When the process of mkcd/mkdvd is running and i have 61510 of 61510 files (100%) 0512-038 mksysb: Backup Completed... (1 Reply)
Discussion started by: stetsip
1 Replies

10. AIX

Can I use mkdvd to create bootable DVD from mksysb on tape

Hi, Is it possible to use mkdvd to create a bootable DVD using a mksysb on tape as the source image? On the system concerned, we don't have enough free space to create the mksysb to file first, so would like to use the existing tape mksysb backup. The DVD disk/s will then be used to boot a... (4 Replies)
Discussion started by: alanp36
4 Replies
itu(1M) 						  System Administration Commands						   itu(1M)

NAME
itu - convert packages to Driver Update format and patch Solaris install media for Install Time Update SYNOPSIS
itu makedu -r solaris_release [-v] [-f] [-d output_dir] [-o iso_file] [-l iso_label] package [package...] itu patchmedia -R media_root [-v] [-f] [-o iso_file] [-l iso_label] pkg_or_patch [pkg_or_patch...] itu makeiso -o iso_file [-v] [-l iso_label] media_root DESCRIPTION
The itu utility converts driver packages to Driver Update (DU) format and patches a Solaris install media with driver packages and patches for Install Time Update (ITU). itu has three subcommands: makedu, patchmedia and makeiso. OPTIONS
The following options are supported: -d output_dir Directory where the Driver Update directory is to be created. -f If output_dir/DU or iso_file already exists, remove it without asking first. -l iso_label Label/volume name of the ISO image (if -o option is specified). -o iso_file Path of the ISO image file to be created. For subcommands patchmedia and makeiso, it will be a bootable ISO image. This option must be specified for subcommand makeiso. -R media_root Top-level directory of on-disk image of Solaris installation media. This option must be specified for subcommand patchmedia. -r solaris_release Solaris release number for which the Driver Update is intended. It takes the form of the output of uname -r, for example, 5.10. This option must be specified for subcommand makedu. -v Verbose. Multiple -v options increase verbosity. SUB-COMMANDS The itu subcommands are described as follows. makedu The makedu subcommand takes one or more driver packages as input and converts them to DU format. At the beginning of an interactive Solaris installation session, these driver updates can be applied to the running kernel, which will then also automatically apply them to the newly installed Solaris at the end of the installation process. The -r option is required to specify the Solaris release number for which the driver updates apply. The solaris_release option argument takes the form uname -r output, for example, 5.10 or 5.11. If the -d option is specified, the resulting DU directory tree is placed in the directory output_dir. If the -o option is specified, a (non-bootable) ISO image of the DU directory tree is written in the file iso_file. This ISO image can be burned onto a CD/DVD using cdrw(1) or cdrecord(1) (not a SunOS man page). See the "Examples" section below for an example of creating a DU on a floppy. At least one of -d and -o option must be specified. If both are specified, then both an ISO image and a directory tree are generated. patchmedia The patchmedia subcommand takes a list of driver packages and patches as input and applies them to the miniroot of a Solaris install media. It also places them in a subdirectory called ITUs under the Solaris install media's top-level directory: media_root/ITUs When booting a system from the updated media, the patches and packages will be part of the booted Solaris image. They will also be applied to the target system being installed at the end of the installation process. The -R option must be entered on the command line to specify the Solaris install media. Note that the install media must be on a location that is writable by itu. If the -o option is specified, a bootable ISO image of the patched install media is also created in the file iso_file. The ISO image can then be burned onto a CD or DVD. makeiso The makeiso subcommand runs mkisofs(8) to create a bootable Solaris ISO image of the Solaris install media media_root and writes it to the file iso_file. The ISO image file can then be burned onto a CD or DVD with utilities such as cdrw(1) or cdrecord(1). (Note that mkisofs(8) and cdrecord(1) are not SunOS man pages.) Caution - The Solaris install media media-root must contain the file boot/grub/stage2_eltorito, which will be written to the media boot sectors. This file will be modified with some boot information, thus it has to be writable. If necessary, first save a copy, prior to running this subcommand. OPERANDS
The following operands are supported: package [package...] One or more driver packages. pkg_or_patch [pkg_or_patch...] One or more patches or packages. media_root The top-level directory of a Solaris install media. EXAMPLES
Example 1 Creating a DU CD/DVD The following commands create a Driver Update CD/DVD containing the packages SAMPLEpkg1 and SAMPLEpkg2. # itu makedu -r 5.10 -o my.iso SAMPLEpkg1 SAMPLEpkg2 # cdrw -i my.iso Example 2 Creating a DU Floppy The following commands create a Driver Update floppy containing the driver package MYdriver. # rmformat -F quick /dev/rdiskette # mkfs -F pcfs /dev/rdiskette # mount -F pcfs /dev/diskette /mnt # /usr/bin/itu makedu -r 5.10 -d /mnt /export/MYdriver # umount /mnt # dd if=/dev/rdiskette of=floppy.dd The itu command above creates the DU directly onto the floppy mounted on /mnt. The dd invocation stores an image of the floppy in the file floppy.dd. This is useful for distributing a DU floppy in file form. From the file, the floppy can then be recreated as follows: # dd if=floppy.dd of=/dev/rdiskette Example 3 Patching the Solaris Install Media The following command patches the Solaris install media in /export/s10u1 with patch /opt/patches/123456-07 and driver package /opt/pkgs/MYdriver. The command also creates a bootable ISO image with ISO label "MyS10U1" in the file /tmp/dvd.iso. # /usr/bin/itu patchmedia -R /export/s10u1 -o /tmp/dvd.iso -l MyS10U1 /opt/patches/123456-07 /opt/pkgs/MYdriver Example 4 Creating a Bootable ISO Image The following commands create the bootable ISO image mydvd.iso of the Solaris install image /export/solaris-10u1 with ISO label "Special- S10". # /usr/bin/itu makeiso -o mydvd.iso -l "Special-S10" /export/solaris-10u1 # cdrw -i mydvd.iso ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
cdrw(1), patchadd(1M), pkgadd(1M), attributes(5) mkisofs(8), (/usr/share/man/man8/mkisofs.8), in the SUNWfsman package (not a SunOS man page) SunOS 5.11 25 Jul 2008 itu(1M)
All times are GMT -4. The time now is 08:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy