Netapp snapmirror replication¶
- Acquire read/write access to the snapmirrored resources. Either swapping the syncs direction (in geocluster mode), or breaking-off the syncs (default disaster recovery mode).
- sync update
- Trigger a snapmirror sync.
- sync quiesce
- Trigger an ultimate snapmirror sync then suspend the resync scheduling.
- sync resume
- Resume snapmirror sync schedule (rollbacks the effect of quiesce).
- sync break
- Break-off the snapmirror resource.
- sync resync
- Re-establish the snapmirror synchronization.
- sync swap
- Re-establish the snapmirror synchronization using current destination as new source.
The --force flag is honored by the 'start' command only. It disables the exit on quiesce failure in the 'quiesce -> break' sequence. Be aware it means that the service will take over with a lagged data cursor.
- The snapmirror are operational and the lag in under sync_max_delay
- The snapmirror are in one of the following state: * transfer is in progress * lag is beyond sync_max_delay
- slave filer is unreachable
- resource is not in snapmirrored state
Service configuration for Netapp¶
Key-based ssh access to the filers. The root account's key-pair is used by OpenSVC. The filer account used is settable in the service configuration file. The filer account must have snapmirror handling capabilities granted. Cluster mode
- This is the default disaster recovery mode. Upon service startup on a DRP node, the snapmirrored resources are quiesced if the master filer is still joinable, then broken-off. The DRP node data cursor on the broken-off resources is considered volatile (still can be manually synchronized to the primary filer before failback to production node).
- This mode is dedicated to multi-site clusters. Upon service startup on a secondary node, the snapmirrored are quiesced and sync directions are swapped to set the 'source' to the filer local to the secondary node taking over the service.
The mode is deduced from the node's host mode : a PRD host mode implies the swap sync mode, otherwise the split sync mode is selected.
Service configuration file¶
;type = netapp # # 'filer' # mandatory. 'filer' points the nas head to pass commands to. In most case # you need to specify localized filers using the 'filer@node' syntax. # ;filer@vm4 = nasprd ;filer@vm5 = nasdrp # # 'path' # mandatory. Specifies the volume or qtree to drive snapmirror on. # ;path = /vol/vol1 # # 'user' # mandatory. Specifies the user used to ssh connect the filers. Nodes should # be trusted by keys to access the filer with this user. # ;user = nasadm # # 'sync_min_delay' # optional. Set the minimum delay between syncs in minutes. If a sync is # triggered through crond or manually, it is skipped if last sync occured # less than 'sync_min_delay' ago. # ;sync_min_delay = 30 # # 'sync_max_delay' # optional. Default value is 1440 minutes (1 day). Unit is minutes. # This sets to delay above which the sync status of the resource is to be # considered down. Should be set according to your application service # level agreement. The cron job frequency should be set between # 'sync_min_delay' and 'sync_max_delay'. # ;sync_max_delay = 1440
Netapp user account setup¶
Create a role¶
toaster> useradmin role add opensvc -a login-ssh,cli-snapmirror*,cli-snap*
toaster> useradmin group add osvc -r opensvc toaster> useradmin user add opensvc -g osvc
Setup ssh key-based authentication¶
If the ssh setup has already been done skip the following command. Run secureadmin status to check.
toaster> secureadmin setup ssh SSH Setup --------- Determining if SSH Setup has already been done before...no SSH server supports both ssh1.x and ssh2.0 protocols. SSH server needs two RSA keys to support ssh1.x protocol. The host key is generated and saved to file /etc/sshd/ssh_host_key during setup. The server key is re-generated every hour when SSH server is running. SSH server needs a RSA host key and a DSA host key to support ssh2.0 protocol. The host keys are generated and saved to /etc/sshd/ssh_host_rsa_key and /etc/sshd/ssh_host_dsa_key files respectively during setup. SSH Setup will now ask you for the sizes of the host and server keys. For ssh1.0 protocol, key sizes must be between 384 and 2048 bits. For ssh2.0 protocol, key sizes must be between 768 and 2048 bits. The size of the host and server keys must differ by at least 128 bits. Please enter the size of host key for ssh1.x protocol  Please enter the size of server key for ssh1.x protocol  Please enter the size of host keys for ssh2.0 protocol  You have specified these parameters host key size = 768 bits server key size = 512 bits host key size for ssh2.0 protocol = 768 bits Is this correct? [yes] Setup will now generate the host keys. It will take a minute. After Setup is finished the SSH server will start automatically. toaster> Tue Feb 9 10:02:20 GMT [secureadmin.ssh.setup.success:info] SSH setup is done and ssh2 should be enabled. Host keys are stored in /etc/sshd/ssh_host_key, /etc/sshd/ssh_host_rsa_key, and /etc/sshd/ssh_host_dsa_key. toaster>
Trust all PRD nodes root public keys on all filers. Trust DRP nodes root public keys only on their local filer.
Append the keys to
$ cat /nasprd/vol/vol0/etc/sshd/opensvc/.ssh/authorized_keys2 ssh-dss AAAAB3NzaC1kc3MAAACBAMGX7dH ... == root@vm5 ssh-dss AAAAB3NzaC1kc3MAAACBAIPCpkA ... == root@vm4
OpenSVC does not provide assistance in initial snapmirror configuration. The necessary steps are described below to help you kickstart a service setup. OpenSVC declines liability for your breaking your filers. For accurate information please refer to Netapp documentations.
On Source toaster : Ensure target toaster is trusted¶
nasprd> rdfile /etc/snapmirror.allow
Check that target toaster hostname in present in the file
On Target toaster : Restrict destination volume¶
nasdrp> vol restrict vol1
On Target toaster : Initialize snapmirror replication¶
nasdrp> snapmirror initialize -S nasprd:vol1 nasdrp:vol1
On Target toaster : Fill in the /etc/snapmirror.conf to specify the snapmirror policy¶
nasdrp> rdfile /etc/snapmirror.conf nasprd:vol1 nasdrp:vol1 - - * * * nasdrp:vol1 nasprd:vol1 - - * * *
The scheduling is disabled because syncs are drived by OpenSVC and that both replication directions are provisionned for swaps (one of them will appear as 'Uninitialized' in status).
Quiesce a replication¶
# svcmgr -s unxprdencap sync quiesce 2010-02-09 16:51:22,419 - SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror quiesce nasdrp:vol1
Resume a replication¶
# svcmgr -s unxprdencap sync resume 2010-02-09 16:49:29,059 - SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror resume nasdrp:vol1
Split a replication¶
# svcmgr -s unxprdencap sync break 2010-02-09 16:41:15,359 - SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror break nasdrp:vol1
Resync a replication¶
# svcmgr -s unxprdencap sync resync 2010-02-09 16:54:59,290 - SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror resync -f nasdrp:vol1
Diskstart in disaster recovery (split) mode¶
# svcmgr -s unxprdencap start --rid disk * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror quiesce nasdrp:vol1 * SYNC.NETAPP - INFO - start waiting quiesce to finish (max 300 seconds) * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror break nasdrp:vol1 * FS - INFO - mount -t nfs -o rw,intr,soft nasdrp:/vol/vol1 /unxprdencap/netapp
Diskstart in multi-site cluster (swap) mode¶
# svcmgr -s unxprdencap startdisk * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasprd snapmirror quiesce nasprd:vol1 * SYNC.NETAPP - INFO - start waiting quiesce to finish (max 60 seconds) * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasprd snapmirror break nasprd:vol1 * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror resync -f -S nasprd:vol1 nasdrp:vol1 * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasdrp snapmirror release vol1 nasprd:vol1 * SYNC.NETAPP - INFO - /usr/bin/ssh opensvc@nasprd snap delete vol1 nasprd(0099904947)_vol1.1 * FS - INFO - mount -t nfs -o rw,intr,soft nasprd:/vol/vol1 /unxprdencap/netapp