Updating a Yandex BareMetal server connection to Cloud Backup
Note
BareMetal is at the Preview stage.
If you deploy a backup of one server to another, the original server's connection to Cloud Backup becomes outdated. To continue backing up the original server and avoid conflicts with the new one, upgrade the source server connection to Cloud Backup:
-
Get an IAM token.
-
Reconnect to Cloud Backup from the outdated server:
Linux-
Connect to the server over SSH.
-
On your server, install curl
, wget , gawk , uuid-dev , and uuidgen .Note
If you use a distribution other than Ubuntu, install the specified utilities using your package manager commands.
sudo apt install curl sudo apt install wget sudo apt install gawk sudo apt install uuid-dev sudo apt install uuid-runtime
-
Update your connection to Cloud Backup:
wget https://storage.yandexcloud.net/backup-distributions/agent_reinit_bms.sh sudo bash bms_agent_reinit.sh -t=<IAM_token>
Where
-t
is the IAM token you got earlier.Result:
... Deleting old resource bound for instance_id epdoe4g6dbq4******** and resource_id: F07543A1-BDC1-415A-A143-C18E******** Updating ids in Cloud Backup Finished
-
-
Make sure the server is connected to Cloud Backup:
CLIIf you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the
--folder-name
or--folder-id
parameter.Get a list of BareMetal servers connected to Cloud Backup:
yc backup resource list --type bms
Where
--type
is the resource type.Result:
compute_instance_id: epd5sk4auijm******** created_at: "2024-11-17T10:29:40.436155166Z" updated_at: "2024-11-17T10:32:54.580592713Z" online: true enabled: true status: IDLE next_backup_time: "2024-11-24T00:00:00Z" resource_id: ad216376-a8d7-4c28-9a8d-b4ad******** is_active: true init_status: REGISTRED metadata: "null" type: BMS
-
Link the server to a backup policy.