Skip to main content
NetApp Backup and Recovery

Enable preview and hidden features for NetApp Backup and Recovery

Contributors netapp-mwallis
PDFs

Enable preview and hidden features for NetApp Backup and Recovery.

Required NetApp Console role
Backup and Recovery super admin. Learn about Backup and recovery roles and privileges. Learn about NetApp Console access roles for all services.

Available preview features

You can enable the following preview features for NetApp Backup and Recovery.

Available preview feature flags
Feature flag Feature description

"folder-restore-from-local": true

Enables folder-level restore from local ONTAP volume snapshots. By default, ONTAP only supports restoring folders from object storage backups. With this flag enabled, you can also restore entire directories from local and replicated snapshots.

"prioritize-restore": true

Makes the Prioritize restore over existing job queue option selectable during the restore workflow in the Backup and Recovery web UI. When you select this option during the restore workflow, restore operations are prioritized over other queued jobs so they run even when the queue is busy.

Enable preview features

Enable preview feature flag options to use functionality that is not yet generally available. Use preview features with caution in production environments.

Steps

  1. Use SSH to log into the Console agent.

  2. Change to the root user:

    sudo su

  3. Find the Backup and Recovery volume in Docker:

    docker volume ls | grep cbs

    The output should be similar to the following:

    local service-manager-2_cloudmanager_cbs_volume

  4. Find the mount point for the volume:

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

    The mount point differs between cloud and private deployments. This output example shows a cloud deployment:

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

  5. Change to the docker volume config directory, which is inside the mountpoint directory. For example:

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

  6. Create a file that contains the following JSON structure and a key/value pair for each feature flag you want to enable. Name the file based on your deployment type:

    • Cloud deployment: production-customer.json

    • Private / dark site deployment: darksite-customer.json

      Refer to available flags for feature flag information. As an example:

      {
  "feature-flags": {
    "folder-restore-from-local": true,
    "prioritize-restore": true
  }
}

  7. Restart the Backup and Recovery container:

    docker restart cloudmanager_cbs

  8. Reload the Backup and Recovery UI in your web browser.

    Note To disable a preview feature, follow the same steps but set the feature flag value to false.

Disable indexing for all volumes that belong to a storage VM

Follow these steps to disable indexing for all volumes that belong to a specific storage VM, instead of disabling indexing for each individual volume.

Steps

  1. Use SSH to log into the Console agent.

  2. Change to the root user:

    sudo su

  3. Find the Backup and Recovery volume in Docker:

    docker volume ls | grep cbs

    The output should be similar to the following:

    local service-manager-2_cloudmanager_cbs_volume

  4. Find the mount point for the volume:

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

    The mount point differs between cloud and private deployments. This output example shows a cloud deployment:

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

  5. Change to the docker volume config directory, which is inside the mountpoint directory. For example:

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

  6. Create a file named production-customer.json with the following content. Replace the storage VM names in the example with the names of the storage VMs in your environment:

    {
  "indexing": {
    "svms-not-to-index": "storage_vm_1,storage_vm_2,storage_vm_3"
  }
}

  7. Restart the Backup and Recovery indexing catalog container:

    docker restart cloudmanager_cbs_catalog