Solved

I have a single VBR server, using a Data Domain as a repo, and it’s running on VMware. We are migrating from VMware to Nutanix AHV. We’ve already migrated a couple hundred VMs already, and now I’m getting down to needing to move the Veeam server.Doing the migration results in some downtime - the migration process requires that new NIC drivers, etc be installed on the VM. I can easily set the services to manual for that duration, and then restart them when it’s done. BUT … is that the best way to do this? I considered installing a new VBR server natively on Nutanix, and then (somehow) migrating all jobs, etc to it. But the problem is, I only have 1 repo, and I know that multiple VR servers shouldn’t share the same repo. Don’t wanna risk corrupting anything.Has anyone else done this? (migrate a VBR server from one hypervisor to another) If so, what did you do? What should I look out for. Any advice appreciated.

Hello,I noticed something very peculiar. We use the Infrastructure Appliance v13.0.1.1071 for VMware Proxies and hardened repositories. The Backup Server is a Windows box running same version.Every night, we get an eMail saying that check for updates was successful for the Windows Backupserver but failed for all the appliances.When we enable the WebGUI on the appliances and login to their WebGUI’s on port 10433, we go to “Updates” which will say that the last check failed. But when we click on “Check for updates” it works fine. Updates are found, downloaded and installed. All good.So what’s the difference between the automatic daily checks and clicking on “check for updates” on each appliance? We never see the firewall dropping outbound traffic from the appliances around the time the automated daily update checks are done. And the Veeam backup Server (Windows) is the only one, every day, which has no problems checking for updates.The fact that manual checks and patch installs work fine

Hi all,I am currently encountering an issue when backing up a very large NAS.Each file share is over 100 TB, and there are more than 3 backup jobs. The backup process has been running for 140 hours and is still only around 10-15% complete.We are currently backing up from a Nutanix file share and using the “Backup directly from file share” method in Veeam. I have split the proxy into two. The first proxy uses the VBR server itself, and the second proxy uses a VM from Nutanix.Is there another way to make the file share backup process faster? Or has anyone else experienced something similar? Because at this point, the backup process will not meet the RPO.  

Hi,I needed to open a support case, however, when clicked on “Open a case” button I was presented with https://www.veeam.com/upgrade.html?return_url=https%3A%2F%2Fmy.veeam.com page requesting additional details to upgrade my profile. Filled out the form, clicked on “Upgrade profile” button - the page basically just refreshes with my data in it, doesn’t proceed further. Tried several times, also in a different browser.Thank you!

we have initiated veeam replication job from pr site to dr site and failover to dr site,at dr site after failover we imported vm to VCD and renamed vm to new one and makes changes to replica on VCD,after this we failback to production and commit failback,but changes done on dr site vm are not showing up on pr site vm, what could be the possible issues.  

Hi everyone,I have a SureBackup issue and I’m trying to understand the IP selection behavior.SetupRepository server has two NICs:Management NIC 192.168.10.191 Has gateway Domain profile iSCSI NIC 172.16.100.11 No gateway No DNS Used only for iSCSI to Synology ProblemSureBackup fails with: Failed to connect to the endpoint [172.16.100.11:2500]Veeam is trying to connect to the iSCSI IP instead of the management IP.What I verified VBR can connect to 192.168.10.191:2500 → OK VBR cannot reach 172.16.100.11 → expected VeeamTransportSvc is running Port 2500 is listening Firewall rule for 2500 exists iSCSI NIC has no gateway Management NIC has lower metric Windows DNS API returns192.168.10.191172.16.100.11So management IP is first.  

Hey guys,I’m installing a VM on our Synology NAS to act as a Veeam Hardened Repo. I already had it before but now doing it trough Infrastructure Appliance.When I start the installation I get’s stuck in this process: Any recommendations for it? 

Hello,I’m currently planning to migrate from Windows VBR to VEEAM VSA. I’m currently working with tape library, when i installed the VSA, and logged via the WEB interface, i was amazed that the console doesn’t support adding tape servers (Am i missing something ?)Installing the desktop console will fix this ? the desktop client support creating tape libraries ?If working with the client desktop console, the MFA is still supported? we can benefit from the update feature of the VSA or updating the console should be manually ? is there a way to disable the VSA Backup and replication WEB UI to keep only the console working ?Thanks in advance

Hello everyone! So currently we have deployed VBR 12 CE on a virtualized Windows machine running on Proxmox VE 8.4.11. We are backing up our OES Server running on version 24.3.3. We want to be able to backup our OES Server including the network volumes running on NSS and all the metadata for the files on these volumes. Currently we are only doing VM backups. Is this enough to backup the metadata?If not, what would be the best way to ensure the metadata is getting backed up aswell?Is it possible to perform File level restores in this configuration? Thank you, Nico

Do we have a date and location for the next VUG session ? I would be happy to help.

Does anyone know if the issues with adding a workgroup (non-domain) host is limited just to VSA? Or are the same requirements in the Windows version of v13?

I am running Veeam V12 in a vSphere 7 environment and trying to upgrade to 12.3.2.4465. I mount the ISO, run setup and click Upgrade. The upgrade fails every time with the following message."An error has occurred: The system cannot open the device or file specified". I click ok to the message and the upgrade stops. We identified Possible OS or Windows Installer cache corruption.Potential missing or inaccessible .msi files.Potential ISO corruption or mounting issue. Would it be possible to move to a virtual appliance  instead of preparing  a new Windows Server, install the same or newer version of Veeam Backup & Replication, and restore configuration backup to this new server? Please advise.

I am trying to deploy Veeam Data Platform v13 on my windows server however i am getting the error “License is not valid for this product” when attaching the license to it before the deployment. Deployment cant proceed like the previous versions with no license.The foundation license was purchased late September before V13 was released so I suspected that was the case, I went into the license portal and generated a new license for V13 however the same error occurred. I have the windows defender the Kaspersky antivirus disabled to avoid having any error in deploying the license however I am stuck here.

I have ran a backup for the microsoft exchange, now i am testing the restore. We have deleted an email from the inbox. Now I have selected restore application item, microsoft exchange mailbox, the veeam explorer for microsoft exchange opened, I went to the mailbox, selected the email and started the restore. Step by step i added the target mailbox that i want to restore to, selected the onprem microsoft exchange server, i specified the admin user that has access to the exchange server, it didnt automatically populate, so i added the mailbox server manually and selected restore to original folder, is that correct? It is stuck at validating for a whileI am following the guide step by step : https://helpcenter.veeam.com/docs/vbr/userguide/restore_to_onprem.html?ver=13

We’re planning a large-scale migration of Veeam Backup for Microsoft 365, moving the object repository from one S3 backend to another S3 backend (cluster to cluster). We’re talking about approximately 1.2PB of data.The challenge: we want to complete the migration without losing restore points / effective retention, and without duplicating the storage footprint during the retention period (duplicating 1.2PB is not an option).I’d like to ask the community:1️⃣ Has anyone performed an S3 → S3 migration of VB365 data at this scale? What approach worked for you (storage-level replication, incremental sync with aws s3 sync, rclone, endpoint switch, etc.)? What “gotchas” did you encounter (eventual consistency, versioning, object lock, throttling, API limits, lifecycle policies, etc.)? How did you validate that the backup chain / restore points remained intact? 2️⃣ Metadata / internal structure in S3 Does anyone have detailed knowledge of what metadata Veeam relies on when storing VB365 da

Hi Veeam Experts,I am trying to install the Veeam Software Appliance on a bare-metal server.The installer detects the disks and creates the partitions during the Rocky Linux setup, but it stops at the Installation Summary with a “Kickstart insufficient” error and doesn’t proceed further.I have tried both GUI and CLI installations, but the installation is not proceeding further.Could you please advise on troubleshooting steps? Regards,Dhanapal

Bonjour, J’obtiens une erreur lors de la mise à jour du client linux :W: Une erreur s'est produite lors du contrôle de la signature. Le dépôt n'est pas mis à jour et les fichiers d'index précédents seront utilisés. Erreur de GPG : https://repository.veeam.com/backup/linux/agent/dpkg/debian/public stable InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C5A1CF329BB5AC67W: Impossible de récupérer https://repository.veeam.com/backup/linux/agent/dpkg/debian/public/dists/stable/InRelease  Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C5A1CF329BB5AC67 curl https://repository.veeam.com/keys/veeam.gpg | apt-key addNe résoud pas.Une solution svp ? Flamby

Environment: Windows 10 / 11 (Desktop edition) Attempting to install Veeam Agent / Veeam Backup components Description:While trying to install Veeam, the process fails immediately with the following runtime error: An error has occurred: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.Translated: “This action is only valid for products that are currently installed.”The installer runs, but the product does not appear in Programs & Features. Previous versions of Veeam were fully removed, including all files, services, and registry entries. Even after a clean install attempt, the installer fails silently or reports this error.Steps Taken: Verified that all previous Veeam installations were removed. Cleared registry entries related to Veeam under: HKLM\Software\Veeam HKLM\Software\Wow6432Node\Veeam Deleted leftover installer files and MSI cache entries: C:\Windows\Installer\*Veeam* C:\ProgramData\Veeam C:\Program Files\Veeam C:\Pr

Hello,we have been used company certificate into VBR console in main menu …but now we have issue with agents managed by VBR8/10/2025 10:44:54 PM :: Error: Managed session has failed: Failed to validate remote certificate  any hints, how to fix that I will appreciatethank you 

Veeam Microsoft 365 Community Edition Corrupt adb.log file corrupt. Does anyone know how to fix corrupt adb.log files? I already submitted a ticket but since its the Community Edition, I doubt I will get assistance.

Due to some issues with the PostGre SQL database of Veeam B&R CE, I had to uninstall and reinstall Veeam B&R CE. After sucessful installation, I imported the configuration Backup file. Everything worked fine, I had all my Backup Jobs, my Backup Infrastructure and my Physical Infrastcture restored. I was very happy that everything could be restored so easily. But the next day I had some failed Backup jobs in the History. Two servers (no VMs) couldn´t be backuped because of a strange error message:Warning Failed to connect to XXXXXXXX Details: Cannot find package version for component EpAgent package Msi platform X64. OK, it looks like Veeam B&R had some issues to connect with the Agent on this servers. So I uninstalled the Agent on the Server and tried to install the Agent via B&R once again.But it always failed. Veeam B&R can´t install the agent because it can´t find the “EpAgent package Msi platform X64”. It´s no issue from the server I want to backup, because a di

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Hi,Is anyone able to assist here? I’m trying to upgrade to Veeam 13, as part of the overall upgrade I have to upgrade V Orc from my current version 7.1 to 7.2. However, all that I can see in the previous versions is:But the pre-req explicitly says:Upgrade to Orchestrator version 7.2.1 is supported from Orchestrator version 7.2 only; upgrade from Orchestrator versions 7.1, 7, 6, 5 and 4 to version 7.2.1 is not supported:To learn how to manually upgrade from Orchestrator version 7.1 to 7.2, see Veeam Recovery Orchestrator 7.2 User Guide.  However, I’m unable to find the 7.2 version I need to upgrade to 7.2.1. Any help would be appreciated as the Veeam downloads are clearly not fit for purpose. Many thanks,LGH.

Subject: VM Replication Suffix Name IssueSteps how to reach Replica Name Suffix path.Go to: Select Replication → Select Job Name → Right-click → Properties → Step 5 → Job Settings → Replica Settings.Basically, I set it as _repl_VRO, but it is automatically taking _replica instead.If anyone else has faced this issue, please feel free to share your experience. This is from VBR side : Image 1 (Here, you will find the Replica Name Suffix.) This is from VCenter side : image 2RegardsSumit

Hey, I am a new VRO user, and I have just setup my vro server and I am ready to test orchestration plans. I'm running into an issue, and I was hoping that the forum could assist.I have a Prod site VBR server.with a DR site with simple VBR for replication purpose.In same network 3rd site (new machine) with VRO server included embeded components , VBR, ONE,VRO I have connected both vcenters in the configuration. So if i connect only my DR site VBR and added both Vcenter into VRO inventry is it work.Please let me know if you need any other information, I am happy to share with you.