Discussion Boards

We currently have our S3 retention set to 60 days. When I look at restoring from S3, it consists of all incrementals, with a full backup sitting at 61 days.Question 1: If we set our immutability to 30 days, wouldn’t we be at risk of our full backup being corrupted since it’s outside the 30-day window?Question 2: The formula for S3 storage is retention + immutability + block generation (30 days). So if we set retention to 60 days, immutability to 30 days, and S3 block generation to 30 days, would that give us 120 days of retention? Could we restore from 120 days back?Essentially, we are looking to ensure 30 days of immutability and need guidance on configuring that correctly.

 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

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? 

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?

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?

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 

We are using Veeam Backup & Replication(V12)  to take backup of Virtual Machines with Application-aware processing.Some of the virtual machines have SQL Server Databases.We take backup to Disk and Tape.Is it possible to restore SQL Server Database directly from Tape?If yesIs it possible to restore to different virtual machine? 

VeeamOn Tour is coming to your country! 🌍 Keep an eye on this website: https://www.veeam.com/veeamon-tours/ to be the first to register. 🐱 

We have initiated vm instant recovery and migrated to production . The issue is that we have completed the Migration from vCenter instead of the Veeam console, we just wanted to confirm that we are able to hit stop publishing in the Veeam console without impacting the restored and migrated VM.Please advise.

I’m a newbie when it comes to Veeam so I’m still learning the ropes.I have a question about Proxys, and how they can potentially help us improve the speed in which we backup.Currently we have 4 core sites with our B&R located at one of those sites, therefore this one site is backing up the 4 sites job after job then transferring them over to a Linux Hardened Repo as backup copies.The server itsellf has x2 10G nics which I don’t belief are currently being used to their full potential due to them only using Cat5e (wasn’t setup by me).As you can appriciate a lot of load on a single server, so any help on how we can potentially set this up correctly.

A little while ago we purchased an additional SAS storage enclosure for our existing Linux Hardened Repository server. Due to the number of disks, and also because we only have a Host Bus Adaptor rather than a hardware RAID card, we attempted to set this up as 5 md-raid6 arrays of 12 drives each, combined into a single volume using LVM.While initially this seemed to be working, after a little bit we have been getting tons of I/O errors. We exhausted all possible troubleshooting steps in collaboration with Veeam support, but it just seems like this is a wrong setup for a Veeam repository.I recently discovered the concept of “XFS on ZFS”, i.e. the idea of being able to set up a ZFS ZPOOL - which would replace the md-raid and LVM parts mentioned above - and then format this with the XFS filesystem. Apparently this is not a new idea either, as I found it was mentioned briefly in a Veeam webinar at 

Hi, I notice that when I backup the same machine with different jobs (each job contains the same machine) via Agent that B&R stores the backup copies under different directories and hence multiple copies of that machines backup up are saved.  Is there a way to get around this so only one copy is saved? Thanks

Backup Copy job to rotating media is not deleting the previously made backup before starting a new one which makes it immediately fail due to not having space.Retention is 2 restore point, repo space 900 gbNeed to manually delete the full backup filesLegacy mode, enabled this repo uses rotated drive option and continue existing backup chainNot seen this in ver 11 , but after ugrade to ver 12.2 it is reported.Vbr ver 12.2Please advise