diff --git a/feed.xml b/feed.xml
index 667a200..dfdad6b 100644
--- a/feed.xml
+++ b/feed.xml
@@ -8,8 +8,8 @@
You can now use the BlueXP audit service API to export audit logs.
The audit service records information about the operations performed by BlueXP services. This includes the originating IP addresses, workspaces, Connectors used, and other telemetry data. You can use this data to determine what actions were performed, who performed them, and when they occurred.
+The audit service records information about the operations performed by BlueXP services. This includes workspaces, Connectors used, and other telemetry data. You can use this data to determine what actions were performed, who performed them, and when they occurred.
Learn more about using the audit service API
@@ -836,193 +836,7 @@BlueXP backup and recovery now enables you to implement a 3-2-1 strategy where you can have 3 copies of your source data on 2 different storage systems along with 1 copy in the cloud. After activation, you’ll have a:
-Snapshot copy of the volume on the source system
-Replicated volume on a different storage system
-Backup of the volume in object storage
-This new functionality also applies to recovery operations. You can perform restore operations from a Snapshot copy, from a replicated volume, or from a backup file in the cloud. This gives you the flexibility to choose the backup file that meets your recovery requirements, including cost and speed of recovery.
-Note that this new functionality and user interface is supported only for clusters running ONTAP 9.8 or greater. If your cluster has an earlier version of software, you can continue using the previous version of BlueXP backup and recovery. However, we recommend that you upgrade to a supported version of ONTAP to get the newest features and functionality. To continue using the older version of the software, follow these steps:
-From the Volumes tab, select Backup Settings.
-From the Backup Settings page, click the radio button for Display the previous BlueXP backup and recovery version.
-Then you can manage your older clusters using the previous version of software.
-When you create backup files in object storage, by default, the backup and recovery service will create the buckets in object storage for you. You can create the buckets yourself if you want to use a certain name or assign special properties. If you want to create your own bucket, you must create it before starting the activation wizard. Learn how to create your object storage buckets.
-This functionality is not currently supported when creating backup files to StorageGRID systems.
-SAP HANA systems
-Supports connect and copy restore of Non-Data Volumes and Global Non-Data volumes having Azure NetApp Files secondary protection
-Oracle databases
-Supports restore of Oracle databases on Azure NetApp Files to alternate location
-Supports Oracle Recovery Manager (RMAN) cataloging of backups of Oracle databases on Azure NetApp Files
-Allows you to put the database host to maintenance mode to perform maintenance tasks
-Supports restore to alternate location
-Allows you to mount Oracle database backups
-Supports moving backups from GCP to archival tier
-Supports protection of NFS and VMFS type of datastores
-Allows you to unregister the SnapCenter Plug-in for VMware vSphere host
-Supports refresh and discovery of latest datastores and backups
-Backup policies for FlexGroup volumes now can use DataLock and Ransomware protection when the cluster is running ONTAP 9.13.1 or greater.
-There is now a Reports tab where you can generate a Backup Inventory report, which includes all backups for a specific account, working environment, or SVM inventory. You can also create a Data Protection Job Activity report, which provides information about Snapshot, backup, clone, and restore operations that can help you with service level agreement monitoring. Refer to Report on data protection coverage.
-You can now review backup lifecycle as a Job Type on the Job Monitor page, helping you to track the entire backup lifecycle. You can also see details of all operations on the BlueXP Timeline. Refer to Monitor the status of backup and restore jobs.
-A new backup alert has been added: "Backup files were not created because Snapshot policy labels do not match". If the label defined in a Backup policy does not have a matching label in the Snapshot policy, then no backup file will be created. You’ll need to use System Manager or the ONTAP CLI to add the missing label to the volume Snapshot policy.
-When you’re using BlueXP backup and recovery in a site with no internet access, known as a "private mode" deployment, the BlueXP backup and recovery information is stored only on the local Connector system. This new functionality automatically backs up critical BlueXP backup and recovery data to a bucket on your connected StorageGRID system so that you can restore this data onto a new Connector if necessary. Learn more
-If a backup file has been configured with DataLock & Ransomware protection, or if the backup file resides in archival storage, now folder-level restore operations are supported if the cluster is running ONTAP 9.13.1 or greater.
-Now you can choose a bucket that’s in a different project than the project of your customer-managed encryption keys (CMEK). Learn more about setting up your own customer-managed encryption keys.
-The AWS China Beijing (cn-north-1) and Ningxia (cn-northwest-1) regions are now supported as destinations for your backup files if the cluster is running ONTAP 9.12.1 or greater.
-Note that the IAM policies assigned to the BlueXP Connector need to change the AWS Resource Name "arn" under all Resource sections from "aws" to "aws-cn"; for example "arn:aws-cn:s3:::netapp-backup-*". See Backing up Cloud Volumes ONTAP data to Amazon S3 and Backing up on-prem ONTAP data to Amazon S3 for details.
-System-initiated jobs, such ongoing backup operations, are now available in the Job Monitoring tab for on-premises ONTAP systems running ONTAP 9.13.1 or greater. Earlier ONTAP versions will display only user-initiated jobs.
-