Subscribe
Accepted Solution

How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

Hi

 

I have a 11TB CIFS based NTFS volume with 4 qtree's on 7.3.7 controller, that I need to migrate to another controller, the problem I am having is that

 

if I use QSM-

 

Invoke-NaSnapmirrorInitialize -Source 172.16.1.1:/vol/Groups/- -Destination irv-gdc-san1a:/vol/Groups/qtree

 

I only get the base contents of the volume, and not the other qtree's that are co-mingled with folders in the base of the cifs share local path (/vol/Groups)

 

if I use VSM-

 

The volume would be replicated with all data / qtree's. but would remain 32bit.

 

Part of the issue I have is that this is over 10TB / 10 million files. I already have the QSM relationship for the base contents of the volume. If I setup additional QSM's, they would be adjacent to the base contents, and a single cifs share could not access. As part of the cutover plan, I am going to be aliasing the IP address since we have both Windows and Unix clients accessing this data from god knows where. Anyone have any suggestions? I am trying to make this a single cutover event, where the outage is less than an hour, and from previous expireance, if I move the contents from the base QSM  (irv-gdc-san1a:/vol/Groups/qtree --> irv-gdc-san1a:/vol/Groups) it could take hours, and I wouldn't be able to maintain permissions unless I used robocopy with the /MIR and /SEC switches.

 

Any suggestions? TIA!

-jon

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

Can you update to 8.1 or newer?

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

No, unfortunately the source is a single controller so I can't do a NDU, or take an outage...

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

I should clarify snapmirror target is HA pair of 3140's running 8.1.7p4, and as an end result I am trying to get everything to 64 bit volumes.

Thanks,
Jon

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

If you could not take an outage, you would not single controller. If you update source to 8.1 you can use VSM from 32 to 64 bit.

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

What about just migrating the volume a second time to another aggregate with VSM once on target controller? So 32bit volume on single 7.3.7 controller migrated with VSM to 32bit volume on target controller, then subsequent VSM / 64 bit conversion?

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

Yes, that's possible. Do not forget, that in-place conversion without increasing aggregate size beyond 16T is officially supported starting with 8.2.1 if my memory serves me right.

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

Hi Jon,

Is the destination aggregate on the FAS3140 a 64 bit aggregate? If so, you can simply perform a VSM migration from the 32 bit source aggr, the volume will be expanded to 64 bit automatically after breaking the snapmirror relationship.

 

If the destination aggregate is 32 bit and the FAS3140 controllers are running 8.1.4P4 or later you can perform an in-place aggregate extension without adding disks. Check out http://www.netapp.com/us/media/tr-3978.pdf page 7 for details.

 

I hope this helps!

 

Cheers,

d.

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

Destination controller is 3140 running 8.1.4P8, with 64 bit aggregates. I swear I have seen VSM destinations stay 32 bit like their source, but I guess I dont have a VSM to test that theory with. Either way it sounds like the approach  I am going to have to take as at least a first step.  At least I know not to use QSM, since it can't keep the folder heirearchy in my scenario.

 

 

Thanks!

-Jon

Re: How to migrate 32bit volume with qtree and non qtree data to 64 bit volume

You are right of course. I do not know whay I was sure we need 8.1 source to perform 32 to 64 bit VSM; it is only reverse sync that requires it. Thank you!