Kelly, That is not normal. If the DB is top of the tree, and set to non critical, it should not cause the group to offline. Even after we introduced FaultPropagation and ManageFaults the core Critical/Non-Critical behavior should not have changed. Can you open a case on this?
Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, February 29, 2008 11:57 AM To: veritas-ha@mailman.eng.auburn.edu Subject: [Veritas-ha] Question re SFRAC 5.0 We are testing a new SFRAC 5.0 cluster. One of the scenarios is a "shutdown abort" to one instance. When we did this, it took the whole group offline on that node even though the database is the top resource in the dependency tree. Is this normal behavior? I don't remember this every happening before. I remember it only taking the database offline and leaving the mounts up. The database is a non-critical resource with nothing depending on it. Thanks in advance for your help! ************************************************************************ ****************** The information contained in this message, including attachments, may contain privileged or confidential information that is intended to be delivered only to the person identified above. If you are not the intended recipient, or the person responsible for delivering this message to the intended recipient, Alltel requests that you immediately notify the sender and asks that you do not read the message or its attachments, and that you delete them without copying or sending them to anyone else. _______________________________________________ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha _______________________________________________ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
