Recent changes in NetApp Console
![iebuild[bot]](https://avatars.githubusercontent.com/in/311455?v=4){kind=avatar}
Suggest changes
PDFs
Learn about the most recent changes to the features and data services that are part of the NetApp Console. For a complete release history, go to the full set of release notes for each individual service.
|
The following services have been deprecated:
|
20 July 2026
Well-architected dashboard
Introducing the well-architected dashboard in NetApp Console
The well-architected dashboard in NetApp Console provides a single view of your storage systems and configurations across accounts and regions. The dashboard provides insights and recommendations to help you achieve operational excellence. You can view the well-architected status of your configurations, configuration issues organized by the pillars of the well-architected framework for the storage type you use, and a list of configuration issues and recommendations.
Learn more about the well-architected dashboard.
The well-architected dashboard in the Console is available for the following storage systems:
Build your own custom rules
Write custom rules in plain language to make sure your systems follow your organization's standards and NetApp best practices. Test the rules with a dry run, then schedule them to run across your environments.
Cloud Volumes ONTAP
Introducing simplified onboarding of Cloud Volumes ONTAP from AWS Marketplace
NetApp introduces a simplified onboarding flow for Cloud Volumes ONTAP from AWS Marketplace, reducing manual steps and onboarding friction.
Previously, deploying Cloud Volumes ONTAP from AWS Marketplace required navigating multiple screens and manually configuring roles, policies, and credentials. This made onboarding slow and error-prone.
The new onboarding flow simplifies your transition from a marketplace subscription to a fully operational Cloud Volumes ONTAP environment with the following features:
-
Subscription to the dedicated Cloud Volumes ONTAP listing on AWS Marketplace: You subscribe to the Cloud Volumes ONTAP standalone listing on AWS Marketplace, purchase a subscription, and set up your AWS account (if you don't already have one).
-
Guided path on the NetApp Console: You set up your account in the NetApp Console, and the Console automatically onboards you to the deployment journey, displaying the guided path on the right side. In case you need to leave the Console, you can resume the guided journey at a later point.
-
Associating your subscription: You can automatically associate your subscription with the Console, avoiding the manual steps of linking it yourself.
-
Console agent deployment with AWS credentials configuration: You can automatically create the required AWS roles. The process deploys an AWS CloudFormation stack in your AWS account with the required roles and policies for you to review, then associates them with the NetApp Console, eliminating manual IAM setup. You then continue through agent configuration, networking, and security group settings to begin the agent deployment.
-
Deploy a new Cloud Volumes ONTAP system in AWS: You navigate directly to the
Quick createwizard for a faster, simplified Cloud Volumes ONTAP deployment.
Well-architected configuration analysis for Cloud Volumes ONTAP in Azure
The NetApp Console now supports well-architected configuration analysis for Cloud Volumes ONTAP systems running in Microsoft Azure. The Console analyzes your deployments daily and provides a well-architected status, insights, and recommendations to help you maintain systems that align with NetApp best practices and the well-architected framework.
The well-architected dashboard displays the total number of analyzed systems and categorizes their resources by configuration and severity level. If you are a system administrator, you can view recommendations for any configuration issue within your organization directly from the Console dashboard and download a CSV report of all the recommendations. Configurations are categorized according to:
-
Reliability: Ensures workloads operate correctly and consistently, even in the event of disruptions.
-
Security: Safeguards data, systems, and assets through risk assessments and mitigation.
-
Operational excellence: Optimizes architecture to maximize business value.
-
Cost optimization: Reduces and optimizes costs for greater business value.
15 July 2026
Console setup and administration
Console agent 4.9.0
The 4.9.0 release supports both standard mode and restricted mode.
This release of the Console agent includes security improvements and bug fixes.
NetApp Console administration
Console supports role-based access for Cloud Volumes ONTAP.
Amazon FSX for ONTAP
GenAI workload removal from Workloads in the NetApp Console
The GenAI workload has been removed from Workloads in the NetApp Console.
14 July 2026
Cloud Volumes ONTAP
Cloud Volumes ONTAP 9.19.1 RC
You can now use the NetApp Console to deploy and manage the Release Candidate (RC) version of Cloud Volumes ONTAP 9.19.1 in Google Cloud. This version is unavailable for deployment and upgrade in Amazon Web Service (AWS) and Microsoft Azure (Azure).
Support for next-generation Google Cloud VMs in Cloud Volumes ONTAP HA
With 9.19.1, NetApp transitions Cloud Volumes ONTAP high-availability (HA) deployments off N2 VMs to the next-generation Google Cloud C3-series VMs for a faster and more scalable experience.
|
|
This support applies only to single availability zone (AZ) HA deployments. |
You can now take advantage of C3-series VMs while deploying Cloud Volumes ONTAP 9.19.1 and later in Google Cloud. These machines offer improved performance and higher capacity limits. They use Google Virtual NIC (gVNIC) and Hyperdisk Balanced disks for dynamic performance on intensive workloads.
If your Cloud Volumes ONTAP system runs 9.19.1 or later, the preconfigured packages that you use for easy deployments in single AZs automatically use C3 VMs, while enabling you to customize the IOPS and throughput parameters based on your workload needs. Similarly, while creating aggregates, you can add Zonal Hyperdisk Balanced disks to achieve better performance and scalability in Google Cloud. You can also select the LSSD variants of the C3 series machines for default Flash Cache support.
Note these points:
-
In your Cloud Volumes ONTAP deployments you can't change C3 VMs to N2-series VMs and vice versa. However, you can switch instance types among different variants within the C3 family.
Changing the instance type within the C3 family might take longer based on the number of data disks attached. Plan your configuration ahead of time to avoid performance impacts. -
When changing the instance type, if you select c3-standard-44 or c3-standard-88 and their local SSD (LSSD) variants as the target VM, the Google network service egress network tier Tier-1 is applied automatically. If you switch back to any other C3 variant, the egress network tier is set to Standard.
Changing the egress network tier to Tier-1 incurs additional costs. Plan the deployment and upgrade accordingly. -
If you select the LSSD variants of C3, Flash Cache gets enabled by default. You can't switch between C3 LSSD variants in your Cloud Volumes ONTAP deployment, even if the target variant supports Flash Cache.
-
On your C3 VMs, you can add volumes to both new and existing aggregates.
-
When replicating a Cloud Volumes ONTAP system with an N2 VM type to a C3 VM type, the disk type is set by default to Hyperdisk Balanced.
-
You can change the IOPS and throughput settings when adding aggregates through the NetApp Console or by using the
PUT /gcp/ha/aggregates/{workingEnvironmentId}/{aggregateName}API.
Simplified Cloud Volumes ONTAP deployment in Google Cloud
You can now use the Quick create wizard to deploy Cloud Volumes ONTAP in Google Cloud for both single-node and high-availability (HA) configurations. This streamlined process reduces steps, sets default values automatically on a single page, and minimizes navigation for faster and easier deployment.
Introducing access roles for Cloud Volumes ONTAP
NetApp introduces identity and access management (IAM) roles for Cloud Volumes ONTAP, enabling role-based access control (RBAC) for better security and easier compliance. Users can continue to log in to the NetApp Console using their existing credentials for Cloud Volumes ONTAP operations. However, authentication is now routed through identity federation, enabling the Console administrator to have more granular control over these functions. Every user must have one of the following roles for performing any operation on Cloud Volumes ONTAP. Without a role, users can't view or access Cloud Volumes ONTAP instances.
-
Cloud Volumes ONTAP viewer: Grants read-only access to Cloud Volumes ONTAP screens and tabs. Certain screens and action buttons are disabled in this role.
-
Cloud Volumes ONTAP operator: Enables day-to-day management tasks, such as adding volumes, managing storage, and configuring replication.
-
Cloud Volumes ONTAP admin: Provides full access to all Cloud Volumes ONTAP operations.
The Console administrator assigns roles to Cloud Volumes ONTAP users from Administration > Identity. Role permissions are based on a user's organization and apply across all Cloud Volumes ONTAP systems in that organization.
Cloud Volumes ONTAP enforces RBAC using a local cache of each user's permissions, which is refreshed automatically once every hour. When a user is assigned a new role or their existing role is changed, it may take up to one hour for that change to take effect, after which, all workflows permitted by the roles are enabled.
|
|
When a Console agent is deployed for the first time, or an existing Console agent is upgraded to Console 4.9.0 or later, a one-time seeding process automatically assigns Cloud Volumes ONTAP roles to all existing users in the organization. This process can take up to 30 minutes to complete. And when complete, the Console assigns appropriate roles to the existing users. |
Cloud Volumes ONTAP roles apply to Amazon Web Service (AWS), Microsoft Azure (Azure), and Google Cloud environments.
13 July 2026
Backup and Recovery
Enhanced multi-bucket support for all workloads
In this Backup and Recovery release, you can now protect the workloads within a system with up to 100 buckets per system across different cloud providers.
For details about NetApp Backup and Recovery, refer to Learn about NetApp Backup and Recovery.
Disaster Recovery
Kubernetes updates
Disaster Recovery has introduced the following changes for Kubernetes-based workloads:
Manage Trident Protect from the Sites menu
Disaster Recovery now supports managing Trident Protect directly from the Sites menu in the Disaster Recovery UI. You can upgrade Trident Protect or remove it from Disaster Recovery, streamlining management of your Kubernetes resources.
For more information, see Manage sites.
VMware updates
Disaster Recovery has introduced the following changes for VMware-based workloads:
Fail over empty datastores
Replication plans that include empty datastores can now be failed over successfully without excluding them from the plan or forcing failover. During failover, Disaster Recovery automatically mounts the empty datastore at the disaster recovery site, allowing VMs to be added and protected for failback operations.
For more information, see Failover to a remote site.
vCenter network automapping
You can now configure network mapping relationships at the vCenter level (that is, outside of the replication plan dialog). Once configured, Disaster Recovery automatically applies these network mappings when you add or edit a replication plan, streamlining replication plan management.
Disaster Recovery continues to support per-plan overrides. Existing network mappings defined within a replication plan can still be edited on a per-network basis; these mappings take precedence over the vCenter-level definitions.
Disaster Recovery viewer role tightening
The ability to view the Upgrade System tab has been removed from the Disaster Recovery viewer role. This change aligns the role with the more appropriate experience for read-only users. Learn about user roles and permissions in NetApp Disaster Recovery.
System performance enhancements
Disaster Recovery has introduced changes to reduce system resource consumption and improve performance across operations.
07 July 2026
Ransomware Resilience
Exclude file paths from user behavior alerts
Ransomware Resilience supports exclude specific file paths from user behavior monitoring alerts. You can exclude file paths if you know them to not be at risk or are performing work on files in a volume that might trigger alerts.
For more information, see Exclude file paths from alerts.
ARM template for Microsoft Sentinel
Ransomware Resilience now offers an Azure Resource Manager (ARM) template for connecting to Microsoft Sentinel as a SIEM, offering a secondary method to faciliate deployment.
For more information, see Connect to a SIEM for threat detection and analysis.
29 June 2026
Ransomware Resilience
Automated responses to user activity alerts
Ransomware Resilience now supports automating snapshot creation and user blocking when a user activity alert is generated. With automated responses, you can block a user as soon as a warning is generated and create a snapshot for recovery, enabling a swifter response without manual intervention.
For more information, see Automate responses to user activity alerts.
Digital advisor
Health Check GraphQL migration and data accuracy improvements
Health Check module has been enhanced with improved data accuracy and version recommendations aligned to currency standards. As part of this release, it has been migrated from the Public API to GraphQL, delivering improved performance, flexible querying, and long-term support.
Recommended software
Recommended Software enhancements in the Health Check module now provide more accurate and consistent data.
-
Shelf and drive counts under the firmware currency display the accurate per-system values and no longer include HA Pair counts.
-
Minimum and Latest version recommendations are now calculated at the cluster level based on the effective cluster version, in line with currency standards - previously, these recommendations were calculated at the node level.
AutoSupport data dependency
Due to backend improvements, the AutoSupport adoption and recommended software views rely on the latest AutoSupport data. This might affect your current view in the following ways:
| Scenario | Impacted systems |
|---|---|
No data displayed |
Systems that have not sent an AutoSupport since October 2025 |
Outdated values |
Systems that have not sent an AutoSupport in the last 30 days |
Re-trigger AutoSupport on the affected systems listed above to restore current data in Health Check views.
Keystone
New enhancements in the Keystone dashboard in the NetApp Console:
View ADP license distribution for MetroCluster subscriptions
A new License distribution sub-tab is now available on the Advanced data protection (ADP) tab, giving you visibility into ADP license usage across your MetroCluster partner clusters. To learn more, refer to View consumption and health of your Keystone MetroCluster subscriptions.
View ransomware protection status for your volumes
The Volumes in clusters tab in Assets now includes an ARP status column that displays whether Autonomous Ransomware Protection (ARP) is enabled or disabled for each volume, giving you visibility into your ransomware protection posture across managed assets. To learn more about ARP, refer to Autonomous Ransomware Protection (ARP) in ONTAP.
Share feedback using the Feedback tab
You can now provide feedback from any screen in the Keystone dashboard using the new Feedback tab, anchored to the bottom-right edge of the screen. Clicking it opens a panel where you can share your experience and submit comments directly to NetApp.
Improve alerting for capacity usage and subscription expiration
System-generated monitors now provide more granular alerting for capacity usage and subscription expiration.
For subscription expiration, alerts now trigger at five thresholds: 180, 90, 60, 30, and 7 days before expiration, with severity escalating from informational to critical as the date approaches.
For capacity usage, the burst alert threshold is now based on your subscription's committed burst percentage instead of a fixed 20%. For example, if your committed burst is 40%, the critical alert triggers at 140% of committed capacity utilization.
To learn more, refer to View and create alert monitors for Keystone subscriptions.
15 June 2026
Console setup and administration
Private mode release (4.7.0)
A new private mode release is now available to download from the NetApp Support Site
The 4.7.0 release includes updates to the following NetApp Console components and services.
| Component or service | Version included in this release | Changes since the previous private mode release |
|---|---|---|
Console agent |
4.7.0 |
Go to the What's new in NetApp Console page and refer to the changes included for versions 4.7.0. |
NetApp Backup and Recovery |
5.4.0 (08 June 2026) |
|
NetApp Data Classification |
1.54.0 (11 May 2026) |
Go to the what's new in NetApp Classification page. |
Backup and Recovery
Kubernetes workloads enhancements
In this release, Kubernetes workloads introduces the following enhancements:
-
Trident Protect 26.06: This release includes Trident Protect 26.06.
-
Skip application creation during restore: You can now skip automatic application custom resource object creation during restore operations. This reduces unnecessary entries in the application inventory.
-
Restore VM persistent volume claims: When restoring VM-based applications, you can now restore individual persistent volume claims without restoring the entire virtual machine, making recovery faster when specific disks or volumes are affected by corruption or data loss.
-
Job monitor improvements: Job monitoring now provides enhanced visibility into Kubernetes protection jobs. You can view detailed status information about jobs and subjobs, and see the target storage used by each.
For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.
11 June 2026
Cloud Volumes ONTAP
Support for a new Azure region in Cloud Volumes ONTAP
You can now deploy Cloud Volumes ONTAP 9.12.1 GA and later in single and multiple availability zones in Azure in the Malaysia West (malaysiawest) region. This includes support for both single-node and high-availability (HA) deployments.
For a list of all regions, refer to the Global Regions Map under Azure.
08 June 2026
Console setup and administration
Console agent 4.8.0
The 4.8.0 release supports both standard mode and restricted mode.
This release of the Console agent includes security improvements and bug fixes.
NetApp Console administration
This release includes the security improvements and bug fixes.
Backup and Recovery
ONTAP Volumes workloads enhancements
In this release, ONTAP Volumes workloads introduces the following enhancement:
Support for S3-compatible cloud storage: NetApp Backup and Recovery for Volumes workloads now supports backing up to S3-compatible cloud storage.
For details about protecting ONTAP Volumes workloads, refer to Protect ONTAP Volumes workloads overview.
Hyper-V workloads enhancements
In this release, Hyper-V workloads introduces the following enhancements:
-
Restore files and folders to a guest VM improvements: You can now restore files and folders from a snapshot on primary or secondary storage to a guest Windows VM. This capability is now supported for CIFS and SAN VMs.
-
Protection groups now use host time zone scheduling: Protection groups now use the time zone of the Hyper-V host. Protection groups created before host-time-zone scheduling was introduced continue to use their previously configured time (typically UTC). To update these protection groups to use the Hyper-V host time zone, you must re-create the schedules. Refer to Create and manage protection groups for Hyper-V workloads for more information.
For details about protecting Hyper-V workloads, refer to Protect Hyper-V workloads overview.
VMware workloads enhancements
In this release, VMware workloads introduces the following enhancement:
-
Protection groups now use host time zone scheduling: Protection groups now use the time zone of the hosting VMware vCenter Server. Protection groups created before host-time-zone scheduling was introduced continue to run on their previously configured time zone (typically UTC). To use the vCenter time zone, you must re-create the schedules. Refer to Create and manage protection groups for VMware workloads for more information.
For details about protecting VMware workloads, refer to Protect VMware workloads overview.
Data Classification
General improvements
This release of Data Classification includes security improvements and performance enhancements.
Disaster Recovery
Kubernetes updates
Disaster Recovery has introduced the following changes for Kubernetes-based workloads:
Test failover support for Kubernetes workloads
Disaster Recovery now supports testing the failover process for Kubernetes workloads. Testing failover allows you to validate disaster recovery plans. When you complete the test, you can clean up the test failover so the system automatically cleans up test resources to reduce overhead and ensure the consistency of your environment.
For more information, see Test the failover process.
Scheduled test failovers
You can now automate disaster recovery testing by scheduling test failovers. You can set schedules for recurring test failovers to continuously validate recovery plans without manual intervention, helping to maintain confidence in recovery objectives and meet compliance requirements.
For more information, see Manage replication plans.
Scheduled discovery of Kubernetes workloads
With scheduled discovery, you can control how frequently Disaster Recovery scans for new Kubernetes workloads. You can configure discovery intervals to align with your operational cadence, reducing unnecessary system overhead while ensuring new workloads are detected and protected in a timely manner.
For more information, see Customize discovery schedule.
VMware updates
Protection for empty datastores
Disaster Recovery now permits configuring protection for datastores that don't contain any virtual machines (VMs). Any VMs subsequently added to the datastore are automatically detected by Disaster Recovery, at which point you have to provide mapping information.
When you add an empty datastore to a protection plan, you must either remove the datastore from the protection plan before performing a failover or perform a force failover. For more information, see Failover to a remote site.
Restore previously excluded datastores to a protection plan
Datastores that were previously excluded from protection can now be re-included. This enhancement provides greater flexibility when managing and updating your disaster recovery configurations over time.
For more information, see Manage sites, resource groups, and replication plans.
Faster failover for VMFS-based datastores
Disaster Recovery has improved the failover performance for VMFS-based datastores. Host Bus Adapter (HBA) rescan and datastore mount operations are now executed in parallel, reducing overall failover times and minimizing downtime during recovery events.
For more information about failovers, see Fail over with Disaster Recovery.
Ransomware Resilience
Enhanced flexibility for protection strategies
Ransomware Resilience now provides more flexibility in choosing ransomware detection strategies. Previously, all ransomware protection strategies had to include encryption detection. Now, you can enable a ransomware protection strategy with only user behavior detection.
Protection strategies can still include both encryption detection and suspicious user behavior detection. Blocking file extensions can also be added to any protection strategy.
If you disable part of the protection strategy for an existing policy, any extant alerts created under the previous iteration of the policy can only be marked as "Resolved" not "Dismissed." For example, if you had a protection strategy that included encryption detection and suspicious user behavior but you disabled encryption detection, you can only resolve an existing encryption alert for that workload.
For more information, see Protect workloads with NetApp Ransomware Resilience protection strategies.
SOAR playbook enhancements
Ransomware Resilience SOAR playbooks now provide remediation steps after you've blocked a user or taken a volume offline. You can now take a volume back online and unblock a user if the action was deemed not a ransomware threat.
Cloud Volumes ONTAP
Support for new EC2 instances for Cloud Volumes ONTAP in AWS
Cloud Volumes ONTAP 9.16.1 and later support M6id and M6idn EC2 instance families for both new and existing single-node and high-availability (HA) pair deployments in AWS. These 6th-generation instances offer faster processing power, stronger networking capabilities, and higher performance compared to the 5th generation general purpose systems.
-
M6id instances: Provide a balance of compute and memory with high-speed, low-latency local NVMe storage. All M6id instance sizes support Flash Cache. These instances are well suited for workloads such as data logging and media processing.
-
M6idn instances: Provide the same local NVMe storage capabilities as M6id instances. All M6idn instance sizes support Flash Cache.
We do not recommend the smaller-sized m6id.xlarge, m6id.2xlarge, m6idn.xlarge, and m6idn.2xlarge instance types for high-performance or memory-intensive workloads. For these workloads, use an instance type with a higher core count and larger memory.
For more information, refer to Supported configurations for Cloud Volumes ONTAP in AWS.
03 June 2026
Lifecycle planning
Lifecycle planning feature name updates
The following Lifecycle planning features have name changes:
-
The Tech refresh feature is now called System Refresh. Learn how to evaluate a system refresh.
-
The Capacity Additions feature is now called Storage Expansion. Learn how to expand storage.
-
The Renewals feature is now called Support Renewals. Learn how to register for support.
Digital advisor
Digital Advisor widget name updates
The following Digital Advisor features have name changes:
-
The Tech Refresh feature is now called System Refresh. Learn how to evaluate a system refresh.
-
The Capacity Additions feature is now called Storage Expansion. Learn about Digital Advisor widgets.
-
The Renewals feature is now called Support Renewals. Learn about Digital Advisor widgets.
26 May 2026
Ransomware Resilience
Google Cloud NetApp Volumes support (preview)
Ransomware Resilience now supports creating protection groups for workloads in Google Cloud NetApp Volumes systems, enabling you to organize multiple workloads under one policy to streamline management.
For more information, see Create a protection group in Ransomware Resilience.
25 May 2026
Keystone
New enhancements in the Keystone dashboard in the NetApp Console:
Improved display of multiple updates on the same day in the subscription timeline
The subscription timeline chart now shows a number when multiple subscription updates of different types occur on the same day, instead of separate icons. Hover over the number to see all update types for that day. The downloaded report includes a separate row for each update, giving you a complete record of all changes. To learn more, refer to View the timeline of your Keystone subscriptions.
18 May 2026
Ransomware Resilience
Google Cloud NetApp Volumes support (preview)
Ransomware Resilience now supports Google Cloud NetApp Volumes systems, enabling you to efficiently detect and respond to ransomware threats in Google Cloud NetApp Volumes. When you conduct discovery, Ransomware Resilience automatically displays workloads from Google Cloud NetApp Volumes systems. When you discover the systems, they appear in the Ransomware Resilience dashboard. Support for Google Cloud NetApp Volumes in Ransomware Resilience is currently in preview.
For more information, see Learn about Ransomware Resilience. For information about the scope of Google Cloud NetApp Volumes support, review Limitations in Ransomware Resilience.
Clean restore enhancements
Clean restore now supports reports. With reports, you can review and assess clean restores, saving this information offline as a CSV file.
Clean restore also now support stopping the analysis. If you stop the analysis, you must begin the clean restore again.
To learn more about reports, see Download reports in Ransomware Resilience. To learn more about recovery, see Recover workloads with a clean restore.
Cloud Volumes ONTAP
Simplified Cloud Volumes ONTAP deployment in Azure
You can now use Quick create to deploy Cloud Volumes ONTAP in Azure for both single-node and high-availability (HA) configurations. This streamlined process reduces the number of steps compared to the advanced method, automatically sets default values on a single page, and minimizes navigation, making deployment faster and easier.
Digital advisor
Wellness Review
Starting July 2026, the Wellness Review feature will no longer be available in Digital Advisor. For any questions, send an email to ng-activeiq-feedback@netapp.com.
12 May 2026
Cloud Volumes ONTAP
Flexible billing for Cloud Volumes ONTAP and data services in AWS
NetApp offers enhanced billing options for your Cloud Volumes ONTAP subscriptions in AWS, giving you more control over how you pay for Cloud Volumes ONTAP capacity and NetApp data services, such as NetApp Backup and Recovery.
Previously, all Cloud Volumes ONTAP and data services usage were billed together through the NetApp Intelligent Services (NIS) listing in the AWS marketplace.
Due to changes in AWS Enterprise Discount Program (EDP), NetApp has introduced a standalone Cloud Volumes ONTAP subscription in the AWS marketplace that allows you to separate the billing of Cloud Volumes ONTAP capacity from data services. This separation gives you more flexibility in managing your EDP credits and costs. NetApp recommends using the standalone subscription for better cost management of your Cloud Volumes ONTAP usage, while continuing to use the NIS subscription for billing data services after July 31, 2026, when the EDP requirements take effect.
The standalone Cloud Volumes ONTAP subscription in AWS supports only valid capacity-based Essentials or Freemium license packages. The Professional package is not supported. You can select the billing method that best suits your needs:
-
Standalone Cloud Volumes ONTAP subscription (Recommended): Pay for your Cloud Volumes ONTAP usage through the standalone subscription in the AWS marketplace, while continuing to bill data services through the NIS subscription. This is the recommended option for most customers who have both standalone and NIS subscriptions associated with their AWS account in the NetApp Console.
-
Combined NIS subscription: Pay for both Cloud Volumes ONTAP and data services together through the existing NIS listing. The combined approach will be valid for existing customers who have only NIS subscriptions associated with their AWS account in the NetApp Console. However, NetApp recommends that you set your billing preference for your Cloud Volumes ONTAP usage and switch to the standalone subscription for better cost management.
Depending on your subscription type, you get these scenarios:
If you have only a standalone AWS subscription associated with your AWS account in the NetApp Console and no NIS subscriptions, you can select only the Essentials license package during deployment. The data services Backup and Recovery option is unavailable to you.
If you have both NIS and standalone subscriptions associated with your AWS account, and you haven't set a billing preference through the Billing preferences tab in the NetApp Console, Cloud Volumes ONTAP usage continues to bill through NIS by default. This is also the default for any Cloud Volumes ONTAP instance running the Professional package, because the standalone listing does not support Professional. You can set a billing preference and choose how to bill each service:
-
Set the standalone subscription as the preferred billing account for Cloud Volumes ONTAP (with Essentials package). If you have only the Professional package, you can convert it to an Essentials package and charge your Cloud Volumes ONTAP usage by setting the billing preference. We recommend this approach because it helps you manage your Cloud Volumes ONTAP EDP credits more effectively.
-
Use the NIS subscription for billing data services, or the Cloud Volumes ONTAP usage through the Professional package. During deployment, enable the Backup and Recovery data service and select the Professional license package to bill data services through the NIS subscription.
This is applicable if you are an existing customer with NIS subscriptions associated with the AWS account. You can continue billing both Cloud Volumes ONTAP and data services together as you do now. However, NetApp recommends switching to the standalone subscription approach for better cost management of your Cloud Volumes ONTAP usage:
-
Subscribe to a new standalone listing on the AWS portal.
-
Link the standalone subscription to your AWS account.
-
Set your billing preference to the standalone subscription for Cloud Volumes ONTAP usage with the Essentials package.
-
(If applicable) Convert your Professional package to an Essentials package and set the billing preference.
-
Continue billing data services through your NIS subscription.
|
|
No duplicate metering occurs when you use multiple subscription types or migrate between listings. |
11 May 2026
Console setup and administration
Console agent 4.7.0
The 4.7.0 release supports both standard mode and restricted mode.
This release of the Console agent includes security improvements and bug fixes.
NetApp Console administration
This release includes the following new feature.
By default, Digital Advisor shows all NetApp accounts associated with your company, rather than just your Console organization. To limit what is shown in Digital Advisor to a specific account, verify the business account you want to use with your Console organization. Learn how to verify your Console organization
Backup and Recovery
Hyper-V workloads enhancements
In this release, Hyper-V workloads introduces the following enhancements:
-
Protect VMs on SAN storage: You can now protect VMs on SAN object storage.
-
Restore to alternate location enhancements: You can now restore to an alternate location from primary and secondary locations for VMs on SAN storage.
-
Restore files and folders to a guest VM: You can now restore files and folders from a snapshot on primary storage to a guest Windows VM. This capability is supported only for CIFS VMs.
For details about protecting Hyper-V workloads, refer to Protect Hyper-V workloads overview.
KVM workloads enhancements
In this release, KVM workloads introduces the following enhancement:
Restore to alternate location: You can now restore KVM VMs to an alternate destination (this feature is now generally available).
For details about protecting KVM workloads, refer to Protect KVM workloads overview.
Oracle Database workloads enhancements
In this release, Oracle Database workloads introduces the following enhancements:
-
Oracle AI Database 26ai support: Backup and Recovery now supports Oracle AI Database 26ai.
-
Backup verification support: You can now configure backup policies to automatically verify the integrity of your Oracle database backups.
For details about protecting Oracle Database workloads, refer to Protect Oracle Database workloads overview.
VMware workloads enhancements
In this release, VMware workloads introduces the following enhancements:
-
Spanning datastore support for protection groups: You can now choose the behavior of protection groups when protecting virtual machines whose virtual disks span multiple datastores.
-
Clone support: You can now create clones of virtual machine snapshots from primary and secondary storage.
For details about protecting VMware workloads, refer to Protect VMware workloads overview.
Kubernetes workloads enhancements
In this release, Kubernetes workloads introduces the following enhancements:
-
Trident Protect 26.05.1: This release includes Trident Protect 26.05.1.
-
In-place restore for VM-based apps: You can now restore VM-based applications to the original namespace and original cluster.
For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.
Data Classification
Improved Configuration page
Data Classification has updated and improved the Configuration page, enabling an improved usability experience to manage settings, systems, enable scanning, and monitor system health. The new Configuration page provides the existing functionality in an easier to use format in addition to the ability to filter systems by type, error status, and scan status. The new page also provides a summary of connected systems and overviews of active and configured scans.
Review a video walkthrough. For more information, see Scan data sources with Data Classification.
Compliance admin IAM role
Data Classification now supports a Compliance admin role to manage permissions in Data Classification. The Compliance admin role doesn't have access to resources including Console agents and workspaces. Users with the Compliance admin role must be associated with at least one other role.
When installing Data Classification, you should have a Console platform admin role or the Compliance admin role.
If you're an existing user, access should continue as normal. For example, a platform role that has a folder or project admin role has existing access.
For more information, see Data Classification roles.
Deploy Data Classification with OVA
NetApp Data Classification now supports deployment with VMware Open Virtual Appliance (OVA), offering a simplified deployment strategy for on-premises VMware vSphere environments.
For more information, see Deploy Data Classification with OVA.
Disaster Recovery
Kubernetes-based workload support (preview)
NetApp Disaster Recovery now includes support for Kubernetes-based workloads. With Kubernetes support, you can protect applications running on Kubernetes clusters, including OpenShift Virtualization environments. Disaster Recovery supports any version of Kubernetes currently supported by Trident Protect, ensuring seamless integration and robust disaster recovery capabilities for containerized applications.
Key features of Kubernetes-based workload support:
-
Broad compatibility: Disaster Recovery supports all Kubernetes versions compatible with Trident Protect, including Red Hat OpenShift Virtualization.
-
Application-centric protection: You can now protect Kubernetes workloads at the application level, ensuring the recovery of critical services during failover events.
-
Simplified orchestration: Disaster Recovery offers intuitive workflows to automate the backup and replication of Kubernetes workloads, leveraging the same efficient SnapMirror technology used for VMware environments.
Support for Kubernetes-based workloads is currently in preview. To begin protecting Kubernetes-based workloads, see Kubernetes requirements for NetApp Disaster Recovery.
Ransomware Resilience
Clean restore enhancements
Clean restore now supports recovering to an alternate location, enabling you to restore volumes to different systems, storage VMs, and aggregates managed by the same Console agent. Additionally, clean restore has removed the seven-day limitation in searching for viable snapshots for recovery. Clean restore now continues looking through available snapshots for a viable recovery point regardless of distance from the ransomware event.
Google SecOps SIEM support
Ransomware Resilience now supports security information and event management (SIEM) with Google SecOps, enabling you to send data automatically to Google SecOps for streamlined threat analysis and detection.
For configuration information, see Connect Ransomware Resilience to a SIEM.
Azure NetApp Files support is now generally available
Ransomware Resilience now supports Azure NetApp Files systems, enabling you to efficiently detect and respond to ransomware threats in Azure NetApp Files. When you discover workloads, Ransomware Resilience now presents Azure NetApp Files and displays them in the protection dashboard. Ransomware Resilience support for Azure NetApp Files includes detection and protection strategies with snapshots only. Support for Azure NetApp Files is now generally available (GA).
For more information, see Learn about Ransomware Resilience.
SOAR support for blocking users
Ransomware Resilience now supports blocking individual users with Google SecOps and Splunk SOAR playbooks. With this addition, you can automate blocking users when Ransomware Resilience detects suspicious user activity such as a data breach or mass deletion of data.
05 May 2026
Backup and Recovery
Kubernetes workloads enhancements
In this release, Kubernetes workloads introduces the following enhancements:
-
Trident Protect 26.05: This release includes Trident Protect 26.05.
-
Upgrade Trident Protect from Backup and Recovery: If your Kubernetes cluster is running Trident Protect 26.05 or newer, you can now upgrade Trident Protect directly from Backup and Recovery.
-
Native support for protecting VMs: You can now create VM-based applications, enabling you to protect virtual machines the same way you protect any other application.
-
Resource transformations: You can now use resource transformations and resource transformation templates to add, remove, and modify resource attributes during the restore process.
-
View protected resources: You can now view the resources included in each recovery point for an application, and download a detailed JSON report. This gives you full visibility into your recovery points and simplifies audit compliance.
For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.
27 April 2026
Keystone
New enhancements in the Keystone dashboard in the NetApp Console:
Renamed Provisioned capacity label
The label Provisioned capacity is renamed to Provisioned volume capacity. The updated label is also reflected in the related CSV and Excel reports.
Forecast toggle for accrued burst
You can now use the Forecast toggle in the Accrued burst view of the Consumption trend tab to project accrued burst usage for the next 120 days from the current date. To learn more, refer to View forecast data.