04-16-2014 02:26 AM
Solved! Go to Solution.
04-16-2014 06:22 AM
Hi Marius,
Yes CVM provides support for raw volumes. CVM is embedded in volume manager (vxconfigfd) binary, if you enable CVM/CFS license you can use them. While you are running the installer script, you will need to choose the right option to install CVM/CFS
In the scenario you have mentioned, what will happen if node A has problems, this would depend on what role node A had. If node A was master then your DG would disable & volume should report IO errors, this will effect the DB instances running & corresponding service groups should fault
If your node A was slave (node B was master) if your node a has problem with disk paths, parallel DB instance running on node A should fail while your node B should still continue to access as path from node B are alive & active & DG is accessible
For your next question, you can tune multile parameters (systemlist, autostartlist) however why would you want to have an autofailback ? Imagine a setup of 2 node, node A & B. Lets say node A faults & your service group moves to node B. Now your node A comes back online, users using the application in service group will face an outage if failback happens . so rather leave it for a proper outage window & do manual failover.
G
04-16-2014 06:22 AM
Hi Marius,
Yes CVM provides support for raw volumes. CVM is embedded in volume manager (vxconfigfd) binary, if you enable CVM/CFS license you can use them. While you are running the installer script, you will need to choose the right option to install CVM/CFS
In the scenario you have mentioned, what will happen if node A has problems, this would depend on what role node A had. If node A was master then your DG would disable & volume should report IO errors, this will effect the DB instances running & corresponding service groups should fault
If your node A was slave (node B was master) if your node a has problem with disk paths, parallel DB instance running on node A should fail while your node B should still continue to access as path from node B are alive & active & DG is accessible
For your next question, you can tune multile parameters (systemlist, autostartlist) however why would you want to have an autofailback ? Imagine a setup of 2 node, node A & B. Lets say node A faults & your service group moves to node B. Now your node A comes back online, users using the application in service group will face an outage if failback happens . so rather leave it for a proper outage window & do manual failover.
G
04-16-2014 10:15 AM
Hi,
Please also give me your comment on my new discussion "vcs".