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
bup-save(1)						      General Commands Manual						       bup-save(1)

NAME
bup-save - create a new bup backup set SYNOPSIS
bup save [-r host:path] <-t|-c|-n name> [-#] [-f indexfile] [-v] [-q] [--smaller=maxsize] DESCRIPTION
bup save saves the contents of the given files or paths into a new backup set and optionally names that backup set. Before trying to save files using bup save, you should first update the index using bup index. The reasons for separating the two steps are described in the man page for bup-index(1). OPTIONS
-r, --remote=host:path save the backup set to the given remote server. If path is omitted, uses the default path on the remote server (you still need to include the ':'). The connection to the remote server is made with SSH. If you'd like to specify which port, user or private key to use for the SSH connection, we recommend you use the ~/.ssh/config file. -t, --tree after creating the backup set, print out the git tree id of the resulting backup. -c, --commit after creating the backup set, print out the git commit id of the resulting backup. -n, --name=name after creating the backup set, create a git branch named name so that the backup can be accessed using that name. If name already exists, the new backup will be considered a descendant of the old name. (Thus, you can continually create new backup sets with the same name, and later view the history of that backup set to see how files have changed over time.) -f, --indexfile=indexfile use a different index filename instead of ~/.bup/bupindex. -v, --verbose increase verbosity (can be used more than once). With one -v, prints every directory name as it gets backed up. With two -v, also prints every filename. -q, --quiet disable progress messages. --smaller=maxsize don't back up files >= maxsize bytes. You can use this to run frequent incremental backups of your small files, which can usually be backed up quickly, and skip over large ones (like virtual machine images) which take longer. Then you can back up the large files less frequently. Use a suffix like k, M, or G to specify multiples of 1024, 10241024, 10241024*1024 respectively. --bwlimit=bytes/sec don't transmit more than bytes/sec bytes per second to the server. This is good for making your backups not suck up all your net- work bandwidth. Use a suffix like k, M, or G to specify multiples of 1024, 10241024, 10241024*1024 respectively. --strip strips the path that is given from all files and directories. A directory /root/chroot/etc saved with "bup save -n chroot --strip /root/chroot" would be saved as /etc. --strip-prefix=path-prefix strips the given path-prefix path-prefix from all files and directories. A directory /root/chroots/webserver saved with "bup save -n webserver --strip-path=/root/chroots" would be saved as /webserver/etc --graft=old_path=new_path a graft point old_path=new_path (can be used more than once). A directory /root/chroot/a/etc saved with "bup save -n chroots --graft /root/chroot/a/etc=/chroots/a" would be saved as /chroots/a/etc -#, --compress=# set the compression level to # (a value from 0-9, where 9 is the highest and 0 is no compression). The default is 1 (fast, loose compression) EXAMPLE
$ bup index -ux /etc Indexing: 1981, done. $ bup save -r myserver: -n my-pc-backup --bwlimit=50k /etc Reading index: 1981, done. Saving: 100.00% (998/998k, 1981/1981 files), done. $ ls /home/joe/chroots/httpd bin var $ bup index -ux /home/joe/chroots/httpd Indexing: 1337, done. $ bup save --strip -n joes-httpd-chroot /home/joe/chroots/httpd Reading index: 1337, done. Saving: 100.00% (998/998k, 1337/1337 files), done. $ bup ls joes-httpd-chroot/latest/ bin/ var/ $ bup save --strip-prefix=/home/joe/chroots -n joes-chroots /home/joe/chroots/httpd Reading index: 1337, done. Saving: 100.00% (998/998k, 1337/1337 files), done. $ bup ls joes-chroots/latest/ httpd/ $ bup save --graft /home/joe/chroots/httpd=/http-chroot -n joe /home/joe/chroots/httpd Reading index: 1337, done. Saving: 100.00% (998/998k, 1337/1337 files), done. $ bup ls joe/latest/ http-chroot/ SEE ALSO
bup-index(1), bup-split(1), bup-on(1), bup-restore(1), ssh_config(5) BUP
Part of the bup(1) suite. AUTHORS
Avery Pennarun <apenwarr@gmail.com>. Bup unknown- bup-save(1)
All times are GMT -4. The time now is 06:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy