Hi Nils, i am in a similar position, could you list the steps if its not too much work?
Thanks a lot
Cris
--- On Mon, 7/28/08, Nils Vogels bacardicoke@gmail.com wrote:
From: Nils Vogels bacardicoke@gmail.com Subject: Re: Migrating data without service interruption : 3020 -> 3140 To: "Simon Vallet" svallet@genoscope.cns.fr Cc: toasters@mathworks.com Date: Monday, July 28, 2008, 12:00 PM Hi Simon,
On Mon, Jul 28, 2008 at 12:08 PM, Simon Vallet svallet@genoscope.cns.fr wrote:
Hi,
we just received a new 3140 cluster here to upgrade an
existing 3020c
production filer. And now we're looking for a way
to migrate the
existing data (~18TB) with the least possible
downtime.
Ideally, we would use SnapMirror to copy the data on
the new filer and
then transparently (for clients) switch the production
system,
similarly to what happens when a cluster member fails
over to the other
member. But we don't know if this is possible.
So the questions are:
- do you think such a procedure could be successful ?
- do you have any other ideas to migrate the data
without service
interruption ?
I've done this a dozen times, and it's succesfull, however not entirely without downtime. When switching over, you will need to do a last mirror update to catch the last changes with CIFS disabled on the source filer, this usually means a few seconds per volume of downtime and a few hickups when reconfiguring the paths to CIFS shares. If you want me to, I could write you down the basic steps you take to be sure that you will not lose any client data.
Without any interruption, we usually use HSM-like configurations such as Acopia (now F5) and the likes have.
HTH & HAND,
-- Simple guidelines to happiness: Work like you don't need the money, Love like your heart has never been broken and Dance like no one can see you.