NetApp NSM – SAN v NAS creation differences

April 17th, 2009
by Christopher Kusek (PKGuild)

For those of you who manage filers via FilerView or the Command Line, you’ll find this interesting (I swear, I promise you will! :))

The following is what happens when you create a volume using the NSM and choose NAS

image

Language on volume nsm_nas changed to en_US
(This is the what gets set – The rest below are the values set)

(snap reserve)
Volume nsm_nas: current snapshot reserve is 20% or 4096 k-bytes.

(snap sched)
Volume nsm_nas: 0 2 6@8,12,14,16,20

(snap autodelete)
snapshot autodelete settings for nsm_nas:
state : off
commitment : try
trigger : volume
target_free_space : 20%
delete_order : oldest_first
defer_delete : user_created
prefix : (not specified)
destroy_list : none

(vol autosize)
Volume autosize is currently OFF for volume ‘nsm_nas’.

(vol options)
nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=on, maxdirsize=62914, schedsnapname=ordinal,
fs_size_fixed=off, compression=off, guarantee=volume, svo_enable=off,
svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off,
no_i2p=off, fractional_reserve=100, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off

This is the same you’d expect as when creating via the CLI or using FilerView!

Now, this is what happens when you do the same actions, but choose SAN

image

Language on volume nsm_san changed to en_US
Security style for /vol/nsm_san/ changed from ntfs to unix
The space management policy for vol nsm_san has changed: autosize state enabled.
The space management policy for vol nsm_san has changed: autodel state enabled.

(I did edit the words above to fit, but you get the point :) – here are the results)

(snap reserve)
Volume nsm_san: current snapshot reserve is 0% or 0 k-bytes. (Down from 20%)

(snap sched)
Volume nsm_san: 0 2 6@8,12,14,16,20  (Didn’t change)

(snap autodelete)
snapshot autodelete settings for nsm_san:
state                           : on (Turned on now)
commitment                      : try
trigger                         : volume
target_free_space               : 20%
delete_order                    : oldest_first
defer_delete                    : user_created
prefix                          : (not specified)
destroy_list                    : none

(vol autosize)
Volume autosize is currently ON for volume ‘nsm_san’. (Enabled now also)
The volume is set to grow to a maximum of 24 MB, in increments of 1 MB.

(vol options)
nosnap=on, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=on,
convert_ucode=on, maxdirsize=62914, schedsnapname=ordinal,
fs_size_fixed=off, compression=off, guarantee=volume, svo_enable=off,
svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=on,
fractional_reserve=0, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off

 

So, I don’t know about you, but this is pretty damn cool! The coolest bits are – when  I want to create volumes and I don’t want to look up the Best Practices for Vol auto growth and snap auto-deletion, I don’t need to now! Hooray!

Tags: , , , , , ,
Posted in Baltimization, Blog, Christopher Kusek, NetApp, Storage | Comments (0)

  • Archives