cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Three node campus cluster with storage array replication

Dear All,

We have a requirement for three node campus cluster where i need to integrate a netapp snapmirror replication.Two node is in primary site for HA along with dedicated storage and single node is at DR along with separate storage. extended lan and san available across the sites. The replication mode is async.

The question is whether the following configuration for snapmirror resource will work or not ? what are the other options to make it work.

similar setup we have done it in the past but that was with HP storage.

NetAppSnapMirror SM (

VolumeName = unixvol

SnapMirrorSchedule = "0-59/5 * * *"

LocalFilerName @node1 = netapp1

LocalFilerName @node2 = netapp1

LocalFilerUserName = root

LocalFilerPword = aoaMboDodOhmPocMe

RemoteFilerName @node3 = netapp2

RemoteFilerUserName = root

RemoteFilerPword = aoaMboDodOhmPocMe

)

 

We have similar setup for hp eva ca for two node cluster

EVACA eEVACA (

                ManagementServer = "172.16.236.200"

                LocalEVAName @node01 = PR-EVA

                LocalEVAName @node02 = DR-EVA

                DRGroupName = DRG_VCS

                SSSUPath = "/opt/Hewlett-Packard/sssu_linux_x64"

                )

3 Replies
Highlighted

Hello,   Interesting setup

Hello,

 

Interesting setup and not what you'd see usually. If you have an extended SAN, why use Snapmirror? Why not zone node3 into the "Local Filer"?

 

From the config post above i don't think it will work. I approach it as if its a GCO and there are two resources (one per cluster). In this config you would just use Global attributes and in prod netapp1 would be local, and netapp2 would be remote. Vice versa in DR.

So in your config using local attributes, you have to add the perspective to location of the filers from each node. From nodes 1 & 2, netapp1 would be local, and netapp2 would be remote, and from node 3, netapp2 would be local and netapp1 would be remote.

So I think it should look like this. And you should probably configure zones for the service group too.

 

NetAppSnapMirror SM (

VolumeName = unixvol

SnapMirrorSchedule = "0-59/5 * * *"

LocalFilerName @node1 = netapp1

LocalFilerName @node2 = netapp1

LocalFilerName @node3 = netapp2

LocalFilerUserName = root

LocalFilerPword = aoaMboDodOhmPocMe

RemoteFilerName @node1 = netapp2

RemoteFilerName @node2 = netapp2

RemoteFilerName @node3 = netapp1

RemoteFilerUserName = root

RemoteFilerPword = aoaMboDodOhmPocMe

)

Highlighted

Hi uvahpux, If you want to

Hi uvahpux,

If you want to use SnapMirror on NetApp filers, it's working all from filer controllers' configuration. There is no need to put it into VCS/GCO config file.

Since NetApp SnapMirror configuration is on filer's controller OS and it's worked via network between filers, there is no chance to make server trigger or manage it. So no effect from VCS/GCO.

And put filler root account's password in VCS/GCO config file is not safe as it's shows as plaint text.

From VCS/GCO you need to configure application using volumes from NetApp filers only.

Highlighted

Incorrect, we have an agent

Incorrect, we have an agent "NetAppSnapMirror" that controls the failover. And that is the configuration he posted above.