Any change to rootvg (like patching, configuration, tuning, etc.) should be
followed by a mksysb backup (anywhere, to tape, file, NIM, sysback, etc).
But please note that what should be mostly worried about is the "data" that
is normally stored somewhere in another volume groups.
Points:
- mksysb is not an incremental backup utility. A weekly mksysb schedule
would suit in most environments to protect the operating system.
- If you have application files/data in rootvg, make a plan to move then to
another VGs (best practice)
- But If - for any reason - an incremental backup of some rootvg
directories is needed, an intelligent backup system like TSM would help a
lot. A properly designed progressive incremental backup with journal
feature would help you backup the changes easily with a schedule while
occupying minimum space in backup server side.
- mksysb backup can be automated by NIM. This is an excerpt from such a
script:
nim -o define -t mksysb -a server=master -a location=$BACKUP_FILE -a
source=$CLIENT -a mk_image=yes -a mksysb_flags=XeA $RESOURCE_NAME

As you said Arash_AK, how to make an incremental mksysb vi NIM server? Because generating a daily mksysb needs more space, especially when there are a lot of servers to manage ... and I want that my mksysb for each server will be updated daily.

Hi, Write a simple script and add in to crontab of all the servers. Also
you must required more space on Nim. But if your having TSM scheduled for
NIM Then TSM manages the incremental backup of the mksysb images of NIM
client and you will not required more space aswell. Consider the space for
all the mksysb for one day.