Hi Alex
Are there any services at the remote site (I will call it "site B") that users from site A need access to? Then those services need to be redundant too, don't they?
In such a case I would simple issue a "cf takeover" from site A - so node A will provide all the services from node B. It is safe to powerdown this node then. As soon as you switch off the shelves from site B, node A should switch to the remaining plexes at side A and serving data from the mirror-plexes.
After maintenance power up the shelves first, resyncing should occur automatically. How long it takes is depending on the amount of data written. Eventually you will observe an increasing aggr snap reserve.
Me personally would wait for the resync to finish before powering up node B - but I have no reason for that, just a feeling.
Probably the giveback has to be forced then by "cf giveback -f".
If there are no services depending on site B then it is even easier. I simply would halt node B by "halt -f" (thus preventing a takeover during halt) and shut down the site. Whenv site A has no access to the mailbox disks of node B and no cluster interconnect, MetroCluster is just doing nothing but serving data from its local node / services.
Any agree / disagree to these remarks?
Mark