Sunday, March 16, 2008

Netapp How To


Volumes Manipulation:-
    1. Creation:
      vol create <name> <aggr> size
      enter the volume path in /vol/rootvol/etc/exports file (normal nfs format)
      exportfs -a
    2. Resize Volume:
      vol size <name> +/- size
Qtree Manipulation:-
    1. Creation:
      qtree create <absolute-path-to-tree>
      exports changes
      exportfs -a
      assign quota for qtree by changing /rootvol/etc/quotas file.
      quota off <volume-name>
      quota on <volume-name>
    2. Checking Netapp usage for particular qtree (Performance):
      qtree stats
User Manipulation:-
    1. Creation:
      mkdir folder in desired volume
      assign quota for user by changing /rootvol/etc/quotas file.
      quota off <volume-name>
      quota on <volume-name>
    2. Resize quota allocated:
      change quotas file
      quota resize <volume-name>
      Note: quota off/on also works but not recommended as requires a lot more processing than resize. Off/on to be done only during creation/deletion.
CIFS Manipulation:-
    1. Creation:
      cifs shares -add <name> <absolute-path-to-share>
    2. Deletion:
      cifs shares -delete <name>
    3. Access Maniputation to CIFS:
      cifs access <share-name> <user-name> rwx
      cifs access -delete <share-name> <user-name>
    4. Terminating all cifs sessions:
      cifs terminate
Checks And Status:-
    1. sysconfig -r
    2. sysconfig -a
    3. fcstat device_map
    4. fcstat link_stat
Snapshot:-
    1. Reserving size for Snapshots of a volume:
      snap reserve <volume-name> <percentage>
      Do Remember that snapshots may end up taking more space than reserved for them.
    2. Number and Scheduling for Snapshots:
      snap sched <volume-name> #week-#day-#hourly
    3. Creation of a new snapshot:
      snap create <volume-name> <snapname>
    4. Deleting a snapshot
      snap delete <volume-name> <snapname>
Snapmirror:-
    1. Status for Snapmirror:
      snapmirror status
    2. Snapmirroring Data from one Netapp to another:
      options snapmirror.access host=hostname,hostname (This options needs to be set on the source filer to give access to the destination to get data).
      snapmirror initialize -S <source filer:vol/qtree path> <destination volname/absolute qtree path>
      eg: napp2> snapmirror initialize -S napp1:vol1 volume1
      The above command will snapmirror vol1 of napp1 to volume1 of napp2
      One thing to remember: the destination volume needs to restricted before the snapmirror is initialized.
      napp2> snapmirror initialize -S napp1:/vol/vol1/qtree1 /vol/volume1/qtree2
    3. Updating the snapmirror:
      Almost same command as initialize
      snapmirror update -S <source filer:vol/qtree path> <destination >
    4. Breaking the snapmirror:
      breaking a snapmirror is necessory to make the the destination data writable with full control. breaking in done on destination filer.
      snapmirror quiesce <destination data path>
      snapmirror break <destination data path>
    5. Releasing snapmirrors:
      Releasing of snapmirrors is important as snapshots take space and keep on growing as the data on the volume keeps on changing. This needs to be done both on source and destination filers & both have different ways of getting done.
      source: snapmirror release vol/qtree dest:vol/qtree
      Destination: a mere deletion of the snapmirror snapshot will do.
      remember once the snapmirrors have been release the snapmirror cant be resumed.
System Status:-

sysstat <update-time-in-seconds>

System Failure Troubleshooting:-


partner: Command given on the node which has taken over to get data of bad node.
options autosupport.doit "messages(normally the case id)": to generate the autosupport.

No comments: