Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Upgrading clusters to 2k8 (from 2k3) - Questions on CNO/VCO objects.

$
0
0

I am upgrading 2 clusters from Server2k3 to Server2k8 - and the issue is keeping the same VCO's.  Here is the situation.  In order to test before going live, we are completely stopping all cluster services on the 2k3 clusters, and moving over to the 2k8 clusters.  On the 2k8 clusters, our CNO's are different than the 2k3 clusters - but we have to keep the resource names (VCO's) the same.  Same names, same IP addresses.  The issue I'm worried about is when we're done testing on the 2k8 clusters and need to revert back to the 2k3 clusters.. there are now AD computer account objects matching names with the VCO's.  I'm aware this is how 2k8 grants rights for clustering.. whereas 2k3 does not.  The issue being after shutting off all services on 2k8 and reverting back.. the 2k3 clusters are saying an object already exists with that name, and cant bring the cluster name resource online.  Deleting these objects in Active Directory will solve the problem.  My worry is recreating and deleting this VCO so many times during testing, is there a better way to do this??  Will the Server2k3 cluster service account run into any issues having to recreate the resource name so many times over the course of testing??  Thanks in advance. 


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>