Managing cluster-level backup settings
You can change many cluster-level backup settings that you set when activating Cloud Backup for each ONTAP system. You can also modify some settings that are applied as "default" backup settings. This includes changing storage keys, the transfer rate of backups to object storage, whether historical Snapshot copies are exported as backup files, and more.
Cluster-level backup settings are available in the Advanced Settings page.
The full set of backup settings that you can change includes:
Changing the storage keys that give your ONTAP system permission to access object storage
Changing the ONTAP IPspace that is connected to object storage
Changing the network bandwidth allocated to upload backups to object storage
Changing the archival storage class (AWS only)
Changing the automatic backup setting (and policy) for future volumes
Changing whether historical Snapshot copies are included in your initial baseline backup files for future volumes
Changing whether "yearly" snapshots are removed from the source system
View cluster-level backup settings
You can view the cluster-level backup settings for each working environment.
From the BlueXP menu, select Protection > Backup and recovery.
From the Volumes tab, select Backup Settings.
From the Backup Settings page, click for the working environment and select Advanced Settings.
The Advanced Settings page displays the current settings for that working environment.
If you need to make any changes, just expand the option and make the change. All backup operations after the change will use the new values.
Note that some options are unavailable based on the version of ONTAP on the source cluster, and based on the cloud provider destination where the backups reside.
Change the storage keys for ONTAP to access cloud storage
If you have a company policy that requires you to periodically rotate all credentials, for example, every 6 months or a year, this is how you’ll synchronize your cloud provider’s access key and secret key with your ONTAP system. This allows you to update your cloud provider credentials, and then change the keys in your ONTAP system so that the two systems will continue to communicate.
This option is available for on-premises ONTAP systems only, and only when you’re storing backups to Amazon S3, Google Cloud Storage, and StorageGRID.
Just enter the new access key and secret key, and click Apply.
Change the ONTAP IPspace that is connected to object storage
You can change the ONTAP IPspace that is connected to object storage. This option is available when backing up data from on-premises ONTAP systems only - it is not available for Cloud Volumes ONTAP systems.
This option should not be used on a system that is actively backing up volume data to object storage. It should be used only in the case where an incorrect IPspace was selected when initially activating Backup on an on-premises ONTAP system.
Refer to the getting started documentation for backing up data from your on-premises ONTAP systems to your specific cloud provider to make sure your ONTAP setup is configured correctly for the new IPspace. For example:
An intercluster LIF is required on each ONTAP node that hosts the volumes you want to back up.
The LIF must be associated with the IPspace that ONTAP should use to connect to object storage.
The nodes' intercluster LIFs must be able to access the object store.
If you use are using a different IPspace than the Default, you might need to create a static route to get access to the object storage.
Just select the new IPspace and click Apply. After that you’ll be able to select the volumes that you want to back up from aggregates in that IPspace.
Change the network bandwidth available to upload backups to object storage
When you activate Cloud Backup for a working environment, by default, ONTAP can use an unlimited amount of bandwidth to transfer the backup data from volumes in the working environment to object storage. If you notice that backup traffic is affecting normal user workloads, you can throttle the amount of network bandwidth that is used during the transfer. You can choose a value between 1 and 1,000 Mbps as the maximum transfer rate.
Select the Limited radio button and enter the maximum bandwidth that can be used, or select Unlimited to indicate that there is no limit.
Change the archival storage class
If you want to change the archival storage class that’s used when your backup files have been stored for a certain number of days (typically more than 30 days), then you can make the change here. Any backup policies that are using archival storage are changed immediately to use this new storage class.
This option is available for on-premises ONTAP and Cloud Volumes ONTAP systems (using ONTAP 9.10.1 or greater) when you’re writing backups files to Amazon S3.
Note that you can only change from S3 Glacier to S3 Glacier Deep Archive. Once you’ve selected Glacier Deep Archive, you can’t change back to Glacier.
Change the automatic backup setting for future volumes
If you did not enable the automatic backup of future volumes when you activated Cloud Backup, then you can start making automatic backups of new volumes in the Automatic Backup section. You can also select the backup policy that will be applied to those new volumes. Having a backup policy assigned to newly created volumes ensures that all your data is protected.
If you enabled the automatic backup of future volumes when you activated Cloud Backup, then you can change the backup policy that will be used for the newly created volumes in the Automatic Backup section.
Note that the policy that you want to apply to new volumes must already exist. See how to create a new backup policy for a working environment.
Once enabled, this backup policy will be applied to any new volume created in this working environment using BlueXP, System Manager, the ONTAP CLI, or the APIs.
Change whether historical Snapshot copies are exported as backup files
If there are any local Snapshot copies for volumes that match the backup schedule label you’re using in this working environment (for example, daily, weekly, etc.), you can export those historic snapshots to object storage as backup files. This enables you to initialize your backups in the cloud by moving older snapshot copies into the baseline backup copy.
Note that this option only applies to new backup files for new read/write volumes, and it is not supported with data protection (DP) volumes.
Just select whether you want existing Snapshot copies to be exported, and click Apply.
Change whether "yearly" snapshots are removed from the source system
When you select the "Yearly" backup label for a backup policy for any of your volumes, the Snapshot copy that is created is very large. By default, these Yearly snapshots are deleted automatically from the source system after being transferred to object storage. You can change this default behavior from the Yearly Snapshot Deletion section.
Select Disabled and click Apply if you want to retain the yearly snapshots on the source system.