Hi All,
I have a customer with a fabric MetroCluster. It consists of two FAS8200 Systems, each with dual controllers plus associated ATTO 7500N bridges and Brocade 6510 switches. These are currently all installed and in production in a single location. (All running 9.7P4)
They plan to move one node of the MetroCluster to a new DC around 40 Kilometres away i.e. one of the 8200 systems and its associated shelves, bridges and switches will be relocated.
As I understand it, the plan is to keep one MetroCluster node running while the other is being moved. Once the relocated node is up and running, then the data will be re-synced.
I haven't been involved in relocating half of a MetroCluster before and naturally I am wondering what there is to watch out for. For example:
- Is there a documented procedure for doing something like this? (I mean for example something similar to that which the Upgrade Advisor might generate)
- How best to split / stop / start / reconnect the MetroCluster nodes?
- What's the best way to manage the (re-)distribution of the SVMs (if this is manually required / necessary)?
- The aggregates of the remaining, running, node will need to store more data during the move, right? - What's the best way to assess how much space will be required? - Should the aggregate % reserves also be increased during the move?
- Anything to stop or to avoid prior to / during the move?
- Any other advice gratefully received :-)
Thanks in advance!
Yours, Waflherder