copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2024-12-17 |
backup for VPC, backup service, backup plan, backup policy, restore, restore volume, restore data |
vpc |
{{site.data.keyword.attribute-definition-list}}
{: #backup-use-policies}
Apply backup policies by adding user tags to new or existing volumes, virtual server instances, or shares. When these tags match a backup policy tag, a backup is created. {: shortdesc}
Up to 100 tags can be attached or detached in the same operation. Keeping the number of tags low can make it easier to track their usage and your backups.
- Create a backup policy and plan, and specify the tags for the target resources.
- Find the resources that you want to back up.
- Apply backup policy tags to your target volumes, or virtual server instances, or shares in the console.{: ui}
- Apply backup policy tags to your target volumes, or virtual server instances, or shares from the CLI.{: cli}
- Apply backup policy tags to your target volumes, or virtual server instances, or shares with the API.{: api}
- Apply backup policy tags to your target volumes, or virtual server instances, or shares with Terraform.{: terraform}
- Verify that your selected resource is associated with a backup policy. For more information, see View a list of resources that have a backup policy.
Scheduling snapshots of a replica share is not supported. Backup schedules for file shares can be set up only on the source side of a replication pair. When you choose to failover operations to the replica share, the source and replica shares switch roles. After a failover is performed, backup policies need to be removed from what was previously the source and applied to the current source share. Make sure you update the tags on the affected shares. {: important}
{: #backup-next-steps-use}