17.08.2015 Views

Veritas Cluster Server Bundled Agents Reference Guide

Veritas™ Cluster Server Bundled Agents Reference Guide - Symantec

Veritas™ Cluster Server Bundled Agents Reference Guide - Symantec

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

VCS hardware replication agent for NetApp<br />

NetApp SnapMirror agent<br />

165<br />

Sample configuration<br />

NetAppSnapDrive A2-NetAppSnapDrive (<br />

FilerResName = A2-NetAppFiler<br />

VolumeName = vol8<br />

ShareName = data08<br />

LUN = "d85.lun"<br />

MountPath = T<br />

Initiator @VCSW2K288 = { "21:00:00:e0:8b:1c:cc:45",<br />

"21:00:00:e0:8b:90:74:1a" }<br />

Initiator @VCSW2K287 = { "21:00:00:e0:8b:0e:3a:6a" }<br />

)<br />

NetApp SnapMirror agent<br />

The NetApp SnapMirror agent monitors the replication state of filer devices.<br />

When a failover occurs, the agent reverses the direction of replication.<br />

NetApp SnapMirror agent is configured as a resource of type NetAppSnapMirror.<br />

Dependency<br />

The NetApp SnapMirror resource depends on the NetApp Filer resource for<br />

operation.<br />

Agent functions<br />

Online<br />

If the state of the local filer device is SOURCE, the agent creates a lock<br />

file to indicate that the resource can come online. This effectively makes<br />

the devices writable for the application.<br />

If the state of the local filer is SNAPMIRRORED, the agent attempts to<br />

reverse the direction of replication by changing the state of the local filer<br />

to SOURCE and that of the original source to SNAPMIRRORED.<br />

If the original source filer is down, the agent performs a mirror breakoff<br />

to enable local write access, if the filer is not already broken off.<br />

If the original source returns to life, you must resynchronize the data<br />

manually.<br />

Offline<br />

Removes the lock file. The agent does not perform any filer operations<br />

because an offline function does not necessarily indicate an intention to<br />

give up the devices.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!