ONTAP Recipes topics

ONTAP Recipes: Test SVM-DR destination disaster recovery without breaking SnapMirror relationship

ontap_recipes — Fri, 05 Apr 2019 19:56:20 GMT

Did you know that…

You can easily test the SVM-DR destination disaster recovery without breaking the SnapMirror relationship?

Note: In an existing SnapMirror relationship, these steps will help you test the disaster recovery solution without breaking the SnapMirror relationship.

In a SnapMirror relationship, select the volumes to be tested.
destination::> snapmirror show -expand

Create a default subtype vserver on the destination cluster.
destination::> vserver create -vserver <clone_vserver> -subtype default
Note: Create LIFs and export polices to enable NFS traffic.

Create a clone on the destination cluster. Select the parent volume and parent Snapshot copy from the SnapMirror destination vserver as parent vserver.
destination::> vol clone create -vserver <clone_vserver> -flexclone <flex_cone_volume> -type RW -parent-vserver <SVM-DR Destination vserver> -parent-volume <parent_volume> -junction-active true -foreground true -parent-snapshot <parent_snapshot>

Mount the FlexClone volumes on the junction path.
destination::> vol mount -vserver <clone_vserver> -volume <flex_cone_volume> -junction-path /<flex_cone_volume_mountpath>

Mount through NFS on the desired test client. FlexClone volumes should be visible on the client.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Easily Convert a Synchronous SnapMirror Relationship to Asynchronous

ontap_recipes — Fri, 22 Feb 2019 20:05:23 GMT

Did you know you can…?

Easily convert a synchronous SnapMirror relationship to asynchronous

Quiesce the synchronous SnapMirror relationship:
destination::> snapmirror quiesce -destination-path vs1:vol1
Delete the synchronous SnapMirror relationship:
destination::> snapmirror delete -destination-path vs1:vol1
Release the synchronous SnapMirror relationship on the source side with the option to retain the Snapshot copies:
source::> snapmirror release -destination-path vs1:vol1 -relationship-info-only true
Note: The default release operation (without setting relationship-info-only to true) deletes the Snapshot copies created by this relationship. This process does not allow a resync operation for a new relationship created for these volumes.
Create the asynchronous SnapMirror relationship by specifying the required policy:
destination::> snapmirror create -source-path vs0:vol1 -destination-path vs1:vol1 -policy MirrorAllSnapshot
Resync the asynchronous SnapMirror relationship:
destination::> snapmirror resync -destination-path vs1:vol1

For more information about ONTAP, see the ONTAP 9 Documentation Center

ONTAP Recipes: Easily Convert a SnapMirror Relationship to Zero Recovery Point Objective

ontap_recipes — Fri, 22 Feb 2019 20:02:32 GMT

Did you know you can…?

Easily convert a SnapMirror relationship to zero recovery point objective (RPO)

Verify the network round-trip time (RTT) between the two nodes is less than 10ms.
Add a SnapMirror synchronous license to the source node.
Delete the asynchronous SnapMirror relationship:
destination::> snapmirror delete -destination-path vs1:vol1
Release the asynchronous SnapMirror relationship on the source side with the option to retain the Snapshot copies:
source::> snapmirror release -destination-path vs1:vol1 -relationship-info-only true
Note: The default release operation (without setting relationship-info-only to true) deletes the Snapshot copies created by this relationship. This process does not allow a resync operation for a new relationship created for these volumes.
Create the synchronous SnapMirror relationship by specifying a policy of type sync-mirror or strict-sync-mirror:
destination::> snapmirror create -source-path vs0:vol1 -destination-path vs1:vol1 -policy Sync
Note: To create a strict synchronous relationship, use the StrictSync policy instead.
Resync the synchronous SnapMirror relationship:
destination::> snapmirror resync -destination-path vs1:vol1

For more information about ONTAP, see the ONTAP 9 Documentation Center

ONTAP Recipes: SnapMirror Synchronous (SM-S): Calculate your RTT for SnapMirror Synchronous

ontap_recipes — Fri, 22 Feb 2019 19:58:23 GMT

Did you know you can…?

Calculate your round-trip time (RTT) for SnapMirror Synchronous

Run the cluster peer ping command, where the originating-node is the node that hosts the source volume of the relationship and the destination-node is the node that hosts the destination volume of the relationship.

cluster::> cluster peer ping -originating-node sti8080-475 -destination-node sti8080-477

Node: sti8080-475 Destination Cluster: C2_sti8080-477_cluster

Destination Node IP Address Count TTL RTT(ms) Status

---------------- ----------- ----- ---- ------- -------------------------

sti8080-477 172.26.145.10 1 64 0.452 interface_reachable

sti8080-477 172.26.145.12 1 64 0.352 interface_reachable

For intracluster relationships, you can run the network ping command in a similar way.
cluster::> network ping -node sti8080-477 -destination sti8080-475 -show-detail

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Use MetroCluster switchback functionality after a switchover operation

ontap_recipes — Mon, 16 Jul 2018 18:48:42 GMT

Did you know...

You can use MetroCluster switchback functionality after a MetroCluster switchover operation?

NetApp MetroCluster provides synchronous replication for NetApp ONTAP customers and consists of an ONTAP cluster at each customer site. When a site goes down, the switchover functionality is used to move the customer workload to the remote site.

Use the MetroCluster switchback functionality after a MetroCluster switchover operation restores a workload to a remote disaster-stricken site:

1. Verify that the disaster-stricken cluster meets the following requirements:

a. Power and connectivity have been restored to switches, intersite links, and disk shelves.

b. Nodes are rebooted (if necessary).

c. Aggregates are resynchronized through the healing functionality: metrocluster heal-phase root and
metrocluster heal-phase aggregates.

2. Invoke the MetroCluster switchback CLI.

3. Run the metrocluster operation show command to view the status of the switchback operation.

For more information about MetroCluster, see the MetroCluster Management and Disaster Recovery Guide.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Use MetroCluster switchover functionality for synchronous replication

ontap_recipes — Fri, 13 Jul 2018 18:39:06 GMT

Did you know...

You can use MetroCluster switchover functionality for synchronous replication?

Planned outage:

If you are planning an outage due to disaster recovery testing or a planned power outage, run the metrocluster switchover command while both sites are up/functional. If you run the command at the site that will survive, it will shut down in an orderly fashion.

Unplanned outage:

When the remote cluster is already down, force a switchover to start switchover processing:

Make sure the remote site is down.
Note: This step might include halting nodes.

Run the metrocluster switchover -forced-on-disaster true command. When prompted to continue with the switchover, enter yes.

For either type of switchover, run the metrocluster operation show command to view the status of the switchover operation.

For more information about MetroCluster, see the MetroCluster Management and Disaster Recovery Guide.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Run ONTAP consolidated system diagnostic command

ontap_recipes — Fri, 29 Jun 2018 16:54:19 GMT

Did you know that...

There is a simple, consolidated ONTAP command to display a system health summary and alerts, if any?

For example:

cluster_1::> system health subsystem show

Subsystem Health

----------------- ------------------

SAS-connect ok

Environment ok

Memory ok

Service-Processor ok

Switch-Health ok

CIFS-NDO ok

Motherboard ok

IO ok

MetroCluster ok

MetroCluster_Node ok

FHM-Switch ok

FHM-Bridge ok

SAS-connect_Cluster

13 entries were displayed.

cluster_1::> system health alert show

This table is currently empty.

cluster_1::> system health config show

Node Monitor Subsystem Health

------------- ---------------------- --------------- ------------------

node1 node-connect SAS-connect, CIFS-NDO, MetroCluster_Node

node1 system-connect SAS-connect_Cluster, MetroCluster, FHM-Switch, FHM-Bridge

node1 system - ok

node1 controller Environment, Memory, Service-Processor, Motherboard, IO

node1 chassis Environment ok

node1 cluster-switch Switch-Health ok

node2 node-connect SAS-connect, CIFS-NDO, MetroCluster_Node

node2 controller Environment, Memory, Service-Processor, Motherboard, IO

8 entries were displayed.

For more information, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Start the object store profiler through ONTAP CLI to test latency and throughput

ontap_recipes — Wed, 20 Jun 2018 15:23:17 GMT

Did you know that…
You can start the object store profiler through the ONTAP CLI to test latency and throughput performance?

NetApp recommends validating the latency and throughput of your specific network environment to determine the impact it has on FabricPool performance.

Starting in ONTAP 9.4, an object store profiler is available through the ONTAP CLI. You can test latency and throughput performance of object stores before you attach them to FabricPool aggregates.

Note: The external capacity tier must be added to ONTAP before it can be used with the object store profiler.

Start the object store profiler (advanced privilege level required).
storage aggregate object-store profiler start -object-store-name <name> -node <name>

View the results.
storage aggregate object-store profiler show

Note: External capacity tiers do not provide performance similar to that found on the performance tier (typically gigabytes per second).

For more information about FabricPool, see TR-4598: FabricPool Best Practices.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Use inactive data reporting on non-FabricPool aggregates

ontap_recipes — Wed, 20 Jun 2018 15:08:40 GMT

Did you know…

You can use inactive data reporting on non-FabricPool aggregates?

First available in ONTAP 9.4, inactive data reporting (IDR) is an excellent tool for determining the amount of existing inactive (cold) data that can be tiered from a high-performance SSD aggregate to low-cost object storage.

IDR uses a 31-day cooling period to determine which data is considered inactive.

IDR is displayed on the Storage Tiers page in OnCommand System Manager.

IDR is enabled by default on FabricPool aggregates, but more importantly, especially for those considering taking advantage of FabricPool for the first time, you can enable IDR on non-FabricPool aggregates.

Note: IDR cannot be enabled on aggregates where FabricPool cannot be enabled (for example, root, HDD aggregates, NetApp MetroCluster, and so on).

From the ONTAP CLI, complete the following steps:

To enable IDR on a non-FabricPool aggregate, run the following command:
storage aggregate modify -aggregate <name> -is-inactive-data-reporting-enabled true

As an alternative to viewing the amount of inactive data on an aggregate in OnCommand System Manager, you can view the amount of inactive data by running the following command:
storage aggregate show-space -fields performance-tier-inactive-user-data, performance-tier-inactive-user-data-percent

For more information about FabricPool, see TR-4598: FabricPool Best Practices.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Create a FabricPool aggregate by using OnCommand System Manager

ontap_recipes — Wed, 20 Jun 2018 14:12:38 GMT

Did you know…

You can create a FabricPool aggregate by using OnCommand System Manager?

FabricPool works by associating an object store (such as Amazon S3, Microsoft Azure Blob Storage, or StorageGRID Webscale) with an aggregate in ONTAP, creating a composite aggregate: a FabricPool aggregate.

Note: FabricPool requires a capacity-based license when attaching third-party object storage providers (such as Amazon S3) as capacity tiers for AFF and FAS hybrid flash systems. A FabricPool license is not required when using StorageGRID Webscale.

To create a FabricPool aggregate, complete this two-part process:

Part 1: Add the object store to ONTAP.

ONTAP must be able to communicate with the object store before the object store can be attached to an aggregate.

Before you add the object store to ONTAP, you need to identify the following information:

Server name (FQDN; for example, amazonaws.com)
Access key ID
Secret key
Container name (bucket name)

To add the object store to ONTAP, complete the following steps:

Launch OnCommand System Manager.
Click Storage.
Click Aggregates & Disks.
Click External Capacity Tiers.
Select an object store provider and click Add.
Complete the text fields as required for your object store provider.
Click Save and Attach Aggregates.

Part 2: Attach the object store to an aggregate.

You can complete this task can by using OnCommand System Manager.

More than one object store can be connected to a cluster, but only one type of object store can be attached to each aggregate. For example, one aggregate can use StorageGRID Webscale, and another aggregate can use Amazon S3, but one aggregate cannot be attached to both.

Note: Attaching an external capacity tier to an aggregate is a permanent action. After being attached, an external capacity tier cannot be removed.

To attach the object store to an aggregate, complete the following steps:

Launch OnCommand System Manager.
Click Applications and Tiers.
Click Storage Tiers.
Click an aggregate.
Click Actions and select Attach External Capacity Tier.
Select an external capacity tier.
View and update the tiering policies for the volumes on the aggregate (optional). By default, volume tiering policies are set as Snapshot-Only.
Click Save.

For more information about FabricPool, see TR-4598: FabricPool Best Practices.

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Set FabricPool volume tiering policies by using OnCommand System Manager

ontap_recipes — Wed, 20 Jun 2018 14:23:24 GMT

Did you know that…

You can set FabricPool volume tiering policies by using OnCommand System Manager?

After volume creation, you can change the FabricPool volume tiering policy to one of four policies by completing the following steps using OnCommand System Manager:

Launch OnCommand System Manager.
Select a volume.
Click Actions and select Change Tiering Policy.
Select the tiering policy (policy descriptions provided below) you want to apply to the volume. By default, volume tiering policies are set as Snapshot-Only.
Click Save.

For more information about FabricPool, see TR-4598: FabricPool Best Practices.

For more information about ONTAP, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Create a nonshared QoS policy

ontap_recipes — Wed, 23 May 2018 19:54:21 GMT

Did you know that…

You can create a nonshared quality-of-service (QoS) policy?

Customers who want to individually control workloads (volumes, LUNs, or files) with QoS have to create a QoS policy per workload. This results in a proliferation of QoS policies, even though just a few policies such as gold, silver, bronze would meet the customer's needs. With the release of NetApp ONTAP 9.4, a nonshared policy can be created in which each assigned workload gets the policy.

For example, a test application requires three volumes with a QoS ceiling of 1,000 IOPS per volume. Prior to ONTAP 9.4, three QoS policies would be required to achieve this. Starting with ONTAP 9.4, you can create a single nonshared QoS policy to use with all three volumes assigned to the policy.

To create a nonshared QoS policy, complete the following steps in the ONTAP CLI:

1. Create a nonshared QoS policy with a ceiling of 1,000 IOPS.

::> qos policy-group create -policy-group bronze -max-throughput 1000IOPS -is-shared false

2. Assign each volume to the QoS policy.

::> volume modify -volume test_vol1 -qos-policy-group bronze

[Job 40] Job succeeded: volume modify succeeded

::> volume modify -volume test_vol2 -qos-policy-group bronze

[Job 41] Job succeeded: volume modify succeeded

::> volume modify -volume test_vol3 -qos-policy-group bronze

[Job 42] Job succeeded: volume modify succeeded

3. Make sure each volume can serve a maximum of 1,000 IOPS.

::> qos statistics workload performance show

Workload IOPS Throughput

------------ ---- ----------

test_vol1 1000 4000KB/s

test_vol2 1000 4000KB/s

test_vol3 1000 4000KB/s

For more information about ONTAP, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Assign a LUN or file to an adaptive QoS policy

ontap_recipes — Wed, 23 May 2018 20:23:56 GMT

Did you know that…

You can easily assign a LUN or file to an adaptive quality-of-service (QoS) policy?

Complete the following step in the NetApp ONTAP CLI:

During LUN creation, assign an adaptive QoS policy:
lun create -volume vol1 -lun lun1 -size 1TB -ostype windows -qos-adaptive-policy-group extreme

For existing LUNs, you can modify or assign an adaptive QoS policy:
lun modify -volume vol1 -lun lun1 -qos-adaptive-policy-group performance

For existing files, you can modify or assign an adaptive QoS policy:
file modify -vserver vs0 -volume vol1 -file file1 -qos-adaptive-policy-group value

There are three default adaptive QoS policies in ONTAP as well as the ability to create custom policies:

::> qos adaptive-policy-group show

Expected Peak

Name Vserver Wklds IOPS IOPS

---- ------- ----- -------- ----

extreme cluster 0 6144IOPS/TB 12288IOPS/TB

performance cluster 0 2048IOPS/TB 4096IOPS/TB

value cluster 0 128IOPS/TB 512IOPS/TB

Note: When a LUN or file is assigned to an adaptive QoS policy, the IOPS allocated is set based on the size and the amount of space used.

For a 1TB LUN assigned to the performance policy, the floor and ceiling start at 2,048 IOPS. As more space is used in the LUN the ceiling increases automatically to a maximum of 4,096 IOPS.

For a small LUN, a fixed absolute minimum number of IOPS is allocated. For example, if a 20GB LUN is assigned to the performance policy, the floor and ceiling are set to 500 IOPS.

The three default adaptive QoS policies provide the following absolute minimum number of IOPS:

Extreme: 1,000 IOPS
Performance: 500 IOPS
Value: 75 IOPS

For more information about ONTAP, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Capture First Failure Data using NetApp AutoSupport On Demand Performance Archive

ontap_recipes — Tue, 22 May 2018 19:37:41 GMT

Did you know that...

You can capture first failure data using NetApp AutoSupport On Demand performance archive?

You can send up to six hours of performance archive data using a single command. It’s that easy! To send performance archives for a duration of greater than six hours, you can issue back-to-back commands. You also have the flexibility to send performance archives that are collected before, during, and after the issue being troubleshooted has occurred.

Run the following CLI command to send a performance archive as well as a message and corresponding case number. In this example, we collected the archive files from each node in the cluster starting on 12/03/2017 at 8:00 a.m. for a duration of six hours.

cluster1::> system node autosupport invoke-performance-archive -node * -start-date 12/03/2017 8:00:00 -duration 6h -message "Some perf date for 12/03" -case-number 2006123456

Note: For further analysis, contact NetApp support before or after you upload the performance archives.

For more information about using and setting up AutoSupport On Demand, see:

For more information about ONTAP, see the ONTAP 9 Documentation Center.

ONTAP Recipes: Provision ONTAP AFF Storage for MongoDB Using Workflow Automation for MongoDB

ontap_recipes — Mon, 09 Apr 2018 17:15:47 GMT

Did you know that...

You can automate storage provisioning workflows using NetApp OnCommand Workflow Automation (WFA) for MongoDB?

The WFA template for MongoDB provides a guided, automated methodology for provisioning MongoDB storage using the MongoDB vocabulary. The workflow template converts the MongoDB architectural specifications into storage requirements and then provisions that storage.

1. Download and install OnCommand Workflow Automation for Linux from the software downloads section of http://mysupport.netapp.com/.

2. Follow the prompts to download the software and installation guide, and then follow the instructions to install the software and template for MongoDB.

3. Start the workflow to add a MongoDB host:

a. Add a new data center group or choose an existing one from the drop-down menu.

b. Enter the requested information into the GUI, and then click Execute.

4. Start the Storage Controller Details workflow, choose a data center group, enter the requested data, and then click Execute.

5. Start the Provision Storage for MongoDB workflow:

a. Choose the desired MongoDB Scaling Technology (ReplicaSet or Sharding).

b. Enter the requested information into the GUI, and then click Execute.

Repeat this process as needed to provision the desired MongoDB deployment.

For more information about end-to-end storage provisioning for MongoDB, see TR-4674: End-to-End Storage Provisioning for MongoDB.

For more information about ONTAP, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Identify Top Files and Clients

ontap_recipes — Thu, 08 Feb 2018 18:49:08 GMT

Did you know you can…?

Identify top clients and top files by either IOPS or Throughput.

To identify top clients and files, follow these steps in OnCommand System Manager:

1. Select Dashboard.

2. In Applications and Objects, select Objects.

3. Choose Top Clients or Top Files.

4. Choose by IOPS or by Throughput.

5. A sorted list of the top 20 clients or top 20 files will be displayed.

For top clients, the IP address of each client is displayed along with the IOPS or throughput processed by ONTAP.

For top files, the file path is displayed along with the IOPS or throughput processed by ONTAP.

There is no performance impact when top clients or top files monitoring is enabled in ONTAP.

Top clients and top files is supported for both CIFS and NFS protocols.

For CLI users, top clients and top files is available using the statistics top client and statistics top file commands.

For more information, please access the ONTAP 9 documentation center

ONTAP Recipes: Secure data at rest using software encryption and the onboard key manager

ontap_recipes — Fri, 09 Jun 2017 15:56:38 GMT

Did you know you can...

Secure data at rest using software encryption and the onboard key manager?

If you have existing infrastructure and want to encrypt your data for compliance or standard security best practices, use the NVE software-based data-at-rest encryption feature for any SSD or disk type:

1. Install the NetApp volume encryption (NVE) license for each node.

system license add -license-code license_key

2. Start the key manager setup wizard.

security key-manager setup

3. Create a new volume and enable encryption on the volume.

volume create -vserver SVM_name -volume volume_name
-aggregate aggregate_name -encrypt true

Example: cluster1::> volume create -vserver vs1 -volume vol1 -aggregate aggr1 -encrypt true

4. Verify that the volume is enabled for encryption.

volume show -is-encrypted true

For more information, please see the ONTAP 9 documentation center.

ONTAP Recipes: Easily update your existing version of ONTAP

ontap_recipes — Fri, 09 Jun 2017 15:40:27 GMT

Did you know you can...

Quickly update your version of ONTAP using OnCommand System Manager?

Log in to OnCommand System Manager.
Click Configurations > Cluster Update.
Follow the steps in the Cluster Update wizard to perform the upgrade.

For more information, please see the ONTAP 9 documentation center.

ONTAP Recipes: Use ONTAP Storage Efficiency features to get maximum storage efficiency for AFF

ontap_recipes — Wed, 12 Jul 2017 23:57:29 GMT

ONTAP Recipes: Did you know you can...?

Use ONTAP Storage Efficiency features to get maximum storage efficiency for AFF

Storage efficiency is the ability to store and manage data while consuming the least amount of space on disk with little or no impact on performance, resulting in a lower overall cost. Efficiency is not just about making the most of the physical blocks on the disk, it's also about being able to easily provision flexible storage.

All ONTAP Storage Efficiency features are supported on All Flash FAS, including:

Thin provisioning: storage space is dynamically allocated to each volume or LUN as data is written.
Compression: reduces the physical capacity that is required to store data on the storage system by compressing data chunks.
Deduplication: eliminates extra copies of same data by saving just one copy of the data and replacing the other copies with pointers that lead back to the original copy.
Compaction: reduction of storage of data without loss of information by eliminating unnecessary redundancy.

Features enabled on the volume can be viewed and modified using the volume efficiency config command.

volume efficiency config â€“volume $VOL_NAME â€“vserver $SVM_NAME

Thin provisioning is enabled by default (space-guarantee will be none)

volume show -vserver $SVM_NAME -volume $VOL_NAME -fields space-guarantee

About Storage Efficiency

Two modes of operation support flexible volume deduplication, compression and data compaction:

Inline Storage Efficiency
Background (i.e. Post-process) Storage Efficiency

Inline Storage Efficiency

The storage efficiency savings are achieved before the data is written to disk. This also includes cross volume deduplication. All inline efficiency features are enabled by default on newly created or existing flexible volumes of an AFF system. They can be explicitly assigned later by attaching an "inline-only" policy.

To explicity assign an inline policy:

vol efficiency config -volume $VOL_NAME -vserver $SVM_NAME -policy inline-only

Specific Inline features can be enabled by using corresponding fields in above CLI.

Background (i.e. Post-process) Storage Efficiency

The storage efficiency savings are achieved after the data is written to disk. Process can be run by issuing manual commands or setting volume efficiency policies based on schedule or threshold.This is by default disabled on AFF and can be enabled on a volume by attaching a policy/schedule.

To get deduplication, compression and compaction savings on the data written after recent efficiency operation:

volume efficiency start -volume $VOL_NAME -vserver $SVM_NAME dedupe true compression true compaction true

To achieve efficiency savings on old data in the volume:

volume efficiency start -volume $VOL_NAME -vserver $SVM_NAME -scan-old-data true dedupe true compression true compaction true

For background deduplication, a system created policy called "dafault" runs everyday at 12:00AM. To create a custom policy with a different schedule:

volume efficiency modify -vserver $SVM_NAME -volume $VOL_NAME -policy $POLICY_NAME

To enable both inline and background storage efficiencies on a volume which has an "inline-only" policy:

volume efficiency modify -vserver $SVM_NAME -volume $VOL_NAME -policy default

volume efficiency modify -volume $VOL_NAME -inline-dedupe true

-cross-volume-inline-dedupe true -compression true -inline-compression true -data-compaction true

ONTAP Recipes: Manage storage efficiency policies in ONTAP

ontap_recipes — Wed, 12 Jul 2017 23:24:28 GMT

ONTAP Recipes: Did you know you can...?

Manage storage efficiency policies in ONTAP

Background (i.e. Post-process) data deduplication and data compression can be run on a FlexVol volume or Infinite Volume.

You can schedule a deduplication operation by creating job schedules as part of the efficiency policies or you can specify a threshold percentage, which triggers the deduplication or compression operation only after new data has exceeded the specified percentage.
You can disassociate an efficiency policy to stop running any further scheduled based deduplication and data compression operations on the volume by using the volume efficiency modify command.

A volume efficiency policy exists in the context of a Storage Virtual Machine (SVM). The volume efficiency policies support only job schedules that are of type cron."Volume efficiency" is already aliased to "sis" in cluster-shell. Apart from enabling/disabling various storage efficiency features, there are various policies that govern the behavior.

ONTAP provides following storage efficiency policies:

None: none of the storage efficiency features are enabled.
Default:dedupe is ON and deduplication operation start time is set to midnight.
--: dedupe is ON, but the user has set a different schedule than default (midnight), so policy becomes "-".
Inline: inline data compression, inline data deduplication, inline data compaction and inline data zero detection are enabled.

You can typically create policies based on:

Schedule: when the post-process operation (deduplication/compression) should start.
Data Change Rate: how much percentage of data is changed since last operation.
QoS: QoS setting

Following are the useful commands to configure deduplication policies in an ONTAP system.

Creating an Efficiency Policy

Create a volume efficiency policy named pcy1 that triggers an efficiency operation daily.

volume efficiency policy create -vserver vs1 -policy pcy1 -schedule daily

Create a volume efficiency policy named pcy that triggers an efficiency operation when the threshold percentage reaches 40%.

volume efficiency policy create -vserver vs1 -policy pcy1 -type threshold -start-threshold-percent 40%

Setting a Volume Efficiency Policy

Assign the volume efficiency policy named pcy1 with volume vol1.

volume efficiency modify -vserver vs1 -volume vol1 -policy pcy1

Modifyung a Volume Efficiency Policy

Modify the volume efficiency policy named pcy1 to run every hour.

volume efficiency policy modify -vserver vs1 -policy pcy1 -schedule hourly

Modify a volume efficiency policy named pcy1 to threshold 20%.

volume efficiency policy modify -vserver vs1 -policy pcy1 -type threshold -start-threshold-percent 20%

Viewing Volume Efficiency Policies

Display information about the policies created for the SVM vs1.

volume efficiency policy show -vserver vs1

Display the policies for which the duration is set as 8 hours

volume efficiency policy show -duration 8

Disassociate a Volume Efficiency Policy from a Volume

Disassociate the volume efficiency policy from volume vol1.

volume efficiency modify -vserver vs1 -volume 1ol1 -policy -

Delete a Volume Efficiency Policy Not Associated with any Volume

Delete a volume efficiency policy named pcy1.

volume efficiency policy delete -vserver vs1 -policy pcy1

ONTAP Recipes: Configuring an external FTP host to serve data from an ONTAP system

ontap_recipes — Mon, 05 Feb 2018 20:38:52 GMT

ONTAP Recipes: Did you know you can?

Work around the lack of FTP support in ONTAP with CIFS/SMB or NFS

Clustered ONTAP natively does not support FTP access, which means you can't set up an FTP server in Clustered ONTAP like you could with 7-Mode. That doesn't mean you can't use ONTAP to host data accessed via FTP.

ONTAP steps

1. Create a volume on the storage system to host your FTP-accessed data. If desired, create qtrees in the volume to act as directories for users. Create folders inside the qtree for FTP access, if desired.

2. Create a way to access the data (either CIFS share or NFS export).

3. Lock down permissions to the volume at a file/folder level.

FTP server steps (Windows):

Whether you're using a Windows server or client, you can turn FTP on or off as a Windows feature in most versions of Windows:

1. Enable FTP (method will vary based on Windows OS - for example: https://technet.microsoft.com/en-us/library/hh831655(v=ws.11).aspx#Step1)

2. Add an FTP site; set the UNC path to the CIFS share as the physical path.

3. Configure FTP as desired (SSL, IP addresses, ports, authentication, security, etc).

4. Click on sites and click on the FTP site. Click "Basic Settings" and click the "Test Settings" button.

5. If successful, test FTP access, puts, gets, etc.

FTP server steps (CentOS 7):

The following link shows how to configure FTP in CentOS 7.
https://www.unixmen.com/install-configure-ftp-server-centos-7/

For Ubuntu:
https://www.digitalocean.com/community/tutorials/how-to-set-up-vsftpd-for-a-user-s-directory-on-ubuntu-16-04

Additionally, you can find many examples of FTP servers leveraging Docker containers at the Docker hub.

https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=vsftp&starCount=0

1. Install FTP on the Linux VM

2. Install NFS client tools (if not already installed)

3. Mount the NFS export to the client and add it to /etc/fstab to remount on reboots, or use autofs configuration to use homedirs for FTP. Recommended mount options:

rsize=65536,wsize=65536,bg,hard

4.Configure FTP to use the NFS export as the FTP datastore. For vsftp, add the following lines to the /etc/vsftpd/vsftpd.conf file:

user_sub_token=$USER

local_root=/NFSpath/$USER/ftp

5. Configure/secure FTP as desired.

6. Test FTP access, puts, gets, etc.

ONTAP Recipes: Deploy MongoDB replica sets that retain storage efficiency

ontap_recipes — Sat, 08 Jul 2017 00:40:06 GMT

ONTAP Recipes: Did you know you can…?

Deploy MongoDB replica sets that retain storage efficiency

Create a flexvol to host the MongoDB primary. Mount the flexvol on the primary host.
Take a snapshot on the flexvol created in step 1.
Create volume clones based on the snapshot taken in step 2. Create as many volume clones as there are secondaries in the replica set.
Mount one clone volume on each secondary host.
Initialize the replica set. Since the data in the primary and clone volumes is same, the primary and secondary replica sets are in sync immediately.
As the source and clone volumes diverge due to new writes coming in, customers can destroy the older snapshot (from step 2) and recreate a newer set of clones.

The workflow can be easily automated using NetApp WFA (workflow automation) tool or shell scripts and works for both SAN and NAS.

For more information, see the ONTAP9 documentation center

ONTAP recipes: Easily create storage pools

ontap_recipes — Sat, 08 Jul 2017 00:35:28 GMT

Did you know you can...?

Easily create a storage pool

Use System Manager to combine SSDs to create a storage pool, or collection of SSDs (cache disks), which enables you to share the SSDs and SSD spares between an HA pair for allocation to two or more Flash Pool aggregates at the same time.

Both nodes of the HA pair must be up and running in order to allocate SSDs and SSD spares through a storage pool.
Storage pools must have a minimum of 3 SSDs.
All SSDs in a storage pool must be owned by the same HA pair.
You cannot use partitioned SSDs when creating a storage pool by using System Manager.

Click Storage > Aggregates & Disks > Storage Pools.
In the Storage Pools window, click Create.
In the Create Storage Pool dialog box, specify the name for the storage pool, disk size, and the number of disks.
Click Create.

For more information, see the ONTAP9 documentation center.

ONTAP Recipes: Easily create a cluster management interface

ontap_recipes — Sat, 08 Jul 2017 00:29:15 GMT

ONTAP Recipes: Did you know you can…?

Easily create a cluster management interface

Use System Manager to create a cluster management interface or LIF to provide a single management interface for the entire cluster.

1. In System Manager, click the Configurations tab.

2. In the Cluster Settings pane, click Configuration Updates.

3. Click Create Cluster-management LIF.

4. In the Create Cluster-Management LIF dialog box, specify a name for the cluster-management LIF.

5. Assign the IP address by choosing one of the folowing options:

Using a subnet
Without a subnet

6. Select the required ports from the ports details area.

7. Click Create.

For more information, see the ONTAP9 documentation center

ONTAP Recipes: Easily provision storage by creating an aggregate

ontap_recipes — Fri, 30 Jun 2017 23:26:45 GMT

ONTAP Recipes: Did you know you can…?

Easily provision storage by creating an aggregate

You can create an aggregate that consists of only HDDs or only SSDs by using System Manager if all disks are the same size.

1. Choose one of the following methods:

Click Applications & Classes > Storage Tiers.

Click Storage > Aggregates & Disks > Aggregates.

2. Click Create.

3. In the Create Aggregate dialog box, specify the name of the aggregate, the disk type, and the number of disks or partitions to include in the aggregate. The minimum hot spare rule is applied to the disk group that has the largest disk size.

4. Click Change. In the Change RAID Configuration dialog box, specify the RAID type and the RAID group size.

5. Click Save.

6. If you want to mirror the aggregate, select the Mirror this aggregate check box.

7. Click Create.

The aggregate is created with the specified configuration, and is added to the list of aggregates in the Aggregates window.

For more information, see the ONTAP 9 doc center.

ONTAP Recipes: Easily activate or deactivate quotas

ontap_recipes — Fri, 30 Jun 2017 23:03:15 GMT

ONTAP Recipes: Did you know you can…?

Easily activate or deactivate quotas

You can use System Manager to activate or deactivate quotas on one or more selected volumes on your storage system, as your users and their storage requirements and limitations change.

Click Storage > SVMs
Select the SVM, and then click Manage.
Click the Quotas.
In the Quota Status on Volumes tab, select one or more volumes for which you want to activate or deactivate quotas.
Click either Activate or Deactivate.
If you are deactivating a quota, select the confirmation check box and click OK.
Verify the quota status on the volumes in the Status column.

For more information, see the ONTAP9 documentation center

ONTAP Recipes: Easily create an Oracle RAC Application on SAN

ontap_recipes — Tue, 27 Jun 2017 22:23:46 GMT

ONTAP Recipes: Did you know you can...?

Easily Create an Oracle RAC Application on SAN

Use the Oracle application creation feature in ONTAP 9.2 to set up the application with 2 instances of the database, provision the set of volumes needed for its storage and place them on aggregates and nodes that can safely meet the capacity and IOPS requirements of the workload, provision QoS policies to ensure continued compliance with those requirements, and identify the hosts that will access the objects.

An Oracle RAC application can be created for use over NFS in OnCommand System Manager using the following steps:

1. Select the SVM.

2. Click the Applications tab in the menu bar.

3. Click Add Application.

4. In the “Add Oracle Instance” page, specify the following properties of the application:

The name of the database.
The Oracle cluster name, also used to construct object names.
The names of each of the 2 database instances and their SIDs. The names will be used as the next part of the names of objects mentioned above for each database.
The datafile storage service level and size. This describes the size of the database and its desired performance characteristics, in terms of one of the storage service levels offered by the system, such as Extreme, Performance and Value.
Properties of the redo log, similar to the datafile mentioned above.
Enable or disable redo log mirroring.
Select if Grid Binaries and CRS/Voting volumes should be provisioned.

5. Select SAN as the protocol used to access the application.

6. Select the host operating system that will access the application.

7. The name of the initiator group and initiator ids that will access each of the two database instances of the application.

8. Use System Manager to view the details of the Oracle RAC application.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily create an Oracle RAC Application on NFS

ontap_recipes — Tue, 27 Jun 2017 22:14:28 GMT

ONTAP Recipes: Did you know you can? Create an Oracle RAC Application on NFS

Easily Create an Oracle RAC Application on NFS

Use the Oracle application creation feature to set up the application with two instances of the database, provision the set of volumes needed for its storage and place them on aggregates and nodes that can safely meet the capacity and IOPS requirements of the workload, provision QoS policies to ensure continued compliance with those requirements, and identify the hosts that will access the objects.

An Oracle RAC application can be created for use over NFS in OnCommand System Manager using the following steps:

1. Select the SVM.

2. Click the Applications tab in the menu bar.

3. Click Add Application.

4. In the “Add Oracle Instance” page, specify the following properties of the application:

The name of the database.
The Oracle cluster name, also used to construct object names.
The names of each of the 2 database instances and their SIDs. The names will be used as the next part of the names of objects mentioned above for each database.
The datafile storage service level and size. This describes the size of the database and its desired performance characteristics, in terms of one of the storage service levels offered by the system, such as Extreme, Performance and Value.
Properties of the redo log, similar to the datafile mentioned above.
Enable or disable redo log mirroring.
Select if Grid Binaries and CRS/Voting volumes should be provisioned.

5. Select NFS as the protocol used to access the application.

6. Select the host operating system that will access the application.

7. The IP addresses of the hosts that will access the application.

8. Use System Manager to view the details of the Oracle RAC application.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily create a VSI application on SAN

ontap_recipes — Fri, 23 Jun 2017 16:51:00 GMT

ONTAP Recipes: Did you know you can…?

Easily Create a VSI Application on SAN

To create a VSI application for use over SAN without compromising application or overall system performance, follow these steps in OnCommand System Manager:

Select the SVM.
Click the Applications tab in the menu bar.
Click Add Application.
In the “Add Virtual Server Datastores” page, specify the following properties of the application:

The name of the datastore.
The number of datastores, their storage service levels and sizes.
The type of the hypervisor that will host the VMs that access the datastores.
Select SAN as the protocol used to access the application.
Select the host operating system that will access the application.
Indicate name of the initiator group and initiator ids that will access the application.

5. Use System Manager to view the details of the VSI application.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily create a VSI application on NFS

ontap_recipes — Fri, 23 Jun 2017 16:35:45 GMT

ONTAP Recipes: Did you know you can…?

Easily Create a VSI Application on NFS

To create a VSI application for use over NAS without compromising application or overall system performance, follow these steps in OnCommand System Manager:

Select the SVM.
Click the Applications tab in the menu bar.
Click Add Application.
In the “Add Virtual Server Datastores” page, specify the following properties of the application:

The name of the datastore.
The number of datastores, their storage service levels and sizes.
The type of the hypervisor that will host the VMs that access the datastores.
Select NAS as the protocol used to access the application.
Specify the Hyper-V Service account (for hypervisor=Hyper-V) or the host IP address (hypervisor=VMware or Xen).

5. Use System Manager to view the details of the VSI application.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Correlate EMS Messages and Performance Metrics with NetApp OATS

ontap_recipes — Fri, 30 Jun 2017 23:34:37 GMT

Did you know you can…?

Correlate EMS Messages and Performance Metrics with NetApp OATS (ONTAP Analytics and Telemetry Services)

If you’d like to diagnose performance problems in one or more clusters by correlating EMS messages and Key Performance Metrics (KPM), you can deploy the free Netapp ONTAP Analytics and Telemetry Services (OATS) application into your AWS.

OATS performance dashboards display data for multiple clusters, allowing summary and drill down detailed views. OATS data collection imposes almost no overhead on ONTAP and can be used in all performance scenarios. It also provides a complete set of APIs for more advanced integration and data exploration.

To deploy OATS in a matter of minutes:

1. Confirm access to your AWS Account. You’ll need administration privileges to be able to deploy a stack of resources. Go to https://aws.amazon.com for more details.

2. Go to AWS Marketplace (https://aws.amazon.com/marketplace) and search for Netapp OATS. You’ll have three results for the three Amazon Machine Images (AMIs):

NetApp ONTAP Analytic & Telemetry Services (OATS) - Web Portal
NetApp ONTAP Analytic & Telemetry Services (OATS) - Monitoring Services
NetApp ONTAP Analytic & Telemetry Services (OATS) - Trafero Services

3. Accept the Software Terms for each of those machines and continue the deployment through CloudFormation Console, from the Web Portal AWS page. For more information on how to install in AWS, see: https://s3.amazonaws.com/oats-metadata/1.0.1/oats_aws.html

4. Set up the deployment based on your AWS settings, security and network configuration. For details on parameters, see: https://s3.amazonaws.com/oats-metadata/1.0.1/oats_getting-started.html#_deploying_cloud_oats_CFT

5. Your OATS Stack will be deployed in about 15 to 20 mins by Amazon Web Services.

6. Follow instructions to set up a DataCollector container in your environment, with read-only access to the clusters you want to monitor. For details on the DataCollector installation, see: https://s3.amazonaws.com/oats-metadata/1.0.1/oats_datacollector.html

7. Once deployed, the stack will receive data and dashboards will be available.

For more information, see Getting started with OATS: https://s3.amazonaws.com/oats-metadata/1.0.1/oats_getting-started.html

To learn more about OATS watch:

For more documentation, see the ONTAP9 documentation center.

ONTAP Recipes: Easily Create an Oracle Application on SAN

ontap_recipes — Wed, 21 Jun 2017 18:18:34 GMT

ONTAP Recipes: Did you know you can…?

Easily create an Oracle application on SAN

To create an Oracle application for use over SAN without compromising application or overall system performance, follow these steps in OnCommand System Manager:

Select the SVM.
Click the Applications tab in the menu bar.
Click Add Application.
In the “Add Oracle Instance” page, specify the following properties of the application:
- The name of the database.
- The name of the database server.
- The datafile storage service level and size.
- Properties of the redo log.
- Enable or disable redo log mirroring.
- Select SAN as the protocol used to access the application.
- Select the host operating system that will access the application.
- Host mapping information for the initiator group and initiator ids that will access the application.

After creation, details of the Oracle application components will be displayed in the System Manager summary.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily Create an Oracle Application on NFS

ontap_recipes — Wed, 21 Jun 2017 16:31:43 GMT

ONTAP Recipes: Did you know you can…?

Easily create an Oracle application on NFS

To create an Oracle application for use over NFS without compromising application or overall system performance, follow these steps in OnCommand System Manager:

Select the SVM.
Click the Applications tab in the menu bar.
Click Add Application.
In the “Add Oracle Instance” page, specify the following properties of the application:
- The name of the database.
- The name of the database server.
- The datafile storage service level and size.
- Properties of the redo log.
- Enable or disable redo log mirroring.
- Select NFS as the protocol used to access the application.
- Specify the IP addresses of the hosts that will access the application.

After creation, details of the Oracle application components will be displayed in the System Manager summary.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Send ONTAP EMS messages to your syslog server

ontap_recipes — Fri, 16 Jun 2017 18:48:24 GMT

ONTAP Recipes: Did you know you can…?

Send ONTAP EMS messages to your syslog server

Create a syslog server destination for important events:

event notification destination create -name syslog-ems -syslog syslog-server-address

Configure the important events to forward notifications to the syslog server:

event notification create -filter-name important-events -destinations syslog-ems

The default “important-events” work well for most customers.

For more information, see the ONTAP 9 EMS Configuration Express Guide in the ONTAP 9 Documentation Center.

ONTAP Recipes: Send ONTAP EMS messages to your syslog server

ontap_recipes — Fri, 16 Jun 2017 18:21:34 GMT

ONTAP Recipes: Did you know you can…?

Send ONTAP EMS messages to your syslog server

1. Create a syslog server destination for important events:

event notification destination create -name syslog-ems -syslog syslog-server-address

2. Configure the important events to forward notifications to the syslog server:

event notification create -filter-name important-events -destinations syslog-ems

The default “important-events” work well for most customers.

For more information, see the ONTAP 9 EMS Configuration Express Guide in the ONTAP9 documentation center

ONTAP Recipes: Deploy a MongoDB test/dev environment on DP Secondary

ontap_recipes — Thu, 15 Jun 2017 19:27:37 GMT

ONTAP Recipes: Did you know you can…?

Deploy MondoDB test or development environment on Data Protection Secondary storage

Before you begin, you need:

AFF/FAS system as primary storage
FAS system as secondary storage (unified replication for DR and vault)
Snapmirror license on both systems
Intercluster LIF on both systems
MongoDB Replica Set production system
Server to mount the clone database (cloning server)

Set up the cluster peering between primary and secondary systems.
Establish the SVM peering between the SVM that holds your MongoDB production database on the primary system with the SVM on the secondary system that will work as the vault system.
Initialize the relationship to get your baseline snapshot in place.
On the unified replication system, identify the volume(s) which contain the MongoDB replica set LUNs, identify the snapshot that reflects the version, and create a FlexClone based on that snapshot.
Map the cloned LUNs to the cloning server. You don’t have to map LUNs from primary and all secondaries, just pick one (for example, primary member of the replica set) and map its LUNs to the cloning server.
Mount the cloned LUNs filesystem.
Create a MongoDB config file in the cloning server, like the one that already exists in the production environment, except that you will make the dbpath option pointing to the cloned LUNs filesystem and exclude the replication section of the config file.
Connect to your cloned MongoDB database.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Prioritize business critical applications using QoS Min

ontap_recipes — Fri, 21 Jul 2017 17:09:00 GMT

Did you know you can…

Prioritize business critical applications using QoS Min?

QoS allows you to isolate business-critical applications to ensure they meet required performance. To set a QoS Min of 40,000 IOPS for a business-critical application:

1. Log in to OnCommand System Manager.

2. Select the volume provisioned for the business-critical application, then select Actions, Storage QoS.

3. Set the Minimum Throughput to 40,000 IOPS.

4. From the Performance Dashboard, check that the QoS Min of 40,000 IOPS has been met and that latency has been reduced.

Note that competing workloads may show higher latencies and reduced throughput.

For more on QoS watch:

For more information, please see the ONTAP 9 documentation center.

ONTAP Recipes: Easily create a Clone from SQL Database using SnapCenter

ontap_recipes — Fri, 13 Oct 2017 21:27:08 GMT

ONTAP Recipes: Did you know you can…?

Easily create a Clone from SQL Database using SnapCenter

Login to SnapCenter server and click on the “Resources” tab as shown below, navigate and select Oracle DB to be restored once you are in Resources Tab.

2. After selecting the database, user will be navigated to Database Topology view as shown below, please select a data Backup Name and click on the Clone icon:

3. A clone wizard will be launched, define the SID for the Clone Database and click on next button:

4. In the next screen, select the host where the clone database should be created and optionally customize the mount points for the clone database on the database server as shown below:

5. Optionally define a new password for the clone database

6. Proceed till the summary page with default options and click on the “Finish” button to start Clone from backup, after clicking on the “Finish” button, navigate to “Monitor” tab by clicking on the Monitor link as shown below:

7. After the clone is completed, topology page of the source database will have the clone entry as show below

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create a Data Lake using ONTAP Storage

ontap_recipes — Fri, 29 Sep 2017 21:27:50 GMT

ONTAP Recipes: Did you know you can…?

Easily create a data lake using Apache Hadoop and ONTAP storage

The term “data lake” can be defined as a centralized store for enterprise data, including structured, semi-structured and unstructured data, used by multiple enterprise applications.

This recipe highlights the steps how to create a data lake with Apache Hadoop on ONTAP.

Determine hardware and network requirements using the Hortonworks cluster planning guide:

https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_cluster-planning/content/ch_hardware-recommendations_chapter.html

For evaluation purposes, a single server may be sufficient.

A two-node cluster can be configured with two servers: one master node and one worker node.

Larger clusters for actual production will require the following:

1 NameNode server
1 Resource Manager server
Several worker node servers, each running both the DataNode and NodeManager services. The number of worker nodes will depend on the desired compute capacity. The planning guide should help with making that determination.

HA is recommended for production clusters, so you may also need a secondary NameNode server and a secondary ResourceManager server.

2. Determine the data set size. Since, data in a Hadoop cluster can grow quickly, that size should be increased by 20% or more, based on growth projections.

3. Apply the HDFS replication factor to the data set size to determine storage requirements.

For ONTAP storage, a minimum replication count of “2” is acceptable. To get storage requirements, multiply the data set size by “2”.

4. Calculate storage for each datanode so that the total data set will be spread evenly across them.

Per NetApp SAN best practices configure storage as follows:

a. Configure an SVM with the FC protocol enabled

b. Configure LIFs, aggregates, volumes and LUNs to meet storage requirements. Two LUNs per datanode, one LUN per volume should be sufficient.

5. Reference the Hortonworks Ambari Automated install documentation and then complete the Hadoop install:

https://docs.hortonworks.com/HDPDocuments/Ambari/Ambari-2.2.2.0/index.html

a. Determine which server operating system will be used and then configure your servers per the minimum system requirements.

b. On the storage array, create FC igroups and map storage LUNs to the datanodes.

c. On the datanode servers, partition the LUNs, and create the file systems on the datanode hosts.

d. Create mountpoints on the datanodes for the new file systems.

e. Mount the file systems on the datanodes.

f. Follow the procedure outlined in the Ambari documentation for preparing the environment, configuring the Ambari repository, installing the Ambari Server and deploying the HDP cluster. Once the Ambari Server has been installed, the deployment will be a guided, automated procedure.

After the Ambari Hadoop deployment has finished, data can be loaded into HDFS using a number of utilities, including Flume and Sqoop. We’re now able to harness all the power of ONTAP for Hadoop.

Below is a diagram showing an example of an ONTAP based data lake:

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create a Policy for ONTAP to ONTAP to CLOUD topology using SnapCenter

ontap_recipes — Thu, 28 Sep 2017 22:14:40 GMT

ONTAP Recipes: Did you know you can…?

Easily create a Policy for ONTAP to ONTAP to CLOUD topology using SnapCenter

The recipe shows the easy steps that you can follow:

2. Go to “Settings” page > “Policies” tab.

3. You can see list of pre-canned policies, which SnapCenter supports

4. Select “Backup to Cloud ” policy and click on Copy

5. Enter the Policy Name for the newly copying Policy

6. Once the policy has been successfully copied, please select the policy and click on Modify to select the Cloud Bucket associated with AVA

7. You have an option, while modifying, depending on whether you want to capture ACLs or not

8. You can enter the Backup Creation Time, Retention for Respective Nodes and their tiers

9. Scheduled Daily, Weekly and Monthly backups can be set and triggered on primary ONTAP site. You can also configure these backup’s to be transferred from ONTAP to CLOUD at Backup Transfer Start time, based on the less traffic on Clustered ONTAP.

10 Add the hours for Transfer window and Lag time, which is for SnapCenter to monitor the backup transfer.

11. If Snapshot gets transferred within expected hours (Transfer Window + Lag Time), then Volume is in compliant state and scheduled jobs (daily, weekly and monthly) will be marked as Completed.

12. Else Volume is in non-compliant state and scheduled job will be in warning state

For more information, see the ONTAP 9 documentation center and the Data Fabric Solution for Cloud Backup Workflow Guide Using SnapCenter (http://docs.netapp.com/mgmt/topic/com.netapp.doc.df-cloud-bu-wg/home.html?cp=5_4)

ONTAP Recipes: Easily manage NetApp Storage with your corporate Active Directory (AD) login

ontap_recipes — Fri, 22 Sep 2017 21:47:38 GMT

ONTAP Recipes: Did you know you can…?

Easily manage NetApp Storage with your corporate Active Directory (AD) login credentials

This recipe will help you setup NetApp Storage admin accounts that are based on your current login accounts served by your corporate Active Directory server.

The steps illustrated below are for both cluster management vserver (SVM) and data serving SVM.

Pre-conditions:

Ensure that the required network settings [ipaddr, netmask, route, DNS et.al] are in place and the AD server is reachable from the interface(s) configured for the SVM [administrative and/or data SVM].
The ONTAP user account to be created has to be a valid user account defined at the AD server.

PART 1: Data SVM workflow :

You will need an administrative account credentials for the AD server. This is needed for adding the SVM as a machine account at the AD server.

Example : The following sequence of commands is needed to create user account “vs1u1” for a data SVM “vs1” with role “vsadmin” and configure it in AD serving domain “mydomain.com":

Create the AD entry for the SVM

Cluster-1_2::>vserver active-directory create -account-name vs1 -domain mydomain.com -ou CN=Computers -vserver vs1

In order to create an Active Directory machine account, you must supply the name and password of a Windows account with sufficient privileges to add computers to the "CN=Computers" container within the "mydomain.com" domain.

Enter the user name: administrator [This is the administrator privileged account at the AD server]

Enter the password:

2. Verify the AD configuration [Also login to the AD server and verify the entry for “vs1” in the machines’ list for the configured domain]

Cluster-1_2::> vserver active-directory show

Account Domain/Workgroup

Vserver Name Name

----------- ------------- ------------

vs1 VS1 mydomain

3. Create the user account for the SVM. Note that the user name will be in the format <domainname>\<username>

Cluster-1_2::> security login create -user-or-group-name mydomain\vs1u1 -application ssh -authentication-method domain -role vsadmin -vserver vs1

Cluster-1_2::> security login show -user-or-group-name mydomain\vs1u1 -vserver vs1

Vserver: vs1

User/Group Authentication Acct

Name Application Method Role Name Locked

-------------- ----------- --------- ------------ ------

mydomain\vs1u1 ssh domain vsadmin -

4. Login to ONTAP using the account thus created

Client-host-machine> ssh mydomain\\vs1u1@vs1

Password:

vs1::> security login whoami

User: mydomain\vs1u1

Role: vsadmin

PART 2 : Administrative SVM workflow :

For the administrative SVM (cserver), a domain tunnel (tunnel vserver) needs to be created first. This establishes an authentication gateway or "tunnel" for authentication of user accounts with the Active Directory, thus enabling the login to administrative SVM

Identify an already created or create a new data vserver (SVM) that is configured with the AD server as explained in PART 1 (Data SVM workflow). This is the SVM that will be specified with subsequent tunnel command. The tunnel SVM has to be running or this command will return an error. Only one SVM is allowed to be used as a tunnel. If you attempt to specify more than one SVM the system returns an error. If the tunnel Vserver is stopped or destroyed, user authentication requests for administrative SVM will fail.

The following shows example of commands needed to create login user “user_ad_ssh” for administrative SVM “Cluster-1_2”. In this example, the SVM created in PART 1 above is re-purposed as tunnel SVM for the administrative SVM.

Cluster-1_2::> security login domain-tunnel create -vserver vs1

Cluster-1_2::> security login domain-tunnel show

Tunnel Vserver: vs1

2. Create the user

Cluster-1_2::> security login create -user-or-group-name mydomain\user_ad_ssh -application ssh -authentication-method domain -role admin -vserver Cluster-1_2

Cluster-1_2::> security login show -user-or-group-name mydomain\user_ad_ssh -vserver Cluster-1_2

Vserver: Cluster-1_2

User/Group Authentication Acct

Name Application Method Role Name Locked

-------------- ----------- ------------- ------------- ---------

mydomain\user_ad_ssh ssh domain admin -

3. Login to ONTAP administrative SVM using the account thus created

Client-host-machine> ssh mydomain\\user_ad_ssh@Cluster-1_2

Password:

Cluster-1_2::> security login whoami

User: mydomain\user_ad_ssh

Role: admin

Note: Often, authentication does not work as expected due to incomplete/wrong name-services configuration. Ensure you have the right DNS, AD, ns-switch settings.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily manage NetApp Storage with your corporate (NIS or LDAP) login credentials

ontap_recipes — Wed, 20 Sep 2017 18:29:52 GMT

ONTAP Recipes: Did you know you can…?

Easily manage NetApp Storage with your corporate (NIS or LDAP) login credentials

This recipe will help you setup NetApp Storage admin accounts that are based on your current login accounts served by your corp LDAP or NIS Directory server. Such users can login to ONTAP for management access, using the same credentials that allow them to access the corporate network.

Steps:

Pre-conditions:

a. Ensure that the required network settings [ipaddr, netmask, route, DNS et.al] are in place and the NIS/LDAP server is reachable from the interface(s) configured for the SVM [administrative and/or data SVM]

b. Ensure that the directory server [LDAP/NIS] is configured for the SVM

c. Ensure that the lookup for password database in the name services’ ns-switch settings for the SVM, includes the NIS/LDAP as source and is in the preferred order for lookup

d. The ONTAP user account to be created has to be a valid user account defined at the NIS/LDAP directory server

2. Create the admin account in ONTAP choosing appropriate application protocol [http, console, ssh etc] and choose the authentication method as “nsswitch”

Example: Creating the user “user_nis_ssh” for SSH application with “admin” role privileges for cluster SVM “cluster-1_2” specifying the source of authentication as NIS server.

a. Create the ONTAP user account in the security login table choosing the application, authentication method, role and SVM

Cluster-1_2::> security login create -user-or-group-name user_nis_ssh -authentication-method nsswitch -application ssh -role admin -vserver Cluster-1_2

b. Verify the user is created for the SVM

Cluster-1_2::> security login show

Vserver: Cluster-1_2

User/Group Authentication Acct

Name Application Method Role Name Locked

-------------- ----------- ------------- ------ --------

admin console password admin no

admin http password admin no

admin ontapi password admin no

admin service-processor password admin no

admin ssh password admin no

user_nis_ssh ssh nsswitch admin -

c. Verify the login from a client machine using the created user’s credentials

Client-host-machine>ssh ssh user_nis_ssh@ Cluster-1_2

Password:

Cluster-1_2::> security login whoami

User: user_nis_ssh

Role: admin

Note: Often, authentication does not work as expected due to incomplete/wrong name-services configuration. Ensure you have the right DNS, NIS/LDAP, ns-switch settings.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily add 6 SSDs to a 8-SSD AFF-A200 HA-Pair

ontap_recipes — Wed, 13 Sep 2017 18:36:42 GMT

ONTAP Recipes: Do you know you can...?

Easily add 6 SSDs to a 8-SSD AFF-A200 HA-Pair

An AFF-A200 HA pair ordered with 8x SSDs uses the root-data-data partitioning scheme. Typically, the SSDs are provisioned into aggregates such that each controller uses 7 data partitions for filesystem data, and one data partition remains as a spare.

This recipes highlights the steps to add 6x SSDs to such a system.

1. Install the SSDs. They should be the same capacity as the existing SSDs.

2. Go to System Manager and select Hardware and Diagnostics -> Disks

3. Choose the Inventory tab, then Assign.

4. Assign all 6 SSDs to one of the two controllers in the HA pair. Let’s call it Node A.

5. Go to the Hardware and Diagnostics -> Aggregates screen, choose the data aggregate owned by Node A,

then Actions -> Add Capacity.

6. At this point, you will see one small SSD partition, and 6 whole SSDs.

7. Add the smaller disk/partition to the aggregate. This is the spare partition from the original 8-drive configuration.

8. Repeat the Actions -> Add Capacity operation for 5 of the 6 remaining disks. As you provision the whole SSDs into the data aggregate, they will be partitioned to match the rest of the SSDs. One data partition per SSD will be used on this aggregate, and another spare data partition will be created and assigned to the partner node.

9. Return to the Aggregates screen and repeat the Actions -> Add Capacity operation for the data aggregate on the second node in the HA pair. If System Manager gives an error saying you have insufficient spare disks, you can resolve this by returning

to the Disks-> Inventory screen and assign the remaining spare disk back to the second node.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create Snapshot copies on the Secondary (destination) volumes

ontap_recipes — Wed, 06 Sep 2017 23:33:58 GMT

ONTAP Recipes: Did you know you can…?

Easily create Snapshot copies on the Secondary (destination) volumes

Starting with ONTAP 9.0, SnapMirror policy can be specified either to transfer the Snapshot copy from the primary or to create the Snapshot copy directly on the destination volume (of SnapVault, Unified Replication relationships)

This recipe provides the following steps to create Snapshot on Secondary volume either for archival purposes or for establishing a different Snapshot cadence (while not impacting the primary)

1. Create a cron job to define the schedule when you want to create Snapshot copies

“cron create –name < cron_name > -minute < > -hour < > -day < > -month < > “

e.g. “cron create –name monthly_snap –minute 0 –hour 4 –day 1 –month January, February, March, April, May, June, July, August, September, October, November, December”

2. Identify the SnapMirror Policy that correlates to the destination volume (on which you want to create additional Snapshots) and add the rule to that policy.

“snapmirror policy add-rule –vserver < vserver_name > -policy < snapmirror_policy_name > -snapmirror-label < label_name -schedule < cron_name > -prefix < prefix_name > > -keep < count > -preserve < true/false >

e.g. “snapmirror policy add-rule –vserver vs0 –policy vault_policy –snapmirror-label monthly –schedule monthly_snap –prefix monthlySnap –keep 24”

3. For each destination volume that correlates with the SnapMirror policy, verify that Snapshot copy with specified prefix name is created at the above metioned schedule

Please note that the content of the Snapshot created will be same as the latest one (version UUID will be the same).

e.g.

cluster::*> snapshot show dst1 -fields snapmirror-label, version-uuid

vserver volume snapshot snapmirror-label version-uuid

------- ------ ------------ ------------------ -----------------

…

vs0 dst1 weekly.2017-08-27_0500 weekly a051bb54-be63-428f-aacd-37f1323cc3a2

vs0 dst1 monthlySnap.2017-09-01_1600 monthly a051bb54-be63-428f-aacd-37f1323cc3a2

For more information, please see the ONTAP 9 documentation center

ONTAP Recipes: Easily backup local NAS file services data to the cloud using SnapCenter GUI

ontap_recipes — Tue, 05 Sep 2017 19:22:19 GMT

ONTAP Recipes: Did you know you can…?

Backup local NAS file services data (SMB and NFS file shares) to the cloud using SnapCenter graphical user interface

You can back up NAS file services data to the cloud and restore it from the cloud using SnapCenter and AltaVault.

1. Log-in to SnapCenter UI and go to Settings and Policies

2. Select Backup to Cloud Policy and click on Copy

3. Edit the Save policy as and click OK

4. Modify “Backup to Cloud demo_01” policy

a. Edit Local copies

i. Hourly Schedule

ii. Daily Schedule

b. Edit Cloud copies

i. Cloud Configuration

ii. Daily Schedule

iii. Weekly Schedule

iv. Monthly Schedule

5. Go to Resources for NAS File Services

6. Search for the volume which you want to replicate to the cloud

7. Either click on the + of the volume or drag the volume and drop it to the policy created in step 4

8. Click on “Create Backup” from the Policy and monitor the Job’s progress from the Activity Panel on bottom of page

For more information, see the ONTAP 9 documentation center and refer to the Data Fabric Solution for Cloud Backup Workflow Guide Using SnapCenter

(http://docs.netapp.com/mgmt/topic/com.netapp.doc.df-cloud-bu-wg/home.html?cp=5_4)

ONTAP Recipes: Easily move a volume to a different aggregate using System Manager

ontap_recipes — Fri, 18 Aug 2017 00:43:21 GMT

ONTAP Recipes: Did you know you can…?

Easily move a volume to a different aggregate using System Manager

You can easily move a volume in System Manager by selecting a volume, starting the move, and then optionally monitoring the resulting job. When using System Manager, the volume move operation finishes automatically.

1. In OnCommand System Manager, click the SVMs tab

2. Select the SVM, and then click Manage.

3. Click the Volumes tab, select the volume that you want to move, and click Move.

4. Select the destination aggregate and click Move. System Manager displays only aggregates that have enough capacity available.

5. When a new Move Volume dialog box is displayed, leave it open if you want to monitor the volume move job.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Upgrade existing version of ONTAP while retaining Data Protection relationships

ontap_recipes — Thu, 10 Aug 2017 23:45:42 GMT

ONTAP Recipes: Did you know you can…?

Easily upgrade your existing version of ONTAP while retaining Data Protection (SnapMirror, SnapVault, Unified Replication) relationships

Before upgrading a cluster that is running a Data Protection relationship, the operation must be suspended for each node that contains destination volumes.

Please ensure that ONTAP destination version follow the criteria below:

For SnapMirror (DP relationships), the destination node must use an ONTAP version that is equal to or later than that of the SnapMirror source node.
SnapMirror, SnapVault and Unified Replications (XDP relationships) are version-flexible relationships and can support up to two releases difference (up or down) between the source and the destination nodes.

Steps:

1. Suspend all transfer operations

snapmirror quiesce*

Instead, if you want to suspend transfers on a particular destination node and only upgrade that node:

First find the relationships

snapmirror show

Next, suspend the individual transfers

snapmirror quiesce –destination-path <destination>

2. To find which of the SnapMirror relationships are not quiesced

snapmirror show -status !Quiesced

Pleas note, the relationships with ongoing transfers are not quiesced immediately. The transfer completes and then the relationship status goes to ‘Quiesced’.

However, if you need the relationships to be immediately quiesced, the transfers for those ongoing relationships can be stopped.

snapmirror abort –destination-path <destination> -h

3. Upgrade the destination node/cluster

4. Upgrade the source node/cluster

5. Resume the transfer operations

snapmirror resume*

Individual transfer can be resumed with

snapmirror resume –destination-path <destination>

6. To verify that your relationship is not suspended

snapmirror show –status Quiesced

For each SnapMirror relationship that is configured to run on a schedule, you should verify that the first scheduled SnapMirror transfer completes successfully.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily restore a MongoDB Database using MongoDB Ops Manager

ontap_recipes — Thu, 10 Aug 2017 21:16:01 GMT

ONTAP Recipes: Did you know you can…?

Easily restore a MongoDB Database using MongoDB Ops Manager

MongoDB and NetApp have worked together to integrate the MongoDB Ops Manager utility with NetApp’s AltaVault Virtual Appliance (AVA), for MongoDB backups.

Restore operations are performed entirely within the Ops Manager framework. The steps for restoring MongoDB data from an Ops Manager backup are listed below:

1. Open a browser session and enter the fully qualified URL and port number of the Ops Manager Application.

In the example URL below, “opsmgrhost.netapp.com” is the fully qualified hostname of the Ops Manager host, and “8080” is the Ops Manager port:

http://opsmgrhost.netapp.com:8080

An IP address can be used in place of the hostname.

2. Enter the required credentials on the home page.

3. Click the “Admin” link at the top of the screen.

4. Click the “Backup” tab on the left side of the screen and you’ll be directed to the “Backup” screen.

5. Select either “Sharded Cluster Status” or “Replica Set Status”. For this example, we’ll be restoring a replica set.

6. Click the name of the sharded cluster to restore.

7. Click the “RESTORE” button that corresponds to the desired snapshot (Figure 1).

Figure 1: Screen for restoring MongoDB from a backup

The “Select Restore Destination” screen will appear (Figure 2).

8. Choose the “PUSH VIA SECURE COPY” option at the top and populate the required fields.

In this example, a tar file containing the backup files will be pushed out the MongoDB primary replica server, which has an IP address of 192.168.13.201, using scp. The copy will be performed using the target server’s root user credentials, and the destination folder is “/mongodb/data”. Click on the green “FINALIZE REQUEST” button at the bottom to start the process.

Figure 2: Select Restore Destination

9. Log in to the destination server, locate the tar file and unbundle it using Linux command

tar xvf

10. Use the Linux “cd” command to move into the new directory, and verify that the owner and group are “mongod”.

If not, use the “chown -R” command to change them

11. As the root user, execute the following command to start a new MongoDB instance running under a port that is different from the original production instance:

sudo -u mongod mongod -–dbpath /mongodb/data/ntap1bkp -–directoryperdb –-port 27018

In this example, port 27018 was used. The directory containing the unbundled restore files is /mongodb/data/ntap1bkp

12. As the root user, connect to the new instance using the command:

mongo -–port 27018

13. Use the MongoDB commands “show dbs” and “show collections” to verify that the restore was successful and complete. Other queries may be used for a more rigorous check of the new instance.

14. The new instance can be promoted to production, or used for restoring individual databases or collections to the original production instance.

For more information, see the ONTAP 9 documentation center

For more information on how to retrieve a Snapshot with SCP delivery, refer to the following document:

https://docs.opsmanager.mongodb.com/v1.6/tutorial/retrieve-snapshot-scp/

ONTAP Recipes: View or modify a MongoDB Ops Manager Snapshot Schedule

ontap_recipes — Thu, 10 Aug 2017 21:16:30 GMT

ONTAP Recipes: Did you know you can…?

View or modify a MongoDB Ops Manager Snapshot Schedule

MongoDB and NetApp have worked together to integrate the MongoDB Ops Manager utility with NetApp’s AltaVault Virtual Appliance (AVA), for MongoDB backups.

This recipe explains how to change the backup frequency and retention policy for Ops Manager through the Ops Manager GUI.

The steps are listed below:

1. Open a browser session and enter the fully qualified URL and port number of the Ops Manager Application.

In the example URL below, “opsmgrhost.netapp.com” is the fully qualified hostname of the Ops Manager host, and “8080” is the Ops Manager port:

http://opsmgrhost.netapp.com:8080

An IP address can be used in place of the hostname.

2. Enter the required credentials on the home page.

3. Click the “Admin” link at the top of the screen.

4. Click the “Backup” tab on the left side of the screen and you’ll be directed to the “Backup” screen.

5. Click the “Overview” tab at the top of the screen.

6. Click on the ellipsis icon next to the desired preconfigured backup, and then select “Edit Snapshot Schedule”, as shown in Figures 1 and 2 below:

Figure 1: Navigating to the "Edit Snapshot Schedule" screen

Figure 2: Navigating to the "Edit Snapshot Schedule" screen

7. The current backup policy will be displayed on the right side of the screen, shown below in Figure 3.

Figure 3: Backup Policy screen

Figure 4: Provides a magnified view of the “Edit Snapshot (backup) Schedule”.

8. From the “Edit Snapshot Schedule” screen (Figure 4), backup frequency and retention schedules can be set or changed.

In this example:

Ops Manager backups will be created every 6 hours.
The hourly backups will be retained for 5 days.
Daily snapshots will be retained for 7 days.
The retention period for weekly and monthly backups can be configured.
The “Allow point-in-time restores going back to” setting determines the number of days that Ops Manager retains oplogs alongside snapshots. (Op logs are required for point-in-time recovery.)

9. Click the green “Submit” button shown in Figure 3 to activate the new settings

For more information, see the ONTAP 9 documentation center

For more information on how to manage Ops Manager backup policies, refer to the following document:

https://docs.opsmanager.mongodb.com/current/tutorial/edit-backup/

ONTAP Recipes: Easily identify throughput and latency between nodes

ontap_recipes — Fri, 04 Aug 2017 19:37:19 GMT

ONTAP Recipes: Did you know you can...?

Easily identify throughput and latency between nodes

You can check throughput and latency to identify network bottlenecks, or to prequalify network paths between nodes. You can check pairs of node in the same cluster or in two peered clusters.

1. Change to advanced privilege level:

set -privilege advanced

2. Measure throughput and latency between nodes:

network test-path -source-node name -destination-cluster cluster_name -destination-node name -session-type Default

Example:

cluster1::> network test-path -source-node node1 -destination-cluster cluster2 -destination-node node3 -session-type Default

Test Duration: 10.88 secs

Send Throughput: 48.23 MB/sec

Receive Throughput: 48.23 MB/sec

MB sent: 524.74

MB received: 524.74

Avg latency in ms: 301.47

Min latency in ms: 61.14

Max latency in ms: 856.86

If performance does not meet expectations for the path configuration, you should check node performance statistics, use available tools to isolate the problem in the network, check switch settings, and so forth.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily identify remaining performance capacity

ontap_recipes — Thu, 03 Aug 2017 21:45:04 GMT

ONTAP Recipes: Did you know you can…?

Easily identify remaining performance capacity

Performance capacity, or headroom, measures how much work you can place on a node or an aggregate before performance of workloads on the resource begins to be affected by latency. Knowing the available performance capacity on the cluster helps you provision and balance workloads.

1. Change to advanced privilege level:

set -privilege advanced

2. Start real-time headroom statistics collection:

statistics start –object [resource_headroom_cpu | resource_headroom_aggr]

3. Display real-time headroom statistics information:

statistics show - object [resource_headroom_cpu | resource_headroom_aggr]

For complete command syntax, see the man page.

Example:

Cluster1::*> statistics show -object resource_headroom_cpu -raw -counter ewma_hourly

Object: resource_headroom_cpu

Instance: CPU_node1

Start-time: 7/9/2017 16:06:27

End-time: 7/9/2017 16:06:27

Scope: node1

Counter Value

-------------------------------- ---------

ewma_hourly -

current_ops 4376

current_latency 37719

current_utilization 86

optimal_point_ops 2573

optimal_point_latency 3589

optimal_point_utilization 72

optimal_point_confidence_factor 1

You can compute the available performance capacity for a node by subtracting the optimal_point_utilization counter from the current_utilization counter. In this example, the utilization capacity for CPU_node1 is -14% (72%-86%), which suggests that the CPU has been overutilized on average for the past hour.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create a SnapLock volume with Volume Append mode enabled

ontap_recipes — Thu, 03 Aug 2017 18:27:50 GMT

Did you know you can…?

Easily create a SnapLock volume with Volume Append mode enabled

1. Install the SnapLock license

license add -license-code <key>

2. Initialize the compliance clock on all the nodes of the cluster

snaplock compliance-clock initialize -node <nodename>

3. Create a SnapLock aggregate of the appropriate SnapLock type

storage aggregate create -aggregate <aggrname> -diskcount <count> -snaplock-type <enterprise|compliance>

4. Create a volume on the aggregate created.

volume create -vserver <vservername> -volume <volname> -aggregate <aggrname> -size <size>

5. Once the volume is created, enable the volume append mode

volume snaplock modify -vserver <vservername> -volume <volname> -is-volume-append-mode-enabled true

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily make a file a WORM_APPEND file on a SnapLock volume via NFS

ontap_recipes — Fri, 28 Jul 2017 18:38:24 GMT

ONTAP Recipes: Did you know you can…?

Easily make a file a WORM_APPEND file on a SnapLock volume via NFS

On the NFS host on which the volume is mounted, create an empty file, change the permissions on the file to read only. This makes the file a WORM file. Now, change the permissions back to read-write. This will make the file a WORM_APPEND file.

touch <file>

chmod -w <file>

chmod +w <file> (setting the write permission to ‘group’ or ‘other’ will also work)

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily make a file into a WORM file on a SnapLock volume via NFS

ontap_recipes — Fri, 28 Jul 2017 18:32:05 GMT

ONTAP Recipes: Did you know you can…?

Easily make a file into a WORM file on a SnapLock volume via NFS

1. On the NFS host on which the volume is mounted, change the permissions on the file to read only. This makes the file a WORM file.

chmod -w <file>

2. To override the default retention period setting and set a retention period greater than the default, you can either:

Explicitly set the time of the file to the retention period required.

touch -a -t <[[CC]YY]MMDDhhmm[.ss]> <file>

Set the autocommit scan period on the volume. This ensures that any file that has not been modified for the period set, will automatically be made a WORM file.

volume snaplock modify -vserver <vservername> - volume <volumename> -autocommit-period <value>

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Easily create a SnapLock volume

ontap_recipes — Fri, 28 Jul 2017 18:16:15 GMT

Did you know you can…

Easily create a SnapLock Volume?

1. Install the SnapLock license.

license add -license-code <key>

2. Initialize the compliance clock on all the nodes of the cluster.

snaplock compliance-clock initialize -node <nodename>

3. Create a SnapLock aggregate of the appropriate SnapLock type.

storage aggregate create -aggregate <aggrname> -diskcount <count> -snaplock-type <enterprise|compliance>

4. Create a volume on the aggregate.

volume create -vserver <vservername> -volume <volname> -aggregate <aggrname> -size <size>

For more information, please see the ONTAP 9 documentation center.

ONTAP Recipes: Attach StorageGRID Webscale as a FabricPool external capacity tier

ontap_recipes — Thu, 20 Jul 2017 19:56:36 GMT

ONTAP Recipes: Did you know you can…?

Attach StorageGRID Webscale as a FabricPool external capacity tier

Storing data in tiers can enhance the efficiency of your storage system. You manage storage tiers by using FabricPool. It stores data in a tier based on whether the data is frequently accessed. FabricPool automatic storage tiering was added in ONTAP 9.2. You can attach NetApp StorageGRID as the capacity tier. Infrequently accessed ("cold") data is stored in the capacity tier. A FabricPool license is not required when using StorageGRID as the capacity tier.

1. Open System Manager and select the Storage Tiers.

2. Click Add External Capacity Tier.

3. Select StorageGRID and enter the requested information. Be sure the Server Name matches the CA certificate used by Storage Grid. You might need to replace the certificate for StorageGRID with a new one that matches the hostname.

4. Click Save and Attach Aggregates.

5. Select one or more eligible aggregates. Aggregates must be SSD-only, and all volumes must be thin provisioned (volume guarantee set to none).

6. Click View and Update Tiering Policy for Volumes.

7. Update policies if needed, and then click Save.

For more information, please see the ONTAP9 documentation center.

ONTAP Recipes: Attach Amazon S3 as a FabricPool external capacity tier

ontap_recipes — Thu, 20 Jul 2017 19:47:19 GMT

ONTAP Recipes: Did you know you can…?

Attach Amazon S3 as a FabricPool external capacity tier

Storing data in tiers can enhance the efficiency of your storage system. You manage storage tiers by using FabricPool. It stores data in a tier based on whether the data is frequently accessed. FabricPool automatic storage tiering was added in ONTAP 9.2. You can attach Amazon S3 or NetApp StorageGrid as the capacity tier. Infrequently accessed ("cold") data is stored in the capacity tier.

Install FabricPool license if not already installed.
Open System Manager and select the Storage Tiers
Click Actions > Attach External Capacity Tier.
Select Amazon S3 and enter the requested information. Enter the S3 bucket name in the Container Name field.
Click Save and Attach Aggregates.
Select one or more eligible aggregates. Aggregates must be SSD-only, and must be thin provisioned (volume guarantee set to none).
Click View and Update Tiering Policy for Volumes.
Update policies if needed, and then click Save.

For more information, please see the ONTAP9 documentation center

ONTAP Recipes: Use QoS floors to prioritize business critical NAS applications

ontap_recipes — Wed, 13 Dec 2017 19:51:13 GMT

Did you know you can....

Use QoS to prioritize business critical applications?

This recipe describes how to use the QoS Floor feature to guarantee a Business Critical Application gets its required service of 40,000 IOPS regardless of interference coming from the Test and Dev Applications.

1. In System Manager, select the Business Critical Volume followed by Actions, Storage QoS

2. Set the Minimum Throughput to 40,000IOPS

Check the performance dashboard to verify that the service level guarantee of 40,000 IOPS is met and latency is reduced.

Note that the test and dev workloads may see impacts meaning fewer IOPS and higher latencies.

For more information, visit the ONTAP 9 Documentation Center.

ONTAP Recipe: Configuring NFS Connector with Apache Tez in HDInsight

ontap_recipes — Wed, 13 Dec 2017 17:23:22 GMT

Did you know you can...

Configure NFS Connector with Apache Tez in HDInsight

This recipe describes how to configure Apache Tez with the Netapp NFS Connector. This guide is specific to HDInsight clusters in Microsoft Azure. The steps in this guide can be generalized to any Hadoop cluster running Tez.

This recipe is specific to HDInsight clusters in Microsoft Azure. The stepscan be generalized to any Hadoop cluster running Tez.

1. Configure the user “hive” and the group “hadoop” across all workers in your Hadoop cluster.

sudo /netappnfs/usergroup.py -u hive -g hadoop -t /netappnfs

2. Copy the Netapp NFS Connector jar files to the fs.defaultFS as configured in Ambari.

hdfs dfs -mkdir /{path to desired location}/aux-jars

hdfs dfs -copyFromLocal /netappnfs/hadoop-nfs-2.7.1.jar /{path to desired location}/aux-jars

hdfs dfs -copyFromLocal /netappnfs/hadoop-nfs-connector-2.0.0.jar /{path to desired location}/aux-jars

3. Add the new auxiliary jar location to the tez-site.conf file (reference).

4. Add the auxiliary jar path using Ambari:

5. Manually edit tez-site.conf, adding the following lines:

<tez.aux.uris>

/{path to desired location}/aux-jars

</tez.aux.uris>

6.Restart the Tez, Hive, Oozie, etc. services

ONTAP Recipe: Configuring Oracle ASM with multiple LUNs per Disk Group

ontap_recipes — Wed, 13 Dec 2017 17:04:28 GMT

Did you know you can...

Configure Oracle ASM with multiple LUNs oer disk group?

Oracle ASM allows for disk groups to be created which span multiple disks or LUN’s. ONTAP LUN’s will appear as Disk Paths in the ASM Configuration Assistant. Multiple LUN’s can be assigned to ASM Disk Groups to improve performance when using ONTAP 9.3.

This recipe describes how to assign multiple LUN’s to an ASM Disk Group:

1. Using the ASM Configuration Assistant, click on the Disk Groups tab.

2. From the Disk Groups tab, select “Create” to launch the “Create Disk Group” window.

3. In the “Create Disk Group” window, enter a name for the new Disk Group in the Disk Group Name field. In our case, we assigned 32 LUN’s to the Disk Group named ORA_DATA.

4. In the “Redundancy” pane, select desired Oracle Redundancy. In this case, we selected External (None) as extra redundancy was not needed for this database.

5. in the “Select Member Disks” pane, check the box for each disk path you wish to use. (The Disk Paths displayed are your previously defined LUN’s visible from your Oracle host.)

6. Click on the “Advanced” button at the bottom of the “Create Disk Group” window to display the “Disk Group Attributes”.

7. In the “Disk Group Attributes” pane, select 64 as the “Allocation Unit Size (MB)”.

8. Click “OK” to create the Disk Group. A window will pop up with the message “Disk Group created successfully.” Click “OK”.

See related Recipe to create an Oracle RAC Application on SAN:

https://community.netapp.com/t5/Data-ONTAP-Discussions/ONTAP-Recipes-Easily-create-an-Oracle-RAC-Application-on-SAN/m-p/132293

ONTAP Recipes: Easily create a NAS Application Container

ontap_recipes — Wed, 13 Dec 2017 16:52:28 GMT

‎

ONTAP Recipes: Did you know you can…?

Easily create a NAS Application Container

To create a NAS Application Container for use over NFS without compromising application or overall system performance, follow these steps in OnCommand System Manager:

1. Select the SVM.

2. Click Applications & Tiers.

3. Click Applications.

4. Click Add an Application.

5. In the “General Applications” Add NAS Container page, specify the following:

application name
size
storage service level

The floor and ceiling IOPS values adjust automatically based on space capacity used by the application.For a 1TB application with “Value” specified, the floor and ceiling start at 128 IOPS. As more space is used by the application the ceiling increases to a maximum of 512 IOPS.

6. Select NFS as the protocol used to access the application.

7. Set the host IP addresses that will access the application.

After creation, details of the application components will be displayed in the System Manager summary.

For more information, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Use FlexGroup QoS ceilings to limit the impacts of test workloads

ontap_recipes — Wed, 13 Dec 2017 16:33:25 GMT

Did you know you can…?

Use FlexGroup QoS ceilings to limit the impacts of test workloads

This recipe will show how to Use ONTAP QoS ceilings to limit the test workload both in IOPS and throughput in ONTAP 9.3.

1. Create a QoS policy with a ceiling of 500IOPS and 2 megabytes/sec (4K block size).

::> qos policy-group create -policy-group test_policy -max-throughput 500IOPS,2MB

2. Assign the test FlexGroup to the QoS policy

::> volume modify -volume test_flexgroup -qos-policy-group test_policy

[Job 40] Job succeeded: volume modify succeeded

3. Check OnCommand System Manager to verify the test FlexGroup is limited by QoS and is not impacting the production workload.

For more information, visit the ONTAP 9 Documentation Center.

ONTAP Recipes: Easily enable SAML Authentication for OCSM in ONTAP 9.3

ontap_recipes — Wed, 06 Dec 2017 23:22:38 GMT

ONTAP Recipes: Did you know you can…?

Easily enable SAML Authentication for OCSM in ONTAP 9.3

Security Assertion Markup Language (SAML) 2.0 is a widely adopted industry standard that allows any third-party SAML-compliant identity provider (IdP) to perform Multifactor authentication (MFA) using mechanisms unique to the IdP of the enterprise’s choosing and as a source of single sign-on (SSO).

There are three roles defined in the SAML specification:

The Principal
The IdP
The Service Provider (SP)

In the ONTAP 9.3 implementation, a principal is the cluster administrator gaining access to ONTAP through OnCommand System Manager (OCSM) or OnCommand Unified Manager (OCUM). The IdP is third-party IdP software from an organization such as Microsoft Active Directory Federated Services (ADFS) or the open-source Shibboleth IdP. The SP is the SAML capability built into ONTAP that is used by OCSM or the OCUM web application.

Steps to enable SAML Authentication for OCSM in ONTAP 9.3:

Open System Manager using the cluster management interface (DNS name or IP address). https://cluster-mgmt-LIF

2. Authenticate using administrator credentials.

Click Configuration > Authentication

3. Select the Enable SAML Authentication checkbox.

4. Configure System Manager to use IdP authentication:

Enter the URI of the IdP.
Enter the DNS name or IP address of the host system.
Optional: If required, change the host system certificate to a CA-signed certificate.

5. Click Retrieve Host Metadata to retrieve the host URI and host metadata information.

6. Copy the host URI or host metadata details.

7. Click Save

8. Click Save and Confirm. Ensure that you have copied the host URI or metadata to the IdP and done the trust configuration on the IdP server. (Refer to your IdP documentation.)

The IdP login window is displayed.

9. Log in to System Manager by using the IdP login window. (You might see a prompt from the IdP stating that you are about to share specific attributes with the ONTAP cluster. You must allow sharing to occur for successful login.)

After the SAML IdP authentication succeeds, the session has a lifetime configured in the IdP. For other service providers (SPs) that use the same IdP, this allows the authentication to exist within the session lifetime period. If OCUM is one of the SPs that uses the same IdP, access to OCUM is allowed without an additional authentication. Thus, single sign-on (SSO) is enabled.

Steps to enable SAML Authentication for OCUM 7.3:

Ensure that you have network connectivity between OCUM, the IdP, and OCUM web clients.

2. Launch the OCUM web GUI.

3. Authenticate using maintenance user credentials.

4. In the upper-right toolbar, click the gear icon and select Authentication in the left Setup menu.

5. If you haven’t enabled remote authentication, you must do so for SAML IdP users to have access to OCUM:

Select the Enable Remote Authentication checkbox.
Set the authentication service to Active Directory or OpenLDAP (Microsoft Lightweight Directory Services is not supported).
Enter the administrator name and password. For AD, specify Base Distinguished Name; for LDAP, specify Bind Distinguished Name, Bind Password, and Base Distinguished Name.
In the Authentication Servers section, enter the authentication server’s DNS name or IP address.
Use Test Authentication to ensure that Remote Authentication Settings are operational.
Navigate to the Settings > Management > Users Page and add users of type remote user or remote group with the OnCommand administrator role.

6. Navigate to Settings > Setup > Authentication > SAML Authentication Page.

7. Click View Host Metadata, copy the metadata into a file, and save it. This file will be used to configure OCUM in the IdP.

8. Select the Enable SAML Authentication checkbox, enter the IdP URL, and click Fetch IdP Metadata to populate OCUM with the IdP data.

9.Click Save and Yes in the warning dialog box.

10. Wait 5 minutes for the OCUM services to restart.

11. Configure the IdP (refer to your IdP documentation).

Populate the IdP with the OCUM metadata from step 7.
Add OCUM as a Relying Party.
Add claim rules. Set Name to urn:oid:0.9.2342.19200300.100.1.1 and Unqualified Name to urn:oid:1.3.6.1.4.1.5923.1.5.1.1.

12. Launch the OCUM web GUI and get redirected to the IdP for authentication

13. Authenticate using a remote user defined in step 5 above

As in the OCSM section, after the SAML IdP authentication succeeds, the session has a lifetime configured in the IdP. For other SPs that use the same IdP, this allows the authentication to exist within the session lifetime period. If OCSM is one of the SPs that uses the same IdP, access to OCSM is allowed without an additional authentication after a successful OCUM authentication

For more information, see the ONTAP 9 documentation center and the OCUM 7.3 documentation.

ONTAP Recipes: Easily Protect your FlexGroup volume in ONTAP 9.3

ontap_recipes — Wed, 06 Dec 2017 02:22:39 GMT

ONTAP Recipes: Did you know you can…?

Easily Protect your FlexGroup volume in ONTAP 9.3

This recipe will show how to create a SnapMirror (or SnapVault/MirrorVault) relationship for FlexGroup volumes in ONTAP 9.3.

1. Open OnCommand System Manager. See if the volume is unprotected under “Volumes.” The volume we’re protecting is Tech_ONTAP (the Tech ONTAP podcast volume)

Clicking on the + sign will show more details.

2. Click on “Configuration” in the left menu, then on “SVM Peers” (for local snapmirrors) or “Cluster Peers” (for remote snapmirrors) if you haven’t already peered the source and destination. In this example, we’re peering SVMs to do a local SnapMirror.

3. Peer the SVM or cluster.

SVM Peering
Click “Create” and choose your SVMs. Click “Initiate SVM peering.” Within a few seconds, you should see “SVM peering successful.” Click done.

Cluster Peering
Cluster peering is needed if you plan on implementing an intercluster snapmirror. In OnCommand System Manager for ONTAP 9.3, this is done with “Cluster Peers.” Doing this also allows you to peer SVMs in the same configuration steps.

4. Next, click on “Protection -> relationships” on the left menu. Then click “Create.”

From here, go to the CLI – System Manager doesn’t currently support creating SnapMirror relationships for FlexGroup volumes. Create the destination volume. It must:

- Be type DP
- Have the same number of member volumes as the source FlexGroup
- Be the same size or greater than the source FlexGroup

The Tech_ONTAP FlexGroup has 8 member volumes and is 10TB in size.

This is the destination volume created. The destination volume must match the source volume’s member volume count and must be as large or larger than the source. Otherwise, a “geometry” error will be seen:

The FlexGroup spans a single aggregate and uses a multiplier of 8 to create 8 member volumes per aggregate. So, in this case, it’s a FlexGroup with 8 member volumes.

5. Decide on a snapmirror policy. You can apply a variety of policies to the mirror. For a DR SnapMirror, use “MirrorAllSnapshots.” If not specified, this is the default.

SnapVault/MirrorVault would use MirrorAndVault.

These are the specific policies and what they do:

6. Create the SnapMirror relationship.

7. Now, initialize the snapmirror. This will take some time, which will depend on the amount of data to transfer and the speed of your connection.

While you can’t currently manage a FlexGroup SnapMirror from System Manager, you can view it:

8. To make the mirror a SnapVault relationship (keeping more snapshots than just the ones on the source), modify the relationship policy to MirrorAndVault.

9. Consider also using a snapshot policy and label for your volume.

Note: Labels cannot be used with the async-mirror policy type.

The policy rules support only two combinations of these labels, either just “sm_created” or both “sm_created” and “all_source_snapshots”. The label is used to define the set of Snapshot copies that you want backed up to the version-flexible SnapMirror secondary volume. Other Snapshot copies on the primary volume are ignored by the version-flexible SnapMirror relationship.

Then, modify the volume to use the new policy:

10. Create a schedule to apply to the SnapMirror relationship using “job schedule create” and then apply it to your snapmirror.

Once a volume is successfully SnapMirrored, System Manager will show it is protected:

If using SnapMirror restore, keep in mind that the entire FlexGroup volume will get restored, not just files or single member volumes.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Inplace Conversion of an existing plain text volume to Encrypted

ontap_recipes — Thu, 30 Nov 2017 22:28:29 GMT

ONTAP Recipes: Did you know you can…?

Easily convert (Inplace) a plaintext volume to encrypted in ONTAP 9.3

1) If the cluster is configured with Onboard/External Key-manager and VE is licensed , then use the below commands to convert an existing plaintext volume to encrypted

>>volume encryption conversion start –volume <> -vserver <>

This will start encryption scan on the volume and converts all existing data to encrypted form.

New incoming data will be written in encrypted form also .

2) You can check the status of the conversion using

>>volume encryption conversion status –volume <> -vserver <>

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily Create a NAS Application Container in ONTAP 9.3

ontap_recipes — Tue, 21 Nov 2017 06:02:14 GMT

ONTAP Recipes: Did you know you can…?

Easily Create a NAS Application Container in ONTAP 9.3

To create a NAS Application Container for use over NFS without compromising application or overall system performance, follow these steps in OnCommand System Manager:

1. Select the SVM

2. Click Applications & Tiers

3. Click Applications

4. Click Add an Application

5. In the “General Applications” Add NAS Container page, specify the following:

The Application Name
The size
The storage service level

6. In ONTAP 9.3 with Adaptive QoS, the floor and ceiling IOPS values adjust automatically based on space capacity used by the application.

There are 3 default Adaptive QoS policies in ONTAP (Extreme, Performance, Value) along with the ability to create custom policies.

::> qos adaptive-policy-group show

Expected Peak

Name Vserver Wklds IOPS IOPS

---- ------- ----- -------------- ---------

extreme cluster 0 6144IOPS/TB 12288IOPS/TB

performance cluster 0 2048IOPS/TB 4096IOPS/TB

value cluster 0 128IOPS/TB 512IOPS/TB

E.g: For a 1TB application with “Value” specified, the floor and ceiling start at 128 IOPS. As more space is used by the application the ceiling increases to a maximum of 512 IOPS.

7. Select NFS as the protocol used to access the application

8. Set the host IP addresses that will access the application

After creation, details of the application components will be displayed in the System Manager summary

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily configure Cluster and SVM peering in ONTAP 9.3

ontap_recipes — Wed, 15 Nov 2017 14:21:06 GMT

ONTAP Recipes: Did you know you can…?

Easily configure cluster and SVM peering in ONTAP 9.3

In ONTAP 9.3, you can use the generate passphrase feature to create a peer relationship with a cluster whose intercluster LIF IP addresses you don't know in advance. You can also “pre-authorize” peer relationships for multiple SVMs on the destination cluster.

This recipe highlights the steps below:

On the data protection destination cluster, create a cluster peer relationship with an unspecified remote cluster, and pre-authorize SVM peer relationships with the SVM “vs1” on the destination cluster:

cluster02::> cluster peer create -generate-passphrase -offer-expiration 2days -initial-allowed-vserver-peers vs1

Passphrase: UCa+6lRVICXeL/gq1WrK7ShR

Expiration Time: 6/7/2017 08:16:10 EST

Initial Allowed Vserver Peers: vs1

Intercluster LIF IP: 192.140.112.101

Peer Cluster Name: Clus_7ShR (temporary generated)

2. Send the generated passphrase in a secure email to the administrator of the data protection source cluster.

3. On the data protection source cluster, use the generated passphrase to authenticate the source cluster to the destination cluster (make sure to authenticate the cluster before the passphrase expires):

cluster01::> cluster peer create -peer-addrs 192.140.112.101

Enter the passphrase:

Confirm the passphrase:

4. On the data protection source cluster, create a peer relationship between the local SVM “pvs1” and the pre-authorized SVM “vs1” on the data protection destination cluster:

cluster01::> vserver peer create -vserver pvs1 -peer-vserver vs1

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily use QoS Max to prevent a FlexGroup from becoming a bully object

ontap_recipes — Wed, 15 Nov 2017 13:51:28 GMT

ONTAP Recipes: Did you know you can…?

Easily use QoS Max to prevent a FlexGroup from becoming a bully object

Problem: There is no throttle/mechanism to prevent a FlexGroup from consuming more resource than needed and eventually become a bully.

Let’s consider the scenario of a Production and Test workloads for this recipe and see how we are trying to avoid the Test workload from becoming a bully.

Solution:

Use ONTAP QoS Max/Ceilings to limit the test workloads in both IOPS and throughput. By limiting the test workloads, the production workloads will get their required performance met. QoS Max/ceilings for FlexGroup is a new feature in ONTAP 9.3.

It is available using the command line interface (CLI) and application programming interface (API). QoS Max/Ceilings for FlexGroups supports both NFS and CIFS protocols.

Problem Example:

Figure 1 shows an ONTAP cluster with a FlexGroup provisioned for production applications and a second FlexGroup provisioned for test applications. Without QoS, the test workloads are interfering with production workloads resulting in slow application response time.

Figure 1: FlexGroup used for Production Applications is not meeting its required service level due to interference from Test workloads

Solution Example:

Use ONTAP QoS ceilings to limit the test workload both in IOPS and throughput.

Using ONTAP command line interface (CLI):

1. Create a QoS policy with a ceiling of 500IOPS and 2 megabytes/sec (4K block size).

::> qos policy-group create -policy-group test_policy -max-throughput 500IOPS,2MB

2.Assign the test FlexGroup to the QoS policy

::> volume modify -volume test_flexgroup -qos-policy-group test_policy

[Job 40] Job succeeded: volume modify succeeded

Using OnCommand System Manager:

1. Verify the test FlexGroup is limited by QoS and is not impacting the production workload.

2. Both the test and production FlexGroup have a load of 2000IOPS with a block size of 4K

3. The test workload is QoS limited to 500IOPS and 2MB throughput. Since the offered load to the test FlexGroup is 2000IOPS there is QoS induced latency of ~30 milliseconds.

The production workload is not QoS limited and is able to serve 2000IOPS with no QoS induced latency.

Figure 2: Use System Manager to verify the production workload is no longer impacted

Figure 3: Use System Manager to verify the test workload is QoS limited

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily assign a volume to an Adaptive QoS Policy

ontap_recipes — Wed, 13 Dec 2017 19:10:16 GMT

ONTAP Recipes: Did you know you can…?

Easily assign a volume to an Adaptive QoS Policy in ONTAP 9.3

Adaptive QoS is available using the following:

ONTAP CLI (steps shown below)
System Manager Application Provisioning
ONTAP API
ONTAP SDK

To assign a volume to an Adaptive QoS Policy, follow these steps in the ONTAP command line interface (CLI):

1. During volume create, assign an Adaptive QoS policy:

volume create -volume vol1 -size 1TB -aggregate data_aggr -qos-adaptive-policy-group extreme

2. For existing volumes, you can modify or assign an Adaptive QoS policy:

volume modify -volume vol1 -qos-adaptive-policy-group performance

3. There are 3 default Adaptive QoS policies in ONTAP along with the ability to create custom policies:

::> qos adaptive-policy-group show

Expected Peak

Name Vserver Wklds IOPS IOPS

---- ------- ----- -------- ----

extreme cluster 0 6144 IOPS/TB 12288 IOPS/TB

performance cluster 0 2048 IOPS/TB 4096 IOPS/TB

value cluster 0 128 IOPS/TB 512 IOPS/TB

When a volume is assigned to an Adaptive QoS policy, the IOPS allocated to the volume is set based on the volume size and the amount of space used in the volume.

For a 1TB volume assigned to the “performance” policy, the floor and ceiling start at 2048 IOPS. As more space is used in the volume the ceiling increases automatically to a maximum of 4096 IOPS.

For a small volume, a fixed “absolute minimum” number of IOPS will be allocated. For example, with a 20GB volume assigned to the “performance” policy, the floor and ceiling will be set to 500IOPS.

The fixed IOPS allocation is as follows for the 3 default Adaptive QoS policies.

Extreme –1000 IOPS
Performance – 500 IOPS
Value – 75 IOPS

Note: Adaptive QoS is applicable to both AFF & FAS platforms. However, QoS min is not enforced on Non-AFF platforms.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily rekey an encrypted volume in ONTAP 9.3

ontap_recipes — Thu, 09 Nov 2017 20:03:39 GMT

ONTAP Recipes: Did you know you can…?

Easily rekey an encrypted volume in ONTAP 9.3

In ONTAP 9.3, you can rekey an encrypted volume in place.

1. Rekey an encrypted volume:

cluster1::> volume encryption rekey -vserver vs1 -volume vol1

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily configure KMIP servers for NetApp volume encryption in ONTAP 9.3

ontap_recipes — Thu, 09 Nov 2017 19:34:39 GMT

ONTAP Recipes: Did you know you can…?

Easily configure KMIP servers for NetApp volume encryption in ONTAP 9.3

In ONTAP 9.3, you can configure KMIP servers for NetApp Volume Encryption.

1. If you are upgrading to ONTAP 9.3 from a previous version, delete any external key management configurations for the cluster:

cluster1::> security key-manager delete-kmip-config

2. Configure key manager connectivity for cluster nodes:

cluster1::> security key-manager setup

3. Enter the appropriate responses in the wizard.

4. Add a KMIP server at the IP address 20.1.1.1:

security key-manager add -address 20.1.1.1

5. Add another KMIP server for redundancy:

security key-manager add -address 20.1.1.2

For more information see the ONTAP 9 doc center

ONTAP Recipes: Easily configure SSH Multifactor authentication for administrator accounts (MFA)

ontap_recipes — Thu, 09 Nov 2017 19:23:11 GMT

ONTAP Recipes: Did you know you can…?

Easily configure SSH multifactor authentication for administrator accounts (MFA) in ONTAP 9.3

In ONTAP 9.3, you can require that administrators log in to an admin or data SVM with both an SSH public key and a user password.

Enable SSH MFA for a local user account:

cluster-1::> security login create -vserver engData1 -user-or-group-name admin2 -application ssh -authentication-method publickey -role admin -secondauthentication-method password

Please enter a password for user 'admin2':

Please enter it again:

Warning: To use public-key authentication, you must create a public key for user "admin2"

2. Create a public key for the administrator:

cluster1::>security login publickey create -vserver engData1 -username admin2 -index 5

-publickey “ssh-rsa AAB3NzaC1yc2EAAAABIwAAAIEAspH64CYbUsDQCdW22JnK6J/vU9upn

Kzd2zAk9C1f7YaWRUAFNs2Qe5lUmQ3ldi8AD0Vfbr5T6HZPCixNAIzaFciDy7hgnmdj9eNGed

Gr/JNrftQbLD1hZybX+72DpQB0tYWBhe6eDJ1oPLobZBGfMlPXh8VjeU44i7W4+s0hG0E=tsmith

@publickey.example.com"

For more details on SSH MFA authentication, see “Enabling SSH Multifactor Authentication” in the Administrator Authentication and RBAC Power Guide

ONTAP Recipes: Easily backup Resource Groups using SnapCenter

ontap_recipes — Mon, 30 Oct 2017 21:02:19 GMT

ONTAP Recipes: Did you know you can…?

Easily backup Resource Groups using SnapCenter

If a resource group has a policy attached and a schedule configured, then backups occur automatically according to the schedule.

This recipe highlights the quick steps on how to backup resource groups on demand.

In the vCenter GUI, click "home" in the toolbar, and then select SnapCenter Plug-in for VMware from the drop-down list.

2. In the left Navigator pane, click Resource Groups.

3. In the Objects tab of the Resource Groups page, select the resource group you want to back up, and then click -> (Run Now , highlighted below) in the toolbar.

4. If the resource group has multiple policies configured, then in the Backup Now dialog box, select from the drop-down list the policy you want to use for this backup operation, and then click Yes.

5. Click OK to start the backup.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create a VM/Datastore Resource Group using SnapCenter

ontap_recipes — Mon, 30 Oct 2017 18:31:21 GMT

ONTAP Recipes: Did you know you can…?

Easily create a VM/Datastore Resource Group using SnapCenter

Before you begin: You must have at least one backup policy created before you can create a resource group.

1. Log in to VMware vSphere Web Client and click on SnapCenter Plug-in for VMware vSphere on the VMware vSphere Web Client Home screen.

2. Click on Resource Groups from the NetApp section of the navigation pane on the left hand side.

3. Click on the + icon on the resource groups page to create a new resource group.

4. Select the vCenter (in case of linked mode) from the drop down, provide a name, description and email notifications if required.

5. On the Resources page, in the Available Entities list, select the resources you want in the resource group, then click > to move your selections to the Selected Resources list.

Note: Make sure you have added the Storage Systems before you create a resource group and they are running clustered Data ONTAP 8.2.2 or later.

You can also create a resource group with one resource by clicking Home -> VMs and Templates then right-click a VM or datastore, select NetApp SnapCenter from the drop-down list, and then select Create Resource Group from the secondary drop-down list.

6. On the Spanning Diskspage, select an option:

Always exclude all spanning datastores [This is the default for datastores.]
Always include all spanning datastores [This is the default for VMs.]
Manually select the spanning datastores to be included

7. On the Policies page, select one or more policies from the list

8. On the Schedules page, configure the backup schedule for each selected policy.

9. Review the summary, and then click Finish.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily restore individual files by attaching a virtual disk from primary backup

ontap_recipes — Mon, 23 Oct 2017 18:30:43 GMT

ONTAP Recipes: Did you know you can…?

Easily restore individual files by attaching a virtual disk from primary backup using SnapCenter

You can attach one or more virtual disks from a primary backup to the parent VM (the same VM that the virtual disk was originally associated with and not a different VM). This makes it easier to restore one or more individual files from a drive instead of restoring the entire drive. You can detach the virtual disk after you have restored the files you need.

1. In the vCenter GUI, click "home icon" in the toolbar, and then select VMs and Templates from the drop-down list.

2. In the left navigation pane, right-click the VM, then select NetApp SnapCenter in the drop-down list, and then select Attach virtual disk in the secondary drop-down list.

3. On the Attach Virtual Disk pane, in the Backup section, select a backup.

You can filter the backup list by clicking "filter icon" and selecting a date and time range, or if you want backups that contain VMware snapshots, or if you want mounted back ups and selecting the location. Click OK.

4. On the Attach Virtual Disk pane, in the Selected Disks section, select one or more disks you want to attach and then click Attach.

5. Verify that the virtual disk is attached by performing the following:

a. Click " home icon" in the toolbar, and then select VMs and Templates from the drop-down list.

b. In the left Navigator pane, right-click a VM, then select Edit settings in the drop-down list.

c. In the Edit Settings box, click Manage other disks and then expand the list for each hard disk to see the list of disk files.

6. The Edit Settings page lists the disks on the VM. You can expand the details for each hard disk to see the list of attached virtual disks.

You can access the attached disks from the host operating system and then retrieve the needed information from the disks.

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily restore and get full recovery of tablespaces in Oracle DB using SnapCenter

ontap_recipes — Mon, 23 Oct 2017 18:02:24 GMT

ONTAP Recipes: Did you know you can…?

Easily restore and get full recovery of tablespaces in Oracle Database using SnapCenter

Login to SnapCenter server and click on the “Resources” tab as shown below, navigate, and select Oracle DB to be restored once you are in Resources Tab.

2. After selecting the database, navigate to Database Topology view as shown below, and select a data backup and click on the restore icon:

3. After clicking on the restore icon, Restore wizard will be launched (below). Select the list of tablespaces to be restored, search the required tablespace name and select from the drop-down menu as shown below and click on the Next button:

4. Select “All the logs” option in the next screen:

5. Proceed with all the default options till the summary page and start the restore and recovery operation with the finish button:

6. Monitor page will display the status of the Restore job as shown below:

For more information, see the ONTAP 9 documentation center

ONTAP Recipes: Easily create OnDemand Backup of SQL DB or Instance using SnapCenter SQL Plugin

ontap_recipes — Fri, 13 Oct 2017 23:00:25 GMT

ONTAP Recipes: Did you know you can…?

Easily create OnDemand Backup of SQL DB or Instance using SnapCenter SQL Plugin

2. Click on “Resources” link from left pane on the dashboard and select “Microsoft SQL Server” plugin from the plugin drop down as shown below.

3. Click on the “New Resource Group” button on the right side as shown below:

4. Enter the resource group name and click on the next button

5. Select Resource Type for protecting the SQL resources. For protecting the databases at instance level select “Instances” from dropdown; otherwise select “Database” for protecting specific databases as shown below:

6. Select Databases as “Resource Type” and select desired databases from left pane to be protected and click on the ”>>” as shown below. Click on the Next button.

7. Now, select an existing protection policy(FullAndLogBackupPolicyOnDemand) to be applied for this resource group form the dropdown as shown below and click on next button:

8. Continue to the next screen by skipping the verification settings page by clicking on the next button:

9. Update the E-mail notification settings (if any changes required) and click on next button:

10. Click on “Finish” button on the Summary page to complete the Resource Group Creation wizard:

11. After clicking on the Finish button, the wizard will disappear and Resource group will be created and you will land on “Resource Group” (RG) details page. Click on “Backup Now” button as shown below:

12. Backup dialog will popup, click on the “Backup” button as show below:

13. On demand backup will get triggered and to know the status of the job, click on the Monitor tab as shown below:

14. The Backup job status will be displayed on the Monitor view as shown below:

For more information, see the ONTAP 9 documentation center

ONTAP Recipes topics

ONTAP Recipes: Test SVM-DR destination disaster recovery without breaking SnapMirror relationship

ONTAP Recipes: Easily Convert a Synchronous SnapMirror Relationship to Asynchronous

ONTAP Recipes: Easily Convert a SnapMirror Relationship to Zero Recovery Point Objective

ONTAP Recipes: SnapMirror Synchronous (SM-S): Calculate your RTT for SnapMirror Synchronous

ONTAP Recipes: Use MetroCluster switchback functionality after a switchover operation

ONTAP Recipes: Use MetroCluster switchover functionality for synchronous replication

ONTAP Recipes: Run ONTAP consolidated system diagnostic command

ONTAP Recipes: Start the object store profiler through ONTAP CLI to test latency and throughput

Did you know that…You can start the object store profiler through the ONTAP CLI to test latency and throughput performance?

ONTAP Recipes: Use inactive data reporting on non-FabricPool aggregates

Did you know…

You can use inactive data reporting on non-FabricPool aggregates?

ONTAP Recipes: Create a FabricPool aggregate by using OnCommand System Manager

Did you know…

You can create a FabricPool aggregate by using OnCommand System Manager?

ONTAP Recipes: Set FabricPool volume tiering policies by using OnCommand System Manager

Did you know that…

You can set FabricPool volume tiering policies by using OnCommand System Manager?

ONTAP Recipes: Create a nonshared QoS policy

ONTAP Recipes: Assign a LUN or file to an adaptive QoS policy

ONTAP Recipes: Capture First Failure Data using NetApp AutoSupport On Demand Performance Archive

ONTAP Recipes: Provision ONTAP AFF Storage for MongoDB Using Workflow Automation for MongoDB

ONTAP Recipes: Identify Top Files and Clients

ONTAP Recipes: Secure data at rest using software encryption and the onboard key manager

ONTAP Recipes: Easily update your existing version of ONTAP

ONTAP Recipes: Use ONTAP Storage Efficiency features to get maximum storage efficiency for AFF

ONTAP Recipes: Manage storage efficiency policies in ONTAP

ONTAP Recipes: Configuring an external FTP host to serve data from an ONTAP system

ONTAP Recipes: Deploy MongoDB replica sets that retain storage efficiency

ONTAP recipes: Easily create storage pools

ONTAP Recipes: Easily create a cluster management interface

ONTAP Recipes: Easily provision storage by creating an aggregate

ONTAP Recipes: Easily activate or deactivate quotas

ONTAP Recipes: Easily create an Oracle RAC Application on SAN

ONTAP Recipes: Easily create an Oracle RAC Application on NFS

ONTAP Recipes: Easily create a VSI application on SAN

ONTAP Recipes: Easily create a VSI application on NFS

ONTAP Recipes: Correlate EMS Messages and Performance Metrics with NetApp OATS

ONTAP Recipes: Easily Create an Oracle Application on SAN

ONTAP Recipes: Easily Create an Oracle Application on NFS

ONTAP Recipes: Send ONTAP EMS messages to your syslog server

ONTAP Recipes: Send ONTAP EMS messages to your syslog server

ONTAP Recipes: Deploy a MongoDB test/dev environment on DP Secondary

ONTAP Recipes: Prioritize business critical applications using QoS Min

ONTAP Recipes: Easily create a Clone from SQL Database using SnapCenter

ONTAP Recipes: Easily create a Data Lake using ONTAP Storage

ONTAP Recipes: Easily create a Policy for ONTAP to ONTAP to CLOUD topology using SnapCenter

ONTAP Recipes: Easily manage NetApp Storage with your corporate Active Directory (AD) login

ONTAP Recipes: Easily manage NetApp Storage with your corporate (NIS or LDAP) login credentials

ONTAP Recipes: Easily add 6 SSDs to a 8-SSD AFF-A200 HA-Pair

ONTAP Recipes: Easily create Snapshot copies on the Secondary (destination) volumes

ONTAP Recipes: Easily backup local NAS file services data to the cloud using SnapCenter GUI

ONTAP Recipes: Easily move a volume to a different aggregate using System Manager

ONTAP Recipes: Upgrade existing version of ONTAP while retaining Data Protection relationships

ONTAP Recipes: Easily restore a MongoDB Database using MongoDB Ops Manager

ONTAP Recipes: View or modify a MongoDB Ops Manager Snapshot Schedule

ONTAP Recipes: Easily identify throughput and latency between nodes

ONTAP Recipes: Easily identify remaining performance capacity

ONTAP Recipes: Easily create a SnapLock volume with Volume Append mode enabled

ONTAP Recipes: Easily make a file a WORM_APPEND file on a SnapLock volume via NFS

ONTAP Recipes: Easily make a file into a WORM file on a SnapLock volume via NFS

ONTAP Recipes: Easily create a SnapLock volume

ONTAP Recipes: Attach StorageGRID Webscale as a FabricPool external capacity tier

ONTAP Recipes: Attach Amazon S3 as a FabricPool external capacity tier

ONTAP Recipes: Use QoS floors to prioritize business critical NAS applications

ONTAP Recipe: Configuring NFS Connector with Apache Tez in HDInsight

ONTAP Recipe: Configuring Oracle ASM with multiple LUNs per Disk Group

ONTAP Recipes: Easily create a NAS Application Container

ONTAP Recipes: Use FlexGroup QoS ceilings to limit the impacts of test workloads

ONTAP Recipes: Easily enable SAML Authentication for OCSM in ONTAP 9.3

ONTAP Recipes: Easily Protect your FlexGroup volume in ONTAP 9.3

ONTAP Recipes: Inplace Conversion of an existing plain text volume to Encrypted

ONTAP Recipes: Easily Create a NAS Application Container in ONTAP 9.3

ONTAP Recipes: Easily configure Cluster and SVM peering in ONTAP 9.3

ONTAP Recipes: Easily use QoS Max to prevent a FlexGroup from becoming a bully object

ONTAP Recipes: Easily assign a volume to an Adaptive QoS Policy

ONTAP Recipes: Easily rekey an encrypted volume in ONTAP 9.3

ONTAP Recipes: Easily configure KMIP servers for NetApp volume encryption in ONTAP 9.3

ONTAP Recipes: Easily configure SSH Multifactor authentication for administrator accounts (MFA)

Did you know that…
You can start the object store profiler through the ONTAP CLI to test latency and throughput performance?