or you can clear the snapmirror snapshot within the volume to remove the relationship.


--
Daniel Leeds
Senior Systems Administrator
Edmunds.com



-----Original Message-----
From: Kleinbrahm, Robert [mailto:rkleinbrahm@firstrepublic.com]
Sent: Fri 4/27/2007 1:03 PM
To: Suresh Rajagopalan; Leeds, Daniel; toasters@mathworks.com
Subject: RE: Data migration


I had the same thing happen to me. Solution is to turn snapmirror off on
both the source and destination before mounting the lun.



Netapps response on this.

1.                   Turn off SnapMirror on source filers

2.                   Turn off SanpMirror on destination filers.

Snapmirror no longer detects a previously SnapMirrored relationship.

When connecting to that LUN, the mounting process takes very little
time.



This worked for me and is quite fast.



Bob K.





________________________________

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Suresh Rajagopalan
Sent: Friday, April 27, 2007 12:05 PM
To: Leeds, Daniel; toasters@mathworks.com
Subject: RE: Data migration



OK I tried these steps with a small 20g volume.  Unmount the source lun,
do final snapmirror update, break mirror, set fs_size_fixed on. Now When
I try to connect the new lun via snapdrive on the destination, I get
(after the prompt for SFSR) the following error message:



Unable to connect disk

Failure in checking policies

Error: unable to find a snapshot containing a consistent virtual disk to
restore



This happens on both snapdrive 4.1 and 3.1.1R1.   What am I missing?



Thanks

Suresh









________________________________

From: Leeds, Daniel [mailto:dleeds@edmunds.com]
Sent: Thursday, April 26, 2007 3:26 PM
To: Suresh Rajagopalan; toasters@mathworks.com
Subject: RE: Data migration



snapmirror is what you want.  you can set it up anytime prior to the
migration and let it run on a schedule or manually to build the initial
baseline.  after that you just do a snapmirror update to keep it in
sync.

we have done this so many times it's second nature. quite simply:

1) create target volume and initialize snapmirror relationship to source
while lun is live and serving data
2) setup maintenance window and take filesystem/lun offline
3) perform final snapmirror update
4) break snapmirror relationship and bring new lun/volume online
5) mount new lun/filesystem and serve up data

snapmirror is a really handy product :)

--
Daniel Leeds
Senior Systems Administrator
Edmunds.com



-----Original Message-----
From: owner-toasters@mathworks.com on behalf of Suresh Rajagopalan
Sent: Thu 4/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







The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

First Republic Bank and its subsidiaries do not take responsibility for, or accept time-sensitive instructions sent by email including orders, funds transfer instructions or stop payments on checks. All instructions of this nature must be handled by direct communication, not email.

We reserve the right to monitor and review the content of all email communications sent or received. Emails sent to or from this address may be stored in accordance with regulatory requirements.