Netapp White Paper

Netapp White Paper

STEP 1 Setup DR vFiler fas6280b_vfiler1 from FAS6280B to  FAS6280A and FAS3270

vFiler DR fas6280b_vfiler1 from simulator node fas6280b to both fas6280a and fas3270

Step 1a - fas6280b_vfiler1 on FAS6280B to  FAS6280A DR vFiler

  • Source/target volumes and IPSpaces must exist with the same name – pre-set already in the sims)
  • Do not protect volumes used by vFiler DR with Protection Manager
  • Verify that SnapMirror is running on the source controller
  • fas6280a>snapmirror on
  • fas6280a>vfiler status -a # no vfiler running since we migrated in lab5
  • fas6280a> vfilerdr configure -c secure -l root:netapp01
  • “y” to keep the same IP address and subnet (you can change for DR)
  • use the same 255.255.255.0 subnet
  • “n” to use different dns (keep the same DNS since you can change for DR)
  • use “ns1” interface on the drvfiler
  • fas6280a> vfilerdr status
  • fas6280a> snapmirror status
  • fas6280a> vfiler status -a # you will see the stopped drvfiler

Step 1b - fas6280b_vfiler1 on FAS6280B to  FAS3270 DR vFiler

  • Use “-s” option for snapmirror sync (ignore “too many active transfers at once errors” from the simulator)
  • fas3270vfiler status -a
  • fas3270vfilerdr configure -s -c secure -l root:netapp01
  • enter nothing for “alternate” IP twice when it asks each time
  • “y” to keep the same IP address and subnet (you can change for DR)
  • use the same 255.255.255.0 subnet
  • “n” to use different dns (keep the same DNS since you can change for DR)
  • use “ns1” interface on the drvfiler
  • fas3270vfilerdr status
  • fas3270 snapmirror status
  • fas3270vfiler status -a
  • Delete the DR vfiler (this was an example to create two, but for the lab we will failover locally to the FAS6280A node.)… the volumes will still be available to vfiler0.
  • fas3270vfilerdr delete # this will take some time
  • fas3270vfiler status -a

STEP 2 – Failover vFiler DR

FailovervFilerby activating the DR vfiler on FAS6280A after a disaster on the source FAS6280B

FAS6280B_vfiler1 will be shut down to simulate a disaster and FAS6280A_vfiler1 DR will be brought online (STOP on node B and dr on node A) *** NOTE THE FILER NAMES TO ISSUE COMMANDS ***

The elegance of vfilerDR is that is breaks ALL mirrors automatically and it also has all the shares, exports and iSCSI mappings from the source which automates the dr environment. Without vFilerDR, you would have to manually break mirrors, manually create shares, exports, igroups, mappings. vFiler DR also migrates the vfileretc configuration which is how it automates matching the source settings.

  • fas6280b> vfiler stop fas6280b_vfiler1 # simulate a disaster
  • fas6280b>ifconfig ns1 0.0.0.0 # Bug in 7.3.3/7.3.4/7.3.5 - The sim on nodeb leaves the IP on ns1 even the vfiler is stopped, so remove the .104 to eliminate the redundant IP on the network. Stopping the source vfiler should disable the IP but it does not in these releases – pending BURT
  • fas6280a> vfilerdr activate
  • fas6280b>vfiler status -a # confirm fas6280b_vfiler1 is stopped
  • fas6280a>vfiler status -a # confirm fas6280b_vfiler1 is running

STEP 3 – Resync vFiler DR back to Production and REsync DR

Step 3b - Resync the DR site from the 6280A dr node to the 6280B prod node.

  • fas6280b> vfilerdrresync-c secure -l root:netapp01
  • fas6280b> vfilerdr status
  • fas6280b snapmirror status
  • fas6280bvfiler status -a

Step 3c - Stop the DR vfiler on FAS6280A and activate the PROD vfiler on FAS6280B

*** NOTE THE FILER NAMES TO ISSUE COMMANDS *** this is the opposite of what we did in step 2 to activate the dr side.

  • fas6280a> vfiler stop fas6280b_vfiler1
  • fas6280a>ifconfig ns1 0.0.0.0# similar to before (pending BURT)
  • fas6280b>vfilerdr activate
  • fas6280b>ifconfig ns1 192.168.150.104 netmask 255.255.255.0 up# have to ifconfig since we turned it off before… we could use “setup -e” from the vfiler but that would whack setup files
  • fas6280b>vfiler status -a # confirm fas6280b_vfiler1 is running
  • fas6280a>vfiler status -a # confirm fas6280b_vfiler1 is stopped

Step 3d - Resync the PROD vfiler on FAS6280B to the DR vfiler on FAS6280A

  • fas6280a> vfilerdrresync-c secure -l root:netapp01
  • fas6280a vfilerdr status
  • fas6280a snapmirror status
  • fas6280avfiler status -a

Step 3e - Release snapmirror relationships left over from the resync of the original source

  • fas6280a>snapmirror release fas6280b_vfiler1_root fas6280b:fas6280b_vfiler1_root
  • fas6280a>snapmirror release fas6280b_vfiler1_san fas6280b:fas6280b_vfiler1_san
  • fas6280a>snapmirror release fas6280b_vfiler1_nas fas6280b:fas6280b_vfiler1_nas

STEP 4 – Add a Volume and IP to the source vFiler and add those resources to the DR vFiler

NOTE: FAS6280B is the Source and FAS6280A is the Destination (DR)

NOTE: “vfilerdrresync” updates snapmirror.conf to 0-59/3 (every 3 minutes) so it is recommended to save the snapmirror.conf file prior to a drresync so that you can reset to prior settings after the resync.

Adding VOLUMES

Step 4a Source vFiler – Create a new volume and add it to fas6280b_vfiler1 on FAS6280B

  • fas6280b> vol create new_vol -s none aggr1 20m
  • fas6280b> vfileradd fas6280b_vfiler1 /vol/new_vol
  • fas6280b> vfiler status -a fas6280b_vfiler1 (or -r) # confirm volume added to vfiler

Step 4b DR vFiler – Add the new source volume to the target vFiler by creating the volume then use dr resync on FAS6280A

  • fas6280a vol create new_vol -s none aggr1 20m
  • fas6280a> vfilerdrresync-c secure -l root:netapp01 # this will mirror the new volume (and also update snapmirror.conf so edit for prior schedule)
  • fas6280a vfilerdr status
  • fas6280a snapmirror status
  • fas6280avfiler status -a # confirm new_vol is now owned by the stopped drvfiler

Adding IPs (same as changing IPs – KB1011371)

Step 4c Source vFiler – Create a new IP and add it to fas6280b_vfiler1 on FAS6280B

  • fas6280b> vfiler add fas6280b_vfiler1 -i 192.168.150.110
  • fas6280b ifconfig ns1 alias 192.168.150.110 # this will link the vfiler IP to the ns1 interface. This can be done with “setup -e” but that would whack some vfileretc filers.
  • fas6280b> vfiler status -a fas6280b_vfiler1 # confirm .110 is configured

Step 4d DR vFiler – Create a new IP and add it to fas6280b_vfiler1 on FAS6280A

NOTE: this is not done with DR resync but is done on the DR vfiler itself, so adding or changing an IP is different than adding or changing a volume. Changing/adding/removing the DR vfiler IP is done on the DR vfiler itself. The initial IPs are given at the vfilerdr configure command and are not modified with a wizard, but by activating the DR vfiler. Be careful of DUPLICATE IPs if it matches the source. The ONLY way to modify this is to activate the drvfiler.

  • fas6280avfilerdr activate
  • fas6280a vfiler add fas6280b_vfiler1 -i 192.168.150.110 # duplicate IP will occur – disconnect or use no-vfiler-ip boot option if production if using the same ip
  • fas6280a> ifconfig ns1 192.168.150.110netmask 255.255.255.0 # we could run “vfiler run fas6280b_vfiler1 setup” and whack setup files too
  • fas6280b>vfiler stop fas6280b_vfiler1 # stop vfiler so we can resync
  • fas6280a>vfiler status -a # confirm fas6280b_vfiler1 is stopped
  • fas6280a> vfilerdrresync-c secure -l root:netapp01
  • fas6280a vfilerdr status
  • fas6280a snapmirror status
  • fas6280avfiler status -a # confirm .104 and .110 are attached to the vFiler

*** SIMILARLY you can use the method above to change IPs and remove IPs on the DR vFiler since IP settings are not used from the source vFiler. ***

STEP 5 – vFiler DR when Mirrors ALREADY exist on the target

This step must be completed to continue on with labs 6-9

ONTAP 7.3.5

  • *** With ONTAP 7.3.5, we have a new “-u” option in vfilerdr configure that will not re-initialize mirrors already initialized. *** Prior to this, we had to manually create the vfiler then stop and resync it. All mirrors in the vfiler must be initialized prior to using “-u”.
  • Procedure (7.3.5)
  • This step will show how to create a DR vfiler if mirrors already exist before vfiler DR. vfilerdr configure initializes mirrors from scratch which may not be desired if mirrors already exist for volumes. This procedure will create the drvfiler by manually creating it on the target (all mirrors done manually) then doing a drresync instead of a dr configure. If a customer has TeraBytes of Mirrors already running, then don’t want to run “vfilerdr configure” which will re-initialize those target mirrors. This procedure is also useful for when we ship drives between sites, snapmirror to tape, or use a third in the middle FAS controller to initialize mirrors.**
  • Using the fas6280b_vfiler1 source vfiler to the FAS3270 already has mirrors running. At a customer this might be a 10TB usable volume and you would not want to re-init with the “vfilerdr configure” method. So, mirror remaining volumes manually and manually create the drvfiler, then run “vfilerdrresync” to create the destination DR vfiler.
  • Mirror any remaining volumes NOT mirrored that are in the source vfiler (make sure to use the same volumes names on source and dest) – REPEAT for ALL volumes NOT mirrored yet – simulate mirrors already exist
  • fas3270vol restrict fas6280b_vfiler1_root
  • fas3270vol restrict fas6280b_vfiler1_nas
  • fas3270vol restrict fas6280b_vfiler1_san
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_root fas6280b_vfiler1_root
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_nas fas6280b_vfiler1_nas
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_san fas6280b_vfiler1_san
  • fas3270volcreate new_vol -s none aggr1 20m # create new missing volume
  • fas3270vol restrict new_vol
  • fas3270snapmirror initialize -S fas6280b:new_vol new_vol

NOW CREATE THE vFILER DR USING the ‘-u’ option..much easier than resync and the extra steps below to get the same result.

  • fas3270>vfilerdr configure -u -c secure -l root:netapp01
  • fas3270> snapmirror status
  • fas3270> vfiler status # note vfiler is now a drvfiler
  • Update/Fix /etc/snapmirror.conf for 3 minute interval update that was automatically updated by resync

SKIP *** Prior to ONTAP 7.3.5 *** SKIP TO NEXT STEP “CLEANUP”- SINCE OUR SIM is 7.3.5 – REFERENCE ONLY

  • This step will show how to create a DR vfiler if mirrors already exist before vfiler DR. vfilerdr configure initializes mirrors from scratch which may not be desired if mirrors already exist for volumes. This procedure will create the drvfiler by manually creating it on the target (all mirrors done manually) then doing a drresync instead of a dr configure. If a customer has TeraBytes of Mirrors already running, then don’t want to run “vfilerdr configure” which will re-initialize those target mirrors. This procedure is also useful for when we ship drives between sites, snapmirror to tape, or use a third in the middle FAS controller to initialize mirrors.**
  • Procedure (pre-7.3.5)
  • Using the fas6280b_vfiler1 source vfiler to the FAS3270 already has mirrors running. At a customer this might be a 10TB usable volume and you would not want to re-init with the “vfilerdr configure” method. So, mirror remaining volumes manually and manually create the drvfiler, then run “vfilerdrresync” to create the destination DR vfiler.
  • Mirror any remaining volumes NOT mirrored that are in the source vfiler (make sure to use the same volumes names on source and dest) – REPEAT for ALL volumes NOT mirrored yet – simulate mirrors already exist
  • fas3270vol restrict fas6280b_vfiler1_root
  • fas3270vol restrict fas6280b_vfiler1_nas
  • fas3270vol restrict fas6280b_vfiler1_san
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_root fas6280b_vfiler1_root
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_nas fas6280b_vfiler1_nas
  • fas3270snapmirror initialize -S fas6280b:fas6280b_vfiler1_san fas6280b_vfiler1_san
  • Quiese and Break all mirrors on target – REPEAT for ALL volumes
  • fas3270snapmirror status # wait until mirrors are initialized – REPEAT COMMAND UNTIL Mirrors are IDLE
  • fas3270snapmirrorquiesce fas6280b_vfiler1_root
  • fas3270snapmirror break fas6280b_vfiler1_root
  • fas3270snapmirrorquiesce fas6280b_vfiler1_nas
  • fas3270snapmirror break fas6280b_vfiler1_nas
  • fas3270snapmirrorquiesce fas6280b_vfiler1_san
  • fas3270snapmirror break fas6280b_vfiler1_san
  • Manually create the vfiler on the destination on the broken mirrors (you only need the root volume of the vfiler (using -r option) from the source since it will pick up member volumes automatically from the root configuration – the network will be unconfigured)
  • fas3270vfiler create fas6280b_vfiler1 -r /vol/fas6280b_vfiler1_root
  • Check the Status and Stop the vfiler
  • fas3270vfiler status -a
  • fas3270vfiler stop fas6280b_vfiler1
  • fas3270vfiler status -a
  • If the vFiler IP Address(es) are not correct, perform the next 3 steps to add the correct IP and remove the wrong IP….
  • Add .105
  • fas3270vfiler add fas6280b_vfiler1 -i 192.168.150.105
  • fas3270vfiler status -a
  • Remove .104
  • fas3270 vfiler remove fas6280b_vfiler1-i 192.168.150.104
  • fas3270vfiler status -a
  • Bring up the .105 interface so it is configured (using an alias since ns1 is already used for fas6280a_vfiler1 with the .103 IP)..you would also edit /etc/rc.. see below.
  • fas3270 ifconfig ns1 alias 192.168.150.105
  • fas3270vfiler status -a # note that the interface is now configured
  • Edit /etc/rc on fas3270 (.102) to add the ifconfig for this interface
  • Optionally – use vfiler setup FAS3270vfiler run vfilername setup -e ns1:ip:subnet - **** NOTE: You can ifconfig a new interface or ifconfig alias an existing interface from vfiler0, or run “vfiler run vfilername setup -e interface:ip:subnet”. Setup will wack several setup files (hosts, hosts.equiv, resolv.conf, exports, nsswitch.conf) so be careful to restore from .bak if needed. Setup -e will create an alias if the interface is already in use. Also note that the vfilerroute add default is not in the 3270 and should be added if the controller were to reboot and need the route to a different subnet.
  • CIFS to \\192.168.150.102\c$
  • Open \etc\rc … add the line below the ifconfig of ns1
  • ifconfig ns1 alias 192.168.150.105
  • Backup /etc/snapmirror.conf first since the file will be modified so that the mirror schedules for the vFiler’s volumes are replicated every 3 minutes. Save the file so you can change back to the prior schedule.
  • fas3270rdfile /etc/snapmirror.conf
  • Run a DR resync from source to target *** THIS IS THE TRICK to RESYNC even though DR CONFIG was NEVER done, but resync still works as long as all names, ipspaces, active mirrors and volumes are the same and exist.
  • fas3270vfiler stop fas6280b_vfiler1 # if not stopped already
  • fas3270vfiler status # note vfiler is stopped
  • fas3270vol create new_vol -s none aggr1 20m # create new missing volume
  • fas3270vol restrict new_vol
  • fas3270snapmirror initialize -S fas6280b:new_vol new_vol
  • *** WAIT FOR VOLUME to show online (console message) from the vFiler ***
  • fas3270snapmirrorquiesce new_vol
  • fas3270snapmirror break new_vol
  • fas3270vfilerdrresync-c secure -l root:netapp01 # instead of dr configure, we resync the manually created vfiler.
  • fas3270snapmirror status
  • fas3270vfiler status # note vfiler is now a drvfiler
  • Update/Fix /etc/snapmirror.conf for 3 minute interval update that was automatically updated by resync

Cleanup

  • Stop the DR vfileron FAS6280B and activate the vFiler on the FAS3270
  • fas6280b> vfiler stop fas6280b_vfiler1
  • fas6280b>vfiler status -a # confirm fas6280b_vfiler1 is stopped
  • fas3270vfilerdr activate
  • fas3270 vfiler status -a # confirm fas6280b_vfiler1 is running
  • Halt the cluster simulator nodes since we will do the rest of the labs on the FAS3270
  • fas6280a> halt -f
  • fas6280b> halt -f

1MultiStore Hands-On Lab 5: vFiler DR

Top View