Originally posted by: apple08

dear AIX gurus,
i'm running mksysb using NIM. where can i see if the mksysb log whether it completed successfuly or not? hope to hear from you. thank you

Originally posted by: apple08

via smit.log

Originally posted by: MarkTaylor

only if you are running the nim operation via smit. There are nim logs under /var/adm/ras you may want to check out also.

HTH
Mark Taylor

Originally posted by: apple08

dear Sir,
thank you
why i got this error? 0512-003 savevg may not have been able to archive some files after 70% backup completed. below is the backup log. how to overcome this. the backup is done via NIM, we don't have tape drive available since the dynamic lpar tape drive move has failed. hope to hear from you. thank you
Backing up 111586 files..............................
29 of 111586 files (0%)..............................
48 of 111586 files (0%)..............................
810 of 111586 files (0%)..............................
933 of 111586 files (0%)..............................
933 of 111586 files (0%)..............................
1053 of 111586 files (0%)..............................
11625 of 111586 files (10%)..............................
33597 of 111586 files (30%)..............................
39029 of 111586 files (34%)..............................
45736 of 111586 files (40%)..............................
47202 of 111586 files (42%)..............................
78576 of 111586 files (70%).............................
0512-003 savevg may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.
cannot access ./tmp/croutJHUpw2: A file or directory in the path name does not e
xist.

Originally posted by: MarkTaylor

/tmp/crout* are cron output files, the file was there when the savevg/mksysb took a list of files to backup, but by the time the backbyname command came to backup the file it had been removed. Use mksysb -ie (use /etc/exclude.rootvg) and set up /etc/exclude.rootvg to exclude ^./tmp/crout*

Your backup will be fine, its just a warning btw ..

HTH
Mark Taylor

Originally posted by: apple08

dear Sir,
thank you. its really helpful.
we just setup NIM last year. i feel backup using local a bit not confusing. coz when we backup via NIM, it did't say backup was completed successfully or not. like the attachment. it just say Ok.

Originally posted by: SystemAdmin

So you can do it in a script:

nim -o define -t mksysb -F -a server=master -a mk_image=yes -a location=/export/eznim/mksysb/${NIM_HOST}/${SAVE_NAME} -a source=${NIM_HOST} -a mksysb_flags=em ${SAVE_NAME} >/export/eznim/mksysb/${NIM_HOST}/${SAVE_LOG} 2>&1

rc=$?
if $rc -ne 0
then ...
Regards

Originally posted by: apple08

dear Sir,
instead of using smit, i'm using script is it? that would be great to pipe the log to a file.wish smitty could have this option. would appreciate you can verify my steps:
1.
vi /disk1/scriptnim
!#/usr/bin/ksh
nim -o define -t mksysb -F -a server=master -a mk_image=yes -a location=/export/images/mksysb_apple_120109 -a source=NIM01 -a mksysb_flags=em mksysb_apple_120109 >/export/images/mksysb_apple_120109.log 2>&1

rc=$?
if $rc -ne 0
wq!

2. to exce
cd /disck1
./scriptnim
hope to hear from you. thank you

Originally posted by: SystemAdmin

I think the nim operation to create a mksysb doesn't return 0 if there were warnings. This is a pain as I have to parse the output for errors, even though the mksysb is good.

It would be awesome if AIX had the ability to verify a mksysb was good.

Originally posted by: SystemAdmin

OK, your script is fine.

NIM DEFINE set a rc = 1 when something is wrong during the mksysb.
But sometimes, it's not an true error. It happens that a tmp file has been deleted between the build of files list and the backup time. In this case NIM set an error.

When a rc=1 has been detected, you should check manually the log file to find the error and see if it is a true error or not.

I run a script each sunday which start a NIM DEFINE for all of my partitions (more than 50) and I get an error on one mksysb each 2-3 weeks. Not too much.

Originally posted by: apple08

dear Sir,
"I run a script each sunday which start a NIM DEFINE for all of my partitions (more than 50) and I get an error on one mksysb each 2-3 weeks. Not too much."
meaning u schedule the mksysb every week for all your more than 50 lpars. thats great
are u using this script:
nim -o define -t mksysb -F -a server=master -a mk_image=yes -a location=/export/eznim/mksysb/${NIM_HOST}/${SAVE_NAME} -a source=${NIM_HOST} -a mksysb_flags=em ${SAVE_NAME} >/export/eznim/mksysb/${NIM_HOST}/${SAVE_LOG} 2>&1

if not, i can't imagine how ur script looks like. can u share?

hope to hear from you. thank you

Originally posted by: apple08

dear Sir,
NIM can run one mksysb at a time right? how you perform your msksyb using NIM on sunday. hope to hear from you. thank you