Your SlideShare is downloading. ×
vFiler migration with SM
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

vFiler migration with SM

568

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
568
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
27
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. OR vFiler Migration with SM TBC PPMC Quincy Re: 3 Way vFiler Migration? created by Scott Gelb in Data ONTAP - View the full discussion 3 way isn't supported... but for vFiler DR, you could have 2 targets.. .A can vFiler DR to both B and C. For migrate and data motion it is a one way thing... if you want to create multiple vFiler targets then I would use vFiler DR and use separate IP addresses on activation if that is the goal. vfiler migration and data motion move an entire vfiler and handle the mirrors in the
  • 2. vfiler process. So if 50 volumes in the vfiler, all is handled by data motion in the NMC or the vfiler migrate command. The requirements are in the data motion guide with limits on volume counts (depends on controller type). The target filer needs to have the exact same volume names and same ipspaces for the vfiler then it migrates. Prove of Concept Red Hat Enterprise virtualization Environment Current Status: FilerA (Prod1) and DR FilerC are in the same location FilerB (Prod2) another location Customer having issues with Snapmirror transfers Customer is replacing Production Source filer with a filer that is in another location SnapMirror relationship has been setup between FilerA (Prod1) and FilerB (Prod2) FilerA (Prod1) has a relationship with DR FilerC FilerB (Prod2) will be future source for DR FilerC Vfiler migration will be between FilerA and FilerB until FilerA is taken from production SnapMirror transfers in process to move all volumes from FilerA(Prod1) and FilerB(Prod2) To eliminate transfer issues between FilerB(Prod2) and DR FilerC resync will only be neccessary Steps Taken: Setup WebEX Asked customer to connect WebEX Asked customer to run through the process of performing SnapMirror transfer between filers Customer able to resync between FilerA and FilerB Asked customer to run command snap list vol name to display the common snapshot between all three filers
  • 3. No common snapshot between FilerB and FilerC Asked customer to run command snap create vol name to create a common snapshot between all three filers After the common snapshot is in place break relationship between Filer A and B for that volume Asked customer to perform a snapmirror update -S between source and destination Asked customer to check status of snapmirror for test volume Common snapshot available on both source and destination After changes are made on the Source (Prod2) customer will need to perform resync Customer will modify snapmirror relationship source on DR FilerC to FilerB (Prod2) Next Steps: Customer will perform all transfers during scheduled downtime Current Business Impact: None Contacts: Doug Cox - Douglas.Cox@providence.org - (503) 216-6064 Update : Case text : Public Notes - 01/20/2012 13:51:37 PST: Bryan Giddens Visibility : PUBLIC Note: Did a webex 626728560 The customer wanted to move the snapmirror source from 2855 to 8086 gave the customer a KB, customer said he was going to use on a test system. Moving volume SnapMirror sources http://now.netapp.com/NOW/knowledge/docs/ontap/rel80/html/o ntap/onlinebk/GUID-6C850BA4-E522-4F68-841FD7E273ADE782.html Subject : E-mail : NetApp Log # 2002829254 , Case Update Notificatio 01/20/2012 13:51:37 PST: Bryan Giddens
  • 4. Visibility : PUBLIC Note: This is a case notification message. The below case has been updated. Please take appropriate action. Update Type: Status has been updated Public Notes Added: By: Bryan Giddens (GIDDENS) Did a webex 626728560 The customer wanted to move the snapmirror source from 2855 to 8086 gave the customer a KB, customer said he was going to use on a test system. Moving volume SnapMirror sources http://now. netapp.com/NOW/knowledge/docs/ontap/rel80/html/on

×