Community

 Want to use VEEAM for my Proxmox Backup but got some Problem to get the Worker up and running. When i want to set up the Worker manually there is not Network to Add.The Network Access goes over Linux Bridge and the Veeam License is Enterprise.Has Anyone a clue where i can search or fix it.

customer on veeam v12.2. They have storeonce at both sites and S3 at site2.With backup copy at storage level (catalyst), Veeam controls the copy via the storeonce appliances performing the replication.If I choose image-level backup copy, this gives options for VMs and repos to copy. We also have “data transfer” for Direct. When it says direct is this storeonce to storeonce like storage level copy or does data go via another route?I need to know if there are considerable differences. thanks

Hi all, just wanted to get this out there in case you hadn’t seen it, my friend, fellow Vanguard and all around good dude Brad Jervis will be presenting with @Rin and @safiya this Thursday at 10 AM EST on archiving M365 data with Veeam Backup for Microsoft365. If you are concerned about compliance and cost management you should definitely tune in!https://www.linkedin.com/events/7243244346731290624

If you wish to explore the capabilities of Veeam Backup and Replication v11A, then you probably upgrade to this version. Kindly visit the following URL for more of these capabilities/features.Here is a link to the complete guide highlighting on all the needed steps.You may be notified if there is an update of the Veeam Backup and Replication. Upon clicking on this notification, you will be redirected to the following KB (download) link.

Hello!I’m currently running VBR CE v11.0.0 on Windows Server 2012 R2.  We are only backing up a total of 4 VMs.My initial task was to move a couple of the backups to a new backup repository.  But, the ‘move’ functionality apparently isn’t available in v11.  Rather than try to upgrade our current instance of Veeam, I’d like to just install a the newest version of VBR CE on a new instance of Windows Server.My question is: Keeping in mind the difference in versions, should I be able to take a backup of the DB config and import it to the new Veeam install as suggested here?  If the difference in versions is an issue, what’s the best way forward?Once I have a new instance up-and-running, the ability to move the backups to new repositories should be available, I believe.

Does anyone know when is the new immutable installable ISO release date? I’m currently waiting for it to deploy our new VHR.

Running VBR v12.0. Created a backup job. Ran the job and got an error so went back in and try to edit the job. I got the error below. First time, I encountered this error. The backup log just showed the same information. I have a similar job running in our “staging” VBR but not having any error. The backup job is a storage snapshot and does handle SQL transaction logging. I saw in the Veeam’s Forum the same error message but this was for a backup copy job. What do you think is happening here? 

Every once in a while, someone asks me to protect an Azure workload that does have the most direct approach available for it in a Veeam product. Today I’ll focus on Azure Key Vault, but I’ll see if I can broaden the scope a bit over time with future posts. Why backup Azure Key VaultAzure Key Vault is used as a source to manage anything from encryption scopes on Azure Storage to allowing customer managed keys for services, storing public/private key pairs, custom secrets, and certificates. Losing Azure Key Vault contents could pose a serious problem, but exporting data out for backup purposes could also create quite some risk – thankfully backup jobs allow data encryption. Soft deleteAzure Key Vault comes with soft delete, allowing recovery of deleted vaults an

With the recent announcement that Hyper-V is strategic to Microsoft, as the main focus of Server 2025 you can imagine I've spent more time on the topic than usual lately. I normally don’t post on here, but I figured I'd share. To get the basic stuff out of the way, yes you can Instantly Recovery ‘any’ workload to Hyper-V, and it can be automated with PowerShell - it will probably make it

Hello,I have a very old running setup of ESXI 5.0.0 and ESXI 5.1.0 Hosts with 10 VMs (Win Server 2008R2, Suse enterprise 12, Win Server 2016 and windows 7 Pro.). The setup also includes an Equallogic storage.Is it possible to migrate the existing VMs to a new Host server with ESXI 8.0 ? 

I was chatting with a few friends just now and I was reminded of the old internet. You know, the fun internet where things like Facebook and Instagram didn’t exist. Fark was active. Slashdot was where you got all your technical news from, BBSs were still active and you looked forward to the next Strongbad email. My favorite fun internet was ASCII Star Wars.telnet towel.blinkenlights.nlAnyone else have any gems from the old days you can remember and share? Many of the younger generation may not remember, but I do, and I miss it.

Hi, Does Any One Know A Way Of Reproducing The Daily E-Mail That Is Sent Which Contains In A Report:-Veeam Backup for Microsoft Office 365 Type Name Status Start time End time Items Data size Details  Also, What does T

If you set your S3 repos gateway server to direct mode, I would have expected the entity getting in touch with backup data to do the offload.In direct to object jobs it works just like that. Proxy will do the upload with a primary job. Repo will do the upload with a backup copy job. But with SOBR offloading to capacity tier it seems to be the VBR server doing the offload for all S3 buckets in direct mode.Can someone confirm this observation?Would be another reason to always have GW servers specified for each and every S3 repo.

Hello,Can someone here help me to understand about malware detection in Veaam.What will happened if there any malware inside the source VM, will Veaam canceling the backup job? As i know Veaam can integrate with other 3rd party antivirus vendor. If VBR server using Microsoft Defender, this mean Veaam will use Windows Defender to scanning the malware?

Hi all,In the first part of our deep-dive evaluation of OOTBI we go deeper into Object Storage and the technology.What is it, what are the benefits, pitfalls,…We also look what’s inside the OOTBI’s box, dismantle it, analyse the components and show you step by step how to configure this optimized device for Veeam under 15 minutes.Read it all here (prepare for a long-read….) Let me know if you like it. We’ll prepare a second article where we look at performance and maintenance.

Hey Everyone,I wanted to share that Veeam now claims compatibility support of VMware vSphere 8.0.3 in the latest version of Veeam Backup & Replication V12.1.2.172.Please be aware of a couple of important limitations:Backup jobs including vCLS VMs: Due to changes in vSphere 8.0.3, backup jobs that include vCLS VMs (typically when using vSphere Cluster or ESXi Server scope) may fail. As a temporary solution, you can manually exclude these VMs from your backup jobs or utilize Global VM exclusions.  Veeam is aware of this issue and plans to address it in the upcoming V12.2 update.NSX-T 4.2.0 support: At this time, we have not been able to test and confirm support for NSX-T 4.2.0 due to Broadcom's current unavailability of the software for backup partners. We are actively working with Broadcom to resolve this and will provide updates as soon as possible.For more details, please refer to the following KB Articles:

I have a backup failure showing error: Failed to open VDDK disk [[vsanDatastore] be123456677777777/vm1vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [dc1.nm.org];Port: 443;Login: [;VMX Spec: [moref=vm-1104];Snapshot mor: [snapshot-253990;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}. It was working only when selecting nbdssl transport mode . i know it is using network over ssl .Can someone advise why it is working only nbdssl and what is it doing in the background?

We would like to ensure that all backups from October 1, 2024, through October 4, 2024, are retained without expiring and remain accessible throughout the year if needed.. How can we achieve this?

I was honored to be selected as a delegate last week to Edge Field Day 3 in Santa Clara, CA. While there I presented an Ignite Talk on utilizing Object Storage in your Disaster Recovery strategy. This is the shorter version of this talk that I’ve been giving this year but the only one that’s made its way to YouTube so I thought I’d share. Are you leverage Object today?  

The sequel of part 2 😉And it seems that a part 4 is also needed 🙄 Backup copy job : VBR creates the first time of course a full backup file on the currently attached disk When you swap the disk and if it is empty, it will create a full backup on itIf there is a backup chain on it for this job, it will create a new incremental in the current chain. The latest incremental is the start point of the new incrementalThe retention policy will be applied, so all backup-files that are outdated will be removed from the backup chainBecause I always use a backup copy job in combination with rotated drives as a offline/airgapped solution I always recommend the customer to swap the disks on a weekly basis. Therefore I mostly configure the job with 7 to 10 restore points meaning 1 full and 6 to 9 incrementals.I don’t care about the total wanted restore points, I see the number of restore points

Hi, I am using Veeam backup and replication 12 (free edition).I am trying to import a .vbk encrypted file, which is stored on a remote NAS (QNAP).I am accessing this NAS through SMB protocol.I wrote the (correct) encryption key, and after I get this error:Failed to import backup Error: access denied, failed to open storage for read access. Storage [filename.vbk] I also tried to configure access permission to that repository (NAS) with "everyone" allowed, but I got same error. Any suggestion? Thank you.Full error (from file Util.BackgroundOperation.log) is [25.09.2024 09:46:51.335] <14> Error                  [AP] (db9320fe) error: Accesso negato[25.09.2024 09:46:51.335] <14> Error          Failed to open file [\\nas-xxx.domain.com\Veeam\serverD2020-10-04T082748_CB05.vbk] in readonly mode.[25.09.2024 09:46:51.335] <14> Error          --tr:Error code: 0x00000005

We have multiple backup servers and run a configuration backup on them daily. I’m looking for suggestions on how to keep these config backups safe ?I originally had a script that emailed these to a mailbox to keep “air-gapped”, but the size of the file became too large.  Perhaps there’s a way of reducing these, but I suspect the size will creep up again making them too big. Currently the config backup for Site A goes to Site B and visa versa, but i want something better. Yes, I  could have a scheduled task to copy them elsewhere. Any other thoughts / suggestions. TIA