Discussion Boards

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.

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,We have published VBR plugin to a tenant in VMWare vCloud director for VBR v12. It was successfully published, roles and self service configured. However, when i log into customer tenant from vCloud director and goto veeam protection under more. it pops up Error "Unable to connect to the Veeam backup infrastructure. Please contact service provider". Thanks.Best Regards,Farhan Ali

Need some clarification. On this scenario i have a windows server that run an app and i want to backup the whole server (in case we ever need to restore it i can just dump it on a vm) but i want to make this whole backup daily and immutable. For what i understand there is a set number of days for immutability but not sure how does this work for daily backups.  Whats the correct settings to do on this case?  Are these backups like whole backup every day or its incremental only? Thanks.

Hi everyone, I’d like to get some feedback before deploying Veeam v13 in our environment. I’ve been tied up with other projects over the last six months, so I haven’t tested or worked with v13 yet. Our infrastructure is fully virtualized. We currently run two VMs: One VM running Veeam, performing daily jobs to an external Ubuntu hardened repository One physical server running Veeam, backing up everything to its own ReFS-based storage  My questions are: What is the best approach for deploying v13 — on a physical server or a virtual machine? Is it possible to use hardened storage with Veeam on the physical server?  Thanks in advance for the input!

Hello,I’ve created a bootable USB Drive using the “Create Recovery Media” tool and wanted to test the bare metal recovery. But every time I boot from the USB stick a Windows Recovery screen appears saying the kernel is missing or contains errors.And after searching for this issue I found this post which describes the exact problem I have: https://superuser.com/questions/1804131/windows-10-re-kernel-is-missing-or-contains-errorsPS: I’m using Veeam Agent for Microsft Windows to create the backups

I have a backup job for my desktop computer that has 3 SSDs, with the C drive being an NVMe drive. Once the job begins, NVMe usage jumps to 100% and response time also jumps to the 1000s of milliseconds. I have IO throttling enabled in settings but that doesn’t help. Basically makes the computer unusable while a backup is running because the computer is sluggish and stutters constantly.

Hi Folks,I would appreciate if someone can offer a suggestion on how to troubleshoot the following error: Error: Failed to create snapshot: Backup job failed.Cannot create a shadow copy of the volumes containing writer's data.VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].   This is the result of an attempt to backup a Windows folder, which is on an ReFS disk F: (the folder has about 5 GB of content and the disk F: has 150+ TB of free space).  The backup repository has about 28 TB of remaining capacity.  The repository is on a ReFS disk mounted as disk E:.Stuff that I already tried:Rescanned the backup repository Recreated the backup repository Restarted the backup server Tried to backup other folders on drive F: with same resultsAppreciate any input.Thank you!-sul.

Hi,We have a Malware Detection on our terminal server and all of them come from C:\Users\(Username)\AppData\...Such like the following:[\\?\c:\Users\Username\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\DeviceSearchCache]New files: 1 Deleted files: 2New files: AppCache133660689737733525.txt, Deleted files: AppCache133660298026316423.txt, AppCache133660298053314107.txt, [\\?\c:\Users\Username\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData]New files: 1 Deleted files: 1New files: C02877841121CC45139CB51404116B25_A71D3C9ACFD0888B19B4EAA86FAA4437, Deleted files: 80237EE4964FC9C409AAF55BF996A292_C0427F5F77D9B3A439FC620EDAAB6177, [\\?\c:\Users\Username\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content]New files: 1 Deleted files: 1New files: C02877841121CC45139CB51404116B25_A71D3C9ACFD0888B19B4EAA86FAA4437, Deleted files: 80237EE4964FC9C409AAF55BF996A292_C0427F5F77D9B3A439FC620EDAAB6177, [\\?\c:\Users\Username\AppData\Local\Packages\Microsoft.Windows.Cortan

Hi team, I have a new backup I am running that is failing at the first full. It fails and says that it cannot find a VMDK file that is located in an excluded disk. The error reads: “Processing servername Error: File 'X.vmdk' was not found. This disk is a USB attached storage device, but it was added to vmware as an iscsi drive so that we can exclude it in VBR. I have double checked the disk exclusions and confirmed that I have told the job to only back up the correct disks (the disks that aren’t this USB attached storage). I have also checked the checkbox to remove excluded disks from configuration. The file is present in vcenter. I checked. I can’t figure out what is going on and why this job is failing due to a file that should not even matter because I have excluded from the job, the disk the file is located on.

We would like to ensure that all backups from October 1, 2024, through October 4, 2024, are retained without expiring and remain accessible throughout the year if needed.. How can we achieve this?

Hi Team, My customer has a setup for StoreOnce (3660 with Firmware 4.3.7) and Veeam (12) configured with Veeam Standard license.Scenario 1:Customer tried to take a VM backup to one of a catalyst store which failed due to licensing issue in the logs. However, I did not get any documentation mentioning Veeam standard edition doesn’t support catalyst stores. As per Catalyst store configuration I double checked and its as per HPE standards.Error: “Backup to HPE StoreOnce Catalyst requires valid enterprise edition of Veeam Backup and replication.” Scenario 2:Customer tried to back up the same test VM on StoreOnce NAS share and that passed successfully. Resolution:Could you share me any documentation which says the Veeam standard edition does not support StoreOnce catalyst store? Are there any changes in Veeam that needs to be done to support the above Below are the backup logs captured?      

Cybersecurity is a constant battle, and backups are a prime target. That's why I'm exploring how to integrate Palo Alto's Cortex solution with Veeam to further strengthen.Can you help me with these questions?What kind of integration exists between Cortex and Veeam? Is it a native integration or does it require additional components? What layers of protection does Cortex offer to my Veeam backups? Does it detect threats in real-time, analyze suspicious behavior, prevent ransomware attacks? How does backup scanning work with Cortex? Is it automatic? Can I customize scanning policies? What kind of threats does it detect? Can Cortex protect my backups both on-premise and in the cloud? Does the integration work with different cloud providers? What impact does Cortex have on the performance of my Veeam backups and restores? Should I consider additional resources?

Hello Team,Quick question - Does the Veeam Replication Re-IP concept work only for VM with Single network adapter?What if the replicating VMs has multiple network adapters? The Re-ip cannot be used?Thanks in advance!~ Ravi Kumar S

I have a different error- Failed to index guest file system. Failed to zip folder 'c:\users\.....Appdata\Local\Temp\GuestIndexData.zip. I am seeing the below warning on backup jobs. We have VEM installed so cannot disable Guest indexing. Backup will complete successfully with this warnings. Using Domain admin account for Guest processing and indexing. Warning :Failed to index guest file system. Failed to zip folder 'C:\Users\tn\AppData\Local\Temp\66ddcb73-b3b1-4fea-8333-ffa67ef9aace' to file 'C:\Users\tn\AppData\Local\Temp\66ddcb73-b3b1-4fea-8333-ffa67ef9aace\GuestIndexData.zip'VBRCatalog is saved in C: drive and have 386 GB free of 599 GBVBR 12.1 version VEM 12.1 Please advise.

Hi All,required your help on this issue.We are trying to add a RHEL 8 installation (physical machine) as Linux hardened repository.It fails with error - Veeam transport installation fails on Linux repository. There no ports block or firewall blockingWe are working per article https://www.veeam.com/kb4250, but any other leads  .  

HiWill CDP be compatible with Oracle ensuring transaction consistent replicas?

Greetings everyone...I am working out the resources for physical backup server with local disks. Might I know if my workout is correct?Data size: 30TB (Exchange + File Share)Policy: 30 daily, 4 weekly, 12 monthly, 3 yearlySource: Sangfor HCI (requires to install agent), single siteAs refer to VSE https://calculator.veeam.com/vse/Backup Server + DB + Repository = 8 CPU, 20GB RAM for Veeam to work(No Proxy and Enterprise Manager required)And will add some resources for Windows OS Regarding storage, 249.43TB from VSE  So I add some buffer and for Windows OS with ~300TB disks space Assumptions:ReFSNo backup copy jobGeneric Pessimistic: daily change 10%, compress ratio 50%, annual growth 10% Is my thinking correctly?

Orchestrator Error, Veeam One Monitoring Service cannot access its database.Initially got the error, “The embedded Veeam Backup and Replication server is not Healthy, state = Communication Error”.So digging more into the issue showed the error above. When I ran VeeamOne client, it said it cannot connect to the Veeam One server.I noticed at the top of the client it shows Community EditionThis is weird, why would it say Community Edition, if VRO is showing a valid license I ran the Veeam One setting utility and was able to connect successfully  I opened a ticket to Veeam support and we have been going back and forth for almost 2 weeks now and no results yet. Hoping you folks can give me ideas where to go next.

Hello everyone,I am looking for advice on how to manage a migration from a VMWare host to a Hyper-V host while maintaining backups continuity under Veeam B&R 12.2 with only 2 sockets licensed. BackgroundWe have decided to move from VMWare to Hyper-V.  Our environment is small and it makes solid economic sense over the lifetime of the current Windows Server edition.  The Windows Server licensing was bought before Veeam expanded support to other hypervisors, so Proxmox VE was not in scope for this move.  We have timed our migration to coincide with a hardware refresh, so we will move from a two-host ESXi setup (VMWare VSphere Essentials with Veeam managing replication to the second host) to a two-host Hyper-V setup.  Again, we intend to use Veeam to manage replication because Windows Server Hyper-V Replication is constrictive compared to the options we have under Veeam, for our risk profile.There are 18 VMs in scope for the move.  The bulk of the data is approximately 50TB of data fr

Not Veeam related..but be careful guys! :)https://kb.vmware.com/s/article/90947

I’ve read the requirements which call for 16GB RAM and 8 cores.How will this run on a 12GB Windows 10/11 machine with 6 cores (Intel i5-10400 CPU @ 2.90GHz)? There’s little else running on the machine.

Customer is running backups of their VM’s at PROD site to at SOBR and running a backup copy for that job to their DR site (also to a SOBR).   They want to replicate some key VMs to their DR site as well and was hoping to seed those replicas from a the backup copy at the DR site.  Apparently seeding replicas from a backup (or backup copy) on a SOBR is not supported.   Trying to understand why not and how to work around this other than going back to non-SOBR backup repositories?  

Just wondering if there is any official information on Veeam Update 12.1.2 out yet? What might be coming with it, improvements to SOSAPI? I have heard rumors but wanted to know if I had missed any official news.Thanks

Hopefully no one uses exFAT but if you do check out this KB referencing corrupted files that are possible.KB4233: exFAT Filesystem may corrupt Veeam backup files