Hello All,
I thought I'd pop up a question that has dumbfounded both Veritas and MS support. Ultimately, what's the best practice to recover cluster server operations to a different set of hardware when you're using MSCS and Veritas' VSFW MSCS Option allowing shared disks to be dynamic.
In our past attempts we've regrettably had to settle for only getting one node up and using an alias to address the shared storage. We've tried restoring to unconfigured hardware, configured hardware, Veritas on, veritas off and the latest was a recommendation to recover to a VM using a differential recovery tool.
We have a W2k3 cluster utilizing VSFW 5.0 MSCS option, Multipathing and replicated netapp storage to the hot-site. Backup is through TSM complemented by Indigo Stone's ERRM
If you have any past experience on beating this animal, would love to hear it.
I thought I'd pop up a question that has dumbfounded both Veritas and MS support. Ultimately, what's the best practice to recover cluster server operations to a different set of hardware when you're using MSCS and Veritas' VSFW MSCS Option allowing shared disks to be dynamic.
In our past attempts we've regrettably had to settle for only getting one node up and using an alias to address the shared storage. We've tried restoring to unconfigured hardware, configured hardware, Veritas on, veritas off and the latest was a recommendation to recover to a VM using a differential recovery tool.
We have a W2k3 cluster utilizing VSFW 5.0 MSCS option, Multipathing and replicated netapp storage to the hot-site. Backup is through TSM complemented by Indigo Stone's ERRM
If you have any past experience on beating this animal, would love to hear it.
