welp there weren't any responses, but i was able to figure it out anyway.

For the master and secondary domain issue; it's as easy as moving all the VMs you want off the master, then detaching it, the second domain becomes the new master automatically.

For the Cluster A to B move; I shut down all the VMs, created a temporary secondary data domain (with no data), then was able to put the master into maintenance mode, detach it, and the temporary secondary data domain became the new master.
I then attached Cluster A's old master domain to Cluster B, and was able to bring up all the VMs immediately.  This whole process took less than an hour, mostly because I spent time poking at stuff, but realistically took just 15 mins.

I also learned a lot about moving VMs to a new NFS, first step being copy all the templates and for thin clients their referenced disks to the new NFS, then shut down the VMs and move their disks. All real easy through the UI.



On Fri, Apr 17, 2015 at 10:00 AM, David Smith <dsmith@mypchelp.com> wrote:
FWIW I've done lots of goog searches and came up with a lot of old info, so I thought I'd ask here for the latest before going down the wrong path.

Two issues here; running 3.5

First issue;
On one domain, I have a master and secondary data domain.
Eventually I want to move everything from the master to secondary, and promote the secondary data domain to master, and retire the current master.
Whats the best process for this?  


Second issue;
I have two clusters, for now we'll call them A and B
Cluster A has a master data domain that I want to effectively shut down (turn all VMs off, shut down the domain) --- can I then reattach that domain as a secondary to Cluster B and reactivate the VMs?