Support for NetApp Console local deployment: This release of NetApp Backup and Recovery supports NetApp Console local deployment in preview status.

90 days of job retention: Backup and Recovery now retains job information in the Job Monitor for 90 days.

Restore to alternate location support for SAN VMs: You can now restore SAN-based VM backups to an alternate location.

Multiple backup delete support: You can now delete multiple backups at a time.

Preview support for air-gapped resources: If running NetApp Backup and Recovery in NetApp Console local deployment, you can discover, protect, and restore air-gapped Kubernetes resources. This feature is in preview for this release.

Prioritize restore jobs over backups: You can now prioritize restore jobs over backup jobs when you restore VMs or files.

Discover ONTAP systems and volumes without Backup and Recovery activation: You can now discover systems and volumes without activating Backup and Recovery.

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.

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.

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.