Solved

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

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.

I am preparing to update Veeam for Microsoft 365 from 8.1.2.180 to 8.3.0.2201 and I just want to make sure I am all set in case there are any issue after the update. I don’t believe I have any PostgreSQL or NATS setup that I can recall from when I set this up. I suppose if I do it is all default. It also appears there is no config backup option in this program. We do back up this server, but it does hold both V365 and VBR, so not sure if that complicates things from a restore standpoint if there is a problem with the V365 update.I’m probably overthinking it, but it is the first time I will be updating V365 and just want to make sure my jobs and repositories don’t break or need adjustments after the update.The main reason for this update other than the prompt for an update was that we received a one time email last week saying “License update interrupted: License contract has been terminated” even though subscription and user licenses are active as far as we can tell. Possibly a glitch

Hi all,I’m looking for best practices / guidelines for integrating Kasten K10 with an existing Veeam Backup & Replication (VBR) environment, specifically around network design and traffic flow.Current Veeam B&R setup (simplified)VLANs / networks in use MGMT VLAN – control/management traffic iSCSI VLAN Backup Traffic VLAN – L2 only, dedicated NICs All control-plane communication happens over the MGMT VLAN, while all heavy data movement is isolated to the Backup Traffic VLAN.Veeam components VBR Server Connected only to MGMT VLAN Proxy Servers Connected to MGMT, iSCSI, and Backup VLANs Integrated with Dell PowerStore via the Veeam plugin Data path: SAN → Proxy → Repository over Backup VLAN Repository Servers Connected to MGMT VLAN and Backup VLAN Kasten K10 on OpenShift Deployed via the Operator on worker nodes Integrated with multiple storage systems via CSI Configured locations: S3 object storage Existing Veeam B&R repositories Pol

Hello,i would like to ask, if somebody is not experiencing that issue, that big environments have issue with SSL connection? we have all in one boxes - VBR, VEM and postgresql is on the same machine at the end of postgresql.conf #------------------------------------------------------------------------------# CUSTOMIZED OPTIONS#------------------------------------------------------------------------------# Add settings for extensions heressl = onssl_cert_file = 'backup_server.crt'ssl_key_file = 'backup_server.key'ssl_ca_file = 'backup_root.crt' in svc_veeambackup.log we see[02.03.2026 11:40:10.307]    <35>   Error (3)    0: Breaking connector[02.03.2026 11:40:10.307]    <35> Warning (3)    Failed to obtain connection: [Failed to connect to [::1]:5432]. Attempt 1 of 20. in pg_hba.conf is preferred connextion via ssl# IPv4 local connections:hostssl    all             all             127.0.0.1/32            scram-sha-256host    all             all             127.0.0.1/32      

Hi,we are planning to use the Veeam Data Cloud for Salesforce Backup. We need to keep backups for 2 years. What, if we decide to switch the backup-partner. For example Salesforce native backup? We cancle our subscription. Fair-Use-Policy will delete the backups after 30 days, correct? What options do we have, to keep  the backups as long as our requirements are? The same question would be, if we decide to use veeam backup for m365 in the data cloud. Here we would have onedrive files, with a retention time of 2-10 years.  We do not plan to quit anything, but we need a valid exit strategie if we decide to use a cloud product. 

Hi everyone,I am currently reviewing the design of our Veeam Backup & Replication server and would like to follow best practices for disk layout.At the moment our VBR server is a VM with the following specs: 8 vCPU 32 GB RAM Windows Server Local SQL instance Only one virtual disk (C:) which is a VHDX located on HDD storage Currently everything is located on this single disk, including: Veeam installation SQL database Veeam logs Veeam catalog configuration backup Windows OS I am considering adding an additional virtual disk located on SSD storage and moving the Veeam-related components there to improve performance and follow recommended architecture.My questions are: What is the recommended way to migrate components from the existing C: disk to the new disk without breaking the installation? Which components should ideally be moved to the new disk (SQL DB, catalog, logs, etc.)? Is it necessary to stop Veeam services during the migration? Are there any known p

Hi all. Running Windows Server 2019 as a standalone Hyper-V server. The server is in a workgroup.I have installed the community edition of VBR 12, and configured my backup repository.When trying to configure a new Hyper-V backup job, Veeam gives me a message to say that it cannot connect to the ADMIN$ share. However, if I type \\localhost\ADMIN$ into the run box, then the folder does open.I’ve tried setting my host name to localhost, to the server name and to it’s IP address. I’ve also tried with the current logged in credentials, and have tried by enabling the administrator account.Any help would be appreciated.Thanks, and have a great weekend!

Good day Running Veeam Community v12 with a VMWare environment. I am running a backup of 3 VMs. Since I installed Veeam I cannot do a backup copy of a job for one of my servers. The 2 other servers that I run a backup copy and send it in a remote location works but that server I always get this error: Processing [server name] Error: Times out waiting for NFS async IO block callback. Timeout: 180000 msec Failed to download disk 'filenameofserver-flat.vmdk'. Shared memory connection was closed. Failed to upload disk 'filenameofserver-flat.vmdk' Agent failed to process method {DataTransfer.SyncDisk}.Some restore points were not processed The local backup works but I cannot get the backup copy to workI created a different backup job for this server alone but I also get that error. The option I was thinking to do is to do a backup job just for this but i’d like to figure out why only that server on the same host as the 2 other servers is causing me this problem. Thanks for the help

Hello everyone,After upgrading Veeam Backup & Replication from version 12.3.2.4165 to 13.0.1.1071, we also upgraded Veeam Plug-In for Microsoft SQL Server using the ISO 13.0.1.1071, which installed Veeam Plug-In version 13.0.1.180.The upgrade process completed successfully without any visible errors.However, after the upgrade, SQL Server backups are no longer running successfully.All SQL backup jobs are now failing with the following error:Error: [Microsoft][ODBC Driver 17 for SQL Server] Database is invalid or cannot be accessed Before the upgrade, backups were working correctly with no issues.Has anyone experienced a similar issue after upgrading to Veeam 13?Any suggestions on what to check would be greatly appreciated.Thank you in advance for your help.

Hello everyone,I would like to get some advice regarding the optimal Veeam architecture for a two-site environment.Infrastructure Hyper-V environment Two locations: Vienna Novi Sad Sites connected with 1 Gbps IPSec tunnel Repository available in both locations Current components: Backup Server Hyper-V hosts acting as on-host proxies Repository Vienna Repository Novi Sad Current designRight now the backup jobs run like this:VMs from both locations → backup to Vienna repositoryThen we run Backup Copy jobs from:Vienna Repository → Novi Sad RepositoryThis means that VMs located in Novi Sad follow this path:Novi Sad VM → Vienna Repo → Backup Copy → Novi Sad RepoSo effectively the data crosses the WAN twice.ExampleVM located in Novi Sad: Backup goes NS → Vienna Backup Copy goes Vienna → NS ObservationDuring the first full backup we see relatively low throughput (~7 MB/s) and Veeam reports Network bottleneck.This is expected since the traffic goes through an IPSec tunne

Hello,I have to configure S3 Wasabi for the first time and I would like to be sure about the configuration.I will use it as backup copy repository with immutability.1) I create the bucket on Wasabi with versionning + object lock enabled2) I create a policy on Wasabi based on https://helpcenter.veeam.com/docs/backu ... positoriesI need the policy "Immutability Enabled and Helper Appliance Configured Beforehand" right ?How could I limit the policy only to the bucket "backupbucket" ? Because if I understand correctly, the policy in Veeam documentation has permission on all buckets.3) I create a new user and assign the policy4) I create the repository to veeam and set the desired immutability.I think I need some help on part 2 to be sure the user can only write to the "backupbucket".Thanks for your help