SnapMirror is the best tool to use in
this situation if you’re migrating from Flexvols to Flexvols. It’s
really simple.
Create your baseline SnapMirror (qtree
or volume) a week in advance and set up your incremental schedule based on
filer loads. You can start with a min daily/nightly incremental. I like to
monitor the SnapMirror status output after each incremental to get an idea on
the amount of data transferring. Let’s stay you started the baseline on a
Sunday, first incremental on a monday and the cutover date was Friday evening @
10pm. On Friday, you want to bump up the incrementals more frequently so the
deltas get transferred more frequently. Once 10pm rolls around, disconnect the
LUN and run a couple more incrementals. Break the snapmirror relationship but
don’t release it yet until you confirm the data integrity. Connect to the
LUN. Confirm your data and clean up your SnapMirror relationship. You should be
able to do everything under 30 mins….if you’re prepared.
4Base Technology, Inc.
From:
owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Suresh Rajagopalan
Sent: Thursday, April 26, 2007
3:02 PM
To: toasters@mathworks.com
Subject: Data migration
I need to migrate a 1.4Tb lun from one filer to another with
minimal downtime (< 30 mins). So clearly some copying of data has to
be done prior to the actual move.
Would snapmirror or flexclone be the most appropriate for
this? I’m not sure how I would get a consistent copy of the
lun over to the other filer. This is not a database, the lun contains
flat files on NTFS.
Thanks
Suresh