Discussion Boards

I have been using BackBlaze for cloud storage for about 5 years with Veeam12. I am now moving to Veeam 13 and want to attach to a new bucket. I created the bucket and attached to BB using a new application key. The problem I am having is when I got to ‘Select Folder’ I can see the bucket but cannot list any folders under the bucket. Since I cannot list the folders I cannot select a folder which means I cannot continue. There are no errors generated. Any ideas aside from open a support ticket?

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}.

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, 

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?   ​

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?

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 

I was trying to configure a VBR location profile for my OpenShift cluster, but it says ‘Repository not found’.When I runcurl -v -k -u Administrator:<password> https://<vbr-ip>:9419/api/v1/repositories, it doesn’t return any value.

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?

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 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,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.

When trying to add a Hyper-V host to VBR 13 from either the web console or GUI, we receive the error ‘Samba failed with error: NT_STATUS_ACCESS_DENIED - Can’t load /etc/samba/smb.conf.  The same error occurs when trying to add MS Server 2022 and 2025.  The MS server has it’s firewall disabled.Anyone else experienced this issue?Dave