Connecting an existing Yandex BareMetal server to Yandex Cloud Backup

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

1. View the description of the CLI command to activate the service:

   yc backup provider activate --help
   

2. Activate the service in the default folder:

   yc backup provider activate --async
   

   Where --async displays the operation progress info. This is an optional parameter.

   Result:

   id: cdgmnefxiatx********
   description: activate provider
   created_at: "2024-10-14T09:03:47.960564Z"
   created_by: ajec1gaqcmtr********
   modified_at: "2024-10-14T09:03:47.960564Z"
   done: true
   metadata:
     '@type': type.googleapis.com/yandex.cloud.backup.v1.ActivateProviderMetadata
     folder_id: b1go3el0d8fs********
   response:
     '@type': type.googleapis.com/google.protobuf.Empty
     value: {}
   

After activation, the system automatically creates the following backup policies:

• Default daily: Daily incremental backup with the last 15 backups retained.
• Default weekly: Weekly incremental backup with the last 15 backups retained.
• Default monthly: Monthly incremental backup with the last 15 backups retained.

If you prefer not to create them, use the --skip-default-policy parameter.

1. View the description of the command for leasing a server:

   yc baremetal server create --help
   

2. Get a list of configurations:

   yc baremetal configuration list
   

3. Lease a server:

   yc baremetal server create \
     --hardware-pool-id <pool> \
     --configuration-id <configuration_ID> \
     --storage "partition={type=<file_system>,size-gib=<partition_size>,mount-point=<mount_point>},raid-type=<RAID array level>,disk={id=<disk_number>,size-gib=<disk_size>,type=<disk_type>}" \
     --os-settings "image-id=<image_ID>,image-name=<image_name>,ssh-key-public=<public_SSH_key_contents>,ssh-key-user-id=<SSH_key_user_ID>,password-plain-text=<user_password>,password-lockbox-secret={secret-id=<secret_ID>,version-id=<secret_version>,key=<secret_key>}" \
     --rental-period-id <lease_period> \
     --network-interfaces private-subnet-id=<private_subnet_ID> \
     --network-interfaces public-subnet-id=<public_subnet_ID> \
     --name <server_name> \
     --description "<server_description>" \
     --labels <label_key>=<label_value>
   

   Where:

   • --hardware-pool-id: Pool to lease a server from.

   • --configuration-id: Server configuration ID.

   • --storage: Disk partitioning settings. This is an optional parameter. Possible settings:

     • partition: Disk partition:

       • type: File system. The possible values are Ext3, Ext4, Swap, or Xfs.
       • size-gib: Partition size in GB.
       • mount-point: Mount point.

     • disk: Disk:

       • id: Disk number.
       • size-gib: Disk size in GB.
       • type: Disk type.

     • raid-type: RAID array level.

     Note

     The disk partitioning parameters are vital to have your server restored from a backup later on. For more information, see Restoring a VM or Yandex BareMetal server from a backup.

   • --os-settings: OS settings. To lease a server without an operating system, skip this parameter. Possible settings:

     • image-id: ID of one of the available Yandex Cloud Marketplace public OS images.

     • image-name: Name of one of the available Yandex Cloud Marketplace public OS images.

     • ssh-key-public: Public SSH key contents. You will need to create your own SSH key pair to establish a secure server connection.

     • ssh-key-user-id: SSH key user ID.

     • password-plain-text: Root user's password.

       Warning

       This option requires you to maintain password security. Save the password you generated in a secure location. Yandex Cloud does not store it, and you will not be able to retrieve it once the server is deployed.

     • password-lockbox-secret: Yandex Lockbox secret:

       • secret-id: Secret ID.
       • version-id: Secret version.
       • key: Secret key.

     You can install the OS from a custom ISO image later.

   • --rental-period-id: Server lease period. The possible values are 1 day, 1 month, 3 months, 6 months or 1 year.

     When this period expires, server lease will automatically be renewed for the same period. You cannot terminate the lease during the specified lease period, but you can refuse to extend the server lease further.

   • --network-interfaces: Network settings:

     • private-subnet-id: Private subnet ID.
     • public-subnet-id: Dedicated public subnet ID. This is an optional parameter.

     Warning

     The dedicated public subnet does not have a DHCP server; therefore, on the network interface of the server connected to such subnet, you should manually configure a static IP address from the subnet’s range of available public IP addresses and specify the default gateway address.

     For the Cloud Backup agent to exchange data with the backup provider servers, make sure the server has network access to the IP addresses of Cloud Backup resources based on the following table:

     Port range	Protocol	Destination name	CIDR blocks
     80	TCP	CIDR	213.180.193.0/24
     80	TCP	CIDR	213.180.204.0/24
     443	TCP	CIDR	84.47.172.0/24
     443	TCP	CIDR	84.201.181.0/24
     443	TCP	CIDR	178.176.128.0/24
     443	TCP	CIDR	213.180.193.0/24
     443	TCP	CIDR	213.180.204.0/24
     7770-7800	TCP	CIDR	84.47.172.0/24
     8443	TCP	CIDR	84.47.172.0/24
     44445	TCP	CIDR	51.250.1.0/24

   • --name: Server name.
   • --description: Server description. This is an optional parameter.
   • --labels: Server labels. This is an optional parameter.

To establish a server connection, specify the server public IP address which you can get using the management console, in the Public address field under Network settings on the server page.

1. In the terminal, run this command:

   ssh root@<server_public_IP_address>
   

   If this is your first time connecting to the server, you will get this unknown host warning:

   The authenticity of host '51.250.83.243 (51.250.83.243)' can't be established.
   ED25519 key fingerprint is SHA256:6Mjv93NJDCaf/vu3NYwiLQK4tKI+4cfLtkd********.
   This key is not known by any other names.
   Are you sure you want to continue connecting (yes/no/[fingerprint])?
   

2. Type yes into the terminal and press Enter.

3. Enter the password you specified when creating the server and press Enter.

To establish a server connection, specify the server public IP address which you can get using the management console, in the Public address field under Network settings on the server page.

Make sure the Windows account has read access to the key folder.

1. To connect to the server, run the following command in the command line:

   ssh root@<server_public_IP_address>
   

   If this is your first time connecting to the server, you will get this unknown host warning:

   The authenticity of host '89.169.132.223 (89.169.132.223)' can't be established.
   ECDSA key fingerprint is SHA256:DfjfFB+in0q0MGi0HnqLNMdHssLfm1yRanB********.
   Are you sure you want to continue connecting (yes/no/[fingerprint])?
   

2. Type yes into the terminal and press Enter.

3. Enter the password you specified when creating the server and press Enter.

1. See the description of the CLI command for associating a BareMetal server with a backup policy:

   yc backup policy apply --help
   

2. Get the ID of the policy you want to associate your server with:

   yc backup policy list
   

   Result:

   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   |          ID          |      FOLDER ID       |  NAME   | ENABLED |     CREATED AT      |     UPDATED AT      |
   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   | abc7n3wln123******** | ghi681qpe789******** | policy1 | true    | 2023-07-03 09:12:02 | 2023-07-03 09:12:43 |
   | deflqbiwc456******** | ghi681qpe789******** | policy2 | true    | 2023-07-07 14:58:23 | 2023-07-07 14:58:23 |
   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   

   Create a new backup policy as needed.

3. Get the ID of the server to associate. To do this, go to the relevant folder in the management console and select BareMetal from the list of services. The IDs are specified in the server list, the ID field.

4. Associate the server with the backup policy, specifying the policy ID:

   yc backup policy apply <policy_ID> \
     --instance-ids <server_ID>
   

   Where --instance-ids is the ID of the BareMetal server being associated with the policy.

For more information about this command, see the CLI reference.

Run this command, specifying the backup policy and server IDs:

yc backup policy execute \
  --id <policy_ID> \
  --instance-id <server_ID>

Wait for the operation to complete.

You can also run this command in asynchronous mode using the --async parameter and track the backup process using the yc backup resource list-tasks command.

1. Get a list of backups for the server, specifying its ID:

   yc backup backup list \
     --instance-id <server_ID>
   

   Save the backup ID.

2. Restore your server from the backup, specifying their IDs:

   yc backup backup recover \
     --destination-instance-id="<server_ID>" \
     --source-backup-id="<backup_ID>"
   

   The recovery of your BareMetal server will start. Wait for it to complete.

   You can also run this command in asynchronous mode using the --async parameter and track the backup process using the yc backup resource list-tasks command.

   For more information about the yc backup backup recover command, see the CLI reference.