NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedule for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application consistent snapshots
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Configuring storage for different deployments
- About incremental backup for PaaS workloads
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Cloud asset cleanup
Cloud assets are cleaned up automatically during cleanup cycle or manually based on the following criteria:
No active protection plan to cloud asset.
Asset is not discovered in last 30 days (cleanup age).
No recovery points exist.
Asset is marked for deletion (asset is deleted on Snapshot Manager).
User can enhance this cloud asset cleanup criteria by updating cleanup-age and providing specific filter criteria for assets through bp.conf file. Following parameters must be configured in bp.conffile:
CLOUD.CLEANUP_AGE_MINUTES
CLOUD.CLEANUP_FILTER
For example,
/usr/openv/netbackup/bin/nbsetconfig
nbsetconfig> CLOUD.CLEANUP_AGE_MINUTES = 180
nbsetconfig> CLOUD.CLEANUP_FILTER = provider eq 'aws'
nbsetconfig>
User can also manually run the POST query using the cleanup-assets named query with the following request body and then run GET with query ID obtained from the POST response, as described in the following example:
{
"data":{
"type":"query",
"attributes":{
"queryName":"cleanup-assets",
"workloads":["cloud"],
"parameters": {
"cleanup_age_minutes": 180
},
"filter": "provider eq 'aws'"
}
}
}