Storage Service Deployment Guide - NetApp · ONTAP Storage Service Operations Guide Operating and Monitoring Systems Based on a Service Design Workshop Dan Herington, Paul Mantey

Technical Report

ONTAP Storage Service Operations Guide Operating and Monitoring Systems Based on a Service Design Workshop

Dan Herington, Paul Mantey

September 2016 | TR-4558

Abstract

This document describes the operation and management of system, management, reporting,

and automation tools required to deliver a storage service catalog. These instructions are

derived from a NetApp® service design workshop.

The services that are implemented for each solution vary; therefore, this document provides

general instructions that require customization based on the results of the workshop.

2 Clustered ONTAP Storage Service Operations Guide © 2016 NetApp, Inc. All rights reserved.

TABLE OF CONTENTS

1 Introduction ........................................................................................................................................... 3

1.1 Overview ......................................................................................................................................................... 3

1.2 How to Use This Document ............................................................................................................................ 3

2 Shared Storage Service Platform Operations ................................................................................... 3

3 Manage Service-Level Policies ........................................................................................................... 4

3.1 Create New Provisioning Policy ...................................................................................................................... 4

3.2 Update Provisioning Policy ............................................................................................................................. 7

3.3 Delete Provisioning Policy............................................................................................................................... 8

3.4 Add Cluster to Adaptive QoS Policy Manager ................................................................................................. 9

3.5 Starting/Stopping the Adaptive QoS Service................................................................................................. 10

4 Tenant Customer Onboarding ........................................................................................................... 11

4.1 Onboard New Tenant .................................................................................................................................... 11

4.2 Update Tenant Configuration ........................................................................................................................ 22

5 Storage Object Lifecycle .................................................................................................................... 22

5.1 Provision New Volume .................................................................................................................................. 22

5.2 Move Volume Between Service Levels ......................................................................................................... 27

5.3 Deactivate Volume ........................................................................................................................................ 30

5.4 Delete Volume .............................................................................................................................................. 33

6 Reporting and Alerts .......................................................................................................................... 34

6.1 Create Storage Service Report Folder .......................................................................................................... 34

6.2 Consolidate Reports into Storage Service Reports Folder ............................................................................ 35

6.3 Reporting Options ......................................................................................................................................... 40

6.4 Run Chargeback Report ............................................................................................................................... 41

6.5 Run Storage Pools Days to Full Report ........................................................................................................ 42

6.6 Capacity and Performance Workload Analysis ............................................................................................. 43

6.7 Application Workload Analytics Report ......................................................................................................... 43

References ................................................................................................................................................. 44

Version History ......................................................................................................................................... 44

LIST OF TABLES

Table 1) Ongoing management task categories. ............................................................................................................ 3


1 Introduction

1.1 Overview

This document is a companion to the ONTAP Storage Service Deployment Guide, which focuses on

architecting, designing, installing, and configuring a shared storage service platform based on the NetApp

ONTAP® storage management software. This document focuses on the operational tasks necessary to

keep the platform running. In addition, this document assumes that an enterprise or a service provider

develops the workflows necessary to perform the tasks described in this document.

Both of these documents were developed at a NetApp service design workshop performed for a NetApp

customer that led to the deployment of a shared storage service infrastructure. This customer chose to

name service levels after precious metals, a practice that normally refers to storage tiers (for example

Platinum, Gold, and Silver).

For completeness, this document illustrates how to create uniquely named storage levels. Customers

who want to use their own naming convention, as our example customer did, can follow the steps in this

guide. However, NetApp recommends that you use the default naming convention (Extreme, Value, and

Capacity). Doing so greatly simplifies the creation of naming policies and the movement of aggregates.

1.2 How to Use This Document

This document details the specific steps followed by a NetApp service provider to convert the concepts

developed in the service design workshop into a fully realized shared storage service platform. This

technical report is designed to serve as a template and guide for taking other service provider and

enterprise customers through this process. Wherever possible, this document lists any assumptions that

NetApp made during implementation.

2 Shared Storage Service Platform Operations

This section outlines the various management tasks that an operations team must perform during the

overall lifecycle of the shared storage service platform.

Table 1) Ongoing management task categories.

Task Description Frequency Notes

Manage service-level

policies

Create, update, and delete

service-level policies

(section 3)

When needed As business or customer

requirements dictate

Onboarding new

tenants

Create and delete tenants

(ipspace, broadcast domain,

SVM, and so on) (section 4)

When needed As requested by tenant

customer

Storage lifecycle Create, move, deactivate,

and delete volumes (section

5)

When needed As requested by tenant

customer

Monitoring and reporting Section 6 Daily or

weekly

As determined by

operational processes

The specific tasks in each of these categories are covered in a subsequent section.

http://www.netapp.com/us/media/tr-4548-deploy.pdf


3 Manage Service-Level Policies

In the service design workshop, the service provider defined a set of performance service levels to

implement with the Adaptive Quality of Service (QoS) Service Management tool on the shared storage

service platform. This section describes the steps necessary for creating, updating, and deleting these

provisioning policies through the NetApp Workflow Automation (WFA) Service-Level Objective (SLO)

pack.

Note: Instructions for locating and installing the WFA SLO pack are included in the companion document ONTAP Storage Service Deployment Guide.

The Adaptive QoS Policy Manager runs as a Windows service, waking up every 60 seconds to query the

system to determine what volumes exist in each aggregate that has service definitions. It then makes

sure that ONTAP QoS is configured for that volume.

Configuration of the Adaptive QoS Policy Manager is accomplished using a WFA workflow entitled

Manage Adaptive QoS Policy Configuration, which is located in the adaptive QoS workflow group. This is

highlighted in the following screenshot.

3.1 Create New Provisioning Policy

To create a provisioning policy, complete the following steps:

1. Access the Manage Adaptive QoS Policy Configuration WFA workflow, as described earlier.

2. Double-click Manage Adaptive QoS Policy Configuration. The following dialog box appears:



3. Under User Inputs, click Manage Service Levels.

4. Under Manage Storage Service Levels, click the drop-down menu in the Action field. Click Add to add an adaptive QoS policy.


5. Fill out the following fields:

Storage Service Level Class. Select an easily identifiable name for the storage service-level

class. In this example, Tier0-Platinum indicates the highest-level tier of service for this

cluster.

SLO Max Performance (IOPS/TB). This is the SLO-defined performance determined in the service design workshop. It is typically 2x or 4x the SLA guaranteed to the customer. In this example, we selected 12288.

Percentage of SLO Max Performance. This is the ratio of the SLA to the SLO. For our example, the SLO max performance is 12,288 IOPS/TB, and the SLA guaranteed to the customer is 6,144, or 50% of the SLO.

Aggregate Include by Regular Expression. This is the name of the aggregates to which this

adaptive QoS policy applies. In this example, any aggregate having the text tier0 or platinum

in the aggregate name is included (note that the | symbol denotes or).

Minimum IOPS. This field sets a minimum IOPS threshold to make sure that customers with very small volumes receive sufficient bandwidth for them. For example, if a customer has a 10GB volume within the platinum aggregate, that volume would be throttled to approximately 12 IOPS


by the adaptive QoS throttle. To make sure that reasonable performance is achieved, set a minimum that makes sense for the customer volume.

QoS Policy Enforcement. This can be set to Thick, Thin, or Effective. In this example, we have selected Effective.

6. The following fields are optional and can be used to address configuration corner cases if required:

Aggregate Exclude by Regular Expression. This parameter allows the exclusion of specific aggregates that might otherwise be selected for inclusion based on the aggregate include statement.

Volume Include (REGEX). This parameter allows the inclusion of a volume in this service level that is in an aggregate that would not normally be included.

Volume Exclude (REGEX). This parameter allows the exclusion of specific volumes in an aggregate that would normally be included.

Disk Types (REGEX). Not recommended. This parameter allows the inclusion of aggregates based on disk type rather than name.

Hybrid? Not recommended. In a manner similar to disk type, this parameter allows the inclusion of hybrid aggregates that include both spinning disk and SSDs.

7. After you have completed all necessary fields, click Execute to create the adaptive QoS service-level policy. Repeat these steps as necessary for all of the other service levels to be defined.

8. For the sake of clarity, NetApp also recommends that you remove the out-of-the-box service levels that you are not supporting in your service.

3.2 Update Provisioning Policy

To update an adaptive QoS provisioning policy, complete the following steps:

1. From the Adaptive QoS folder in WFA, click Manage Adaptive QoS Policy Configuration, as demonstrated in the section “Create New Provisioning Policy,” to open the following dialog box.


2. Under User Inputs, select Manage Storage Service Levels.

3. Under Manage Storage Service Levels, click the drop-down menu in the Action field. Select Update to update an existing adaptive QoS policy.

In this example, we are updating the Tier0-Platinum policy minimum IOPS from 1,024 IOPS to 2,048

IOPS. The other fields can also be modified in this workflow. See the section “Create New Provisioning

Policy” for details on the usage of the other fields.

After all of the fields have been revised as needed, click Execute to update the adaptive QoS service-

level policy.

3.3 Delete Provisioning Policy

To delete an adaptive QoS provisioning policy, complete the following steps:

1. From the Adaptive QoS folder in WFA, click Manage Adaptive QoS Policy Configuration, as demonstrated in the section “Create New Provisioning Policy,” to open the following dialog box.


2. Under User Inputs, select Manage Service Levels.

3. Under Manage Service Levels, click the drop-down menu in the Action field. Select Delete to update an existing adaptive QoS policy. From the drop-down menu, select the name of the storage service-level class to be deleted.

4. Click Execute to delete the provisioning policy.

3.4 Add Cluster to Adaptive QoS Policy Manager

After the WFA SLO pack has a defined set of service-level policies, you must point the tool at the

appropriate clusters to be managed. To add a cluster to Adaptive QoS Policy Manager, complete the

following steps:

1. Under User Inputs, click Add/Delete Clusters from QoS Configuration.


2. Under Add/Delete Clusters, click the drop-down menu in the Action field. Select Add from the Cluster Action drop-down menu. In the Cluster Details field, click the boxes next to the desired clusters to be managed with this QoS configuration. Then click Execute.

Note: If your desired cluster does not show up in the Cluster Details pane, it is likely because OnCommand® Unified Manager (OCUM) and/or WFA have not yet discovered the cluster. First check if it has been discovered in OCUM and, if so, select the Execution tab. Select your OCUM server under Data Sources and click Acquire Now.

3.5 Starting/Stopping the Adaptive QoS Service

Now that the service-level policies have been defined and the appropriate clusters have been added to

the configuration, the service can be started and/or stopped at any time. To perform this task, complete

the following steps:

1. Select Manage AQoS Service in the WFA workflow.


2. You must fill in the WFA administrator credentials so that the Adaptive Quality of Service (AQoS) service can get the cluster credentials from WFA. Doing so makes sure that the cluster credentials are kept secure.

3. Click Execute.

4 Tenant Customer Onboarding

This section describes the tasks require to add, manage, and delete tenants in the shared storage

solution. For this solution, tenant boundaries are managed by using storage virtual machines (SVMs), a

feature of NetApp ONTAP software. Each SVM is a secure container that provides a virtual storage

system on each tenant network and isolates the volumes provisioned for each tenant from all other

tenants.

4.1 Onboard New Tenant

To onboard a new tenant, you must create an SVM for that tenant. The steps required to prepare for the

creation of the SVM include the following:

Create an IPspace for the tenant. This enables each tenant to have overlapping IP address ranges.

Create a broadcast domain for the tenant network.

Define the subnet for the tenant network.

After these steps are complete, you can run the Create SVM wizard to create the SVM for the tenant.

To create the IPspace, complete the following steps:

1. Creation of the IPspace requires the use of the command line on the cluster. With a terminal utility

(for example, PuTTY), log in to the cluster. Enter the command ipspace create –ipspace

tenant1 to create the IPspace, where tenant1 is the name of the SVM to be created. This is the

only command that requires the command line, so you can now log out of the cluster.


2. The remaining tasks can be completed using OnCommand System Manager. Log in with the following URL: http://<ip or host name of your cluster>/sysmgr.

3. After you are in System Manager, navigate in the left panel to the Network menu within the Configuration folder. The Network configuration menu appears.

4. Select the Broadcast Domain tab from the Network configuration manager.

5. Click the Create button to open a dialog box.


6. In the pop-up menu, complete the following fields as shown in the previous screenshot:

Name. Broadcast domain name specific to the new tenant. In this example, we used tenant1-

bd.

MTU. Specify the maximum transition unit (MTU) for this network.

IPspace. Select from the drop-down menu the name of the IPspace specific to this tenant that

you created in the previous step. In this example, we used tenant1.

Assign Ports. Select the port names for the ports to be assigned to the new broadcast domain. These are the ports that have been assigned to the tenant’s VLAN.

7. When finished, click Create.

8. After you create the broadcast domain, select the Subnet tab.


9. After you create the broadcast domain, you must create a new subnet for that broadcast domain.

10. Navigate to the Subnets tab and click Create in the menu bar.

11. In the Create Subnet menu, fill in the following fields:

Name. Give the subnet a name. In this example, we used tenant1-subnet.

Subnet IP/Subnet Mask. Determine the subnet IP/subnet mask for the new tenant SVM. In this

example, we used 192.168.2.1/24.

IP Addresses. Declare a set of IP addresses to be used by the new tenant SVM. In this example,

we created two: 192.168.2.198 and 192.168.2.199.


12. Select the broadcast domain from the drop-down menu, as shown here:

13. Select the appropriate broadcast domain to be associated with the subnet. In this example, we used

tenant1-bd.

14. Click OK to populate the Broadcast Domain field in the main pop-up menu.

Note in the previous screenshot that the Show Ports on This Domain arrow has been selected. The port name should match those assigned to the broadcast domain in the previous step.

15. Confirm that all fields have been filled in and click Create.


As shown earlier, the new subnet tenant1-subnet has been successfully created with the

properties described in the creation process.

16. The next step in onboarding the tenant is to create an SVM. In the navigation column on the left side, select the Storage Virtual Machines folder in System Manager.

17. Select the appropriate cluster from the Storage Virtual Machine folder on the left. Click Create to create a new SVM.


18. This brings up the Storage Virtual Machine (SVM) Setup dialog box.

19. Complete the fields as follows:

SVM Name. This is the name given to the new tenant’s SVM. In this example, we used

tenant1-svm.

IPspace. Select the IPspace from the drop-down menu. The IPspace created earlier should

appear. In this example, it is tenant1.

Volume Type. Determine the types of volumes to be used by this SVM. Select either FlexVol or Infinite Volume. In this example, we selected FlexVol.

Data Protocol. Select CIFS, NFS, or iSCSI. In this example, we are using the NFS protocol.

Default Language. Select the default language for the SVM.


20. Continue filling out the fields as follows:

Security Type. Select either UNIX (Linux) or NTFS (Windows).

Root Aggregate. Select the appropriate aggregate in which to place the root volume. The SVM namespace is managed from the root volume.

21. Click Submit and Continue to start step 2 of creating an SVM.


22. In the Data LIF Configuration section, use the drop-down menu to select the appropriate subnet.

23. Click Browse to select the appropriate port.

24. Select the appropriate port from the Select Network Port or Adapter pop-up menu.

25. Click OK to return to the main Storage Virtual Machine (SVM) Setup wizard.


26. Select the appropriate port name from the Browse pop-up.

27. Click Submit & Continue.

Under the Administrator Details section, input the appropriate credentials for:

User Name. This is your SVM admin user name.

Password. This is the password for the SVM admin user.

Confirm Password. Reenter the password for the SVM admin user.

Click Submit & Continue to complete the SVM creation process.


28. At this stage, the administrator should receive a confirmation that the administrator has successfully completed the steps for creating an SVM.

29. Click OK.

This completes the process for creating an SVM, which completes as shown here:

Successful completion brings the user back to the System Manager home page. The new SVM appears

under the cluster in which it was created.


4.2 Update Tenant Configuration

Although there are many things that can be changed in a tenant configuration, none of them pertain to the

management of the service levels for the adaptive QoS script (WFA SLO pack). Standard updates to the

customer SVM should be followed according to the ONTAP Administrators Guide.

5 Storage Object Lifecycle

This section lists the tasks required to manage the lifecycle of storage objects for a tenant. This includes

the provisioning, modification, and deletion of volumes at the request of a tenant.

Note: This section assumes there is a “man-in-the-loop” process for responding to tenant requests for storage. All of these processes can be automated with an API called by an orchestration system or self-service portal. Orchestration is outside of the scope of this document.

5.1 Provision New Volume

Use System Manager to navigate to the SVM where the new volume is provisioned. This example

provisions a new volume into the SVM created in the section “Onboard New Tenant.”

To provision a new volume, complete the following steps:

1. Navigate to the Volumes folder within the Storage folder for the particular SVM for which you want to create the new volume.

2. Click Create at the top of the menu bar. Doing so brings up the following menu:

http://mysupport.netapp.com/documentation/productlibrary/index.html?productID=30092


3. Under the General tab, name the volume.

4. Click the pull-down menu to select the aggregate for the new volume. Make sure to select the aggregate appropriate for the service policy you want to implement for the new volume. Here we

choose an aggregate that includes platinum in its name because we know that this aggregate is

being managed by the Adaptive QoS Policy Manager that we configured previously.

5. Click OK. This brings you back to the main Create Volume menu.


6. Select the appropriate field under Storage Type:

Click NAS (used for CIFS and NFS access) if this volume is the primary volume for a workload.

Click Data Protection (Used as Destination Volume) if this volume is used as the destination for a NetApp SnapMirror® or NetApp SnapVault® protection relationship.

7. Complete the necessary fields within Size:

Total Size refers to the total size of the volume.

Snapshot Reserve (%) refers to the total amount of the volume that should be held in NetApp Snapshot® copy reserve.

8. Select Thin Provisioned under Thin Provisioning.

9. Next, select the Storage Efficiency tab.


10. Under the Storage Efficiency tab, select Enable Storage Efficiency. NetApp highly recommends enabling storage efficiency for all volumes. Depending upon the types of workloads, you might also want to enable compression.

11. Click the Quality of Service tab.


12. Navigate to the Quality of Service tab within the pop-up menu.

13. Make sure that the Manage Storage Quality of Service box is not selected. Quality of Service is managed by the WFA SLO pack.

14. Finally, move back to the General tab to complete the operation as shown following.

15. Click Create to complete the creation of the new volume.

16. The new volume appears in the Volumes viewer for that SVM, as shown below.


17. Verify that the newly created volume shows up in the summary screen.

Note: The Policy Group and the Maximum Throughput parameters have been set. This is because the Adaptive QoS Policy Manager detected the existence of a new volume in the platinum aggregate it is managing, created the policy, and then set it for the volume. In this case, the Max Throughput parameter is set to the policy minimum because the volume is both small and empty.

5.2 Move Volume Between Service Levels

To move a volume between service levels, complete the following steps:

1. Navigate in System Manager to the volume you want to move, as shown here.

2. Click Move on the toolbar.

3. The Move pop-up appears for the volume to be moved. The upper section describes the attributes of the source volume, including its name, size, the aggregate in which it is currently located, and the type of storage media used (in this example, SAS).

4. Select the appropriate destination aggregate for the volume move. In this case, we are moving the

volume SQLDB001 from the platinum service level down to the silver service level.

Note that both the Before Move and After Move sizes for both the Source Aggregate Available Space and Destination Aggregate Available Space are listed at the bottom of the pop-up menu.

5. Click Move to initiate the move. System manager confirms this request before executing the move, as follows.


6. System Manager confirms that you intend to move the volume from the source aggregate to the destination aggregate.

7. Click Move to confirm the move. System Manager produces a status box showing the job ID for the volume move that you initiated.


After confirming your intent to move the volume from the source aggregate to the destination aggregate, System Manager initiates the volume move job. A status box appears presents the following information:

Job status: in_progress

Job ID: 15905 (in this example)

The time to complete the volume move depends largely on the volume size and the current load on the controllers executing the move.

8. Clicking the Job ID hyperlink produces a graph similar to the following screenshot:

9. In this example, we see that the volume move has already completed.


10. Navigate back to the Volumes page for the tenant SVM created earlier.

11. Select the volume moved (in this example, SQLDB001).

12. Under the General Information section, confirm that the policy group has changed to the desired new policy group. In this case, we moved SQLDB001 to an aggregate that the Adaptive QoS Policy Manager was managing in the silver tier. Therefore, when AQoS detected the volume in the silver aggregate, it changed the Policy Group and Maximum Throughput parameters to the settings defined for the Tier2-Silver policy group.

5.3 Deactivate Volume

NetApp recommends that customers operating a shared storage service platform deactivate a volume for

a reasonable period of time (one week to one month) prior to deleting it. This allows the user of that

volume to determine whether they need the data in that volume. To accomplish this, unmount the volume

from the SVM namespace and then take the volume offline. This makes the data inaccessible, but does

not delete it.

The following process shows how to deactivate the volume (SQLDB001) created in the section “Provision

New Volume.”

Unmount Volume

To unmount a volume, complete the following steps:

1. Use System Manager to navigate to the Namespace folder for the tenant SVM.

2. Select the volume listed in the appropriate path. In this case, we selected SQLDB001.

3. Click Unmount from the menu bar. System Manager asks Are You Sure You Want to Unmount the Volume ‘SQLDB001’? and offers the option (by checking the box) Force Volume Unmount Operation.


4. Click Unmount to confirm the action.

Take Volume Offline

To take a volume offline, complete the following steps:

1. Navigate back to the Volumes folder as shown on the left side of the following screenshot.

2. Select the volume to deactivate. In this example, SQLDB001 has been highlighted in blue.

3. Click Status in the menu bar.

4. Select Offline.


5. System Manager asks Are You Sure You Want to Take the Volume ‘SQLDB001’ Offline?

Note: Data contained in the volume and its qtrees or LUNs is unavailable if the volume is taken offline.

6. Click Offline.

7. Confirm that the volume has been taken offline by looking under the Status column for that particular volume.

Note: It is a recommended best practice to bring the volume offline and wait 7 to 31 days before deleting it. By using this method, you can bring the volume back online if the customer needs data from it.


5.4 Delete Volume

After the volume has been taken offline, it can be deleted by using the following procedure:

1. Use System Manager to navigate to the Volume folder for the storage SVM containing the volume.

2. Click Delete in the menu bar.

3. A pop-up menu asks you to confirm that you want to delete the volume.

4. Check the box next to OK to Delete the Volume(s) and Its Data.

5. Click Delete.

6. System Manager deletes the volume from the system.


7. After completion of the volume delete process, System Manager shows that the volume no longer exists.

6 Reporting and Alerts

NetApp recommends using NetApp OnCommand Insight (OCI) for monitoring the shared storage service

platform environment. OCI is a powerful tool that can be customized in a variety of ways. It can present

reporting and alerts that fit with the system management paradigm and processes used by the service

provider or enterprise customer.

Four different types of reports are essential to effectively monitor the shared storage service platform

environment:

Aggregate capacity. This feature monitors capacity available within the aggregate. The service provider should monitor the Days to Full parameter and track against time so that they can order additional capacity and handle growth on the system.

Chargeback

System service-level performance capacity

Volume performance against service level

See the ONTAP Storage Service Deployment Guide for instructions on how to download and deploy the

OCI capacity management package from the NetApp Automation Store website.

6.1 Create Storage Service Report Folder

To create a convenient location for the reports you use regularly, complete the following steps:

1. Navigate to the public folders and click the New Folder icon on the menu bar.


http://automationstore.netapp.com/


2. This starts the New Folder wizard, as shown here.

3. Give the new folder a name. In this example, we used Storage Service Reports.

4. Click Finish to complete the New Folder wizard.

6.2 Consolidate Reports into Storage Service Reports Folder

To select the various reports that you want to bring together in the Storage Service Reports folder,

complete the following steps:

1. Select the Capacity Management reports as shown in the following screenshot.


2. Navigate back to the Capacity Management folder created during setup and deployment of the environment. Select the appropriate reports from the list and click the Copy icon in the menu bar.

3. Navigate back to the Storage Service Reports folder just created by the New Folder wizard.

4. Click the Paste icon in the menu bar.


5. Successful completion of the Paste operation populates the new Storage Service Reports folder with the desired Capacity Management reports.

6. Acquire the Storage Pools Days to Full Details report from the Storage Manager Dashboard to continue filling out our Storage Service Management report suite, as shown here.

7. Select the Storage Manager Dashboard by clicking it. This brings up the contents of that folder, as shown here.


8. Select Storage Pools Days to Full Details from the list and click the Copy icon in the menu bar.

9. Navigate back to the destination folder Storage Service Reports, as shown here.

10. Click the Paste icon in the menu bar to paste the Storage Pools Days to Full Details report tool into the folder.

11. Navigate back to the Reports section to get the Chargeback report generator. Click the Reports folder.


12. Select the Chargeback report and click Copy to copy the Chargeback report from the menu.

13. Navigate back to the Storage Service Reports folder.


14. Add Chargeback to the list by clicking the Paste button.

6.3 Reporting Options

To generate reports in several different output formats, complete the following steps:

1. Change the output format for the report (for example, PDF, XML, or Excel) by selecting the blue arrow icon in the Actions column. Click the blue arrow icon to the left of the name to run the report in the standard HTML format.

2. In this example, we clicked the blue arrow under the Actions column, which brings up the Run with Options menu. Select the desired format from the drop-down menu.


3. Click Run to run the report (in this case, PDF formatted).

6.4 Run Chargeback Report

Navigate back to the Storage Service Reports folder and click the blue arrow to run the Chargeback

report. The following screenshot shows a sample Chargeback report. Note the different tiers with different

chargeback levels.


6.5 Run Storage Pools Days to Full Report

The Storage Pools Days to Full report can help you determine when you need to purchase more storage

in a particular storage tier.

Navigate back to the Storage Service Reports folder. In this case, we clicked the blue arrow that runs the

Storage Pools Days to Full report as standard HTML.

This screenshot presents an example of the Storage Pools Days to Full Details screen. For organizations

purchasing storage in a capacity-on-demand model, the column to the right is critical. When this report is

exported in Excel format, this table can be sorted on this field. Close attention should be paid to pools for


which the number of days to full is approaching or is less than the typical time it takes to approve,

purchase, deliver, and install additional capacity.

6.6 Capacity and Performance Workload Analysis

The Capacity and Performance Workload Analysis report helps you determine when systems within the

cluster are reaching capacity from a performance perspective.


Capacity and Performance Workload Analysis report as standard HTML.

After selecting the cluster HA pair you want to analyze, you see three Utilization Trending charts at the

top of this report. The left chart, entitled Capacity Utilization Trending, is measured in GB. This chart

shows the trend of space utilization in the HA pair. The center graph, entitled Node Utilization Trending,

and the right chart, entitled Disk Utilization Trending, are measured in IOPS and provide a view into the

performance capacity of the systems.

These graphs help track the overall utilization of the system, both from a capacity and an IOPS

performance perspective. This report should be carefully reviewed on a weekly basis to determine

whether the system requires additional disk capacity or if additional controllers are required to meet the

performance capacity requirements of the solution. Make sure there is sufficient headroom on the nodes,

disks, and overall capacity.

6.7 Application Workload Analytics Report

The Application Workload Analytics report helps you determine how well specific workloads are

performing in relation to their storage service level.


Application Workload Analytics report as standard HTML.


When running this report, you must select the tenant application and the service level in which application

is running. In the preceding figure, the chart in the middle of the page—IO Density Trending by Volume—

is characterized in IOPS/TB. The horizontal threshold lines reflect the SLO and SLA settings given to that

volume, as defined by the service level under which it operates. The customer might want to customize

this report through a professional services (PS) engagement to optimize report layout and format.

References

The following references were used in this TR:

Data ONTAP Administration Guides http://mysupport.netapp.com/documentation/productlibrary/index.html?productID=30092

OnCommand System Manager Guides http://mysupport.netapp.com/documentation/productlibrary/index.html?productID=61372

Version History

Version Date Document Version History

Version 1.0 September 2016 Initial release.




Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications.

Copyright Information

Copyright © 1994–2016 NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark Information

NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud

ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Flash Accel, Flash

Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol,

FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp Fitness,

NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANshare, SANtricity,

SecureShare, Simplicity, Simulate ONTAP, SnapCenter, SnapCopy, Snap Creator, SnapDrive,

SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,

Snapshot, SnapValidator, SnapVault, SolidFire, StorageGRID, Tech OnTap, Unbound Cloud, WAFL, and

other names are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other

countries. All other brands or products are trademarks or registered trademarks of their respective holders

and should be treated as such. A current list of NetApp trademarks is available on the web at

http://www.netapp.com/us/legal/netapptmlist.aspx. TR-4558-0916

http://mysupport.netapp.com/matrix

http://www.netapp.com/us/legal/netapptmlist.aspx

Documents

Storage Service Deployment Guide - NetApp · ONTAP Storage Service Operations Guide Operating and Monitoring Systems Based on a Service Design Workshop Dan Herington, Paul Mantey