Community

OS is Linux Mint Mate 22.  Been running VAL v.6 successfully for some time, now looking to update to v.13.  File downloaded, only option seems to be .iso for which I use Balena Etcher.  BE says, problem with this file, and cannot continue.  Ran the download three times, BE tells me the same thing with each of the downloaded files.Previous Veeam downloads were .deb files, used for ubuntu/debian systems.  Could be there isn’t or won’t be such for v.13.  Anyone know whether v.12 is available?

I was running the Community Edition ver. 8.2.0.2202 on my Windows Server 2025 when a notice appeared to install the latest update for Veeam Backup for Microsoft 365 8.3.    (Community Edition)I did that upgrade but it jacked up my system. I got an "Installation Failure" with no useful information in the log. After much searching, I found this https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/unable-to-install-vbo365-on-a-fresh-windows-11-system-t101611.htmlI used some of the suggestions there and I finally got 8.3.0.2201 installed.But now I get the "No connection could be made b/c the target machine refused it." I briefly saw something about a installation issue with multi-homed server

Happy Wednesday, Community!Some good news came from the Veeam KB Support team yesterday. There will now be the ability to change log location for all of the Veeam Software Appliances → VSA, VIA, VHR. I know there have been some posts on here for those early in testing out VDP v13 where space has become an issue on the VSA. This change allows VDP users to modify the log location to a more robust storage location on the the Appliances to hopefully mitigate encountered space issues.But keep in mind...if you do indeed modify the log location on your Appliances, there is a caveat as noted at the top of the KB -“Automated log collection tools built into both the Veeam Backup & Replication Web UI of the Veeam Software Appliance and the "Create support bundle" function within the Host Management Console collect logs only from the default log location, /var/log/VeeamBackup/ . As such, Diagnostic logging stored in a differen

Hi All,Can you backup normal vms in Red Hat Openshift with VBR or do you need to use Veeam Kasten?Thanks,Benny

I’m wrapping up the first phase of my Veeam for AWS journey.I actually started this lab from some ideas I shared in the post below: In this video, I go through the full workflow:• Protecting AWS workloads like EC2, RDS, DynamoDB, VPC, EFS, and FSx• Creating Replicas, Snapshost, Backups and performing restores• Testing cross-region recovery (Virginia, Ohio, and California) Link bellow:https://www.youtube.com/watch?v=j76Xt0R55Pg&t=63s(It’s only in Portuguese, but the YouTube subtitles work really well.)

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

Dear Veeam team,I am trying to uninstall VBR 13 but get stuck the issue below. I have checked both services: Veeam Backup Update Service and Veeam Backup Service. There is no Veeam Backup Service anymore.Please advise me for this case 

Hello Community,I would like to check if anyone has practical experience or official guidance regarding the following scenario.Has anyone successfully presented a LUN from a Dell Unity array via Fibre Channel to either: Veeam Backup Appliance v13, or Veeam Hardened Repository (JeOS) with the intention of using that LUN as: a backup repository, or an additional backup disk for the repository? My main concern is related to the fact that both the Veeam Software Appliance and VHR (JeOS) are locked down by default for security and immutability purposes. I could not find clear documentation or a community thread that explicitly discusses: Whether FC-based block storage is supported in this scenario Any 

Last Friday was officially rolled out Veeam One training in Veeam University Pro.If you are interested in VMCE+ certification, this is the right way how to achieve it. Are still not decided? I am starting it right now and let you know about the training!  

Sizing Veeam environments has always been a mix of experience, assumptions, and spreadsheets. But that just changed. With the new Scenario Builder, Veeam takes a big leap forward, making multi-site sizing clearer, smarter, and far more predictable—turning complex design decisions into a structured, repeatable process.    

we are veeamawsbackup                   7.1.0.8                                 amd64        Veeam Backup for AWS. we want to upgrade veeamaws 10. can some one please provide the procedure for the same.

I’m unable to connect VSPC to Cloud Connect. When I try to add the Cloud Connect server from Configuration → Catalog → Veeam Cloud Connect, it fails with “Failed to connect to the deployment service.” I’ve already tried disabling Windows Firewall and antivirus, but the issue persists. I can install the agent manually on the Cloud Connect server without any errors; however, after installation, the server only appears under Discovery in VSPC and does not show up under Catalog → Cloud Connect → Veeam Cloud Connect Integration. Both servers are on the same subnet with no firewall in between.  

Backup for vmsrv0 on hyper v host1 worked always before, but for hyper v host1 i forgot that i turned off vmsrv0 vm LOL, so veeam was backing up a turned off vm. I went into host1 and switched from vmsrv0 to vmsrv1 running the same/replica (OS-Suse Linux Enterprise 12), did not continue backup chain, i just created a new backup to drive. Now i get vmsrv1 Processing vmsrv1 Error: Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectable protocol device was closed. Failed to upload disk 'shadowSpec>' Agent failed to process method {DataTransfer.SyncDisk}. Hard disk 2 (4 TB) Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectab

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 sam

​ ProxyPool Swapper for Veeam Backup for M365If you regularly onboard new tenants in Veeam Backup for Microsoft 365, chances are this scenario sounds very familiar.A repository gets assigned to a proxy pool, and at some point you want to move it—quickly and without hassle. A common approach is to use a dedicated onboarding proxy pool for the initial full backups of new tenants, and a separate, permanently assigned pool for ongoing operations. Once those initial backups are complete, only incremental, day-to-day changes remain. These smaller, predictable workloads can then be handled by a proxy pool that’s specifically designed and sized for daily processing.From an architectural perspective, this makes perfect sense. From an operational perspective… it can get a bit tedious.Another use case I frequently run into is the need to quickly access logs for a specific job or repository. To do this, I assign the repository to a local Windows proxy, which g

Sorry to rant, but I have nowhere else to turn, and it's beginning to impact our clients. Veeam 13 has been absolutely horrible to install on all our backup servers. The upgrades are breaking the installs on current backup servers. It is straight up failing to install and start the Veeam service on a brand new server, and Veeam support has been unable to figure it out for two weeks. I've put escalation requests in and I'm getting nowhere. has anybody seen behaviour like this? The people on the Veeam subreddit agree that Veeam 13 has been horrible to roll out.

 The new HPE StoreOnce 7700 and 5720 Gen5 are now officially a Veeam Ready Repository certified as Primary Target Repository, passing all compatibility/functional tests, as well as extensive performance tests for both backup and restore operations with Veeam Backup & Replication 13.Part of the qualification test is random IOPS on a backup target to simulate Secure Restore (a virus-scanning process) executed within the Veeam Instant VM Recovery context.Certification Test Settings:Caching used: Yes Read/write caching: StoreOnce uses explicit application prefetch/caching/buffering in RAM. Also leverages Linux page cache (filesystem read/write caching), and the RAI

Hi All,  Has anyone seen hotadd Linux (Rocky 9.7) VM proxies go sideways and not mount after upgrading to v13? I also added a new v13 appliance proxy and the result were the same. Changing transports to net work fine. On this client side logging it shows: Error: Access to [/dev/sdb] is denied.Failed to check whether access to path is grantedFailed to open disk for write.Failed to download disk 'snapshot-909174XXXX'. CC tenant job logging has: <842>    Info (3)    Skipping VcdDatastore (VcdRef=[urn:vcloud:datastore:GUIDXXXXXX], Name=[*CLIENT_DS*]) because it does not have valid underlying vCenter resources VCSA 8.3VCD 10.4xVBR 13Rocky 9.7 latest Kernel.  We have a Sev1 open but its currently pending logging reviews.  

Hi since upgrading my PVe to version 9.1 and the VBR to 13, the backup performance have degraded a lot. We have 1 worker per pve host, storage is Ceph. Did someone encounter this issue?

As we know VMCE will be retired and VMCA was retired, so anyone know what the new certication path now?

Running Veeam agent for Linux, v. 6.3.2.1207_x86_64. OS is Mint MATE 22.  Been making weekly backups for a year or more, just now trying a test recovery on spare computer- loaded some files, ran b/u to ext. drive, deleted files.  Have Recovery Media on stick, using steps in user guide.  All good thru several menus until “Mount Local Disc” which brings up a menu “Select Local Disc” but there are no items from which to select.  Backup drive lights up, so recognized by system.  What am I missing?  

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.

Now we can create the actual backup job. Let’s go back to Home–>Jobs and add a CDP PolicyAdd the computer we created in the protection group.Next we choose our Datastore, Host, and Resource Pool. Under Policy settings we can choose our replica suffix. Note this has to be unique, I had the job fail during testing because it already existed.Finally, we can set our RPOs and retention.

I was surprised when I started looking at Scale to discover that they have been around since 2012, announcing their HC3 appliance powered by HyperCore. Then in 2019 8.2 released with major updates and security mitigations, and the key piece for what I think their use case fits was announced in 2022 Scale Fleet Manager. More on that in a bit. The Scale HyperCore has self-healing capabilities and is very simple. The simple interface is easy to use and manage and would be a small learning curve for any VMware administrator. Their Fleet Manager web-based portal allows customers and MSPs to manage, deploy, and monitor distributed infrastructure. This makes it easy to manage edge computing or small ROBO locations.Veeam support for Scale was just released in 2025 with version 12.3.2 to include backup and restore of Scale VMs into Scale, or from other platforms into Scale, and recovery of Scale into other Veeam supporte

Greetings, friends! I want to share with you the new Grafana Dashboard for Veeam Backup & Replication, no Enterprise Manager is needed, and it uses 100% VBR API.Small note: For those familiar with the data protection scene, you might recall that we’ve already got a Grafana Dashboard dedicated to the Veeam Enterprise Manager API since 2020. Grafana Dashboard for Veeam Backup & Replication API When you finish this article, if you follow all the steps, you should have something similar to this. It might be different according to your environment, number of days you select, protected workloads, jobs, etc.