Community

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. 

This was my second V100, and it definitely had a rougher story than the first one. Mostly because my previous company — a Veeam VASP partner — basically shut down, and just a month before the event I had started at a new company. I had no clue what I’d be doing there, whether I’d still work with Veeam clients, or if they’d even let me attend.Actually, they told me I’d probably be assigned full-time to a client using a totally different backup system. Not exactly thrilling, but the location was super convenient (close to home), and given the collapse of my old company and how hard it was to find something else, I took the job.Luckily, the new company let me go and assigned me to another client using Veeam — a win, though one I’m paying for dearly 😅. At that point I regretted not flying in on Sunday to attend the Monday workshop I really wanted to join. But since spots were limited, I didn’t feel right reserving one without being sure I could go

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 

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 

This year is my first as a Veeam Legend, and along with that recognition came an invitation to attend the Veeam 100 Summit in Prague. When first hearing I was invited, I experienced two emotions, excitement and trepidation. After all, this would not only be my first time visiting Czechia, it would also be my first time visiting the EU. However, seeing blog posts on the community from previous summits gave me an idea of what to expect. What I did not expect (but was pleasantly surprised about) was how quickly I was adopted into a small group of V100ers. Throughout the sessions I was able to understand their roles within their respective organizations, and their unique challenges, and afterwards when we went for dinner and to explore the city I felt that I was getting to know them as friends more than colleagues.Towards the end of the Summit and during the Dalrymple Toast and Brad Jervis Memorial Award presentation, I was struck by emotion while we remembered Brad and th

Let's continue setting up our Proxmox Lab.Previous entry: Download the ISO file from the Proxmox site .I then wrote it to a USB Thumb drive to boot and Install, I use a Mac, so I did it with BalenaEtcher.Now, I will post a few screenshots of the installation process.I did the same steps on the three nodes, just changing the managing IP address and hostname, the rest, the same:

BackgroundRecovery tokens are available for agent and plugin backups. They allow for easy and secure access to backups within repositories from a remote system, without the need to allow access to the full repository via credentials. To keep things easy, Veeam decided to have a fixed timeout for these tokens of 24h once created. This is usually sufficient for most recovery cases. So, the token is delivered to the workload owner and he can recover his - and only his - workload within these 24h.Creating Recovery Token - Veeam Agent Management GuideCreating Recovery Token - Veeam Plug-ins for Enterprise Applications Chall

Greetings community, it was so good seeing you last week. We've discussed during the sessions, and after about the strict DISA STIG password complexity, and password rotation, there is a forum on the public VBR when using hundreds of appliances. Since then I couldn’t sleep properly as I imaged myself changing dozens of appliances with the 2 default accounts. So I’ve built an script of course.TLDR Automate rotation of local OS accounts on VSA, Hardened Repos, and VIA nodes through Host Management API only. Handles OTP, does self change for veeamadmin, proper self flow for Security Officer, writes CSV for your vault. GitHub Code on GitHub: https://github.com/jorge

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, 

Hey everyone, I started a blog series for my obsession topic “Object Storage” and created 4 blog posts on “everything you need to know to size and architect for Object Storage”. My last and final one was around Benchmarking, which you can find here. Part 4/4 https://www.virtualhome.blog/2025/11/04/veeam-object-storage-benchmarking-part-4/This last part of the series concentrates on how to benchmark object storage systems and how to benchmark “Veeam I/O patterns” + “Object Lock Retention” settings. Feel free to have a look and give feedback :) This blog post was originally created to collect all my experience in a series with Object Storage.Here is a little sneak peak: 

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?

The walkthrough of the official #VMCA 2022 practice exam question 02 is ready. 

The walkthrough of the official #VMCA 2022 practice exam question 28 is ready.Did you have to check the scenario document? Which section did you locate the information inside? 

The walkthrough of the official #VMCA 2022 practice exam question 07 is ready. 

The walkthrough of the official #VMCA 2022 practice exam question 01 is ready. 

Everything shown here is included in all OpenShift subscriptions.As enterprises shift from VMware to OpenShift Virtualization, one of the most common questions is: how do networking concepts map across? This post walks through key visual mappings to help make that connection.Figure 1: Virtual Machine Networking in OpenShiftThis diagram shows how VMs in OpenShift can connect to: OpenShift SDN (for pods and services), or External networks via Multus and nmstate. Supported interface types include: Linux Bridge VLAN Bond Ethernet This architecture i

Hi Hello everyone,I am here to share with you my experience configuring VBR for the Azure Local environment, a step-by-step guide to configuration.Link:KB4047: Veeam Support for Azure Stack HCIRenaming Azure Stack HCI to Azure Local - Azure Local | Microsoft LearnAzure Local solution overview - Azure Local | Microsoft Learn

Greetings friends! I have seen this question popping up since VSA was released. How do we monitor VSA, or any other hardened appliance? There is a clear announcement about support for things like this, bear this in mind before you continue. Grafana Dashboard for Veeam Software Appliance (Unofficial + unsupported)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, etc.Dashboard – SummaryUptime and Latest Data Collection – Two main widgets that will show us if everything is alright. Appliance Information Table – Another great set

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.