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
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..
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
rdiff-backup-fs
RDIFF-BACKUP-FS(1) General Commands Manual RDIFF-BACKUP-FS(1)NAME
rdiff-backup-fs - Filesystem for accessing rdiff-backup archives.
SYNOPSIS
rdiff-backup-fs <mount_point> <repository> [repositories ...] [-option ...]
DESCRIPTION
rdiff-backup-fs is a filesystem in userspace that reads rdiff-backup archives and provides convenient access.
OPTIONS --debug <0-4>
Run rdiff-backup-fs in foreground with given verbosity of debug messages.
-f, --full
Store information about all revisions in memory. CAUTION: this may take a lot of memory if your archive contains many revisions.
-l, --last
Displays files from the most recent increment as directories, each holding every version of the file. CAUTION: this stores informa-
tion about all revisions in memory and therefore may take a lot of memory if archive contains many revisions.
-c <n>, --caching <n>
How many files retrieved from the rdiff-backup archive may be cached by filesystem. By default rdiff-backup-fs will cache up to 10
files. If this switch is set to 0, no caching will be done.
-r <n>, --revisions <n>
How many revisions should be stored in memory for on demand revision retrieval. By default rdiff-backup-fs will store up to 10 revi-
sions in memory.
-d, --directory <path>
Set directory for directory with temporary files. By default rdiff-backup-fs uses /tmp.
-v, --version
Print version of rdiff-backup-fs and exit.
SEE ALSO rdiff-backup(1)COPYRIGHT
rdiff-backup-fs is Copyright (c) 2007-2011 Filip Gruszczyski.
rdiff-backup-fs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published
by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
AUTHORS
Filip Gruszczyski <gruszczy@gmail.com>
RDIFF-BACKUP-FS(1)
07-31-2019
