Mksysb tape fails to clone system
I am attempting to clone an identical hardware (7208) RS6000 server. I am using a mksysb tape that completes with an error: "boot image is too large".
The client has only rootvg and has put everything in there. I am going to attempt building the tape with it not packed and excluding their application/data directories.
I have a document that is referenced by the error message that says I can boot from install media and then do a recovery. I tried that and it failed similarly.
As the RAM disk is only 128MB, I am going to exclude any file that is larger than 64MB as well. There are not many. I'm afraid that a temp file may fill up the RAM disk root file system.
Anything else I should try?
Thank you.
The client has only rootvg and has put everything in there. I am going to attempt building the tape with it not packed and excluding their application/data directories.
I have a document that is referenced by the error message that says I can boot from install media and then do a recovery. I tried that and it failed similarly.
As the RAM disk is only 128MB, I am going to exclude any file that is larger than 64MB as well. There are not many. I'm afraid that a temp file may fill up the RAM disk root file system.
Anything else I should try?
Thank you.
gheist
"identical" should read "with same or later microcodes"
Hi,
you write >> boot from install media and then do a recovery. I tried that and it failed similarly. <<
Are you able to boot from installation media? If yes, it should then always be possible to restore the mksysb from tape. The (possibly too large) boot image on tape is not needed for such a restore.
Once you got a running system (mksysb restored or not), please check immediately the microcode levels. It might well be that the firmware of the target system is too old.
Furthermore, before creating the mksysb tape, try to deinstall all 'devices...' filesets which are not needed. I saw systems with tons of printer drivers installed - but without a single printer used. Graphics and terminal drivers are good candidates, too.
Why on earth do you still use 5.2? And, what is a 7208? I only know the 8mm tape bearing that number.
wmp
you write >> boot from install media and then do a recovery. I tried that and it failed similarly. <<
Are you able to boot from installation media? If yes, it should then always be possible to restore the mksysb from tape. The (possibly too large) boot image on tape is not needed for such a restore.
Once you got a running system (mksysb restored or not), please check immediately the microcode levels. It might well be that the firmware of the target system is too old.
Furthermore, before creating the mksysb tape, try to deinstall all 'devices...' filesets which are not needed. I saw systems with tons of printer drivers installed - but without a single printer used. Graphics and terminal drivers are good candidates, too.
Why on earth do you still use 5.2? And, what is a 7208? I only know the 8mm tape bearing that number.
wmp
RS/6000 was renamed pSeries 7 years ago - at the time 7208 was top-of-the-line SASD...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can install microcodes on 2nd system by creating floppies on windows PC