Tech ONTAP Blogs

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Tech ONTAP Blogs

BlueXP Backup and Recovery May'25 Updates v4.0.3

jacoba
NetApp
NetApp
‎2025-05-14 12:54 AM
621 Views

BlueXP Backup and Recovery May'25 Updates v4.0.3

 

 

BlueXP Backup and Recovery Support for SnapMirror Cloud Resync

 

Introduction

 

The SnapMirror to Cloud Resync (SM-C Resync) feature is designed to streamline data protection and continuity during volume migrations in NetApp environments. When a volume is migrated—using SnapMirror Logical Replication (LRSE)—from one on-premises NetApp deployment to another, or to a cloud-based solution such as Cloud Volumes ONTAP (CVO) or Cloud Volumes Service (CVS), SM-C Resync ensures that existing cloud backups remain intact and operational.

This functionality eliminates the need for a time-consuming and resource-intensive re-baseline operation, allowing backup operations to continue seamlessly post-migration. SM-C Resync is particularly valuable in workload migration scenarios, supporting both FlexVols and FlexGroups, and is available starting with ONTAP version 9.16.1.

By maintaining backup continuity across environments, SM-C Resync enhances operational efficiency and reduces the complexity of hybrid and multi-cloud data management.

 

How BlueXP Backup and Recovery SnapMirror Cloud Resync Works

 

While customer completes a Tech Refresh or migrating volumes from one ONTAP cluster to another, it's important that your backups continue to work without interruption. This is exactly what BlueXP Backup and Recovery SnapMirror Cloud Resync helps with—it ensures that your cloud backups stay consistent even after a volume migration.

 

Let’s break it down with an example:

Imagine you have an on-premises volume called Vol1a. This volume has three snapshots: S1, S2, and S3. These snapshots are like restore points. Vol1 is already being backed up to a cloud object store endpoint using SnapMirror to Cloud (SM-C). However, only S1 and S2 have been backed up to object store so far.

Now, you want to migrate Vol1 to another ONTAP cluster. To do this, you create a SnapMirror Logical Replication (LRSE) relationship to a new cloud volume called  Vol1b. This transfers all three snapshots—S1, S2, and S3—from Vol1a to Vol1b.

 

Once the migration is complete:

  • The original SM-C relationship (Vol1a → Object store) is deleted.
  • The LRSE relationship (Vol1a → Vol1b) is also deleted.
  • Vol1b is now your active volume.

At this point, you want to continue backing up Vol1b to the same cloud endpoint. But instead of starting a full backup from scratch (which would take time and resources), you use SnapMirror Cloud Resync.

 

Here’s how the resync works:

  • The system checks for a common snapshot between Vol1a and Object store. In this case, both have S2.
  • Because of this shared snapshot, the system only needs to transfer the incremental changes between S2 and S3.
  • This means only the new data added after S2 is sent to object store, not the entire volume.

This process is efficient and smart. It avoids re-sending data that’s already backed up, saves bandwidth, and ensures that your backup chain continues smoothly after migration.

 

 

jacoba_0-1747208084197.png

 

🔔 Important Note

  • ✅ The destination ONTAP cluster must be running ONTAP version 9.16.1 or later.
  • ✅ The old source ONTAP cluster must be protected using BlueXP Backup and Recovery.
  • ⚠️ Migration or tech refresh is not performed using BlueXP Backup and Recovery. It should be carried out by a professional services team or a qualified storage administrator.
  • 🔄 The migration team is responsible for creating the SnapMirror relationship between the source and destination ONTAP clusters to facilitate volume migration.
  • 🚫 Ensure that the migration during tech refresh is based on SnapMirror-based migration.
  • ❗ SnapMirror Cloud Resync after migrations using SVM-Migrate, SVM-DR, or Head Swap methods are not currently supported.

Steps to Perform Volume Migration and SM-C Resync in BlueXP Backup and Recovery

 

 

jacoba_1-1747208149742.png

 

1. Pre-Migration Checklist: Steps to Complete Before Starting the Migration

Before initiating the migration process, the Tech Refresh team must ensure the following prerequisites are completed to avoid data loss and ensure a smooth transition:

  1. Old ONTAP Cluster is Protection Enabled
    • All volumes that are to be migrated must be protected using BlueXP Backup and Recovery.
  2. Record Volume Instance UUIDs (Important)
    • Note down the Instance  UUIDs of all volumes before starting the migration. These identifiers are critical for mapping and resync operations later.
  3. Take a Final Snapshot (Important)
    • Before deleting any existing SnapMirror relationships, take a final snapshot of each volume to preserve the latest state.
  4. Document SnapMirror Policies (Important)
    • Record the SnapMirror policy currently attached to each volume’s relationship. This will be needed during the SnapMIrror Cloud resync process.
  5. Delete the SnapMirror Cloud  Relationships
    • Delete the existing SM-C relationship with the object store.
  6. Create SnapMirror relationship with new ONTAP Cluster for Migration 
    • Create a standard SnapMirror relationship to migrate the volume to the new target ONTAP cluster.

 

2.  Post-Migration Checklist: Steps to Perform After Migration

Once the migration is complete, the following steps must be carried out to re-establish protection and prepare for resync:

  1. Record New Volume Instance UUIDs (Important)
    • Note the Instance UUIDs of all migrated volumes in the destination ONTAP cluster.
  2. Create SnapMirror Policies (Important)
    • Confirm that all required SnapMirror policies are available in the old ONTAP Cluster are correctly configured on the new ONTAP cluster.
  3. Add New Working Environment to BlueXP
    • Add the new ONTAP cluster as a Working Environment in the BlueXP Canvas.

 

3. Performing SnapMirror Cloud Resync Using BlueXP Backup and Recovery

To resume cloud backups from the newly migrated volumes, a SnapMirror Cloud  Resync must be performed. Follow these steps to initiate the resync process:

  1. Prepare the Resync Details Sheet
    • Update the resync-details Excel sheet with the following:
      • Old volume Instance UUID (from the source cluster)
      • New volume Instance UUID (from the destination cluster)
      • SnapMirror policy to be applied
  1. Upload the Excel Sheet
    • Upload the completed Excel sheet into the BlueXP Backup and Recovery Resync interface.
  2. Enter Provider and Network Information
    • Provide the necessary cloud provider and network configuration details required for the resync operation.
  3. Start the Resync Process
    • Initiate the SnapMirror Cloud Resync. The system will use the common snapshot (e.g., S2) to transfer only the incremental changes, ensuring efficient and seamless backup continuity.

 

Using BlueXP Backup & recovery to Resync the SnapMirror Cloud Relations

 

jacoba_9-1747207273504.png

 

Prerequisite:-

  1. Add New Migrated Working Environment to BlueXP
    • Add the new ONTAP cluster as a Working Environment in the BlueXP Canvas.
  2. Old Source Working Environment Details
    • Make sure that the old source Working Environment details are available on the BlueXP Backup and Recovery Volume Dashboard

 

Steps to Perform SnapMirror Cloud Resync in BlueXP Backup and Recovery

 

1. Navigate to the Backup Settings
From the Volume Dashboard page, click on Backup Settings. Then, under Advanced Settings, select Resync Backup.

  1. Open the Resync Working Environment Page
    Clicking Resync Backup will open the Resync Working Environment page.

jacoba_2-1747208209749.png

 

2. Specify the New Source Environment
Enter the New Source Working Environment—this is the new ONTAP cluster where the volumes have been migrated.

 

3. Select the Existing Target Object Store
Choose the Existing Target Object Store that contains the backups from the previous (old) source working environment.

 

4. Prepare the Volume Mapping CSV File

    • The next important step is to make sure that we upload the CSV sheet where details of the volumes to be migrated are populated.
    • In order to start filling in the details of the volumes to be migrated, make sure to download the CSV sheet by clicking on the “Download CSV Template” button on the “Re-sync working environment” screen, which provides you with a template of the details that need to be filled in.

jacoba_3-1747208256678.png

 

5. Fill in Volume Mapping Details
In the CSV file, enter:

    • The old Volume Instance UUID
    • The new Volume Instance UUID
    • The SnapMirror policy to be applied to the new relationship

 

6. Upload the Completed CSV File
Once the CSV is filled out, upload it using the Upload button under Upload Volume Mapping Details.

 

7. Enter Network and Provider Settings
Fill in the required Network and Provider Settings details.

 

8. Submit the Configuration
Click Submit to begin the validation process.

 

9. Validation Process
BlueXP Backup and Recovery will validate that each volume selected for resync has at least one common snapshot. This ensures the volumes are ready for the SnapMirror Cloud Resync process.

 

10. Review Validation Results
After validation, the UI will display:

  • The New Source Volume names
  • The Resync Status for each volume

 

11. Check Volume Eligibility
The table will indicate which volumes are eligible or not eligible for resync.

If a volume is not eligible, it means no common snapshot was found.

 

Important:

To ensure volumes remain eligible for SnapMirror Cloud Resync, always take a final snapshot of each volume before deleting any existing SnapMirror relationships during the pre-migration phase. This preserves the latest state of the data..

 

12. Initiate Resync
After reviewing the table, click Resync to proceed with the SnapMirror Cloud Resync.

 

jacoba_5-1747208398971.png

 

 

13. Monitor the SnapMirror Cloud Resync
Once the SnapMirror Cloud Resync is initiated you can monitor the status of the job under the Job Monitoring page.

 

jacoba_6-1747208573846.png

 

Support for Third Party MinIO Object store (PREVIEW)

 

Introduction

In the previous release, BlueXP Backup and Recovery introduced preview support for third-party object stores, starting with Wasabi. In the current release, this support has been expanded to include MinIO, also in preview mode. 

 

Getting Started

To begin using this preview feature, users must enable a specific flag on the connector (Click here for more details on how to enable the preview feature). Once enabled, users can enter the connection details of their MinIO third-party object store in the protection workflow by choosing “Third party Compatible” object store in the backup section.

 

How do I Backup my ONTAP volumes to Third-Party MinIO Object-store

 

1. To begin protecting your data, select the volumes that need to be backed up using the BlueXP Backup and Recovery protection wizard.

 

2. In the "Define Backup Strategy" section, choose the required protection options. For this setup, select both "Local Snapshot" and "Backup".

 

3. Under the "Local Snapshot" protection policy, enter the appropriate snapshot policy based on your retention and recovery requirements.

 

4.In the "Backup" section, you will be prompted to select a provider. To back up the volumes to a third-party object store such as MinIO, click on the "S3 Compatible" option.

 

jacoba_7-1747111724578.png

 

 

5. Clicking on "S3 Compatible" will open the "Provider Settings" panel, where you need to enter the "S3 Compatible Details" and the corresponding access credentials

 

jacoba_8-1747111724623.png

 

 

6. Next, select the desired "Backup Policy" and click "Next". Review your configuration on the summary page and activate the backup to complete the setup.

 

Preview Mode Limitations

 

While this feature is in preview, there are certain limitations:

  • Bring Your Own Bucket (BYOB) is not supported
  • Enabling DataLock in the policy is not supported
  • Enabling Archival mode in the policy is not supported
  • ONPREM ONTAP environments are only supported
  • MetroCluster is not supported
  • Options to enable bucket-level encryption are not supported

 

This preview version is designed to gather user feedback and ensure robust integration with third-party object stores before full functionality is rolled out. Users are encouraged to explore this new capability and provide feedback to help enhance the service. Please do not use this build in production environments.

 

Disclaimers

 

  1. Performance Guarantee: Our products are sensitive to S3 API latency and IOPs. To achieve AWS S3 equivalent performance, it is essential that the object stores provide AWS S3 equivalent latency and IOPs guarantees. NetApp will not undertake performance-specific improvements tailored to the varying performance profiles of third-party object stores.
  2. Data Corruption: NetApp will not be held responsible for any data loss or service downtime resulting from issues with third-party S3 object stores.
  3. Feature Support: NetApp will not support any features specific to third-party S3-compliant storage that are not already supported with AWS S3.
  4. NetApp Support: NetApp's support engagement with third-party object stores is currently under review. Specific terms and prerequisites must be met for NetApp to provide support for solutions involving S3-compliant object storage other than NetApp StorageGRID and NetApp ONTAP S3.

 

How do I Enable the Preview Feature

 

  • Login to Connector
  • Switch to Superuser

 

Run the command: `sudo su`

 

  • List Docker Volumes and Identify the CBS Volume

 

Run the command: `podman volume ls | grep cbs`
Expected output: local service-manager-2_cloudmanager_cbs_volume

 

  • Inspect the Volume to Get the Mountpoint
    • Run the command:

 

podman volume inspect service-manager-2_cloudmanager_cbs_volume | grep Mountpoint

 

    • Expected output: "Mountpoint": 

 

/var/lib/docker/volumes/service-manager-2_cloudmanager_cbs_volume/_data

 

  • Navigate to the Docker Volume Directory
    • Change directory to the mountpoint obtained in the previous step:

 

cd /var/lib/docker/volumes/service-manager-2_cloudmanager_cbs_volume/_data/cbs_config

 

  • Locate and Edit the `production-customer.json` File
    • Ensure you are in the correct directory and the `production-customer.json` file is present.
    • Open the `production-customer.json` file in your preferred text editor and add the following JSON snippet, ensuring the JSON structure is properly maintained:

 

{
   "feature-flags":
    {
        "allow-s3-compatible": true
     }
}

 

    • Save the changes to the file.
  • Restart the Cloud Manager CBS Service
    • Run the command: `podman restart cloudmanager_cbs`

 

All Community Forums
Public