Andrey - does this mean datamotion (vFiler migration) should be possible between 7.3.5.1 and 8.1?
(currently we get the error  "Minimum ONTAP version required for Automated  Online Migration is 7.3.3")
We are using the latest OnCommand 5 and  NMC 3.1 
Last time Netapp support supplied a testpoint workaround to bypass this check - it seems bogus - both source and dest are > 7.3.3

thanks

On Nov 29, 2011, at 9:17 PM, Borzenkov, Andrey wrote:

It’s right there in 8.1 release notes:
 
Starting with Data ONTAP 8.1, you can replicate volumes by using SnapMirror between 32-bit and
64-bit volumes. For both synchronous and asynchronous volume replication, the SnapMirror source
and destination volumes can be either 32-bit or 64-bit.
 
 
---
With best regards
 
Andrey Borzenkov
Senior system engineer
Service operations
 
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] 
Sent: Wednesday, November 30, 2011 9:14 AM
To: Borzenkov, Andrey
Cc: George T Chen; toasters@teaparty.net
Subject: Re: 8.1 32->64bit volume convert
 
Andrey, George - thanks for the feedback
 
Anyone have a list of the test points?
This one disables model checks - 
 
testpoint -m Dfmutil -n disable-model-checks -e 1 -r 1 –q


Is there one for ontap version checks?
Again - I am in pure test mode and have heard many conflicting stories - just want to see what's possible - we certainly were made to hold out for 8.1 for datamotion support for our upgrade plans.
 
Andrey - can you elaborate on your 8.1 statement ?  Cite any TR's ?
 
thanks
 
On Nov 29, 2011, at 9:01 PM, Borzenkov, Andrey wrote:


On the other hand, Sync Snapmirror and regular Async Snapmirror are block
based and do require that source and destination be the same type (either
32-bit or 64-bit).  


It's no more so for 8.1 which OP has.