2013-06-04 05:31 PM
Not sure if I am attempting some thing that is not possible, but I thought I had done this before.
Have a new NetApp system at our DR site
Need to migrate/move volumes from old FAS to new FAS whilst maintaining history etc in OnCommand Unified Manager version (5.2RC1) along with the SnapMirror and Snapvault relationships.
I don't want to have to re-baseline all the relationships.
We are currently running ONTAP 7.3.6 at Prod and DR , new DR system is running ONTAP 8.1.1 .
I have added the new aggregates on the new FAS in to the resource pools for the Datasets.
I am then using the Secondary Space Wizard to setup the migration, which it does, but when I run the job this is the error I get.
FASXX:/DC_AU_DFM_Data: Could not proceed with baseline transfer as the migration source volume 'FASBB:/DC_AU_DFM_Data'(14747) has been resized to 168 GB. Refresh host information either by executing 'dfm host discover' CLI or navigate to 'Hosts > Storage Systems' page in Management Console and press 'Refresh' button for 'FASBB.dc.local'(76)
FASBB is the old system FASXX is the new system
2013-06-04 10:04 PM
You should use space management wizard only on snapmirror / snapvault destination volumes.
AFAIK I am not sure whether you can migrate a vol (vol move) in 7-mode from one controller to another.
AFAIk in 7-mode vol move is from one aggr to another.
2013-06-06 03:11 PM
Can you clarify few things here ?
2013-06-06 03:18 PM
2013-06-07 02:57 AM
Can you try the migration once more and let me know if you still face this error ? If you are running 5.1 or later we have Dynamic secondary sizing for mirror.
It could be possible that during your process of migration start the destination volume( in case of migrations its the source) got resized.
Can you try the suggestion and re-run ? Because the update job resizes the volume on the filer, but the size isn't updated on the dfm database until the dfmonitor run( which by default runs once every 30min)
The migration wizard picks the size of the volume from the database and not the filer, so there is possibility that the data in the db could be stale during this time upto 30 mins.
2013-06-11 02:28 AM
Have just successfully migrated some other volumes.
the only difference I can see is that this volume that wont work has a provision policy type of SAN.
All the volumes that worked were NAS
2013-06-17 05:32 AM
Is there any Igroup or WWPN mapping done for luns in these volumes ?
What is the exact error message you get when you run this migration wizard ?
I recommend you to open a case with netapp, if you still face this problem.