Assigning tags on snapshots and Restore Point Collection
When a snapshot of host (instance) / disk (volume) is initiated through NetBackup Snapshot Manager, tags from source would be applied on created snapshot as follows:
When snapshot of host is taken, tags (for AWS and Azure) or labels (for GCP) assigned in host/VM would be applied to snapshots.
When snapshot of disk is taken, tags (for AWS and Azure) or labels (for GCP) assigned in disk would be applied to snapshots.
While taking snapshot, NetBackup Snapshot Manager also applies few labels/tags to the snapshot.
If number of NetBackup Snapshot Manager required tags and source tags are greater than the allowed maximum tag limits, then these extra tags would not be copied from source (host/VM) and keys of these skipped tags would be logged as warning in NetBackup Snapshot Manager logs.
For Azure | For Azure Stack | For AWS | For GCP | For OCI |
|---|---|---|---|---|
Maximum tags limit: 48 Maximum tags that can be assigned on resources in Azure stack: 15 | Maximum tags limit: 15 Maximum tags allowed on instance/disk: 13 | Maximum tags limit: 50 Maximum tags allowed on instance/volume: 40. Remaining 10 tags would be reserved for NetBackup Snapshot Manager for creating snapshot. | Maximum labels limit: 62 | Maximum tags limit: 61 |
Keys used in Azure: cp:data, createdby | Keys used in Azure Stack: cp:data, createdby | Keys used in AWS: cp:data, src-volume, src-vol-region, cloudpoint-replicated, src-inst-region, createdby, cp:host-snapshot-name, cloudpoint-description, cloudpoint-src-region, cloudpoint-src-account | Keys used in GCP: instance_id, createdby | Keys used in OCI: createdby, cp:data, cp:host-snapshot-name |
There are some tags/labels which NetBackup Snapshot Manager assigns to snapshot. It is recommended not to assign these tags to any of the resources such as instance (host) and disk (volume). During snapshot, if any of the NetBackup Snapshot Manager tags are found on the asset then these tags would be skipped and not assigned to the corresponding snapshot.
If does not exist, then new would be created using instance tags and NetBackup Snapshot Manager tags.
If exists and no tags, then instance tags and NetBackup Snapshot Manager tags would be applied to the existing .
If exists without the
createdby: cloudpointtags, then preserve the existing tags of and add new tags from instance and NetBackup Snapshot Manager required tags.If exists with
createdby: cloudpointtags, then preserve the existing tags of and add new tags from instance and required tags of NetBackup Snapshot Manager.