Community

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.

The general availability (GA) of Red Hat OpenShift 4.18, 4.19, and 4.20 on VMware Cloud Foundation 9 and VMware vSphere Foundation 9 represents more than just expanded platform support. It marks a natural evolution for organizations modernizing their VMware-based infrastructure while continuing to run Kubernetes at enterprise scale. 🔄With the introduction of VCF9, Broadcom delivers a more integrated and standardized VMware platform. Red Hat aligns with this architecture by offering certified OpenShift deployments that preserve the operational model customers already trust. Organizations running OpenShift on vSphere 8 or VCF 5 can therefore move to VCF9 without rethinking how clusters are deployed or operated. ✅From a networking standpoint, OpenShift on VCF9 follows a clear and validated design. VMware NSX provides the infrastructure networking layer, while OVN-Kubernetes delivers the OpenShift-native overlay network.

The long-awaited gift for the Blog has arrived!Thank you again to everyone for the votes! Below is a thank-you video to the entire dedicated organization.https://youtube.com/shorts/cKjloP8kPTU?si=xX9XWII_Ib_xngFp  

I am using /api/query?type=’BackupJobSession’ to retrieve all backup job sessions. Does anybody know if this query will retrieve sessions for ‘Backup to Tape’ jobs as well? I don’t have the ability to setup such jobs in my lab and I can not test it. Alternatively is there a different query to retrieve sessions for such jobs? 

Hello,Using Veeam 365 community edition, backing up our Sharepoint site always end with warnings of: Processing site: https://**********.**** completed with warning: Failed to backup item version: /********/********/********/.****, version: 2.0, Download timeout exceeded (last error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..). All retry attempts failed. Re-run the backup job to proceed. Total count of failed items: 17The file it stops on changes each time and the number of files, still backs up most data but it is never fully successful. We have 20 backup applications, the backup is running and downloading data but it’s average processing rate is only around 500kbpsAnyone else seen this, what other logs to check in Veeam or Office 365 or a fix? Running version 8.3.0.2201 P20251212 

Hi Everyone,​@JonahMay  and I sat down (remotely 😀) and I asked him all those burning questions about AI that we are all asking. Jonah has been doing a lot with AI so has some create stories to tell. He also offers his predictions on what we as data protection experts need to be thinking about.So Jonah will I be digging ditches in a few years? Find out here:https://www.buzzsprout.com/2545760/episodes/18630608

Hello. As part of our Physical Infrastructure in VB&R12, we have a Physical Windows Server that has storage attached by fibre channel. The Veeam agent is installed on this server and the service uses the Local System account. I am attempting a "Managed by agent" backup of this server, but when this runs, I get the error message "Volume G:\ does not exist" for files from the FC-attached storage. Outside of Veeam, I checked that the server's local SYSTEM account has access to G: and it could read the files there just fine. Why can't the backup job see that volume? Thank you.

Veeam Data Platform Advanced and Premium Editions give organizations powerful tools to document and report on their environment. This includes gathering data around capacity planning, protection policies, and performance insights. By utilizing this functionality, teams gain visibility into their data protection environment to help maintain security, achieve consistent compliance, and improve operational efficiency.The latest release of the Veeam Data Platform brought major updates to Veeam ONE’s reporting capabilities. By delivering a faster, more interactive experience, reporting within the platform has become more modern, moving away from traditional SQL Server Reporting Services (SSRS) to HTML5-based reporting. You will see this experience with Veeam Data Platform and Veeam Backup for Microsoft 365 reports.This modernization is accompanied by a new PostgreSQL-powered Veeam ONE Reporting Database designed to accelerate large report generation. Reports that used to ta

After Part q, 2 and 3, lets finish with creating the VPN account and setup the client.Now, let's create a VPN user, to be able to set it up into our phone / laptop, and start using our WireGuard VPN.Connect to your new deployed server via sshNow, lets execute the command: pivpn addlets create the account

Enterprise Manager Self-Service Portal - Server Error. I remember being able to fix this before but can’t remember the particulars. I had to go to IIS, I think application pools.   

Since this step is similar to the below, I will not be dropping the entire content here. Kindly take a look at the following guide for more information “Building VIHR: Ransomware-Proof Repository with Veeam JeOS”.The article walks through the steps on ho

Hi teamCan someone shed some light on this and how best to go about it.We have Nutanix cluster A and Nutanix cluster B.VM have been moved from cluster A with Nutanix Move, which creates a new VM on cluster B and syncs data. My guess is that it creates a new UUIDThere is an existing backup to a Wasabi Repo from cluster A.How can I re-create/re-point the backups that are on the repo so that the copied VM on cluster B can continue to use the backups already there?I am not so sure if there is a remap function for this. I also cannot add vm from the new cluster to the existing job as it only allows me to select existing one. It appears that you select cluster first when creating the job.My guess is I may have to create a new job and let old one age out?