Showing posts with label ontap. Show all posts
Showing posts with label ontap. Show all posts

Thursday, 31 May 2012

NetApp OSSV Notes

So, Open System Snap Vault is NetApp's answer to backing up everything that you can't backup with SMVI (VMware VMs) or Snap Manager for Exchange/SQL Server/SharePoint.  Here's a table a notes about the different backup methods I'm finding out about from NetApp.  Quick overview from NetApp here.  Note, FAQ says that Linux OS backup is not supported.

It's software you install on a physical or virtual machine that does NetApp block level backup of any data (NetApp or otherwise) to a NetApp SnapVault node.

I thought it simply used NDMP protocol, but it seems it sends the data with QSM (Qtree Snap Mirror) and seems to setup the relationship or do the backup management with NDMP:


NDMP port (default value is 10000)
FILESERVER port-10555.
QSMSERVER port-10566.

Components:
  • NetApp Host Agent (install this first)
  • Host Agent Plugin (comes with Host Agent)
  • NetApp OSSV

Host Agent

Windows: agentsetup-2-7-win32.exe
Linux: ./agentsetup-2-7-linux.bin

Unpacking files needed for the installation ...
Beginning the installation ...

Starting agent.
        You may now point your browser to
            http://127.0.0.1:4092/welcome
        to configure the agent software.

This is NTAPagent service (which runs /opt/NTAPagent/ntap_agent) on linux 
or ntap_agent.exe on Windoze





Like this diagram shows, set a password for the "admin" login on the Host Agen application on your backup client.  This is unhelpfully referred to as the Mgt API Password here.










Install Host Agent Plugin

Windows runs this automatically: 
c:\Program Files\netapp\snapvault\manageability\InstallHostAgentPlugins.exe

But for Linux you need to run:
./ossv/manageability/InstallHostAgentPlugins.sh
before you can get DFM to connect to OSSV on your backup client.

OSSV
License OSSV on your SnapVault servers with these generic licenses available from NetApp Now website.

Install OSSV on your backup client
uses port 10000 for NDMP backup between client and NetApp
configure NDMP user/password and SnapVault filers (names separated by commas)

Runs on most OS'es (Windows, Linux, Solaris, etc.) but you can only create luns from Windows OSSV.

Seems to be different versions of OSSV for Windows 2003 and Windows 2008, but same for Host Agent. 

Gotcha: SnapVault relationship wouldn't create on my Linux backup client until:
1.  stop service on linux backup client
service snapvault stop
2. backup and edit /usr/snapvault/config/snapvault.cfg:

changing:

[QSM:Check Access List]
Type= CheckBox
value= TRUE

to:


[QSM:Check Access List]
Type= CheckBox
value= FALSE



3.  And starting service again.  
service snapvault start
This was much easier than getting the syntax for the svsetstanza command.  (^;

Installing OSSV on Linux



mv ossv_linux_v3.0.1.tar.gz ossv_linux_v3.0.1.tar
tar -xvf ossv_linux_v3.0.1.tar
cd ossv
[root@linux ossv]# ./install
Installer invoked in /home/kevin/ossv
Using default /tmp as the temporary directory
Expanding distribution file
OSSV
3_0_1_2011FEB17_RC
Have you read and agreed to the terms of the license?
(y = yes, n = no, d = display license) (y n d) [d] : y
Please enter the path where you would like
the SnapVault directory to be created [/usr/snapvault] :
Enter the User Name to connect to this machine
via the NDMP protocol : backups
Please enter the password to connect to this machine
via the NDMP protocol :
Confirm password:
Enter the NDMP listen port [10000] :
Enter the hostname or IP address of the SnapVault secondary
storage system(s) allowed to backup this machine.
Multiple hostnames or IP addresses must be comma seperated.
> : SnapVaultHost
NetApp Host Agent is recommended for managing OSSV.
OSSV could not detect NetApp Host Agent on this system.
If you install this software later, you can install OSSV plugins using
/usr/snapvault/manageability/InstallHostAgentPlugins.sh
Writing ndmp password to password file
checkinstall running
CHOSEN_CLASSES=ossvcore
PKG_BASE=/usr/snapvault
This is a new installation - not an upgrade
Trace Directory = /usr/snapvault/trace
Temp  Directory = /usr/snapvault/tmp
preinstall running
Installing ossvcore
Copying uninstallation scripts
postinstall running
HOST_OS=Linux
Creating Trace Directory /usr/snapvault/trace
NV_UPGRADE=FALSE
Creating database directory /usr/snapvault/db
Installing libraries
libsvdb.so
libsvgui.so
libsvndmp.so
libsvplugin.so
libsv.so
libsvxctl.so
libsvxpm.so
Creating symbolic links
Installing base npk's
Checking for components in /home/kevin/ossv/packages
Installing additional npk's
Install normal package
Successfully installed '/home/kevin/ossv/packages/ossv2300.npk'
Checking for extra components in /home/kevin/ossv/extrapackages
Copying non-installable additional npk's
Setting gathered configuration values
Installing OSSV Services
Will link to '/usr/snapvault/etc/startup.sh'
Starting OSSV Services
Checking install validity
SnapVault home directory: '/usr/snapvault'
SnapVault database directory: '/usr/snapvault/db'
SnapVault temporary directory: '/usr/snapvault/tmp'
SnapVault Database and Temporary directories have 71% space left (47182Mb)
SnapVault service is running
SnapVault listener is running
Snapvault NDMP interface on port 10000:
   Vendor     : Netapp
   Product    : SnapVault
   Version    : 3_0_1_2011FEB17_RC
   Host       : maserati
   Host Id    : CED5936CC94D727724CFDEE23D77C48F
   OS Type    : Linux
   OS Version : 2.6.9-5.ELsmp
   IPV6       : Ndmp Server is responding correctly
   IPV4       : Ndmp Server is responding correctly
Snapvault QSM interface on port 10566:
   IPV6       : QSM Server is responding correctly
   IPV4       : QSM Server is responding correctly
Validating filesystems:
   Mount point / (/dev/mapper/VolGroup00-LogVol00) is suitable for backup
   Mount point /proc (none) is a special mount, unsuitable for backup
   Mount point /sys (none) is a special mount, unsuitable for backup
   Mount point /dev/pts (none) is a special mount, unsuitable for backup
   Mount point /proc/bus/usb (usbfs) is a special mount, unsuitable for backup
   Mount point /boot (/dev/cciss/c0d0p1) is suitable for backup
   Mount point /dev/shm (none) is a special mount, unsuitable for backup
   Mount point /proc/sys/fs/binfmt_misc (none) is a special mount, unsuitable for backup
   Mount point /var/lib/nfs/rpc_pipefs (sunrpc) is a special mount, unsuitable for backup
NetApp Host Agent is installed on this system.
Check Succeeded
Installation appears valid
Installation completed successfully
[root@linux ossv]#




Bits & Bobs:
LREP: allows out-of-band data transfers to keep load off normal channel, can be used to transfer data to portable disk for physical transfer to another location.

Enable OSSV compression on SnapVault if required.


DFM setup:

Go to OSSV tab in NetApp Mgt Console on DFM server
Click "Add" 
have NDMP username and password ready
password needs entering as it is shown from the command on the SnapVault server from the ndmpd command:

ndmpd password backup
where NDMP user is called "backup"

CLI snapvault check:
test206:C:\                                              SnapVault:/vol/sva_OSSV_test/test206_OSSV_test_test206_C__
         Uninitialized  -          Transferring fes206:SystemState                                      SnapVault:/vol/sva_OSSV_test/test206_OSSV_test_fes206_SystemState
         Uninitialized  -          Transferring
SnapVault> snapvault status "SnapVault:/vol/sva_OSSV_test/test206_OSSV_test_test206_C__"
Snapvault is ON.
Source                Destination                                                State          Lag        Status
test206:C:\            SnapVault:/vol/sva_OSSV_test/fes206_OSSV_test_test206_C__  Uninitialized  -          Transferring
SnapVault>snapvault status -l "destination volume/path"




Friday, 13 January 2012

NetApp vol copy of snapshot for vSphere

Using Data from a NetApp snapshot via vol copy

make sure the destination volume is not being used,
if mapped to VMware delete VMFS and unmap and rescan from vCenter

offline the volume

verify the snapshot needed with snap list command

vol copy -s start snapshot_wanted source_vol_with_snap dest_vol_alredy_offlined

online the destination volume and you'll see message from NetApp CLI warning that lun has been offlined as it is copy and therefore has duplicate information as the source:

Fri Jan 13 14:51:52 GMT [SnapVaultA: lun.newLocation.offline:warning]: LUN /vol/sv_lun_svcopy/sv1/lun96 has been
taken offline to prevent map conflicts after a copy or move operation.

go to FilerView and change the path and lun number of the lun for the dest. volume.

Now you can online the volume and map it out with the correct, non-duplicate, lun number.

rescan storage on vCenter
add Storage and choose "Assign a new signature" when adding dest. lun into vCenter.
find the VMFS on your dest. lun which will have it's old name but after prefix "snap-xxxxx" and rename it appropriately.

add the VMDK on the VMFS on the lun to your VM and you're laughing!


Wednesday, 11 January 2012

Snapvault Backups

These instructions are in NetApp's docs, but they're kinda vague, especially when it's time to do the "snapvault snap create" commmand--which volume should be named? SnapVault copy or Source? I've logged this with NetApp and our expert consultants and neither got to the correct answer easily or quickly.

1. Create lun for destination on snapvault

2. set schedules for retention, but disable snapshots as in this case they'll be ran from NetApp client via script which has ssh access.
netapp1> snapvault snap sched src_vol src_vol_weekly
snapvault> snapvault snap sched src_vol src_vol_weekly

3. Ensure remote access between MetroCluster source and Snapvault Destination is good.

4. Establish initial baseline transfer between both volumes on both heads.
SnapVault> snapvault start -S netapp1:/vol/volume sv_volume

5. connect schedules
SnapVault> snapvault snap sched -x blah:/blah blah

SnapVaultA> snapvault snap sched
...
xfer sv_vol sv_vol_snap_sv_weekly 12@- preserve=default,warn=0

netapp1> snapvault snap sched
create vol sv_vol_snap_sv_weekly 4@-

Note: we keep 4 copies of the snapshot on the source/primary/MetroCluster and 12 copies on the destination/secondary/SnapVault

6. create new snapshots and verify date/time stamps

SnapVault> snapvault snap create sv_vol sv_vol_snap_sv_weekly

NOTE: this next command is the bit that goes in your script on the NetApp client right after quiescing/stopping your database and right before starting it up again:

7. remember always pull TO snapvault, don't push:
SnapVault> snapvault update netapp1:/vol/vol/sv1
Transfer started.
Monitor progress with 'snapvault status' or the snapmirror log.

SnapVault> snapvault snap create sv_vol sv_vol_snap_sv_weekly
NetApp> snapvault snap create vol sv_vol_snap_sv_weekly


8. Verify snapshots (look for Status and Contents fields below)

SnapVault> snapvault status -l SnapVault:/vol/sv_vol/sv1
Snapvault is ON.
Source: netapp1:/vol/volume/qtree
Destination: SnapVault:/vol/sv_vol/sv1
Status: Transferring
Progress: 4856300 KB
State: Snapvaulted
Lag: 03:25:19
Mirror Timestamp: Wed Jan 11 09:10:45 GMT 2012
Base Snapshot: SnapVault(1573980687)_sv_vol_snap_sv_weekly
Current Transfer Type: Update
Current Transfer Error: -
Contents: Transitioning
Last Transfer Type: Update
Last Transfer Size: 4735288 KB
Last Transfer Duration: 00:01:02
Last Transfer From: netapp1:/vol/_sv_vol_snap_sv_weekly/qtree

SnapVault> snapvault status -l SnapVault:/vol/sv_vol/sv1
Source: netapp1:/vol/sv_vol_snap_sv_weekly/qtree
Destination: SnapVault:/vol/sv_vol_snap_sv_weekly/sv1
Status: Idle
Progress: -
State: Snapvaulted
Lag: 00:04:00
Mirror Timestamp: Wed Jan 11 12:34:05 GMT 2012
Base Snapshot: SnapVault(1573980687)_sv_vol_snap_sv_weekly-base.0
Current Transfer Type: -
Current Transfer Error: -
Contents: Replica
Last Transfer Type: Update
Last Transfer Size: 5165432 KB
Last Transfer Duration: 00:01:54
Last Transfer From: netapp1:/vol/sv_vol_snap_sv_weekly/qtree

The destination will say, "snapvaulted" under Status when completed.