1753751
Members
5095
Online
108799
Solutions
Craig,
Haven't done it myself, but have been giving it some though for some customers recently... I'm sur it could be made to work, but I doubt it would be very elegant for one main reason - Given the way that HPUX maps hardware paths in a SAN, the hardware path to the boot disk is unlikely to be the same on the host attached to the 2nd Symm - this has two important consequences:
1. Sometimes the contents of the AUTO file on a LIF volume contain a hardware path - obviously the boot isn't going to work if it does - thsi isn't too bad as the AUTO file doesn't HAVE to contain a hardware path, but secondly:
2. Hardware paths govern disk device file names, which will also change - which pretty much inevitably means that the root volume group wouldn't activate - you would need to always boot to LVM maintenance mode and reconstruct the root VG and then reboot again in order to boot your RDF'd image - to me this seems more hassle and risk than just keeping an ignite image and a fast tape drive to hand.
But YES in theory you could make it work.
HTH
Duncan
I am an HPE Employee
Haven't done it myself, but have been giving it some though for some customers recently... I'm sur it could be made to work, but I doubt it would be very elegant for one main reason - Given the way that HPUX maps hardware paths in a SAN, the hardware path to the boot disk is unlikely to be the same on the host attached to the 2nd Symm - this has two important consequences:
1. Sometimes the contents of the AUTO file on a LIF volume contain a hardware path - obviously the boot isn't going to work if it does - thsi isn't too bad as the AUTO file doesn't HAVE to contain a hardware path, but secondly:
2. Hardware paths govern disk device file names, which will also change - which pretty much inevitably means that the root volume group wouldn't activate - you would need to always boot to LVM maintenance mode and reconstruct the root VG and then reboot again in order to boot your RDF'd image - to me this seems more hassle and risk than just keeping an ignite image and a fast tape drive to hand.
But YES in theory you could make it work.
HTH
Duncan
I am an HPE Employee
Well you wouldn't want to be paging/swapping to a SRDF'd disk - what would be the point?
- The SRDF would slow up the paging/swapping process slightly
- You'd be replicating data which is completely useless to your other symm nothing in swap space is retained across reboots.
SO either keep swap on an internal disk, or at least on a non-SRDF'd disk. I personally like the idea of swap being on internal - that way if you have some kind of panic and TOC during boot (maybe caused by the SAN??), you can get at the resultant dump on a local disk, as long as you have a recovery CD.
Of course your memory should be suitably sized that you NEVER have to do any significant page outs or swap anyway.
HTH
Duncan
I am an HPE Employee
- The SRDF would slow up the paging/swapping process slightly
- You'd be replicating data which is completely useless to your other symm nothing in swap space is retained across reboots.
SO either keep swap on an internal disk, or at least on a non-SRDF'd disk. I personally like the idea of swap being on internal - that way if you have some kind of panic and TOC during boot (maybe caused by the SAN??), you can get at the resultant dump on a local disk, as long as you have a recovery CD.
Of course your memory should be suitably sized that you NEVER have to do any significant page outs or swap anyway.
HTH
Duncan
I am an HPE Employee