I periodically create a mksysb of my AIX systems, especially if there's a hardware or LVM change. I'm concerned about what I should and should not restore on top of the mksysb with TSM. The rootvg filesystem files periodically change, but at the same time I fear restoring certain files would be detrimental, such as files under /dev/ or the TSM client files. I'm looking for some advice for the future on how to handle a potential disaster. Buying sysback or Cristie is unlikely at my organization.
-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
AIX BMR with mksysb and TSM
- Thread starter pong3d
- Start date
moon-buddy
ADSM.ORG Moderator
I use mksysb to backup the TSM server. Rootvg, the necessary files and file structure for any AIX server in question are the ones being backed up.
When DR test comes around, the home and other application related directories and files are restored via TSM recovery methods (for a TSM Server) or via TSM restore for non-TSM servers. Oracle servers should be functional from a binary viewpoint minus the DB and LOG volume data which will be restored via TSM.
For LPAR type servers, this is a lot easier via images.
When DR test comes around, the home and other application related directories and files are restored via TSM recovery methods (for a TSM Server) or via TSM restore for non-TSM servers. Oracle servers should be functional from a binary viewpoint minus the DB and LOG volume data which will be restored via TSM.
For LPAR type servers, this is a lot easier via images.
