Showing posts with label netapp basic introducation. Show all posts
Showing posts with label netapp basic introducation. Show all posts

Monday, 2 January 2012

Netapp Most Commonly Used Commands


sysconfig (-a, -r, -c, -t, -m)‏

Shows information about filer (hardware, disks, aggregates & RAID groups, ...)‏

options

Queries or changes values for various “registry” options

setup

Walks through initial setup questions: filer name, IP addresses, etc., but does not erase any data

cifs setup

Walks through CIFS setup questions: domain/workgroup membership etc.

sysstat -x -s 1

Prints out all-round performance statistics

license

Adds/removes/prints licenses on filer

version (-b)‏

Prints out Data ONTAP & Diagnostics/Firmware version numbers

rdfile

Reads a text file and prints contents to console (Unix “cat”)‏

wrfile

Reads from console and sends output to text file (Unix “Cat >”)‏

snap (restore)‏

Performs snapshot operations, eg. restore from snapshot

snapvault

snapmirror


Manipulates/controls SnapMirror/SnapVault/OSSV operations from the command-line

cf

Controls clustering, eg. enabling/disabling, forcing takeover & giveback

aggr

Creates/expands/destroys/manipulates aggregates, eg. change options

vol

Create/resizes/destroys/manipulates volumes, eg. change options

df

Shows free disk space (volumes, aggregates, also inodes)‏

qtree

Creates/manipulates qtrees (=special directories)‏

vif

Creates/destroys/manipulates virtual network interfaces (eg. team interfaces for failover or load-balancing)‏

ifconfig

Sets network IP configuration (put in /etc/rc to survive reboots)‏

ifstat

Shows network interface statistics

netdiag

Performs basic network diagnostic testing

ndmpd

ndmpcopy

Manipulates NDMP settings, or use ndmpcopy to copy files via NDMP

priv set/priv set advanced/priv set diag

Goes into advanced/diagnostics mode


Thursday, 10 November 2011

Snapmirror schedule configuration

Three Type of  Snapmirror Configuration 

 
  • Snapmirroe initialize should run in destination filer only.
  • After initialize the snapmirror , destination filer will move all the data from primary filler to secondary.
  • Now create a new file in /etc/snapmirror.conf for scheduling sync (or) Async (or) semi-sync
  • Because once we excute the initialize and update command in destination side, it will touch the snapmirror.conf in etc path for any snapmirror sechedule.
sync mode

 Its is licensed product
 The source system acknowledges a client write operation only after both the source and destination systems have completed the write operation. The sync option provides a recovery point objective of 0 seconds


sec> license add <snapmirror_sync>
sec> wrfile -a /etc/snapmirror.conf src:vol1   dst:vol1  - sync

Note:
if u created that snapmirror.conf initialize no need to do snapmirror update
if snapmirror initialized just run snapmirror update

sec> snapmirror update -S src:vol1 dsr:vol1   # to enable the /etc/snapmirror.conf file

#  syncs will happen every minute

sec>  snapmirror update  # to enable the /etc/snapmirror.conf file

Async mode

async is not license product.
async will transfer as per schedule..

sec> wrfile -a /etc/snapmirror.conf src:vol1   dst:vol1 - 0 23 * *

Note:
if u created that snapmirror.conf initialize no need to do snapmirror update
if snapmirror initialized just run snapmirror update
 
sec>   snapmirror update -S src:vol1 dst:vol1    # to enable the /etc/snapmirror.conf file

#  syncs will happen at every 11:00 pm

Semi sync mode
 Its is licensed product.
The source system acknowledges the client write operation immediately after the source receives the data. The destination system is synchronized with the source at intervals of approximately 10 seconds. The semi-sync option provides a recovery point objective of about 10 seconds. This means that if the source becomes unavailable, you might lose up to 10 seconds worth of data changes. The semi-sync mode provides a performance advantage over the sync mode.
license name snapmirror_sync
 

sec> license add <snapmirror_sync>
sec> wrfile -a /etc/snapmirror.conf src:vol1   dst:vol1  - semi-sync
 
Note:
if u created that snapmirror.conf initialize no need to do snapmirror update
if snapmirror initialized just run snapmirror update


sec> snapmirror update -S src:vol1   dst:vol1     # to enable the /etc/snapmirror.conf file

data transfer will happen after 10sec after scheduling

 
 
 
 
Please write your valuable comments, about my blogspot.

Friday, 7 October 2011

Netapp Hardware Connection

This Diagram is Netapp High-Availability


Controller 1 : Filer 1
Controller 2 : Filer 2

Controller 1 Active Shelves : Disk shelf
Controller 2 Active Shelves : Disk shelf

Switch/Fabric : Fibre channel Switch (brocade or cisco)

host : may be Windows or unix server

Advantage Netapp High-Availability :


  • If any Hardware failure in this structure, the another hardware will take over that.
  • For Example: If netapp controller 1 got failed means in the next second controller 2 will take over the controller 1 resources like LUN, CIFS and NFS Shares.



Filer back side view