Discussion Boards

Hello,I have a problem with configuring the Backup Job.We have one server hosted on Hetzner and I need to backup it just once and restore it.I don’t know what could be the prerequisites for this, do I need to expose our VBR ports to the Hetzner?Currently I manage to create protection group, added Hetzner server without any problems, rescaning is working, but when I try to create a backup job using Veeam agent it fails with the following error message:3/4/2024 14:03:40 :: Failed to send backup job configuration to X Error: Failed to update backup job Managed by agent job name: Agent Backup Policy 3.Invalid job configuration.Connection problems.Exception has been thrown by the target of an invocation.Failed to establish connection: no valid IP addresses were found.A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed be

Hi, my backup is showing this error, can someone please help me? Both machines are VMs in Hyper-V.  

Hello Veeam People,I have problems with opening Guest File Restore from Backups.I’m trying to configure some restores for our Revit Server scenarios.The problem is that I choose which point I want, proced to browse the files and then I’m stuck with the following popup window: What can be the issue here, I checked the Mount Server, it’s the VMs where our Repos are connected via iSCSi.Windows Server VMsThank you in advance.

Hi Community,  I just keep getting this error on one of my esxii and I am stuck in here. we already tried to troubleshoot the esxii by restarting every servicies and the esxii itself but it is not working. We have 3 other esxii that are just working fine but this one just show this error.NB: We gave an account with max privilege to try the backup Error: Failed to open VDDK disk [[Datastore_DELL_PowerEdge_120] VM-DNS1/VM-DNS1-1-000001.vmdk] ( is read-only mode - [true] ) Logon attempt with parameters [VC/ESX: [192.168.1.170];Port: 443;Login: [xxx];VMX Spec: [moref=vm-32];Snapshot mor: [snapshot-135];Transports: [nbd];Read Only: [true]] failed because of the following errors: Failed to open disk for read. Failed to upload disk 'vddkConnSpec>' Agent failed to process method {DataTransfer.SyncDisk}.

I’m testing several On-Prem S3 Object Backups ( Backing up Object Storage in 12.1) no matter which of the 4 systems I try I get the attached error. All of the systems have “buckets” that Veeam 12.1 has written to, and they have data in them, and are set as repo’s in VBR that I am using for this test. Suggestions? Error is attached - I get it on all of them. 

I am having trouble accessing the remaining 3 workstations I don't know where they are I only have 4 workstations here. I am here at the VBR.

Hi, I have a protection group of 8 windows machines.  The machines were added to the protection group using their host names.  The machines get their ip from a DHCP server.  I see that one of the machines, originally with ip 192.168.1.151, is not 192.168.1.155 and is not being backed up.  Is there a way to update the protection group for the new ip?  Unfortunately, I cannot revert back to the original ip because that ip is now being used by another machine (that’s not part of the protection group).

Hello Everyone,We are using Veeam Data Cloud for Microsoft 365 Flex with a license for 250 users.During the initial setup, we tested with 1 user to validate the configuration. After confirming everything was working properly, we deleted this backup job and created a new policy to protect the actual 250 production users.However, we are still seeing the backup for the original test user, and the license usage shows 251 users consumed, even though our license count is 250.I have a few questions regarding this situation: How can we delete or revoke this test user so that it no longer consumes a license? If we keep the test user without removing it, will this impact production users (e.g., only 249 users protected)? Is there any automatic cleanup or retention process that eventually removes ol

Object First storage is used in our main data center.Regional backups are first stored locally, then copied to Object First at the main site using a forever incremental job (using Scale Out repo and Object First configured as capacity tier)Now If full backup data needs to be sent to AWS (e.g., when decommissioning a regional application server), it can be done from the main site through a secondary copy—without using the regional office’s primary copy.

I always having this issue when perform the backup or replication, the virtual machine will create the snapshot and once finish will delete the snapshot. When this activity happen the VM will like stun and loss ping. How can we perform resolve this? 

Build new windows (2022) server for Veeam B7R 12.3.2.4165 and imported the config from older server.Since then every backup job has a warning “Sending e-mail report Details: Failed to wait mutex VeeamMailServiceAzureToken: timeout 00:01:00 sec exceeded”  Opening options takes sometimes 10 min or more, but when it does I can send test mails successfully.After saving the first backups work with email, after a day its the same error.When opening options sometimes this message appears: I don't know what's wrong here server has plenty of power.Grtz.Bart P.s. old server did not have this problem. 

We are getting a VMAStopDrivers error message when trying to uninstall the Veeam Backup & Replication software. We are running from Programs & Features on an account with full admin access to the computer, on Windows 11 Pro v25H2.Trying to update to the most recent version of Veeam (in order to refresh the program files) doesn’t go through, due to the same error message, so stuck in a position with an older version installed (vulnerability) but unable to remove or update 

Hi Community,Has anyone successfully reverted Veeam ONE from version 13 to version 12? Are there recommended steps or considerations to avoid issues during the downgrade? Any official guidance or lessons learned would be greatly appreciated.

Hello Community, This is a failover cluster setup, and node one is working fine; the second node is having the error below. While taking the DB level backup, including logs being truncated every second? Unable to retrieve next block transmission command. Number of already processed blocks: [173]. Error: bad allocation 

Hi,I have a few backups running to a Repository on an NAS, shared by nfs3://[IP ADDX]/Backups/etc…It works fine for my esxi backups. I’m trying too backup a hyper-V VM and and getting the below message. It does succeed in creating as folder in the repository for the packup to go, and the permissions are are same as the others, so I’m not sure what credentials its trying to use since it’s writing to the same place that works for other backup jobs:“… Processing … Error: Failed to reset previous connection exception: Permission deniedFailed to open storage for read/write access. Storage: [target path] ....Agent failed to process method {Stg.OpenReadWrite}.  “I’m not sure if this means it can’t read the source or can’t write the target. If the former, what do I have to do because use a local admin to access the source? If the letter, why can this job not write to the repository when other jobs can?Thanks, 

We use paid Veeam B&R v12.x (VUL/Essentials) to back up NetApp ONTAP SMB/NFS to a local repo and are evaluating off-site immutable copies via SOBR + S3/Wasabi/Azure (Object Lock) vs Cloud Connect (VCSP). What’s your real-world take on job layout (per-share vs per-volume), snapshots, NAS proxies, performance and €/TB/month, plus restore/ACL fidelity, cross-protocol restores, and immutability/lifecycle gotchas? Any proven tuning or pitfalls to avoid?

Hello everyone,I am new to this community and have already tried my luck in a closed thread about the Veeam VM Migrator Utility.However, I currently have a question about this utility.Are there any experience reports on migrating individual vSphere VMs using the Migrator Utility?Is individual migration with this tool even intended? Thank you in advance for your feedback!

i have vbr 12.3 installed on VM from where i had to add storeonce vsa ,however when i add username and password,it shows error saying unable to login to ip:port 16022...what could be the reason

Since yesterday all our existing configured backup jobs to Azure Blob storage are failing and attempts to create new object storage repository are failing on Validating Credentials.  Error: Unable to access object storage (reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (xstorageaccountnamex.blob.core.windows.net:443))Any ideas?  I’ve tried rotating the access key in Azure and updating that in the Cloud account in Veeam m365 backup.  This has started to occur a week after upgrading to v8 which was ok initially.

I have been (legally) ordered to provide “any and all” copies of backups for a client dating back two years. Veeam 8.1.2 Community runs on a Win10 Virtual Machine and runs 3 routines dailyExchange, SharePoint + Teams, OneDriveManual restore will take a year and $9K of external USB hard drives.Wondering if there is a way to give them a copy of the Veeam virtual machine with backups disabled and the only restore options are save locally. I do not want them to accidentally trigger a restore job that overwrites the live data.Disabling the 3 jobs is not appealing because they can be enabled easily.I changed the global admin password associated with the organization but did not affect Veeam operation.  This would allow us to continue to the original Veeam backup server for daily backups.In typing this, it seems that providing them with a searchable and restorable archive is what I am looking for.  Plus it cannot interfere with the ongoing backup o

Hello Team,I just finished setting up Veeam backup community edition 12.2 and added Proxmox VE server into Veeam backup.  Now, I tried to configure “worker”, but it was failed.  I used DHCP and set static IP address.  The error I got was “Failed to obtain an IP address: The operation timeout exceeded” and “Worker xxxx(hostname) test failed.  I am not sure if worker name should be registered in DNS record, or it should be any hostname which doesn’t exist in DNS?  I tried to both of them, but I still have no luck.Also, the worker host seemed to be created on Proxmox VE server.  I can see this and I can ping this from Veeam backup host (Windows 11 PC).   I appreciate for you help!!

2025-11-06 Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM ParallelsHello,I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.Troubleshooting Steps Completed:I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the set

Hi all,I want to update Veeam Agent for Windows from 6.3.2.1205 to 6.3.2.1302. The in place upgrade doesnt’t work:  Will my backup job settings be safe when I uninstall the current installed agent and reinstall the new version of Veeam Agent for Windows?Kind Regards