Veeam for Xen Orchestra has been release today 13.1
-
Yes later I did try and it restore the vm along side the original with the "_" a underscore appended to the end of the name of the vm. Original -
Windows Server 2022. Restored -Windows Server 2022_ -
After trying a few more restores the other vms did not get this name change. Not sure why it happened to the one vm, but the other retained their original names and tags.
-
@acebmxer You need two Disk with 300GB
-
@acebmxer You need two Disk with 300GB
If this is a reply to my initial post. I have already got it installed. Where do you see this 300GB requirement?
https://helpcenter.veeam.com/docs/vbr/em/system_requirements.html?ver=13
Disk Selection Logic: When selecting a disk for system and adjacent functions, Veeam Software Appliance automatically chooses an SSD over an HDD, and selects the smaller disk of the two available. The sizing recommendations for Disk 1 below remain valid for the system disk.
Disk 1: 240 GB1 minimum. This disk hosts Veeam JeOS, Enterprise Manager Veeam Backup & Replication software, configuration database and instant recovery cache.
Recommended sizing depends on the number of protected workloads. Sizing also accounts for configuration database growth as you add more workloads to protect:
480 GB1 SSD for small environments (up to a few hundred workloads).
960 GB1 SSD for medium-sized environments (up to a few thousand workloads).
Multi-TB1 SSD for large environments. Larger capacity increases the disk space available to instant recovery cache, allowing for running more machines for longer time.
Note: After Veeam Software Appliance deployment, adding new storage devices or resizing existing ones is not supported. Plan your disk capacity carefully before you start the deployment.Disk 2: 240 GB1 minimum. This disk hosts guest file system catalogs and backups, therefore recommended sizing depends on your backup storage needs. Any additional disks found in the system during Veeam Software Appliance deployment will be automatically joined with Disk 2 into the single Logical Volume Manager (LVM) spanned volume.
This is only backing a few vms around 10 vms, and actual location is to nfs storage.
-
So I ended up going with the Windows B&R as i could net setup the windows mount server when setting up the repo for the backups. It would setup the linux one but not the windows one. This was with using the veeam console from a windows client. So i ended up with the Windows one.
Now after a few backups i am see this warning / error....
8/5/2026 5:34:50 PM Warning : Failed to use CBT: [Task e75c4247-2ee1-7b51-088c-b970ace60f3d (Async.VDI.list_changed_blocks) failed: . SR_BACKEND_FAILURE_460. . Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]First i thought it was because i maped the new job to older backups from Beta v1. So i purged all old backups and started fresh. The full backups were successful. Now on first delta 4 out of 7 vms have that warrning.
This a Veeam issue or xcp-ng?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login