| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
|
#1
| ||||
| ||||
Hi I have a problem with a Customer installation of IBM TSM for Backup and Restore (AKA Sysback). I took a sysback image of a given server running AIX 5.2 and when trying to restore rootvg in a new brand p520 internal disks are not recognized. I have tryied upgrading the source server but this has led to a major disaster that even required restoring the source from a mksysb backup. So i want to try using the sysback image. In Linux you can load drivers from another media in a Rescue enviroment when installing. Anyone knows a way to solve this problem ?? TIA
__________________ cd3lgad0p |
|
#2
| ||||
| ||||
It's been ages since I've used sysback so I can't help you directly sorry. If I remember correctly it's just some window dressing to allow you to pipe a mksysb across the network so it's probably a mksysb underneath it all. When restoring a mksysb on a system with different hardware than the original (again it's been a while!) we used to boot from installation media first (i.e AIX 5.2 install CD's). One of the options you get is to restore or install from mksysb tape. By going this way it "knows" where to go for drivers while restoring the mksysb from tape. |
|
#3
| ||||
| ||||
Hi Thanks. In fact restoring with sysback has an option used to give the system the media device where new software can be found. I was about to use /dev/cd0 but my system does not configure the DVD unit as well. Your idea is quite good. I'm trying it.
__________________ cd3lgad0p |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |