SHIFT-WIKI - Sjoerd Hooft's InFormation Technology
This WIKI is my personal documentation blog. Please enjoy it and feel free to reach out through blue sky if you have a question, remark, improvement or observation. See below for the latest additions, or use the search or tags to browse for content.
Resize SnapMirror Volumes
Summary: How to resize a volume in a snapmirror on a Netapp Filer.
Date: Around 2012
Refactor: 16 April 2025: Checked links and formatting.
Resizing snapmirrored volumes comes in two ways, resize the target volume and resizing the source volume. Since the target volume has to be at least the size of the source volume that's the one we resize first.
Note that if you shrink the volume you'll need to shrink the source volume first.
AIX NIM Disaster Recovery
Summary: ALthough AIX is by now on version 7.3 I find these old pages so fascinating I decided to keep them. On this page I'll show you how to use AIX NIM in your disaster recovery procedure. This page is for AIX 5.3 and AIX 6.1.
Date: Between 2010-2013
Refactor: 21 December 2024: Checked formatting.
Rename SnapMirror Volumes
Summary: How to rename volumes in a SnapMirror relationship on a NetApp filer.
Date: Around 2014
Refactor: 16 April 2025: Checked links and formatting.
Renaming volumes in snapmirror relationships is quite easy, and far more easy than I expected it to be. It comes down to turning snapmirror off on the target, simply renaming the volumes, editing snapmirror.conf and then turning snapmirror on again. This is an example output.
Starting at the target, turn snapmirror off and rename the target volume:
dstfiler01b> snapmirror status Snapmirror is on. Source Destination State Lag Status srcfiler01b:PRD_01B_006 dstfiler01b:TARGET_04B_006 Snapmirrored 00:00:26 Idle srcfiler01b:PRD_01B_007 dstfiler01b:TARGET_04B_007 Snapmirrored 00:00:26 Idle srcfiler01b:PRD_01B_001 dstfiler01b:TARGET_04B_001 Snapmirrored 00:00:26 Idle dstfiler01b> snapmirror off dstfiler01b> vol rename TARGET_04B_01 TARGET_04B_016 'TARGET_04B_01' renamed to 'TARGET_04B_016'
Then rename the volume on the source filer:
srcfiler01b> snapmirror status Snapmirror is on. Source Destination State Lag Status srcfiler01b:PRD_01B_006 dstfiler01b:TARGET_04B_006 Source 00:01:33 Idle srcfiler01b:PRD_01B_007 dstfiler01b:TARGET_04B_007 Source 00:01:33 Idle srcfiler01b:PRD_01B_001 dstfiler01b:TARGET_04B_001 Source 00:01:33 Idle srcfiler01b> vol rename PRD_01B_01 PRD_01B_016 'PRD_01B_01' renamed to 'PRD_01B_016'
Then, on the target edit the snapmirror.conf (remember you need an empty line at the end):
dstfiler01b> rdfile /etc/snapmirror.conf # 20130228 sjoerdhooft removed old snapmirrors srcfiler01b:PRD_01B_001 dstfiler01b:TARGET_04B_001 - * * * * srcfiler01b:PRD_01B_006 dstfiler01b:TARGET_04B_006 - * * * * srcfiler01b:PRD_01B_007 dstfiler01b:TARGET_04B_007 - * * * * dstfiler01b> wrfile /etc/snapmirror.conf # 20130228 sjoerdhooft removed old snapmirrors srcfiler01b:PRD_01B_001 dstfiler01b:TARGET_04B_001 - * * * * srcfiler01b:PRD_01B_006 dstfiler01b:TARGET_04B_006 - * * * * srcfiler01b:PRD_01B_007 dstfiler01b:TARGET_04B_007 - * * * *
Then, still on the target, enable snapmirror again:
dstfiler01b> snapmirror on dstfiler01b> snapmirror status Snapmirror is on. Source Destination State Lag Status srcfiler01b:PRD_01B_006 dstfiler01b:TARGET_04B_006 Snapmirrored 00:02:51 Idle srcfiler01b:PRD_01B_007 dstfiler01b:TARGET_04B_007 Snapmirrored 00:02:51 Idle srcfiler01b:PRD_01B_001 dstfiler01b:TARGET_04B_001 Snapmirrored 00:02:51 Idle
This wiki has been made possible by:
NetApp SnapMirror: Using Data
Summary: In this article I'll describe a couple of scenarios I could think of regarding the usage of snapmirror data.
Date: Around 2014
Refactor: 13 February 2025: Checked links and formatting.
First Scenario: ESX ISO Store
In this scenario we have a ISO store in our easy accessible acceptance location. This ISO store is used by ESX to mount ISOs to install VMs. However, we need these ISOs in our production environment as well. Copying the ISOs manually is quite a hassle, so we want this to go almost automatically.
Second Scenario: Disaster Recovery
In this scenario we'll pretend that our production site is unavailable and we'll have to do a failover using the snapmirrored data. When the disaster is resolved we'll also do a switch-back.
In these scenarios the snapmirror has already been set up as described here.