Unsolved
This post is more than 5 years old
9 Posts
0
476
How to setup Solaris to provide SRDF bootdisk cluster-like functionnality ?
Hello,
We have 2 identical solaris machines (A & B) and 2 Symmetrix on 2 sites. We would like to move from internal scsi boot disk to SRDF symmetrix bootdisks. This way we can be able to backup server A on the B hardware or the opposite according our needs.
We also have PowerPath. I would like to know if we have to use persistent binding four our symmetrix boot devices (until now we don't) to make sure the emcpower devices will always be the same even if we have minor differents thirds luns on the SAN.
I suspect a boot -r in a case of a different naming of Solaris could fail the boot processing.
Any experience about that configuration will be appreciated.
Regards
Dak
We have 2 identical solaris machines (A & B) and 2 Symmetrix on 2 sites. We would like to move from internal scsi boot disk to SRDF symmetrix bootdisks. This way we can be able to backup server A on the B hardware or the opposite according our needs.
We also have PowerPath. I would like to know if we have to use persistent binding four our symmetrix boot devices (until now we don't) to make sure the emcpower devices will always be the same even if we have minor differents thirds luns on the SAN.
I suspect a boot -r in a case of a different naming of Solaris could fail the boot processing.
Any experience about that configuration will be appreciated.
Regards
Dak
taylor3
33 Posts
0
January 24th, 2007 10:00
I imagine you will want to enable persistent binding to avoid hardware path changes making it impossible/difficult to boot off of once you convert to SAN bootdisks.
Thanks,
Taylor
Dakota2
9 Posts
0
January 25th, 2007 01:00
We don't use persistent binding because all SAN disks belongs to Veritas Volume Manager and until now it would have been a non necessary constrainst.
At a first glance, I suppose making persistent binding on the boot lun is necessary. But i'm not sur of the behaviour of the R1/R2 rollover behaviour (i guess the powercf -Z exists for that).
The main concern is to be sure the link emcp device -> (CxTydZ)s -> R1/R2 when the backup will go on.
I was hoping a blueprint could exist about this subject.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
February 27th, 2007 12:00
If you are just mirroring siteA boot device to siteB and you attempt to boot - you have risk to have all that not they way siteA seen. I
now , when you boot - you specify in OpenBootProm which path is the boot device - you can boot -a and change "root" to whatever path you think is right (vxio is here for masking it for Veritas). Once this moves on - system attempts to remount / and all filesystems from /etc/vfstab - and this must be under VX (swap incusive) to make it work .
Now - in case hardware path change - only way is to split mirrors , unencapsulate system per Veritas docs, recreate /etc/path_to_inst and boot with single disk - then encapsulate it back.
hope this helps a bit.
Regards
c16435