Roles and Responsibilities in NetApp Storage Admin

Roles and Responsibilities in NetApp Storage Admin

Select some important points 

• We are doing remote support. 
• Checking the storage critical Events. 
• Controlling & Monitoring Network Interface. 
• Checking the status of aggregate and volume usage using DFM. 
• Checking the ticketing tool and mails.
• Configuring and troubleshooting SnapMirror Environment. 
• Performing Daily health check to monitor the usage of LUN, Aggregate and volume utilization. 
• Configuring H drive for the users in the environment. 
• Restoring the data using snap restore and CIFS shares. 
• Dealing with permissions (Adding/removing the security groups to the shares) for share folders in CIFS. 
• Configuring and troubleshooting SnapVault Environment. 
• Performed DR test for the environment. 
• Snapshot, lunclone, flexclone management. 
• Setting up and troubleshooting V-Filer Environment. 
• Lun management (LUN creation, LUN snapshots, Manual and automatic igroup management, LUN restore) using Snapdrive. 
• Setting up and troubleshooting NFS, CIFS, and SAN (FC and ISCSI) Environment. 
• Configuring windows ISCSI Boot LUN for the environment. 
• Ontap OS upgrade from 7.3.3 to 8.0 7 mode. 
• Storage remediation like HBA driver and firmware upgrade. 
• Adding disk shelf to the existing storage for standalone and High availability controllers. (involved in ontap upgrade documents team ) 
• Assigning LUN’s (FC and ISCSI) to distributed server in various environments. 
• Resolving the hardware issues in co-ordination with Netapp. 
• Managing the reports using operations manager. 
• Working with qtree’s for efficient storage utilization for the users. 
• Performing Deduplication for the volumes. 
• Volume resize, aggregate disk add and lun resize 
• Alias, zoning configuration for the servers connected in FC environment in brocade switches. 
• Able to create/Expand aggregate, volume, Qtree for NAS environments, LUN’s, Igroups for SAN environments and also reclamation the LUN’s and SAN ports if any (De-commissioning projects).

Please write your valuable comments, about my blogspot.

Network Ports for NetApp

Product/Source	Port	Protocol	Target	Direction
SnapDrive dfm integration	8088	http	DFM server	bi-directional
SnapDrive dfm integration - secure	8488	https	DFM server	bi-directional
snapdrive webservice	4094	http	filer/vfiler	bi-directional
snapdrive webservice - secure	4095	https	filer/vfiler	bi-directional
Snapdrive autosupport	25	TCP	SMTP server	one way
Snapdrive iscsi	3260	TCP	filer/vfiler	bi-directional
Snapdrive netbios RPC	137	TCP	filer/vfiler	bi-directional
	138	TCP	filer/vfiler	bi-directional
	139	TCP	filer/vfiler	bi-directional
	1512	TCP	filer/vfiler	bi-directional
Snapmanager for SQL	808	TCP	SQL server	bi-directional
Snapmanager for Exchange	808	TCP	SQL server	bi-directional
OSSV-ndmp	10000	TCP	DFM server	bi-directional
OSSV-snapvault	10566	TCP	filer/vfiler	bi-directional
Snapvault-ndmp	10000	TCP	DFM server	bi-directional
Snapvault-traffic	10566	TCP	filer/vfiler	bi-directional
Snapmirror Source	10566	TCP	filer/vfiler	bi-directional
" " " "	10569	TCP	filer/vfiler	bi-directional
Snapmirror Destination	10565	TCP	filer/vfiler	bi-directional
" " " "	10567	TCP	filer/vfiler	bi-directional
" " " "	10568	TCP	filer/vfiler	bi-directional
SMVI	8043	TCP	filer/vfiler	bi-directional

Please write your valuable comments, about my blogspot.

FlexClone

FlexClone

1. Its license futures in NetApp.
2. Flexclone is used for testing purpose. 
3. Flexclone need volume snapshot, using that snapshot we can clone that to new volume.
4. FlexClone volumes always exist in the same aggregate as parent volumes.
5. Clone is in writable copy and without using a lot of disk space. After split the clone that time only clone will take space from the Aggregate.

Commands :

To Create new clone

     fas3070> vol clone create old_vol_name –b new_volume_name snapshot_name

To view clone status

     fas3070>  vol status new_volume_name

To start a clone split:

     fas3070> vol clone split start volname

To stop a clone split:

     fas3070> vol clone split stop

To check the status of a clone split:

     fas3070>  vol clone split status [volname]

To estimate the time of completion:

    fas3070>  vol clone split estimate [volname]

Please write your valuable comments, about my Blogspot.

Comparison of vol copy, ndmpcopy and dump/restore

Comparison of vol copy, ndmpcopy and dump/restore

Description	vol copy	Ndmp copy	Dump/restore
Uses Snapshot	Yes	Yes, but snapshot taken by ndmp is deleted after copy is completed	No
Requires rsh access	Yes	No	No
Destination needs to be restricted	Yes	No	Uses tape drive as destination
Requirements Similar Type of Volume	Trad to Trad and Flex to Flex copy only	Source and destination can be of either flex / Trad Vols	Source could be
Vol size requirement	Destination volume size should be equal or more capacity	No limitation on destination vol size	n/a
Directory level copy possible	No	Yes	Yes

Please write your valuable comments, about my blogspot.

NDMP Copy

1 NDMP Copy

Transfers directory trees between filers using NDMP (Network Data management Protocol)

• Ndmpcopy transfers data between filers/v-filers using the Network Data Management Protocol (NDMP) versions 3 and higher. 
• This process can be thought of as creating a dedicated data pipe between dump running on the source filer and restore running on the destination filer.

1.1 Pre-Requisite

Turn on ndmp by

Filer > ndmpd on

Ping the filers each other and make sure they are reachable

Make sure that the Data ONTAP release on the filers you are using for the copy support NDMP version 3 and/or higher.

Filer >ndmpd version 

For filers running ONTAP version 7.X, change the ndmpd authentication type to challenge

Filer > options ndmpd.authtype challenge

1.2 How to run ndmpcopy command

From the filer use the following syntax to run the command.

Syntax:

ndmpcopy [options] source destination

Where, source and destination are of the form [filer:]path

Options:

-sa username:password This is used for authenticating at source filer

-da username:password This is used for authenticating at source filer

-st text | md5 Source filer authentication type

-dt text | md5 Destination filer authentication type

-l 0 | 1 | 2 Level 0,1 and 2 copy (default is 0)

-d Debug

-f Force flag

-h Help

Example:

Filer > ndmpcopy -sa root:password –da root:password  /vol/vol_s 10.100.201.10:/vol/vol_d

In this example /vol/vol_s directory on the source filer is copied to /vol/vol_d on filer 10.100.201.10

-sa root:password option is specified to user is root  and password is  “password” for the source user authentication and –da for the same purpose at destination filer, Screen shot.

1.3 Problems Faced and Lessons Learnt

• Initially filer was giving ndmp authentication error, this was fixed by specifying the username and password (-sa and -da) option. 
• NDMP can copy at qtree level, but can not copy individual sub directories 
• Snapshot backups are taken for copying the data and snapshot copy is deleted after transfer is over. 
• No need to restrict the destination volume for copy. 
• Also ONTAP version 7.x requires, ndmpd.authtype set to challenge 

 

Please write your valuable comments, about my blogspot.