Molecules of the Storage and Backup world: STORAGE

Showing posts with label STORAGE - NetApp. Show all posts

Wednesday, October 23, 2013

NETAPP - How to enable the autosize and autogrow on NetApp.

NETAPP - How to enable the autosize and autogrow on NetApp.

With this option the volume will grow with a specified space.
The first thing would be to enable the autosize option on the volume.
That can be achieved by running the following command.

NTPboxer*> vol autosize test
Volume autosize is currently ON for volume 'test'.
The volume is set to grow to a maximum of 1258080 KB, in increments of 52420 KB.

NTPboxer*> priv set diag

NTPboxer*> printflag wafl_reclaim_threshold_t
wafl_reclaim_threshold_t = 0x55

THE COMMAND ABOVE STATES THAT WHEN THE VOLUME REACHED 85% (0X55 - HEX FIGURE) IT WILL AUTOGROW BY CERTAIN FRAGMENTS.

NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 996148KB 188KB 995960KB 0% /vol/test/
/vol/test/.snapshot 52428KB 0KB 52428KB 0% /vol/test/.snapshot

With the volume in place i started to dump some data into it to check the autogrow process.

NTPboxer*>
NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 996148KB 205664KB 790484KB 21% /vol/test/
/vol/test/.snapshot 52428KB 0KB 52428KB 0% /vol/test/.snapshot
NTPboxer*> df -k testTue Oct 22 17:01:40 IST [NTPboxer:wafl.vol.full:notice]: Insufficient space on volume test to perform operation. 444MB was requested but only 412MB was available.

AFTER 30 SEcs

NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 996148KB 705192KB 290956KB 71% /vol/test/
/vol/test/.snapshot 52428KB 0KB 52428KB 0% /vol/test/.snapshot

AFTER 20 SECS

NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 996148KB 867568KB 128580KB 87% /vol/test/
/vol/test/.snapshot 52428KB 0KB 52428KB 0% /vol/test/.snapshot
NTPboxer*> Tue Oct 22 17:04:23 IST [NTPboxer:nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server.
Tue Oct 22 17:04:29 IST [NTPboxer:wafl.vol.autoSize.done:info]: Automatic increase size of volume 'test' by 52420 kbytes done.

IF YOU SEE ABOVE THE VOLUME GOT AUTOSIZED WHEN IT REACHED 85%.

NTPboxer*>
NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 1045948KB 888824KB 157124KB 85% /vol/test/
/vol/test/.snapshot 55048KB 0KB 55048KB 0% /vol/test/.snapshot

ADDED another 100mb

NTPboxer*>
NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 1145548KB 959340KB 186208KB 84% /vol/test/
/vol/test/.snapshot 60288KB 0KB 60288KB 0% /vol/test/.snapshot

NTPboxer*>
NTPboxer*> df -k test
Filesystem total used avail capacity Mounted on
/vol/test/ 1195176KB 1074676KB 120500KB 90% /vol/test/
/vol/test/.snapshot 62904KB 0KB 62904KB 0% /vol/test/.snapshot
NTPboxer*> Tue Oct 22 17:12:55 IST [NTPboxer:wafl.vol.autoSize.done:info]: Automatic increase size of volume 'test' by 52420 kbytes done.

IF YOU SEE ABOVE THE VOLUME GOT AUTOSIZED.

Friday, October 4, 2013

STORAGE - NetApp - Adding a ndmpuser in NetApp for NDMP backups

NetApp - Adding a ndmpuser in NetApp for NDMP backups

A ndmpuser can be added to the storage system to make the NDMP backup running.
This ndmpuser can be added to the credentials of the backup software ( NetBackup / Networker).

-----------------------------------------------------------------------------------------------------------------------------------------------------------------

NetApp1> useradmin user add ndmpuser -g "Backup Operators"

New password:

Retype new password:

User <ndmpuser> added.

NetApp1> Mon Apr 8 17:25:40 CST [NetApp1:useradmin.added.deleted:info]: The user 'ndmpuser' has been added.

NetApp1>

NetApp1> ndmpd password ndmpuser

password QKxD########dmL

Thank you..

STORAGE - NetApp - Tracking NFS Issues

NetApp - Tracking NFS issues

Many a times you would have experienced a lot of problems while mounting a NFS volume on any host from a NetApp Storage.
Most of the times we end up checking the log files on the host side thinking that the issue might be with the host itself.

Recently i ran into an issue wherein i was not able to mount a NFS volume from my NetApp controller to the Linux Server.

A couple of thumb rules that you need to follow when you doing a task like this are -

1. The NFS versions on both Storage (NetApp) and the HOST (Solaris /Linux/etc etc).
2. The connectivity between the Storage appliance and the HOST.

If still the issue persists --

Do the following on the Storage appaliance.

At the prompt of the NetApp storage appliance do the following -

NetApp1> options nfs.mountd.trace

nfs.mountd.trace off

NetApp1> options nfs.mountd.trace on

Turning ON this option on the storage appliance will tell you where exactly the problem is.

Hope this helps.

Thank you..

STORAGE - NetApp - Unable to assign serial number to LUN

While attaching the LUN to an igroup which has the host iscsi initiator target set sometimes you might run into a problem wherein the LUN doesnt get attached to the igroup hence not allocating the block based space to the host.

This can be rectified by setting up the counter on your NetApp system --

On your Filer head

Run the following command -

# priv set diag

# lun sn-counter show

This will shoe the current value of the counter.

This would display the countyer set for generating the serial numbers.

#lun sn-counter set -t

This will reset the counter to default.

Once done try to allocate the LUN once again and you should be good to go.

Thank you..