Community

 Over the last few years, the time to execute ransomware attacks dropped 94%; now, criminals take, on average, just 3.85 days to deploy a ransomware attack.On the other side, according to the “Veeam Ransomware Trends – 2023 Global Report”, recovering the affected environment after a ransomware incident takes an average of 3.3 weeks of work, equivalent to 136 business hours of business downtime.Here is the link for this Veeam’s report:https://go.veeam.com/ransomware-trends-report-2023Along with exploiting application vulnerabilities, hackers heavily utilize client-side compromise techniques to deploy ransomware.In each attack, criminals must take well-known steps to reach their targets. Based on this, models were created to identify and prevent cyber intrusion activity. One of the most famous is the Cyber ​​​​Kill Chain, developed by Lockheed Martin.For this purpose, we will focus on four stages of a client-side attack: delivery of exploitation, installation, command-and-control, propag

We are using Veeam Enterprise Backup & Replication 12 in a mixed VMware VM and physical Windows network.We have upgraded all of our Windows servers to Server 2025. Backups on non-domain controllers had no issue post update but our domain controllers are all failing with the same error once the OS was upgraded: Failed to index guest file system. VSSControl: Index failed There are no connectivity issues between the domain controllers and the Veeam servers and proxies. The domain controllers were not all upgraded on the same day, but each would fail as soon as the OS upgrade occurred. So one day the DC running on Server 2022 would be able to be backed up with no issues, the night its upgraded it would fail. No other changes other than OS upgraded. No changes to virtualization or network infrastructure.  

VBR and VEM using PostgreSQL, however VeeamONE still using MSSQL, I am looking forward to see VeeamONE using PostgreSQL, it will be great to unify the DBs for Veeam infrastructure.

Hi,I have recently inherited a site using Veeam Backup & Replication V12One of the components of a Backup Copy Job is failing with the following errorCannot proceed with the job: existing backup meta file 'XXX-XXX-DC01_764B4.vbm' on repository 'XXX-XXX-BK02 - VMs' is not synchronized with the DB. To resolve this, run repository rescan When I run the “repository rescan” I get the warning belowFailed to import backup path /|drs-vms|backups|XXX-XXX-BK02 VM Copy|Cluster Windows VM Dailys|AIR-PIC-DC01_764B4.vbm Details: Root element is missing.387164The repository is offsite and it is a Ubuntu SystemAny advice would be appreciatedThank You

In part I of this series we have seen how to move a tape library with all data to another VBR server which has already data on it.https://community.veeam.com/blogs-and-podcasts-57/veeam-and-tape-i-moving-a-tape-library-with-data-from-one-vbr-server-to-another-1654 The open question was, how do I get my tapes with data to the correct media pools without losing my data…When you select to move a tape to a media pool the following message appears:So, the tapes are marked free, and the data is lost when a tape is moved? A quick check of the helpcenter and the forums says exactly this…https://helpcenter.veeam.com/docs/backup/vsphere/moving_tapes_to_custom_pool.html?ver=110But is this correct?Fortunately, it is not. The tape is marked free when it is moved, but the data on the tape is not lost. Its metadata is deleted from the Veeam database – and this can be recreated. All the tapes from the new library are assigned to the pool “Imported”   Move the tapes to their corresponding media pools.

I am setting up VBO to back up 365 data to the cloud as we are starting to migrate all users to 365. I have read it’s best to separate repos instead of just having one repo for the whole organization.Anyone have an example of best setup? So far I am starting out creating separate repos for OneDrive, Teams, Sharepoint, Groups and separate jobs for each one of those. Is this a good approach? I was also going to add one more repo for Users. Would that cover everything for now as we are currently still using exchange on prem?  Should I also make one repo and job for the entire Org with all data in it? Or only have one repo with everything in it? Just want to make sure I set it up properly so I don’t realize I should have set it up differently a year down the road. Thanks!

Scenario:Very recently a customer asked me if Veeam could leverage Data Domain mtree replica for DR purposes.Of course, the answer is YES! While this idea is not new, I thought it would be a good reminder of Veeam’s backup import capabilities. Steps:You must use Data Domain repository on the source site. It most likely will be declared as a DDboost share. The mtree should be replicated to the DR site. Note that the mtree replica will be Read Only! The mtree replica needs to be exposed as a share over your protocol of choice (CIFS, DDboost), so it can be defined in the DR VBR server. In this example, I chose DDboost.Note again that this DDboost share is Read Only! The last step is to declare that DR DDboost share and import backups You should now be able to access these backups from the “Disk (Imported)” section. Remember that you will have to manually rescan that repository in order to refresh new “mtree replicated” restore points.

Hey all,I'd like to share an experience I encountered with one of my clients who uses the Virtual Lab functionality to test their backups.Problem:Suddenly the SureBackup starts to fail. When the SureBackup job launches, it fails during VM registration with vCenter Investigation:My virtual labs are properly set up in Veeam and the association with the ESXi is OK. As a reminder, a Virtual Lab must be assigned to a unique ESX host. If you move the Virtual Lab Vm to another ESX, your jobs will failed. On the vCenter side, all virtual labs are presents in their respective folder.But I noticed that the Resource pools are all missing.My client is using DRS in his Vmware infrastructure, I asked him if DRS has been disabled recently and the answer was : YES!Impact when DRS is disabled:As resource pools are a bit of DRS functionality, they are deleted when DRS is disabled.Solution:You may turn off vSphere DRS for a cluster.If you disable vSphere DRS, the resource pools are removed from the clust

Backup Copy Job targeting a SOBR (Scale-Out Backup Repository) with a Synology extent are failing.Error;Error (3): No scale-out repository extents have sufficient disk space to store the backup file. (System.Exception)No extents found for backup chain. Tried this registry fix , no luck https://www.veeam.com/kb2282The SOBR extent  has 2.9 TB of free space.Backup objects size is 11.9 TB  I don’t know if this will help the required size Svc.VeeamBackup.RTSDispatcher.log14.05.2025 10:58:22.234]    <32>    Info (3)    [RTS] Updating Extent id = 96963ca1- - actual free space to 722861084509. 2494699352227 is excluded from real free space 3217560436736 as 1% of capacity reserved[14.05.2025 10:58:22.234]    <32>    Info (3)    [RTS] Estimated free space on Extent id 96963ca1- is 722861084509 bytes, (original size = 722861084509, active tasks = 0)[14.05.2025 10:58:22.234]    <32>    Info (3)    [RTS] Updating Container id = 003b65d0 actual free space to 722861084509. 249469935

Since upgrading our backup server to Windows 2025, on Veeam the WD devices are showing as unavailable and we are unable to rejoin them to active directory.This has only happened since upgrading to windows server 2025

Not new to the software but new to setting up a backup system. I will be “promoted” to Backup Administrator and as part of the training I need to set up my own system. Currently, I have VEEAM B&R 12 installed on a desktop and running two tests - one successful, the other is a failure.Test One is creating a simple job - VEEAM to back up a directory on the same desktop which is my “server”. The job works fine, understand the setup and job tasks.Test TWO is creating a simple job to an endpoint (my laptop). I managed to set up the job and laptop has windows agent installed.VEEAM cannot:2025-05-28 1:42:45 PM Failed Failed to send backup job configuration to <laptop> Error: Failed to update backup job  Managed by agent job ID: 04100ad7-e66a-4b4d-8221-74baf1c52987.  Managed by agent job name: Agent Backup Policy 6. 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

Hi all,Relatively new to the community; been working with Veeam a while now, though!After finally sorting some bits out, I’ve built out a home lab to play with Veeam, but also use my own data as a way to gather experience about day-to-day use of Veeam (I am an architect, so naturally, I never touch the product in anger 🙄 - hoping to fixing that!)I’m loosely aware that the Veeam for Mac agent is relatively new, so while I understand there will be bugs, my current experience has been fairly frustrating (I don't want to treat this as a support-request post, so wont go into specifics). What is your experience of using the Mac agent so far?

I wanted to ask here in the community if anyone has developed a Veeam Tape report mainly for size reporting that they can share?  I am looking in to VONE but the reports there are not sufficient enough for our reporting.We have a service that clients send to VCC then it tapes out for long term offline storage.  So each month we need to automate reporting on size for each tenant of consumed data on tape.I am also asking in the Vanguard slack too about this so some of you may see this there as well.  Also doing my Googling too. 😋

VM networking was much simpler. In VMware, there is a lot of planning when managing the network. You create virtual switches per host and assign properties like MTU size, VLAN, etc and pair those with physical NICs. You setup VMkernel NICs with specific roles to control host traffic. With Scale computing, you set a native VLAN on the physical switches and use standard VLAN Trunking to the host. You assign an IP on the management network which uses the default VLAN and then tag VMs on their virtual NICs directly, skipping all the complex concepts of a vSwitch. A separate Linux bridge with different physical NICs or a subinterface with a VLAN is used for the cluster backplane used for storage and inter-node cluster communication depending on how many NICs the host has. If a VM needs to be on multiple networks, you can assign one NIC with a certain VLAN, and another NIC with a different VLAN. You can also choose not to tag at the port and let the guest OS setup VLAN tagging, similar to as

In some situations/scenarios it is absolutely necessary to move the Veeam Configuration Database (PostgreSQL) to another hard disk of the Backup & Replication Server (e.g. if the C: partition is too small). After installation, the Postgres databases are located under: C:\Program Files\PostgreSQL\xx\data (Unfortunately, the path cannot be changed during the Veeam installation).Moving the PostgreSQL database is actually quite simple and can be done with pgAdmin. Before you start the migration, you should create a VMware snapshot and/or a Veeam Configuration Backup.Download pgAdmin from their website (pgAdmin – PostgreSQL Tools) and install it on the Veeam Backup & Replication Server.Add a second hard disk to the VBR server and create a folder for the database in it.Because the PostgreSQL service runs under the “Network service” account, the folder must be correctly authorized. To do this, add the “Network service” user with “Full control” to the folder under “Security”.Stop the V

 We've been a certified Scality ARTESCA partner for almost six months. In addition to my lab installations, I've already deployed four productive ARTESCA systems for our customers, both single-node and three-node cluster systems.Since the beginning of June, version 3.1.1 has been available for Scality ARTESCA.  Documentation & Release NotesThe corresponding documentation and release notes can be found at https://documentation.scality.com/ . Access is via OneLogin with an existing Scality account. To upgrade from version 3.1.0 or 3.0.X to the latest version, follow the steps described here: https://documentation.scality.com/Artesca/3.1.1/upgrade.html . Or check out the step-by-step process in the corresponding blog post here 😉.  ARTESCA UIAfter successfully logging into the ARTESCA UI with the appropriate authorization… …we are greeted by a notification that a new ARTESCA version is available.The update components can be downloaded via the ARTESCA UI, as in this scenario, with the

Hi Team,Got a VM running on a ESXi host. Need to add additional disk space to C: drive. However, couldn’t increase it any further using the VM properties under storage. The provisioned disk capacity is 230GB and the total disk utilization is closer to 230GB as well. The machine is thin provisioned. The connected SAN storage got free available space too. Just wondering the best option to add more disk capacity to C: drive please?Appreciate your feedback.kind regards,Andrew

Using S3 Object Lock’s Governance mode with Veeam Backup & Replication v12.1 Veeam Backup & Replication (VBR) v12.1, which was launched in December of 2023, has many great features and new capabilities.  One of those features is the ability to use S3 Object Lock’s Governance mode when you setup an object storage repository to be immutable.  The purpose of this blog is to introduce you to the Governance mode and how to use it within VBR 12.1.So, what is Governance mode?  To answer that I first need to briefly explain S3 Object Lock.  It is a feature of S3 and S3 Compatible object storage to prevent objects from being deleted or modified until the object lock retention has been met and the lock expires. There are two modes for the object lock retentionCompliance GovernanceCompliance mode has been used by Veeam Backup & Replication since v10 of VBR was released in February of 2020.  Compliance mode locks the objects with a high level of strictness.  This strictness includes: p

For those with IBM Flash System Storage, you will have noticed a surprise at the end of your 12.2 upgrade. It will ask you to install the plug-in on your Veeam server at the end of the process. It will also tell you that backup jobs may not work properly until you do. The first take away is don’t start this upgrade at 3PM on a Friday thinking you have plenty of time to upgrade your entire Veeam infrastructure before the end of the day.  This extra step didn’t take too long but still added some extra time to the process. As with anything, check the release notes, and compatibility with all hardware, software, and firmware before doing installs on production servers.   This is a very simple install that requires hitting next a few times and waiting.  Setup In this test, I’m using both backup from storage snapshots, as well as snapshot only jobs. Snapshot jobs are easy to configure as seen below.For the backup repository, choose snapshot only. If you configure a secondary destination, you

oracle linux virtualization manager is now supported in Veeam B&R and we have just started using it last week.Are there any plans to support it in Veeam One?

Hello,what are the minimum permissions that linux user needs to have to be able to do file level restore using Veeam?Setup is as it follows:I have Rocky Linux 9.5 OS VM and I have Win Server host where Veeam is located. The goal is to be able to do file level restore from that Linux server. The thing is I need user for it.What I would like to do, I only want the user to be able to do restore from one specific directory, I don’t want him to be able to see anything else or do anything else, except the restore part, what is the best way to achieve this?

I had the discussion two times last week, so I think it is worth sharing here.You may have noticed, VMware deprecated image level backup of its vCenter Appliance (VCSA) with vSphere 7. What does this mean? Basically, it is still supported to do image level backup and restore with VCSA 7.0. But it will not be supported in future releases. Notice that U1 and U2 are still 7.0 versions. With 7.n, with n>0, VMware will not support image restore of VCSA any more. From my perspective, this step was taken because problems arise when restoring this Linux appliance. I have seen many appliances requiring a filesystem check after restore or crash. When you are lucky, everything works fine afterwards. If not, you have to file a support ticket.To avoid this, VMware offers a new way for VCSA backup. Since 6.5 it is possible to run file-based backups and restore of VCSA. Since 6.7 this can be scheduled. With this, new protocols are supported as well: FTP, FTPS, HTTP, HTTPS, SFTP, NFS, or SMB. Pleas