Re: [Veritas-ha] I/O Fencing non-CFS

2010-10-13 Thread Gene Henriksen
-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of Everett Henson Sent: Wednesday, October 13, 2010 11:40 AM To: Gene Henriksen; 'veritas-ha@mailman.eng.auburn.edu' Subject: Re: [Veritas-ha] I/O Fencing non-CFS Thanks Gene. I understand it'

Re: [Veritas-ha] I/O Fencing non-CFS

2010-10-13 Thread A Darren Dunham
On Wed, Oct 13, 2010 at 11:39:30AM -0400, Everett Henson wrote: > Thanks Gene. I understand it's possible to import the group manually, > but the discussion here was around how VCS would behave normally, > without manual intervention. You're talking about a system designed to prevent problems in

Re: [Veritas-ha] I/O Fencing non-CFS

2010-10-13 Thread Everett Henson
Thanks Gene. I understand it's possible to import the group manually, but the discussion here was around how VCS would behave normally, without manual intervention. Wouldn't a vxdg -C to clear the private region give the server with the group already imported heartburn? Would it allow both serve

Re: [Veritas-ha] I/O Fencing non-CFS

2010-10-13 Thread Gene Henriksen
IO Fencing works with VCS. Even without CFS/RAC it is the best protection against split-brain. You CAN import a DG on multiple systems by using vxdg -C import to clear the name in the private region. Alternatives include the preonline_ipc trigger (in sample_triggers, copy to triggers, rename p