2012-09-20 06:54 AM
We have LUN a which needs to be moved from one filer to another filer can anybody help me out how to perform this do i need to have a LUN created already at the destination filer of same size or larger to migrate please help me with detailed steps.
Note :- Both the filers are in A-A CLUSTER mode and are FAS2040 now please let me know how i am gonna proceed on this .
2012-09-20 11:52 PM
Yes, as hmuellerpuma said please use snapmirror.
Can you please tell :
1. Is it an iSCSI or FC LUN? Wont make any difference when doing snapmirror.
2. What is this LUN currently used for? Is it used by an Application like exchange etc..?
2012-09-21 12:16 AM
This is a FC LUN. correct...there is no difference.
but as larger as the lun is, as longer takes the delta.
the LUN is used for a Laptop Backup System.
funny thing is, i managed it to mirror from a 32 to a 64 bit aggregate :-)
2012-09-21 06:17 AM
Actually, does it really matter if this is an iSCSI or FC LUN ? and does it really matter which application is using that ?
Snapmirror is volume based so this copies everything below a volume...doesnt matter if its files of a LUN ( which is actually a file in the Volume )
so more important would be giving more information how to do that, limitations and their workaraounds like no mirror from a 32 to a 64 bit aggregate.
and the workarround is a qtree snapmirror.
2012-09-21 10:58 AM
Thats true... but i assume that Nayab is aware of this...He wrote "We have LUN a which....."
So do you agree that if he already has a LUN that this might be already in use and an igroup was already created for this LUN and this igroup was already MAPPED ?
I think he also ZONED it on the FC Switches :-)
Otherwise this request would be senseless... unused LUN ...empty ...moving ??? doesnt make any sense...or do you disagree ?
If it would be unsued, i would create a new Volume/LUN on the other Filer and delete the old one :-)
So the point is that he has to snapmirror that (if he has the License to do so) and has to do the prerequisites as described in several tecnical documents.
To be exactly , we have to ask if he has a Snapmirror Licence and if not, to ask if he could unmap the LUN so that this could stay in an unaccessed state fer a certain time
(depends on the size) so he would have the option to use vol copy or ndmpcopy.
Thats the think we have to ask....not if this is an iSCSI or FC LUN.
2012-09-22 12:47 AM
Coming back to point:
1. Is it an iSCSI or a FC LUN? There is "NO" principle difference in the method of snapmirroring any of these across to the destination. I just want to understand the design here.
2. Is the LUN being using by any application like exchange or oracle? - If yes, then you "can't" simply start the snapmirror. Snapshots is the very basis of snapmirror. When you start the snapmirror, a snapshot is taken of the Source. Having the LUN used by any applications I mentioned, wont give you a consistent copy of snapshot. You need to Quiece the I/O before you start the snapmirror. There are many ways to achieve this.
Explain us a bit about the current senerio and we will help you with the steps. Also to help yourself... be prepared to answer questions that people may ask you... this helps them in better understanding your problem/requirement.
@All: There are multiple method of achiveing the same thing... Just because you dont know ...doesn't mean it can't be done that way.
2012-09-22 10:16 AM
Okay, I am not pointing fingers to anyone but bringing it back to the topic.
Some of the things doesn't make sense to you ? Which things ?
A snap mirror to another filer makes a snapshot ????
Ever observed the transfered data and time when initiated a snapmirror ? Or updated it?
It fully copies over the data and not only a snapshot.
What you say is not true.
Indeed, what you say about the consistency is true.
A snapmirror done on a lun with a database in access is not consistent and not really useable.
So of course the lun must not be in access but only just before you do the last steps before breaking the mirror.
Best thing would be, stopping the database and disable the host side port(s) on the fc switch, then quisece it (means actually last delta will be written where lun io is stopped) and then break the mirror.
Don't forget to change the lun serial of the new lun.
Create Igroup (iscsi or fc), map it and change the zoning fitting to the destination filer. If it is the cluster partner, it should be already zoned before.
What you say about that you can't start a snapmirror while a lun is in access, yes you can and this usually done if you want to copy over a lun to another filer. Just think of a 15 TB LUN to copy over.
Think about how long it takes and that's the way how this is done. As said above, only the last delta must be copied over after the application was shut down properly and the lun is not in access.
8 years of netapp experience proves that what I write.
Senior Administrator Linux & Storage
Wuerzburger Str. 13
Tel: +499132 812415
Fax: +499132 8142415
Cell: +49151 14743929