Discussion Boards

I was trying to upgrade the Veeam Enterprise Manager to v12.3.2.4165, I noticed the version is showing 12.3.2.3617 on the Upgrade page.I view detailed information about Enterprise Manager and its components, the Veeam Backup Enterprise Manager Service build: 12.3.2.4165Veeam Catalog Data Service build:12.3.2.3617Web Site Information Build: 12.3.2.3617bugs?

Hi there,I’m currently in an greenfield V13.0.1 deployment, based on the Appliance.After enabling Remote Access in the Host Management Console of the VBR system - it’s mentioned, that this will be enabled after Security Officers approval and for 8 hours… We did this yesterday. This morning, 12-14 hours later, it was still enabled.  Unfortunately I didn't checked, if it’s only a visible bug or if the service / or Port 22 is really still open. I will check this tomorrow and give another feedback. If this is the case, I will open a support ticket for it.Have anyone seen the same behaviour? Thanks and best, Markus

hello Hi, can you help me please? I have a problem with a SureBackup job in Veeam version 12.3.2.4165. When creating a script, I entered an invalid character, and Veeam let it through, but I can't delete, modify, or disable the job. I've already entered several scripts via PowerShell, but it won't delete the job. Any ideas on how I can delete it?  

Hi Community, Those currently using the Google backup appliance for GCP environment backups, have you recently encountered this type of update behavior? Previously, updates were applied automatically with just one click and also option works Schedule updates through the updater, but now I see an update prompt like in the attached screenshot.  Has anyone performed this update recently? If yes, please share your experience and any best practices.I want to plan this properly and avoid any disruption.

I get the error “30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'                             b4634265-9228-4a5e-9d95-2c12313e89c6”This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… How do I fix this? 

Hi Community, We have a Synology NAS storage in our environment and would like to confirm the following: Is there any possible way to add Synology NAS storage to Veeam Backup? After adding Synology NAS storage to Veeam, is there an option to send data from Synology storage to Google Cloud Storage (Object Storage) through Veeam? Please advise if this approach is supported and share any best practices or documentation that can help us implement this. Thank you for your assistance.

Model: NUC12WSHi5Processor type: 12th Gen Intel(R) Core(TM) i5-1240PMemory: G.Skill RipJaws DDR4 SO-DIMM Series 64GBStorage: SAMSUNG 980 SSD 1TB PCle 3.0x4, NVMe M.2 2280Network: Intel Ethernet Controller I225 SeriesVMware vSphere Edition: ESXi-8.0b-21203435-standard (VMware, Inc.)Veeam Backup and Replication Edition: 12.0.0.1420PreparationDownload VMware-VMvisor-Installer-8.0b-21203435.x86_64.isoDownload VMware-VCSA-all-8.0.0-21457384.isoDownload Veeam Backup and Replication v12 isoVMware vSphere 8 Enterprise Plus licenseVMware vCenter 8 Standard Edition licenseVeeam Data Platform Advanced licenseRemark: When you try to install ESXi 7.0 or 8.0 on a system with 12th Gen Intel 1240 CPU, the installation fails with the following PSOD. You need to follow the following steps to install the ESXi 8.0.Fatal CPU mismatch on feature "Hyperthreads per core"Fatal CPU mismatch on feature "Cores per package"Fatal CPU mismatch on feature "Cores per die"InstallationCreate a bootable USB drive with ES

Hi all,i am facing problems running veeam software appliance vm on esxi .when i run vm mounting iso file ,its says uefi mode needed to run but uefi mode is already enabled,esxi version is 8.0 u3,please help!sohaib

Hello.I tried to uninstall 6.3.2.1205 on Windows Server 2019. Control panel / Uninstall programs... Uninstallation reported that there are more users logged in. I clicked cancel uninstallation. Veeam disappeared from list of installed Programs. When I tried to install 6.3.2.1302 the error pops up »The installation cannot be updated automatically. Please contact Veeam support for assistance with manual update. «I did several reboots. I removed Veeam folders from Program Files and ProgramData, I removed Veeam key from registry (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam). Still “cannot be updated…”How can I convince Veeam Agent installer that I do not want to update. I just want to freshly install or repair installation.Regards, Tomaž

Can we get backup status for VDC M365 using powershell like in VBR?

Backup Job using Storage Snapshot Unable to Find Ontap SnapMirror Relationship for Secondary Target. Backup finished with Warning: Cannot find any relevant ONTAP SnapMirror and SnapVault relationships   Storage Replication between the Source and Target destinations is working. I was looking at the job log and saw that Veeam was able to identify Primary SnapProtections.   There were lines showing WARNING: Replication of all disk snapshots of vm asdasdfasf is not possible for ‘Snapshot Replication’. Thanks again for your input as to possible reasons why this is happening.  

is it possible to backup exchange  calendars, and SSO using Azure AD in veeam m365? thanks in advanced 

Can we use Veeam Backup Replication to backup Azure VM?

Hello Community,I encountered the following error while performing a restore operation: 8:26:00 PM Error: bad allocation Failed to upload disk. Skipped arguments: [EmulatedDiskSpec]; Agent failed to process method {DataTransfer.SyncDisk} What I’ve tried so far:Verified network connectivity between components. Checked available storage space on the target. Restarted the Veeam Backup service.Despite these steps, the error persists. Has anyone faced this issue before? What could be causing the bad allocation error during disk upload, and how can I fix it? Any insights, troubleshooting steps, or best practices would be greatly appreciated.   

Hi,My backup job, for instance, XYZ fails with these messages:   Question: What could cause snapshot creation to fail in Veeam Backup for Google Cloud, and what should I check first?   ​

I have three machines, one, an old Windows 10 (22H2 19045.6332) box and two Windows 11 (24H2 26100-6899) boxes.  All are being backed up with nightly incremental and weekly full using the Windows Veeam Agent for Windows Free edition 6.3.2.1302.  Each time a new version of the Agent is released, I install it and create new Recovery Media.Recently, I needed to restore one of the Windows machines, so using Rufus 4.11 and the most recently created Veeam Recovery Media ISO, I created a recovery USB.This USB booted just fine (although it seemed a little slower than other recoveries), but when it got to the initial menu screen, I had no access to either my keyboard or mouse.  I tried re-creating this on both other machines and both had problems; Windows 10 had not network connectivity and the other Windows 11 machine had the same not keyboard, no mouse problem.As I got a warning from Rufus regarding out of date Windows boot files when creating the Win11 USBs, I went back to Rufus 4.5 which di

I upgraded my vmware (esxi and vcenter) from v7 to v8. What i do is install esxi8 and vcenter8 then i migrate the vm under v7 to v8.After migrated to v8 i run the existing job and get error, i can see the vm size is 0 in the backup job. Then i remove the exising vm in the backup job and select same vm in vcenter8. The backup job is running but vbr make full backup, likely vbr see this is new vm.How i can retain existing backup chain so when vbr backup same vm but in the different vcenter the vbr will continue by doing incremental backup? 

Dear Community,I would like to ask about the potential impact of Palo Alto XDR installed on our Veeam Backup & Replication v12 infrastructure, specifically on: Veeam Backup Server (Windows 11) Veeam Backup Proxy (Ubuntu) Could you please advise on the following: Does Palo Alto XDR require any exclusions to ensure stable Veeam operations? What specific paths, processes, or services should be excluded on both Windows and Linux components? Are there any known impacts or compatibility considerations when Palo Alto XDR is active on VBR v12? Your guidance would be greatly appreciated to help ensure both security and optimal backup performance.Thank you.

HiWe have Fortinet Fortimanager and Fortianalyzer running as VMs. Up until last week, these got backup up absolutely fine. We upgraded these from 7.2.11 to v.7.4.8. Since then, the backups have been marked as suspicous with potential malware activity detected.I’m wondering what is going on. It may just be a coincidence but I don’t believe there is any malware.If I mark the backups as clean, the next backup just gets flagged as suspicious. This only happens on these 2 VMs. All other backups are running fine.  Has anyone come across this sort of issue before? Or am I missing something somewhere?ThanksRoy   

Has anyone set up an HA Cluster with Veeam 13 and figured out how to update the SSL for the FQDN that is used when managing a cluster?  When I go to my FQDN the SSL being is used is the Primary Node SSL so the browser shows unsecure.I would have thought this would have been done automagically when setting up the cluster.  Any ideas or thoughts from those that have done this?

Dear Community Members,We are currently running Veeam Backup & Replication v12.3.2.4165 and considering an upgrade to v13.Our environment includes GCP workloads and a GCP appliance integrated with VBR. Will the GCP appliance remain fully compatible and function as expected after upgrading to v13? 

Hi all,I've written and tested a PowerShell script to harden a standalone Windows Server 2025 machine running Veeam Backup & Replication, based on the CIS Benchmarks (Level 1 & 2). I’m sharing it here in case it helps others — feedback is welcome!What the Script DoesThis script configures the server securely without breaking core Veeam functionality. It includes: Account Policies: Max password age, complexity, and lockout thresholds (CIS 1.1.x, 1.2.x) Guest & Anonymous Access: Disabled for better baseline security Audit Policy: Enabled for all major categories (CIS 17.x) Unneeded Services: Disabled (safe defaults — e.g., Print Spooler, Xbox services) Windows Defender: Hardened settings with MAPS Advanced, PUA protection, etc. Firewall Configuration: Enables Windows Firewall with a default deny-inbound policy Allows Veeam ports: TCP 6160–6162, 445 (SMB), 135–139 (RPC) Blocks inbound RDP (port 3389) entirely (as this is often a target surface) SMB Pr