Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Backup
    • All guides
    • Activating the service
      • Creating and connecting a Linux VM
      • Creating and connecting a Windows VM
      • Reconnecting a VM to Cloud Backup
      • Reconnecting a Linux VM with OS Login to Cloud Backup
      • Updating the Cloud Backup agent
      • Viewing a VM connection status
      • Viewing the backup log
      • Deleting a VM from Cloud Backup
    • Restoring the Cloud Backup agent
    • Viewing operations on service resources
    • Limiting RAM usage by the Cloud Backup agent
    • Viewing backup statistics
    • Setting up Monium alerts
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • Troubleshooting

In this article:

  • Getting started
  • Creating a VM
  1. Step-by-step guides
  2. Compute Cloud in Cloud Backup
  3. Creating and connecting a Windows VM

Creating a Windows Server VM with a connection to Cloud Backup

Written by
Yandex Cloud
Improved by
Danila N.
Updated at August 5, 2026
View in Markdown
  • Getting started
  • Creating a VM

You can back up your Yandex Compute Cloud VMs with supported Windows-based operating systems.

For the proper Cloud Backup agent operation, the VM must meet the minimum requirements.

Getting startedGetting started

  1. Create a service account with the backup.user role or higher.

    You do not have to use a service account when creating a VM using the management console. However, the user creating the VM must have the backup.user role or higher for the folder in which the VM is created.

    Warning

    Starting August 1, 2026, the compute.editor and compute.admin roles get new permissions from the backup.user role, allowing them to connect VM instances to Yandex Cloud Backup, link and unlink them from backup policies.

    If you do not plan to connect your resources to Cloud Backup and do not want to grant such permissions to your users, you can proactively disable these features using the backup.denyActivation authorization policy assigned to your folder, cloud, or organization. For more information on how to create an authorization policy, see Creating an access policy for a resource.

  2. Set up network access for your VM.

Creating a VMCreating a VM

Management console
CLI
  1. In the management console, select the folder where you want to create a VM.

  2. Navigate to Compute Cloud.

  3. In the left-hand panel, select Virtual machines and click Create virtual machine.

  4. Under Boot disk image, select an operating system supported in Cloud Backup.

  5. Under Location, select an availability zone where your VM will reside.

  6. Under Disks and file storages and Computing resources, set up your VM.

    The minimum resource specification required to install and correctly run the Cloud Backup agent is as follows:

    • Free disk space:

      • For Linux-based VMs: 2 GB.
      • For Windows-based VMs: 1.2 GB.
    • RAM: For backups, 1 GB of RAM is required per 1 TB of backup. The RAM requirement depends on the amount and type of data processed by the Cloud Backup agent.

    Tip

    Installing a Cloud Backup agent is a resource-intensive operation. If you want to use a VM in the minimum possible configuration or, for example, a VM with a vCPU performance level below 100%, we recommend increasing the VM's resources during the Cloud Backup agent installation.

    To speed up data backup and recovery, the Cloud Backup agent tends to consume significant amounts of RAM of the resource it is backing up. The agent can even use up all the available RAM, which in some cases may disrupt the resource's other services and make it impossible to complete the backup or recovery process.

    To prevent such issues, limit the amount of data the agent caches in RAM.

    Note

    Limiting the Cloud Backup agent's use of RAM may slow down the backup and recovery operations.

  7. Under Network settings:

    1. Choose a subnet in the selected availability zone.
    2. In the Public IP address field, select Auto.
    3. Select a security group configured to work with Cloud Backup.
  8. Activate a backup:

    1. Enable Backup.

    2. Select Cloud Backup.

    3. Under Cloud Backup, click Select policy and, in the list that opens, select the backup policy that will be used by Cloud Backup to work with the VM.

      Optionally, click Create policy to create a new policy.

    To create a new VM with a Cloud Backup connection, your account must have the backup.user role or higher for the folder you are creating the VM in.

    Note

    If your account does not have the backup.user role or higher, you can connect the VM to Cloud Backup using a service account which has that role.

    To do this, expand the Additional section and select the service account under Service account. If required, create a new service account and assign it the backup.user role.

    For more information, see Connecting Yandex Compute Cloud VMs to Cloud Backup.

  9. Under General information, specify the VM name and description. The naming requirements are as follows:

    • Length: between 3 and 63 characters.
    • It can only contain lowercase Latin letters, numbers, and hyphens.
    • It must start with a letter and cannot end with a hyphen.

    Note

    The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.

  10. Specify the other VM parameters as needed.

  11. Click Create VM.

When the VM switches to the Running status, the Cloud Backup agent will start installing on it. This may take from 10 to 30 minutes.

Once you install the agent, the Cloud Backup VM will be added to Cloud Backup in the Virtual machines tab and associated with a backup policy.

If the VM is not automatically associated with the policy, associate it manually.

  1. Select a folder:

    yc resource-manager folder list
    

    Result:

    +----------------------+--------------------+------------------+--------+
    |          ID          |        NAME        |      LABELS      | STATUS |
    +----------------------+--------------------+------------------+--------+
    | wasdcjs6be29******** | my-folder          |                  | ACTIVE |
    | qwertys6be29******** | default            |                  | ACTIVE |
    +----------------------+--------------------+------------------+--------+
    
  2. Select a subnet:

    yc vpc subnet list --folder-id <folder_ID>
    

    Result:

    +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+
    |          ID          |           NAME            |      NETWORK ID      | ROUTE TABLE ID |       ZONE        |      RANGE      |
    +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+
    | b0c6n43f9lgh******** | default-ru-central1-d     | enpe3m3fa00u******** |                | ru-central1-d     | [10.***.0.0/24] |
    | e2l2da8a20b3******** | default-ru-central1-b     | enpe3m3fa00u******** |                | ru-central1-b     | [10.***.0.0/24] |
    | e9bnlm18l70a******** | default-ru-central1-a     | enpe3m3fa00u******** |                | ru-central1-a     | [10.***.0.0/24] |
    +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+
    
  3. Create the init.ps1 file with a script for installing the Cloud Backup agent on your VM:

    #ps1_sysnative
    echo 'Starting to execute backup agent installation'
    Invoke-WebRequest https://storage.yandexcloud.net/backup-distributions/agent_installer.ps1 -UseBasicParsing | Invoke-Expression
    
  4. Create a VM:

    yc compute instance create \
      --folder-id <folder_ID> \
      --name <VM_name> \
      --zone <availability_zone> \
      --network-interface subnet-name=<subnet_name>,nat-ip-version=ipv4,security-group-ids=<security_group_ID> \
      --create-boot-disk image-id=<image_ID>,size=<boot_disk_size> \
      --cores 2 \
      --core-fraction 100 \
      --memory 4 \
      --service-account-name <service_account_name> \
      --metadata-from-file user-data=<path_to_file_with_script>
    

    Where:

    • --name: VM name.

      Note

      The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.

    • --zone: Availability zone corresponding to the selected subnet.

    • subnet-name: Name of the selected subnet.

    • security-group-ids: ID of the security group configured to work with Cloud Backup.

    • image-id: OS image ID. List of supported Windows-based operating systems.

    • size: Boot disk size.

    • --cores: Number of vCPUs in the VM.

    • --core-fraction: Guaranteed vCPU share, in %.

    • --memory: VM RAM size.

    • --service-account-name: Name of the service account with the backup.user role or higher.

    • --user-data: Path to the previously created file with a script for installing the Cloud Backup agent on your VM.

    In this example, we are creating a VM running Windows Server 2022:

    yc compute instance create \
      --name my-vm \
      --zone ru-central1-b \
      --network-interface subnet-name=my-vpc-ru-central1-b,nat-ip-version=ipv4,security-group-ids=abcd3570sbqg******** \
      --create-boot-disk image-id=fd890bh2sapn********,size=60 \
      --cores 2 \
      --core-fraction 100 \
      --memory 4 \
      --service-account-name backup-user \
      --metadata-from-file user-data=init.ps1
    

    Result:

    done (46s)
    id: abcdho6nspdk********
    folder_id: wasdcjs6be29********
    created_at: "2023-10-09T14:57:06Z"
    name: my-vm
    ...
    placement_policy: {}
    

    Note

    The commands yc compute instance create | create-with-container | update | add-metadata support substitution of environment variable values into VM metadata. When you execute a Yandex Cloud CLI command, these values, specified in the user-data key in $<variable_name> format, will be substituted into the VM metadata from the environment variables of the environment the command is executed in.

    To change such behavior, i.e. to provide a variable name to the VM metadata in $<variable_name> format rather than take the variable value from the CLI command runtime environment, use the two-dollar syntax, e.g., $$<variable_name>.

    For more information, see Specifics of providing environment variables in metadata via the CLI.

When the VM switches to the Running status, the Cloud Backup agent will start installing on it. This may take from 10 to 30 minutes.

Once you install the Cloud Backup agent, the VM will be added to Cloud Backup in the Virtual machines tab and you will be able to associate it with a backup policy. For more information, see Linking a resource to a backup policy

Note

If the Cloud Backup agent fails to install within 30 minutes, contact support for troubleshooting.

Useful linksUseful links

  • Connecting an existing Windows Server VM to Cloud Backup
  • Connecting an existing Linux VM to Cloud Backup
  • Linking a VM to a backup policy
  • Restoring a Yandex Compute Cloud VM or Yandex BareMetal server from a backup
  • Deleting a backup
  • Creating a backup policy

Was the article helpful?

Previous
Creating and connecting a Linux VM
Next
Connecting an existing Linux VM
© 2026 Direct Cursus Technology L.L.C.