Skip to main content
NetApp Knowledge Base

How to upgrade performance tier of NVRAM disk in Azure CVO

  1. Last updated
  2. Save as PDF
Views:
1,233
Visibility:
Public
Votes:
2
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • ONTAP 9.11.x and later
  • Azure
  • NVRAM disk performance tier update
  • no more Feature Policy Variation Request (FPVR)

Description

This article describes the procedure to upgrade NVRAM disk to higher performance tier on Azure for CVO when recommended by NetApp Support or Engineering on performance analysis

NOTE:

  • Ensure that NVRAM disk tier is updated no more than P30 and do not change the disk size
  • If Azure disk performance tier P30 still does not improve performance check if moving to SSD v2 helps with the performance engineer
  • If the Azure CVO is deployed before 9.15.1 and is single node or HA (single AZ) NVRAM is by default on SSDv2 , if deployed in ONTAP versions before - only option is to create a new CVO in 9.15.1 on supported zones and to move the data to new CVO.
  • Azure CVO deployed in 9.19.1 supports NVRAM on SSDv2 for Azure MAZ HA as well.

 

Internal Notes

Procedure to upgrade NVRAM disk on Azure for CVO to higher performance tier:

NOTE: 

  •  TSEs to ensure NVRAM disk is the actual bottlenect from performance analysis from ONTAP side.
  • Ensure not to change the size of the disk ( always 512GB) and change only the performance tier.
  1. Will begin with Node 02 by having Node 01 takeover Node 02.

    • ::> storage failover takeover -ofnode <Node02>

  2. Stop/power off the nodes instance  once takeover is complete (Node 02).
    • In Azure portal navigate to the VM  for Node 02 and click on the stop button
  3. Uprade NVRAM disk
    • In Azure portal navigate to the Resource group for Node 02 and click on the nvram disk.
    • To the left select "size performance".
    • On the bottom click on "Performance Tier".
    • Select P30 - 5000 IOPS, 200MB/s .
    • Click Save.
  4. - Power on the instance.
    • In Azure portal navigate to the VM for Node 02 and click on the play/start button
      • Monitor the boot using the Azure serial console untill we see "waiting for giveback".
  5. - Once we see "waiting for giveback" perform giveback.
    • ::> storage failover giveback-ofnode <Node02>
  6. Will repeat procedure on node 01

  7. Have Node 02 takeover Node 01

    • ::> storage failover takeover -ofnode <Node01>

  8. Stop/power off the nodes instance  once takeover is complete(Node 01).
    • In Azure portal navigate to the VM  for Node 01 and click on the stop button
  9. Uprade NVRAM disk
    • In Azure portal navigate to the Resource group for Node 01 and click on the nvram disk.
    • To the left select "size performance".
    • On the bottom click on "Performance Tier".
    • Select P30 - 5000 IOPS, 200MB/s .
    • Click Save.
  10. - Power on the instance.
    • In Azure portal navigate to the VM for Node 01 and click on the play/start button
      • Monitor the boot using the Azure serial console untill we see "waiting for giveback".
  11. - Once we see "waiting for giveback" perform giveback.

::> storage failover giveback-ofnode <Node01>

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.