Another idea (if you have the space)
Setup the 8200 to match the 3250 (burning the 6 disks for the root aggregates). Don’t use the rest of that shelf. Join the cluster, move everything to the 8200 Unjoin the 3250 Upgrade the 8200 to 9.2 or 9.3 Take one of the shelves from the 3250 and add it to the 8200. Move the root aggregates/volumes to the shelf from the 3250 manually do the ADP on the first shelf and move the root volumes back** remove the 3250 shelf
**never done this for root aggregates so this may need some testing/research
m
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of tmac Sent: Monday, November 27, 2017 10:03 AM To: Jan-Pieter Cornet johnpc@xs4all.nl Cc: Toasters@teaparty.net Subject: Re: Chicken/egg dillema doing a hardware upgrade on a FAS3250
here is an idea...not necessarily supported, but an idea:
1. Install 9.2P1 on your FAS8200 controllers. 2. Initialize them with the Root-Data Partitioning Here is the not necessarily supported part: 3. If you do not have a CN1610 or supported stand-alone cluster swithces -> temporarily utilize a 10-gig switch and convert the 3250 from switchless to switched. 4. I think you might be able to add the FAS8200s into the cluster, they will operate like 9.1 controllers. 5. If they get moved in, you can then vol move the snapmirror volumes in 6. After they are all moved, remove the FAS3250 nodes from the cluster 7. Convert the switched cluster back to a switchless cluster.
again: This process is probably NOT SUPPORTED, but if you are in a pinch, it may work. It might be worth opening a case to see if you can temporarily add 9.2 to a 9.1 cluster.
--tmac
Tim McCarthy, Principal Consultant
Proud Member of the #NetAppATeamhttps://twitter.com/NetAppATeam
I Blog at TMACsRackhttps://tmacsrack.wordpress.com/
On Mon, Nov 27, 2017 at 10:46 AM, Jan-Pieter Cornet <johnpc@xs4all.nlmailto:johnpc@xs4all.nl> wrote: We have a FAS3250 that's primarily backup storage. It hosts a lot of snapmirror targets, and a few mounted filesystems with backup data.
As the hardware is getting old, we've purchased a shiny new FAS8200 with a couple of 8TB drive shelves.
We assume that the FAS8200 can be initialized on 9.2 and above using the ADP on external drives feature, to partition those 8T disks, so we don't have to throw away about 50T of storage just on the root aggregates.
However... the FAS3250 hardware can only run ontap 9.1. Newer versions of ontap are not available on that hardware. And to make the 8200 nodes join the existing cluster, it has to run the same sofware version (9.1), so... it cannot be initialized with ADP.
And you can't initialize first and partition later, because repartitioning wipes all existing data.
That's our dilemma.
I've actually tried to "manually" partition the disks, by going into maintenance mode and using "disk partition" to force the 8200 nodes to see only partitioned disks, and then re-initializing them using boot menu "4 - clean config and reinitialize disks". That fails, and 9.1 doesn't want to write a root FS to partitioned disks (it does wipe them, though). Besides, it would likely be unsupported. I did learn some interesting things about the "disk partition" command, by the way, like the "-b" blocksize is in 4k blocks, and the '-i' option that numbers partitions starts at 1, which is a data partition, and number 2 is the root partition, at least in the 2-partition root/data setup.
So we either have the option to throw away a large chunk of storage for root aggregates, initialize the new nodes on 9.1, join in cluster, and move the existing data using 'vol move' and all the cDOT goodness that comes with it.
... or build the new 8200 as a separate cluster, initialize it with 9.3, partition the disks via the boot menu, and then move the data over using snapmirror, and remounting the clients. That's doable because most of the data is snapmirror target anyway, and there's a limited number of mounted filesystems that would need a remount. It's a shame that cDOT doesn't have "snapmirror migrate" like 7mode did.
Does anyone have any other options? All I could think is get swing gear and basically do the migration twice, first to hardware that supports ontap >= 9.2, then to our new 8200. But I'm not willing to spend a lot of money renting the swing gear and getting a lot of extra setup work basically because of a flaw in netapp software.
Thanks,
-- Jan-Pieter Cornet <johnpc@xs4all.nlmailto:johnpc@xs4all.nl> "Any sufficiently advanced incompetence is indistinguishable from malice." - Grey's Law
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters