hi,
a mksysb is not a snapshot of your system in a istant:
it is built in 3 essential steps
1) write boot image on tape ( no problem if user ... )
2) build image.data ( no relevant if user ... )
3) make a list of all files ( find / > /tmp/list )
4) an oper as: cat /tmp/list | backup -ivpf /dev/rmt0
more or less !
If between step 3 and 4 user create or delete files,
in mksysb will not go new files (no error report),
and some error will be reported becouse file in /tmp/list
are not found on system.
Conclusion:
A) a mksysb with user working is better than nothing
B) a mksysb with: no user, errclear 0,... is the best.
also it is best to backup just the root filesystem when doing a mksysb rather than the whole lot i.e. other filesystems etc.. to avoid this you can create a file in
/etc/ called exclude.rootvg ( more info do man mksysb)
so you back up / , tmp , home , usr, var
But as victorv has sais its is best if no users are on the system , so they don't have opened files .
When I said "all files" I was only referring to the system files. I have only ever backed up rootvg during a mksysb.
If I understand the replies correctly, a mksysb "on the fly" will restore the operating system and every file in rootvg but may throw up a few errors.
As long as I can restore an working OS and rootvg back to where it was in the event of failure and get my users back online straight away, I will be happy. If there are small problems to sort out later then that's OK.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.