NetApp vFiler DR with Data ONTAP Simulator Part 10: Disaster Failover

This article is part of a series.

Disaster Failover is very similar to a planned failover described in part 9 of this series. Because the master is not available unexpectedly the vFiler cannot be stopped and the temporary replication from slave to master has to be set up later before the rollback. When the master is powered on again you have to take care that the vFiler is not started automatically. Otherwise the vFiler is running on master and slave simultaneously. In comparison to the planned failover steps 1, 4 and 5 are moved from failover to rollback.

Read more gblog_arrow_right

NetApp vFiler DR with Data ONTAP Simulator Part 9: Planned Failover

This article is part of a series.

With the configuration tasks of the previous parts you now have an environment where netapp01 can be considered as master and netapp02 as slave. Clients use the share of the vFiler running on the master (netapp01) and the data is replicated to the slave (netapp02). Because of this replication if the master fails you can also start the vFiler on the slave without data loss.

Master-Slave-Configuration

Read more gblog_arrow_right

NetApp vFiler DR with Data ONTAP Simulator Part 8: Create shares on vFiler

This article is part of a series.

In this article a CIFS and a NFS share are created. Unfortunately shares on a vFiler cannot be configured in OnCommand System Manager. Instead the console or SSH has to be used. SSH must be set up first in order to directly connect to the vFiler. You can do so from a session on the first simulator (netapp01). It is possible to run commands on the vFiler from here with vfiler run <name of the vFiler> <command>.

Read more gblog_arrow_right

NetApp vFiler DR with Data ONTAP Simulator Part 7: Synchronous vFiler DR

This article is part of a series.

Note: You can skip this instructions if you only need a asynchronous mirror like described in part 6 and already configured vFiler DR.

In part 6 of this series vFiler DR was created with a asynchronous SnapMirror. This means it takes some time before the data of the vFiler is mirrored to the second simulator. To make sure data is written to the vFiler and its mirror simultaneously you have to create a synchronous SnapMirror. This works only if the volumes of the vFiler have a size of at least 10 GB (as created in part 4). In addition you have to make sure DNS name resolution is working (each simulator has to be able to resolve the other one). If you didn’t configure the DNS settings during initial setup of the simulators (also not configured in part 1) you can do so via OnCommand System Manager (Configuration => Network => DNS). If no DNS server is available you can also add the IPs to the file /etc/hosts on both simulators.

Read more gblog_arrow_right

NetApp vFiler DR with Data ONTAP Simulator Part 6: Create vFiler and configure vFiler DR

This article is part of a series.

Note: In this article vFiler DR is created with asynchronous replication. If you need synchronous replication only create the vfiler as described in this part and then skip forward to part part 7. Do not follow the steps described in the section “Configure vFiler DR”.

Now it is finally time to create the vFiler on the first simulator (netapp01). You can use OnCommand System Manager

or the command line via SSH.

Read more gblog_arrow_right