hello
How can I know which files did not get backuped
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
[TOP]
Initializing mkcd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
Creating image.data file...
Creating mksysb image...
Creating list of files to back up........
Backing up 39961 files..............................
1756 of 39961 files (4%)..............................
30325 of 39961 files (75%)..................
0512-003 mksysb may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.
Populating the CD or DVD file system...
Copying backup to the CD or DVD file system...
Building chrp boot image...
Creating Rock Ridge format image: /backup/cd_image_97702.vol1
Running mkisofs ...
mkrr_fs was successful.
Making the CD or DVD image bootable...
Copying the remainder of the backup to the CD or DVD file system...
Creating Rock Ridge format image: /backup/cd_image_97702.vol2
Running mkisofs ...
mkrr_fs was successful.
--- Post updated at 04:59 AM ---
another question:
how can I make a single iso image instead of getting two VOL1 and VOL2
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 
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:
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!