For NFS SnapMirror offers volume migration; it still takes time to perform the last sync, so it is obviously not fully transparent; but as long as your clients can wait for it, it is as good as you can get.
For CIFS you could migrate data, configure the same name/IP for new filer and start services. It will never be fully transparent (nor is normal cluster failover for CIFS).
For FCP/iSCSI the only way to do it (I can think of) is to use host side mirroring. Add new LUNs, mirror the old one onto new, them break mirror and remove old LUNs.
С уважением / With best regards / Mit freundlichen Grüβen
--- Andrey Borzenkov Senior system engineer
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Simon Vallet Sent: Monday, July 28, 2008 2:08 PM To: toasters@mathworks.com Subject: Migrating data without service interruption : 3020 -> 3140
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 ?
Cheers, Simon
--
Simon Vallet Ingénieur Système/Réseaux CEA DSV/IG/GEN - Genoscope Tél : +33 1 60 87 36 06 Mél. : svallet@genoscope.cns.f