>>> On 3/2/2009 at 6:26 PM, Moeur Tim C <[email protected]> wrote: > Hello list, > > I have a problem looking for a solution and I'm hoping that someone here > might have some suggestions. > > We have recently implemented FCP on our zLinux machines. Our /boot > directory is still 3390, but after the IPL some of the filesystem are > FCP. I've discovered that the /etc/zfcp.conf file will need to be > different when we boot the system here or when we boot it at our DR > site. I'm considering methods to quickly start the system with as > little intervention as possible. I'd rather avoid a three step DR > process to IPL in single user, fix zfcp.conf, boot again. Does anybody > have some suggestions or recommendations for automating this?
The main issue I see in trying to automate this would be ensuring that every time you go to the DR site, you get assigned the same FCP adapters, and the SAN storage so that the WWPN and LUNs don't change every time. If that can't/won't be guaranteed then I think you're out of luck. If it _can_ be guaranteed, then you really don't have to do much. If you run the zfcp_??_configure routines, the udev rules will get updated, and the next time you run a test, it should just work. Alternatives that I can imagine would only be feasible if you have z/VM and a rather small number of guests, since it would require updating a file on each guest's 191 disk to allow current information about that to be read during boot time. One that would introduce a noticeable performance hit would be to have z/VM manage the disks via EDEV, and present them to the guests as minidisks. Then you only have to make changes in one place, z/VM. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
