Explore topic-wise InterviewSolutions in .

The main DIFFERENCE between NAS and SAN is that NAS is an Ethernet BASED while SAN is Fabric based.

NAS- Network ATTACHED Storage:

It enters data on file level and develops space to host in the form of folder of shared NETWORKS.

SAN- Storage Area Network:

It enters data on block level and develops space to host in the form of a DISK.

The main difference between NAS and SAN is that NAS is an Ethernet based while SAN is Fabric based.

NAS- Network Attached Storage:

It enters data on file level and develops space to host in the form of folder of shared networks.

SAN- Storage Area Network:

It enters data on block level and develops space to host in the form of a disk.

NETAPP Infinite Volume is a software abstraction HOSTED over CLUSTERED Data ONTAP

NetApp Infinite Volume is a software abstraction hosted over clustered Data ONTAP

This is a new term in cluster mode and this is USED for mounting.Volume JUNCTIONS are a way to join individual volumes TOGETHER into a single, logical NAMESPACE to enable data access to NAS clients.

This is a new term in cluster mode and this is used for mounting.Volume junctions are a way to join individual volumes together into a single, logical namespace to enable data access to NAS clients.

A Vserver is DEFINED as logical container which holds the volumes. A 7 MODE vfiler is CALLED as a vserver in Clustered mode . 

A Vserver is defined as logical container which holds the volumes. A 7 mode vfiler is called as a vserver in Clustered mode . 

LIF ( LOGICAL interface) : As the name suggest its a logical interface which is created from physical interface of NetApp CONTROLLERS.

LIF ( Logical interface) : As the name suggest its a logical interface which is created from physical interface of NetApp controllers.

If PARTNER shelf POWER is off, if you TRY to takeover it will not TAKE. if you do as force using (-f) it will WORK

If partner shelf power is off, if you try to takeover it will not take. if you do as force using (-f) it will work

• cluster INTERCONNECT cable should be connected.
• shelf connect should be properly done for both the controllers with Path1 and Path2
• cluster license should be enabled on both the NODES
• Interfaces should be properly CONFIGURED for fail over
• cluster should be enabled

Using DFM(Data Fabric Manager) or ALSO using SNMP you can monitor the filer. Using any MONITORING SYSTEMS LIKE .i.e.Nagios

Using DFM(Data Fabric Manager) or also using SNMP you can monitor the filer. Using any monitoring systems like .i.e.Nagios

LUN create -s &LT;lunsize> -t <HOST type> <lunpath>

lun create -s <lunsize> -t <host type> <lunpath>

YES i have DONE ontap upgrade from version 7.2.6.1 to 7.3.3 due to lot of BUGS in OLD version.

Yes i have done ontap upgrade from version 7.2.6.1 to 7.3.3 due to lot of bugs in old version.

If the spare DISK is not added within 24hours,then filer will be SHUTDOWN automatically to AVOID further disk FAILURES and data loss.

If the spare disk is not added within 24hours,then filer will be shutdown automatically to avoid further disk failures and data loss.

• Check the r/w using "cifs stat" &AMP; "sysstat -x 1".
• If DISK & cpu utilization is more then PROBLEM is with filer side only.
• CPU utilization will be high if more disk r/w time, i.e.,during tape backup & also during SCRUB activities.

CIFS STAT

cifs stat

CIFS TOP

cifs top

Check WHETHER IQN number specified is correct
Check whether the created LUN is in “RESTRICT” mode
Check the iscsi status
Un-map and map the LUN once again
Check Network CONNECTIVITY COMMUNICATION

Check whether IQN number specified is correct
Check whether the created LUN is in “restrict” mode
Check the iscsi status
Un-map and map the LUN once again
Check Network connectivity communication

SSH “RLM ip ADDRESS”
RLM_Netapp> system POWER on

ssh “rlm ip address”
RLM_Netapp> system power on

pri> snapvault SNAP SCHED vol1 sv_hourly 22@0-22

• This schedule is for the home DIRECTORIES volume vol1
• CREATES hourly Snapshot copies, EXCEPT 11:00 p.m.
• Keeps nearly a full day of hourly copies

pri> snapvault snap sched vol1 sv_hourly 22@0-22

SIS STATUS

sis status

DF –s &LT;VOLUME NAME&GT;

df –s <volume name>

In the context of disk storage, De-duplication refers to any algorithm that searches for DUPLICATE data objects (for example, blocks, chunks, files) and discards those DUPLICATES. When duplicate data is detected, it is not retained, but instead a “data pointer” is modified so that the storage system references an EXACT copy of the data object already stored on disk. This De-duplication feature WORKS well with DATASETS that have lots of duplicated date (for example, full backups). 

In the context of disk storage, De-duplication refers to any algorithm that searches for duplicate data objects (for example, blocks, chunks, files) and discards those duplicates. When duplicate data is detected, it is not retained, but instead a “data pointer” is modified so that the storage system references an exact copy of the data object already stored on disk. This De-duplication feature works well with datasets that have lots of duplicated date (for example, full backups). 

Add a connection NAME LINE in the snapmirror.conf FILE

/etc/snapmirror.conf
FAS1_conf = multi (FAS1-e0a,FAS2-e0a) (FAS1-e0b,FAS2-e0b)

Add a connection name line in the snapmirror.conf file

/etc/snapmirror.conf
FAS1_conf = multi (FAS1-e0a,FAS2-e0a) (FAS1-e0b,FAS2-e0b)

SnapMirror Async mode replicates Snapshot copies from a SOURCE volume or qtree to a DESTINATION. It will support to replicate more than 800Kms Long. volume or qtree. Incremental updates are based on a schedule or are performed manually using the snapmirror update command. Async mode works with both volume SnapMirror and qtree SnapMirror.

SnapMirror SYNC mode replicates writes from a source volume to a destination volume at the same time it is written to the source volume. SnapMirror Sync is used in environments that have zero tolerance for DATA loss. it will NOTE support more then 300Kms long.

SnapMirror Semi-Sync provides a middle-ground solution that keeps the source and destination systems more closely synchronized than Async mode, but with less impact on performance.

SnapMirror Async mode replicates Snapshot copies from a source volume or qtree to a destination. It will support to replicate more than 800Kms Long. volume or qtree. Incremental updates are based on a schedule or are performed manually using the snapmirror update command. Async mode works with both volume SnapMirror and qtree SnapMirror.

SnapMirror Sync mode replicates writes from a source volume to a destination volume at the same time it is written to the source volume. SnapMirror Sync is used in environments that have zero tolerance for data loss. it will note support more then 300Kms long.

SnapMirror Semi-Sync provides a middle-ground solution that keeps the source and destination systems more closely synchronized than Async mode, but with less impact on performance.

• Check both the HOSTS are reachable by running “PING” command
• Check whether the TCP port 10566 & 10565 are open from FIREWALL
• Check whether the SNAPMIRROR license are installed in both filers

In ONTAP 7 the individual aggregate is LIMITED to MAXIMUM of 16 TB. Where ONTAP 8 supports the new 64 bit aggregate and hence the SIZE of the individual aggregate EXTENDS to 100 TB.

In ONTAP 7 the individual aggregate is limited to maximum of 16 TB. Where ONTAP 8 supports the new 64 bit aggregate and hence the size of the individual aggregate extends to 100 TB.

Ndmp copy:NETWORK data MANAGEMENT protocol(used for TAPE BACKUP)

Vol copy: is used to transfer volume to same or another aggregate 

Ndmp copy:network data management protocol(used for tape backup)

Vol copy: is used to transfer volume to same or another aggregate 

3260

3260

ISCSI-sending block through. iSCSI does not required dedicated network, it will WORK on existing network also. it work's an TCP/IP.

Fcp-send through fibre medium. Required an dedicated FC network. PERFORMANCE is so HIGH COMPARE to the iSCSI

Iscsi-sending block through. iSCSI does not required dedicated network, it will work on existing network also. it work's an TCP/IP.

Fcp-send through fibre medium. Required an dedicated FC network. Performance is so high compare to the iSCSI

Say some PROTOCOLS like NFS, CIFS, ISCSI and FCP

Say some protocols like NFS, CIFS, ISCSI and FCP

SUPPORTED RAID TYPES:

• Raid-4
• Raid-6 
• Raid-Dp

Supported RAID types:

A SNAPSHOT copy is a read-only image of a traditional or FlexVol VOLUME, or an aggregate, that CAPTURES the state of the file system at a point in time.

A Snapshot copy is a read-only image of a traditional or FlexVol volume, or an aggregate, that captures the state of the file system at a point in time.

5%

5%

QTREE is LOGICAL PARTITION of the VOLUME. 

qtree is Logical partition of the volume. 

TRADITIONAL VOLUME: vol ADD VolName no.of.disk

Flexible Volume: vol SIZE VolName +60g

Traditional Volume: vol add VolName no.of.disk

Flexible Volume: vol size VolName +60g

NETAPP&GT; AGGR ADD AggName no.of.disk

Netapp> aggr add AggName no.of.disk

ndmpcopy or SNAPMIRROR

ndmpcopy or snapmirror

NETAPP&GT;QTREE CREATE /vol/vol1/qtreename 
Netapp>qtree SECURITY /vol/vol1/qtree unix|ntfs|mixed

Netapp>qtree create /vol/vol1/qtreename 
Netapp>qtree security /vol/vol1/qtree unix|ntfs|mixed

LUN CREATE –s SIZE –t LINUX /vol/vol1/lunname 

lun create –s size –t linux /vol/vol1/lunname 

FROM STORAGE SIDE:

• VERIFY iscsi/fcp license is ADDED in storage 
• Verify iscsi/fcp SESSION is logged in from server side use command Netapp> igroup show -v 
• Verify luns are mapped to the CORRESPONDING igroup 
• Verify whether correct host type is mentioned while creating igroup and lun 
• Verify whether correct iqn/wwpn number is added to igroup 
• Verify zoning is properly configured from SWITCH side, if it is FCP protocol

FROM STORAGE SIDE:

There is no direct answer for this question but we shall do it in several way. 

• If volume/lun present in ATA/SATA harddisk aggregate, then the volume can be migrated to FC/SAS disk aggregate. Either you can use flash cache to improve performance.
• For NFS/CIFS instead of ACCESSING from single INTERFACE, multi mode vif can be configured to get better bandwidth and fault tolerance.
• Always advised to keep aggr/vol utilization below 90%.
• Avoid doing multiple volume backup in single point of time.
• Aggr/volume/lun reallocation can be done to re–distribute the DATA to multiple disk for better striping performance.
• Schedule scrubbing and De-duplication scanning after business hours.
• Create multiple loops and connect different types of shelf's to each loop
• Avoid mixing up different speeds of disk and different types of disk in a same aggregate.
• Always keep sufficient spare disk to replace in case of disk failure. Because reconstruction time will take more time and cause negative performance.
• Keep the advised version of firmware/software which is recommended by NETAPP.

There is no direct answer for this question but we shall do it in several way.