This section describes how to create a server backup vault.
To ensure post-restoration data consistency, you are advised to back up the entire server.
If you want to back up only some of the disks to reduce costs, ensure that the data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.
For example, the data of an Oracle database is scattered across different disks. If only some of the disks are backed up, restoration restores only the data of the disks that have been backed up, with the rest of the data unchanged. As a result, the data may be inconsistent and applications may fail to start.
You can filter unprotected resources by tag. If a tag is selected, only unprotected resources having the specified tag will be associated with the vault. Or, all unprotected resources will be associated.
Only existing tags can be selected. If no tag is available, create tags on the corresponding resource page. You can select a maximum of 5 tags to search for vaults. If you select more than one tag, the vaults containing any of the specified tags will be returned.
A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for vaults. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 10 tags. See Figure 4.
Parameter |
Description |
Example Value |
---|---|---|
Key |
Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS. A tag key:
|
Key_0001 |
Value |
A tag value can be repetitive or left blank. A tag value:
|
Value_0001 |
A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-f61e.
You can use the default name, which is in the format of vault_xxxx.
You can associate servers with the vault and perform backup for the servers. For details, see Querying a Vault.