Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are replacing our old cluster with a new one. We have some PS hours but my manager has asked me to research moving everything over so we at least know what to expect prior to PS engagement. I was thinking that the most efficient method would simply be svm-dr, but I saw a blog post that said that NetApp prefers to set up new svms and just snapmirror the data over, then break the mirror and make the destinations rw.
Is there any documentation that describes the hardware refresh process and has a list of steps that are considered best practice so we can be ready for this migration?
Solved! See The Solution
1 ACCEPTED SOLUTION
Drew_C has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the hardware/software compatibility allows it, by far the easiest to do is join the new nodes to the existing cluster, configure them, move the lifs and volumes to the new nodes, and fail out the original nodes. This can all be done without any outages whatsoever. I've done this multiple times for very busy environments where unmounting a volume isn't possible without a site outage.
Drew_C has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just did a site with 26 svms. Over 400 volumes.
svmdr all the way
