This just occurred to me - a plan forward to allow data motion and migration to 64 bit

I will test it asap, but basically its this since vfiler migration on 32bit -> 64bit aggrs is not possible, 1) destroy the 64 bit destination aggrs and recreate as 32 bit < 16Tb (leave off disks in execs of 16Tb) 2) datamotion vfilers 32->32 bit aggrs (supported) 3) add remaining disks to aggrs to trigger 64 bit background migration

this should accomplish the twin goals of evacuating prod cluster for the tray upgrades, and getting us onto 64bit aggrs without downtime…

thanks, Fletcher.

On Feb 8, 2012, at 7:24 PM, Borzenkov, Andrey wrote:

As of now there is no known method to do it. ________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Thursday, February 09, 2012 03:37 To: toasters@teaparty.net Subject: Force 64bit aggr migration

Anyone know if its possible to force the in place 32->64bit aggr non-disruptive migration without having to add disk? I'm running into a 8.1R2 data motion issue where NMC is refusing to migrate vFilers from the 32 bit source cluster to the 64bit destination. The destination aggrs are at or above 16Tb so they need to be 64 bit

thanks

Fletcher

There is a way... But not supported.. :-) The only supported way is by adding disks...

Commands below were executed in diag mode (priv set diag)

ontap8-s*> vol create test aggr32b_to_upgrade 100g

Creation of volume 'test' with size 100g on containing aggregate

'aggr32b_to_upgrade' has completed.

ontap8-s*> df -h

Filesystem               total       used      avail capacity  Mounted on

/vol/test/                95GB      536MB       94GB       1%  /vol/test/

/vol/test/.snapshot     5120MB        0TB     5120MB       0% /vol/test/.snapshot

ontap8-s*> aggr 64bit-upgrade start aggr32b_to_upgrade -mode check

Checking for additional space required to upgrade all writable 32-bit

volumes in aggregate aggr32b_to_upgrade (Ctrl-C to interrupt)......

Upgrading a volume to 64-bit consumes additional free space in the volume. The

following table shows the space usage after each volume is upgraded to 64-bit:

Volume Name             Total          Used           Available      Capacity

-----------             -----          ----           ---------      --------

test                   100GB          5657MB         94GB           5%

ontap8-s*> aggr 64bit-upgrade start aggr32b_to_upgrade -mode grow-all

Checking for additional space required to upgrade all writable 32-bit

volumes in aggregate aggr32b_to_upgrade (Ctrl-C to interrupt)......

Started 64-bit upgrade on aggregate aggr32b_to_upgrade and all contained writable volumes

ontap8-s*> Fri Dec 16 13:58:59 GMT [ontap8-s:wafl.scan.64bit.upgrade.start:notice]: The 64-bit upgrade scanner has started running on aggregate aggr32b_to_upgrade.

Fri Dec 16 13:58:59 GMT [ontap8-s:wafl.scan.start:info]: Starting 64bit upgrade on aggregate aggr32b_to_upgrade.

Fri Dec 16 13:59:00 GMT [ontap8-s:wafl.scan.64bit.upgrade.start:notice]: The 64-bit upgrade scanner has started running on volume test.

Fri Dec 16 13:59:00 GMT [ontap8-s:wafl.scan.start:info]: Starting 64bit upgrade on volume test.

Fri Dec 16 13:59:01 GMT [ontap8-s:wafl.scan.64bit.upgrade.completed:notice]: The 64-bit upgrade scanner has completed running on aggregate aggr32b_to_upgrade.

Fri Dec 16 13:59:01 GMT [ontap8-s:wafl.scan.64bit.upgrade.completed:notice]: The 64-bit upgrade scanner has completed running on volume test.

ontap8-s*> aggr status aggr32b_to_upgrade

Aggr State           Status            Options

aggr32b_to_upgrade online          raid_dp, aggr

64-bit

Volumes: test

Plex /aggr32b_to_upgrade/plex0: online, normal, active

RAID group /aggr32b_to_upgrade/plex0/rg0: normal, block checksums

On Thu, Feb 9, 2012 at 8:10 AM, Gelb, Scott sgelb@insightinvestments.com wrote:

That would work…or if a non-guaranteed migration is ok you can also just run vfiler migrate from the command line of the target system.  When the mirror breaks it converts 32 to 64 though so check the burts that came out with that.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Wednesday, February 08, 2012 7:33 PM To: Borzenkov, Andrey Cc: toasters@teaparty.net Subject: Re: Force 64bit aggr migration

This just occurred to me -  a plan forward to allow data motion and migration to 64 bit

I will test it asap, but basically its this since  vfiler migration  on 32bit -> 64bit aggrs is not possible,

1. destroy the 64 bit destination aggrs and recreate as 32 bit < 16Tb (leave off disks in execs of 16Tb)

2. datamotion vfilers 32->32 bit aggrs (supported)

3. add remaining disks to aggrs to trigger 64 bit background migration

this should accomplish the twin goals of evacuating prod cluster for the tray upgrades, and getting us onto 64bit aggrs without downtime…

thanks,

Fletcher.

On Feb 8, 2012, at 7:24 PM, Borzenkov, Andrey wrote:

As of now there is no known method to do it. ________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Thursday, February 09, 2012 03:37 To: toasters@teaparty.net Subject: Force 64bit aggr migration

Anyone know if its possible to force the  in place 32->64bit aggr non-disruptive migration without having to add disk? I'm running into a 8.1R2 data motion issue where NMC is refusing to migrate vFilers from the 32 bit source cluster to the 64bit destination. The destination aggrs are at or above 16Tb so they need to be 64 bit

thanks

Fletcher

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

-- Vriendelijke Groeten, Robin Mesotten robin.mesotten@gmail.com