Enable preview and hidden features for NetApp Backup and Recovery
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.
| Feature flag | Feature description |
|---|---|
|
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. |
|
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.
-
Use SSH to log into the Console agent.
-
Change to the root user:
sudo su -
Find the Backup and Recovery volume in Docker:
docker volume ls | grep cbsThe output should be similar to the following:
local service-manager-2_cloudmanager_cbs_volume
-
Find the mount point for the volume:
docker volume inspect service-manager-2_cloudmanager_cbs_volume | grep MountpointThe 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
-
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 -
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.jsonRefer to available flags for feature flag information. As an example:
{ "feature-flags": { "folder-restore-from-local": true, "prioritize-restore": true } }
-
-
Restart the Backup and Recovery container:
docker restart cloudmanager_cbs -
Reload the Backup and Recovery UI in your web browser.
To disable a preview feature, follow the same steps but set the feature flag value to false.
Disable indexing for volumes
Disable indexing for specific volumes or for all volumes belonging to one or more storage VMs by using the following option flags:
-
svms-not-to-index: A comma-separated list of storage VMs whose volumes should not be indexed -
volumes-not-to-index: A comma-separated list of individual volumes that should not be indexed
-
Use SSH to log into the Console agent.
-
Change to the root user:
sudo su -
Find the Backup and Recovery volume in Docker:
docker volume ls | grep cbsThe output should be similar to the following:
local service-manager-2_cloudmanager_cbs_volume
-
Find the mount point for the volume:
docker volume inspect service-manager-2_cloudmanager_cbs_volume | grep MountpointThe 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
-
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 -
Create a file named
production-customer.jsonand customize the storage VM and volume names to match your environment:{ "indexing": { "svms-not-to-index": "storage_vm_1,storage_vm_2,storage_vm_3", "volumes-not-to-index": "volume_1,volume_2,volume_3" } } -
Restart the Backup and Recovery indexing catalog container:
docker restart cloudmanager_cbs_catalog