NetApp

In this particular blog, we will discuss how to create an NFS share in SVM NetApp cluster mode. NFS share is used in the UNIX server to store data so that Unix users can perform various data operations. NFS Share in NetApp cluster mode belongs to an SVM.

Steps To Create NFS Share In NetApp Cluster Mode

There are four steps to create NFS share in SVM Netapp Cluster-Mode. The first step is to create volume with security style Unix. The second step is to create an export policy. The third step is to create a rule Under export policy.

The fourth step is to assign the newly created export policy to the volume. In this post, we will create an NFS share by using the command line approach.

Check out our post to know the steps to create a CIFS share in NetApp CDot.

Step 1. Create A Volume With Security Style Unix

The following command will create a volume with a security style Unix of the size of 30 MB. SVM name is vs1 and volume name is share1 the junction-path is /share1.

vol create -vserver vs1 -volume share1 -aggregate data_aggr01 -junction-path /share1 -size 30MB

Step 2 Create An Export Policy In SVM

The export policy is basically is a combination of rules. These rules contain UNIX servers that need mounting permission. The below command will create an export policy with name share1 in SVM  vs1.

vserver export-policy create -vserver vs1 -policyname share1

Step 3 Create A Rule Under Export Policy

A rule in export policy contains the information about the UNIX servers that permission to mount. It can contain UNIX server name, IP address, NFS version, and superuser permission.

Below command creates a rule under export policy share1.

vserver export-policy rule create -vserver vs1 -policyname share1 -protocol any -clientmatch 192.168.15.173 -rorule any -rwrule any -superuser any

Step 4: Assign The Export Policy To The Volume Share1

Finally, we need to modify the volume’s export policy from default to the newly created export policy. We can do that by executing the below command.

volume modify -vserver vs1 -volume share1 -policy share1

We have completed all the steps from the Netapp end. Now we should give IP address or FQDN of SVM LIF and the junction path of the volume to Unix administrator.

They will use this information to mount the NFS Share. We need to provide the details in below format.

192.168.15.205:/share1

This concludes the discussion on how to create an NFS share in SVM NetApp cluster mode. If you have any doubt or any knowledge to share please comment don’t forget to subscribe to our YouTube Channel and don’t forget to share this blog as well.

In this post, we will discuss what is FlexClone volume in NetApp cluster mode. Additionally, we will discuss how to create a flex clone in the command line.

Flexclone volume is also called a flexible clone. This is one of the storage efficiency features in NetApp. Flex clones are the point in time copy of a source volume that you can use for testing purposes.

After flex clone creation whatever changes happen in any of the volumes, it does not affect each other data. Due to which, it is a good option for testing.

Clone volume shares the same space of its source volume means it will not consume any extra space from its container aggregate. If you want flex clone to be a separate volume then you can use the split command.

How To Create FlexClone Volume?

We can create a FlexClone volume with CLI and GUI. In this post, we will create a clone volume in the Command line.

You can also refer to the YouTube videos from san&nasTechie for creating FlexClone.

Steps To Create FlexClone Volume

Below is the step by step guide to creating a clone volume in NetApp cluster mode.

Step 1. Check FlexClone Licence

The first step is to check the license for FlexClone. You need a license to enable this feature. You can execute the below command to see the license list.

cluster::> license show

If you do not find the license you must get a license from NetApp sales representative. Otherwise, proceed to the next step.

Step 2. Create a FlexClone volume

You can create a FlexClone volume by using the “volume clone create” command. The below command creates a read-write clone volume vol1_clone from the parent volume vol1.

volume clone create -vserver vs0 -flexclone vol1_clone -type RW -parent-volume vol1

You can also create a clone volume using a snapshot. However, the volume must be a DP volume.

The following command creates a data protection clone volume vol_dp_clone from the parent volume dp_vol by using the base Snapshot copy snap1:

volume clone create -vserver vs1 -flexclone vol_dp_clone -type DP -parent-volume dp_vol -parent-snapshot snap1

Step 3. Split Clone Volume

Clone volume does not have its own space rather it uses its parent volumes space. If you want the clone volume to have its own storage then you need split clone relationship.

The split operation creates a copy of the data in a new volume. First, you must check available space in aggregate because the new volume will consume space from it.

You can execute the below command to estimate the space that the new volume going to consume.

cluster1::> volume clone show -estimate -vserver vs1 -flexclone clone1 -parent-volume volume1

If there is enough space in aggregate than split the clone volume. After this command, the new volume consumes space from its container aggregate.

cluster1::> volume clone split start -vserver vs1 -flexclone clone1

Once the split operation is complete you can verify the status as well. You should see the clone-volume status as false.

cluster1::> volume show -volume clone1 -fields clone-volume
volume clone-volume
——- —— ————
vs1 clone1 false

Here are some sample questions and answers for the NS0 158 NetApp certification exam. This is also called as NCDA Netapp Certified Data Administrator for cluster mode Netapp data on tap 9.1.

These are sample questions and not the expected question for the real exam.

Q 1. Regarding storage failover giveback processes, which st.atement is true?

• A. During giveback, node cl1-01 simultaneously returns ownership of both root and data aggregates to cl1-02.
• B. During giveback, node cl1-01 returns ownership of all aggregates to cl1-02, before reverting the data LIFs back to the home ports.
• C. During giveback, node cl1-01 returns ownership of the root aggregate to cl1-02 before returning ownership of the data aggregates.
• D. During giveback, node cl1-01 moves ownership of the root aggregate to cl1-04 and ownership of the data aggregates to cl1-04.

Answer: C

Explanation:
The following process takes place in a normal giveback. In this discussion, node A has taken over node B. Any issues on Node B have been resolved and it is ready to resume serving data.
References:

NO.2 A customer has a 1,000 GB volume used as a NAS share that has 3x 100 GB files and has no existing Snapshot copies.

The customer creates a Snapshot copy of the volume, adds a 500 Gb file to the volume, and then deletes one of the 100 GB files from the volume. How much free space is in the volume in this scenario?

A. 500 GB
B. 200 GB
C. 300 GB
D. 600 GB

Answer: B

Explanation:
Snapshot copies minimize disk consumption by preserving individual blocks rather than whole files. Snapshot copies begin to consume extra space only when files in the active file system are changed or deleted. When this happens, the original file blocks are still preserved as part of one or more Snapshot copies.

NO.3 Which NetApp management tool verifies the disk-shelf cabling of an existing NetApp cluster?

A. System Setup
B. Config Advisor
C. OnCommand Unified Manager
D. OnCommand System Manager

Answer: B

Explanation:
NetApp Config Advisor is a tool that will allow you to check the health and ensure your NetApp infrastructure is adhering to NetApp best practices. Once the Config Advisor query finishes, view the results and take corrective action on any configuration issues.

NO.4 You are configuring an ONTAP solution for FC host connectivity.

In this scenario, how should the cluster be configured? (Choose two.)
A. The SVM must be configured for Ethernet LIFs.
B. FC ports must be configured as initiators.
C. FCP must be licensed on the cluster.
D. FC ports must be configured as targets.

Answer: C, D

Explanation:
You can configure the FC and the FCoE protocols on the SVM for SAN hosts. LIFs are created on the most suitable adapters and assigned to port sets to ensure data path redundancy.

Based on your requirements, you can configure either FC, FCoE, or both the protocols. Before you begin The FCP license must be enabled on the cluster. All the nodes in the cluster must be healthy. Each node must have at least two correctly configured ports for each protocol (FC and FCoE).

NO.5 You have a FlexVol volume with LUNs and need to set policies to prevent an ENOSPC error on the host. In this scenario, which two commands will keep the LUN available to the host? (Choose two.)

A. volume autosize
B. snapshot autodelete
C. snapshot delete
D. volume size

Answer: B, C
Explanation:
ENOSPC is a UNIX operating system error that sometimes returns the message Not enough space is available to service your request.” The error message occurs because of a shortage of file system space or a lack of available media blocks.

Note: We get ENOSPC errors because Data ONTAP lets the Snapshot copy grow into the volume space. Each writes in WAFL is a write to a new block. If an old block is part of a Snapshot copy, Data ONTAP needs to preserve the old block and the new changed block.

This is not a problem specific to NetApp. Every storage vendor who supports a snapshot feature has to deal with it.

NO.6 To log in to the cluster with OnCommand System Manager, a cluster administrator account must be authorized for which two application types? (Choose two.)

A. HTTP
B. SSH
C. ONTAPI
D. service processor

Answer: A, C

Explanation:
You must have a cluster user account configured with the admin role and the HTTP, ontapi, and console application types.

NO.7 When a two-node cluster is expanded, which cluster configuration would be supported?

A. a 4-node switched cluster
B. a 4-node switchless cluster
C. a 3-node switched cluster
D. a 3-node switchless cluster

Answer: A

Explanation:
If you are adding nodes to a two-node switchless cluster, you must have installed and configured the cluster management and interconnect switches before adding additional nodes. The switchless cluster functionality supports only in a two-node cluster.

Thre are a lot of questions you can from NetApp training sites for Netapp Certification NS0 158. You must practice them as well before attending the exam.

Today we will discuss how we can create ISCSI LUN in SVM NetApp Cluster-Mode and allocate it to a Windows Host. In a previous post, we discussed how to configure iSCSI in Netapp Cluster-Mode. We suggest going through it before learning iSCSI LUN allocation.

Complete Steps For ISCSI LUN Allocation

Below are the overall steps need to perform for creating iSCSI LUN in. NetApp Cluster-Mode.In addition to creation, we will how to map it to a windows host.

• 1. Create Volume in SVM.
• 2. Create a LUN over the volume.
• 3. Create a Port Set in SVM.
• 4. Create an Initiator group in SVM.
• 5. Bind the initiator group to the port set.
• 6. Map the LUN to the Initiator group.
• 7. Discover the device in Windows Server.    

Below is a Youtube video that has a live demo to create and map ISCSI LUN in NetApp Cluster-Mode. You can subscribe to the channel for more such videos.

We are going to discuss each step one by one along with the command.

Step 1: Create Volume in SVM

  The below command creates a volume in SVM. This step is necessary because a LUN can reside over a volume or qtree. The volume should be thick volume as per NetApp’s best practice recommendation.

volume create -vserver vs1 -volume vol1 -aggregate aggr1 -state online -junction-path /vol1 -size 1G -space-guarantee volume

Step 2. Create a LUN On Volume

  In this step, we will create a LUN over a volume. As per your need, we should create a thick or thin LUN. In this command the “-space-reserve enable” makes the LUN as thick.

If you specify “-space-reserve disable” then LUN becomes a thin LUN.

lun create -vserver vs1 -path /vol/vol1/lun1 -size 1GB -ostype windows_2008 -space-reserve enabled   

Step 3. Create Port Set in SVM

  Port Sets are nothing but a grouping of target iSCSI LIFs. It is better to use ports sets when we have multiple iSCSI LIFs on a node. As a result, you can restrict traffic flow between certain target FC ports to a specific initiator.

Below is the command that creates a port set and adds two iSCSI target LIFs.

portset create -vserver vs1 -portset portset1 -protocol iSCSI -port-name iscsilif1,iscsilif2

You can see the port set details by executing the below command.  

portset show -vserver vs1

Step 4. Create An Initiator Group

  In this step, we are going to create an initiator group in SVM. This is also called IGROUP which is nothing but a collection of initiator IQN number. In iSCSI LUN allocation IQN is similar to WWPN in FC protocol.    

igroup create -vserver vs1 -igroup igroup1 -protocol iscsi -ostype windows_2008 -initiator iqn.1991-05.com.microsoft:hostA

Step 5. Bind I GROUP to Port Set

  In this step, we will bind the igroup to the port set. Once this step is completed the initiator will be able to communicate to the iSCSI target LIFs. Below is the command to bind an igroup to port set in SVM.  

lun igroup bind -vserver vs1 -igroup igroup1 -portset portset1

Steps 6: Map iSCSI LUN IGROUP

  In this step, we will map or present the LUN to the initiator group. After that, the LUN will be visible to the initiator. Below is the command to map the ISCSI LUN to an initiator.  

lun mapping create -vserver vs1 -path /vol/vol1/lun1 -igroup igroup1

Step 7. Discover New iSCSI Lun In Windows Server

LUNs on your Storage Virtual Machine (SVM) appear as local disks to the Windows host. You must manually rescan disks to discover the new LUN.

Below are the steps to do it for windows 2008 server.  

Steps 1. Open the Windows Computer Management utility:

Navigate to Computer Management Windows Server 2008 Start > Administrative Tools > Computer Management  

Step 2. Expand the Storage node in the navigation tree.

Step 3. Click Disk Management

LUNs appear in Windows Disk Management as disks. You need to initialize the disk as a basic disk with a GPT or MBR partition table.

You need to format the LUN with a file system such as NTFS, below are the steps to do it.

• Steps 1. Start Windows Disk Management.
• Steps 2. Right-click the LUN, and then select the required disk or partition type.
• Steps 3. Follow the instructions in the wizard.  

Once these steps are completed you can go to My Computer and can see the new drive. Make sure that you create and delete files in the drive.

This concludes the steps on ISCSI LUN creation in SVM and maps it to a windows server.

In this post, we will see how we can recover a deleted volume in the NetApp cluster mode. This feature is available in Data Ontap 8.3 and in the later versions.

If you delete a volume and this feature is available, then you can recover it within a certain period of time.

Step 1. Check Volume Recovery Feature In SVM

First, you need to check if the volume recovery feature is available for an SVM. Execute the below command to see the current status of volume recovery for an SVM.

vserver show -fields volume-delete-retention-hours -vserver vs1

Step 2. Enable Volume Recovery Feature

The value under volume-delete-retention-hours indicates the retention period of volumes in an SVM. If its none then the feature is not available. To enable the feature to execute the below command.

vserver modify -volume-delete-retention-hours 8 -vserver vs1

The above command will set the retention period of 8 hours for all volumes. However, you can increase the extension period by 48 hours.

Note that this feature will be available for volumes that you are going to delete. If you have already deleted a volume then this feature will not recover those volumes.

Step 3. Recover Deleted Volume In SVM

Now if you delete a volume then the volume will move to a pending state. You can view those volumes in the recovery queue. Execute the below command to see volumes under-recovery queue.

volume recovery-queue show -vserver vs1

You can only recover volumes that are in the recovery queue. The below command will recover the volume from the recovery queue.

volume recovery-queue recover -vserver vs1 -volume vv4_1033

Step 5. Access Data Post Volume Recovery

After recovering a volume you must follow the below steps to access the data.

1. Rename the volume running the volume rename command.
2. Set up a junction path by running the volume mount command.
3. Create mappings for LUNs in the volume, run the LUN map command.
4. Associate a snapshot policy and an export policy with the volume.
5. Add new quota policy rules for the volume, with the quota policy rule command.
6. Add a QoS policy for the volume, run the volume modify command.

Recover Deleted Volume Video Tutorial

If the above steps were not helpful then you can watch below YouTube videos with a detail explanation.