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.
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
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.
Script: Bash: File Retention
Summary: A bash script for (log) file retention.
Date: 27 Jun 2011
Refactor: 16 April 2025: Checked links and formatting.
SLES Installation Update Server 11
Summary: How to setup a SLES 11 Installation Server.
Date: Around 2012
Refactor: 16 April 2025: Checked links and formatting.
The installed SLES 11 is installed through this installation report
Although there is already an article on the Suse Installation Update Server, I created this article especially for 11 (64 bit). This article will be less extensive and will only cover installation and update services for SLES 11, while the original article explains the installation for openSuse, SLES 10, updating them, and combining multiple installation and update services.
Before you can start the installation and configuration you'll need storage for the installation and update files. I created a 50 GB disk and created a ext3 filesystem (without updating access time) which will be mounted on /var/data.
When the filesystem is mounted create two directories which will serve as the install and update root:
/var/data # ls -l total 24 drwxr-xr-x 3 root root 4096 Aug 6 12:15 install drwx------ 2 root root 16384 Aug 6 11:54 lost+found drwxr-xr-x 2 root root 4096 Aug 6 11:55 updates