Use t
Use
27 Matching Annotations
- Oct 2025
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
-
Note that VMs can be arranged in VM groups only on Microsoft Hyper-V hosts version 2016 or later.
earlier versions are not supported from v13
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
Add to Backup
Add to backup job
-
Add to Backup
Add to backup job
-
- Dec 2023
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
For example:You configure a replication job with a Microsoft Hyper-V 2008 R2 host used as a source and a Microsoft Hyper-V 2008 R2 host used as a target. VM data is retrieved from the production storage. In this case, the replication job will produce a legacy replica.You configure a replication job with a Microsoft Hyper-V 2012 R2 host used as a source and a Microsoft Hyper-V 2016 host used as a target. VM data is retrieved from the production storage. In this case, the replication job will produce a snapshot replica.Existing Replication JobsAfter you upgrade Veeam Backup & Replication, legacy replication jobs remain as they are. They do not change their type to snapshot replication jobs.After you upgrade Veeam Backup & Replication, replication jobs work as usual. However, if you have legacy replication jobs that use Microsoft Hyper-V Server 2012 host and later as a target, and these jobs were created by Veeam Backup & Replication earlier than 9.0, you will not be able to edit these jobs.Legacy replication jobs can use only the virtual infrastructure as a source of data. Replication from backup is not supported for legacy replication jobs.
hyper-v 2008r2 and legacy replicas are not supported in VBR 12 and vbe 12.1, upgrade is forbidden until it will not be remooved from configuration
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
Unlike the backup server, backup proxies do not require a dedicated SQL database — all settings are stored centrally
important? there are lot of things that we do not install :) postgre as well
-
Before assigning the role of the off-host backup proxy to a machine, you must first add a Microsoft Hyper-V server to the backup infrastructure.
not very important information. possibility of adding hyper-v off-host proxy realy appears only after adding at list one hyper-v host, but I do not think that anybody will try to do it before, because it is usually done from job creation wizard
-
To do this, you must enable the Hyper-V role on this VM (use nested virtualization). For more information, see Nesting Hyper-V with VMware Workstation 8 and ESXi 5 or How to Install Hyper-V on a Virtual Machine in Hyper-V articles
it follows directly from the hyper-v role installation requirement and should be moved near it
-
However, it is not recommended that you use virtualized off-host backup proxies in the production environment.
delete
-
For evaluation and testing purposes, you can assign the off-host backup proxy role to a VM.
delete
-
Versions of a Microsoft Hyper-V host and off-host backup proxy must coincide. For more information, see System Requirements.
relevant only for windows server 2016 and older
-
The role of an off-host backup proxy can be assigned only to a physical machine.
just delete this note
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
x
12.1.0.2131
-
- Feb 2023
-
helpcenter.veeam.com helpcenter.veeam.com
-
2008 R2
the oldest supported version now is 2012, but looks like this without legay replica this sentence lost it's meaning
-
ImportantMind the following exception: you can fail back from the source 2016 host to the target 2012 R2 host only if a VM replica configuration is lower than 8.0.
too specific example. let's delete it or replace with the link to "Supported VM configuration versions for long-term servicing hosts"
-
Source/TargetTarget 2008 R2Target 2012-2022 (the Target OS version must be higher than Source OS version)Source 2008 R2✓✓Source 2012-2022✕✓
not relevant
-
the version of the target host must be equal to or later than the version of the source host:
target host must support configuration version of replica-vm
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
Host and target Microsoft Hyper-V hosts that you select for the replication process must be compatible. For more information, see Supported Platforms for VM Replica Types.
i thonk the better option is to add link to the microsofts documebtation about VM config versions supported by different HV versions or add table from this article and update it every version
Supported VM configuration versions for long-term servicing hosts The following table lists the VM configuration versions for hosts running a long-term servicing version of Windows.
Hyper-V host Windows version 10.0 9.3 9.2 9.1 9.0 8.3 8.2 8.1 8.0 7.1 7.0 6.2 5.0 Windows Server 2022 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✖ ✖ ✖ ✖ Windows 10 Enterprise LTSC 2021 ✖ ✖ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✖ ✖ ✖ ✖ Windows Server 2019 ✖ ✖ ✖ ✖ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Windows 10 Enterprise LTSC 2019 ✖ ✖ ✖ ✖ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Windows Server 2016 ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✔ ✔ ✔ ✔ ✔ Windows 10 Enterprise 2016 LTSB ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✔ ✔ ✔ ✔ ✔ Windows 10 Enterprise 2015 LTSB ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✔ ✔ Windows Server 2012 R2 ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✔ Windows 8.1 ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✖ ✔
-
Host and target Microsoft Hyper-V hosts that you select for the replication process must be compatible. For more information, see Supported Platforms for VM Replica Types.
Sinse now, better to say target host should be compatible with version of virtual machine that we are going to process
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
only
since now we do not have other types
-
Legacy replicas do not use a backup repository for storing metadata.
not relevant
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
Replica from backup is not supported if you replicate data between Windows Server Hyper-V 2008 R2 hosts.
not relevant, 2008r2 are not supported as hv host
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
This is a draft version of the document. Deployment of the draft version to Help Center is disabled. Legacy Replica On This Page Limitations for Legacy Replicas For legacy replicas, Veeam Backup & Replication uses an approach that is similar to reverse incremental backup. During the first run of a replication job, Veeam Backup & Replication copies the VM running on the source host and creates its full replica on the target host. The replica is stored decompressed, in a native Hyper-V format.All subsequent replication jobs are incremental. Veeam Backup & Replication copies only those data blocks that have changed since the last replication cycle. To keep track of changed data blocks for Hyper-V VMs, Veeam Backup & Replication uses its proprietary changed block tracking mechanism.At every incremental job run, Veeam Backup & Replication “injects” changes into the replica to rebuild it to the most recent state of the source VM. It also creates a rollback file to store data blocks that were replaced when the full replica was rebuilt.As a result, for every replicated VM, Veeam Backup & Replication produces a full replica and a chain of rollback files. The replica mirrors the latest state of the source VM, while rollback files serve as restore points. If you need to restore a replica to a particular point in time, Veeam Backup & Replication will apply the required rollback files to get you to that point in time.Veeam Backup & Replication creates and maintains the following types of replica files:Full VM replica (a set of VM configuration files and virtual disks)VRB — replica rollback filesVBK — file that stores hash data describing the current state of a VM replica on the target hostAll files of a legacy replica are stored in a dedicated folder on the target volume.Limitations for Legacy ReplicasThe following limitations apply to the legacy replicas:Legacy replicas can use only the virtual infrastructure as a source of data. Replication from backup is not supported for legacy VM replicas.You cannot clone a legacy replication job that replicates a VM from the source Microsoft Hyper-V Server 2008 R2 host to the target Microsoft Hyper-V Server 2012 host or later using the Veeam Backup & Replication console or Veeam Backup Enterprise Manager web UI.
к праотцам
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
After you upgrade Veeam Backup & Replication, legacy replication jobs remain as they are. They do not change their type to snapshot replication jobs.After you upgrade Veeam Backup & Replication, replication jobs work as usual. However, if you have legacy replication jobs that use Microsoft Hyper-V Server 2012 host and later as a target, and these jobs were created with Veeam Backup & Replication earlier than 9.0, you will not be able to edit these jobs.Legacy replication jobs can use only the virtual infrastructure as a source of data. Replication from backup is not supported for legacy replication jobs.
just delete legacy replicas to upgrade
-
You configure a replication job with a Microsoft Hyper-V 2012 R2 host used as a source and a Microsoft Hyper-V 2016 host used as a target. VM data is retrieved from the production storage. In this case, the replication job will produce a snapshot replica.
all replicas are snapshot now, this note looks unnecessary
-
You configure a replication job with a Microsoft Hyper-V 2008 R2 host used as a source and a Microsoft Hyper-V 2008 R2 host used as a target. VM data is retrieved from the production storage. In this case, the replication job will produce a legacy replica.
HV2008r2 from this version is not supported, and coldm't be added, legacy replicas cannot be created, existing 2008r2 hosts, legacy replicas, legacy peplica jobs should be removed to upgrade VBR
-
-
helpcenter.veeam.com helpcenter.veeam.com
-
This type of migration is only possible if the original device is connected to Veeam Backup & Replication and powered on.
let's add ''..., and the original shared folder with permissions exists''
-