Veeam Data Cloud for Microsoft Entra ID
Top technical сommunity program
Run by users, for users
Start FREE on-demand training
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.
Hello Community!Veeam releaesed an update to it’s VBR product today. Click the link below to view the KB:https://www.veeam.com/kb4743The following CVEs were addressed with this update:CVE-2025-23121 (critical severity)A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain userCVE-2025-24286 (high severity)A vulnerability allowing an authenticated user with the Backup Operator role to modify backup jobs, which could execute arbitrary codeCVE-2025-24287 (medium severity)A vulnerability allowing local system users to modify directory contents, allowing for arbitrary code execution on the local system with elevated permissions.It is obviously recommended to perform the update as soon as you can.You can also view other fixes/improvements from the below KB, as well as find the updater and full ISOs:https://www.veeam.com/kb4696Best.
Anyone using VSPC to patch VBR servers - is there a way to have it patch VEM first and then VBR or is VEM a manual process then use VSPC to patch just VBR?We are moving towards automation and VSPC is a great way to patch/update servers which I am exploring due to the recent 12.3.2 patch that came out.Any insight is appreciated.
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.
We are using a Quantum Scalar i3 tape library with a 25-slot license. Accordingly, we've created a partition for 25 tapes and currently have 25 tapes loaded, the cleaning tape ist tape 26 and not in the partition.The problem:We need to perform a cleaning operation via Veeam using the cleaning tape. However, the cleaning tape is not showing up under 'Unrecognized' or anywhere else in the tape libraries within Veeam.When trying to initiate automatic cleaning from Veeam, it says it cannot find the cleaning tape.Steps already taken: Rescanned the tape library in Veeam Performed a full inventory Ran a catalog operationAdditional Information:• Library Firmware Version: 330G.GS118• Veeam Version: 12.3.1.1139• The cleaning tape is correctly shown in the Quantum Scalar i3 web interface. It has the type set to 'Cleaning', a barcode 'CLN001L1', and is marked as 'Accessible'. Its location is also properly listed.• The cleaning tape is not in the partition of the 25 Tapes.Description of the Library
Veeam Health Check (VHC) 2.0 Is now live! VHC 2.0 features a revamped HTML output as well as the ability to export PDF. The revamped report reimagines the former report to make it more user friendly:Report: Updated color scheme Layout updated to a more “comfortable” viewing experience Cells are padded to make the data less cramped and easier to read Columns are now sortable to aid in examining the data Go To Top Buttons are no longer at the bottom of each table. This has been replaced with a floating “Go To Top” button that is always visible. Job Information: The Job Info tables has been broken down by job type. This separation makes it easier to analyze specific job types as well as totaling up the size of these jobs. Columns have been updated to more useful data such as: Day or Point-based retention GFS retention Compression level Block Size Indexing indicator Malware information tables Configured Settings Excluded objects Events Summary Infected Items inf
The environment described in this architecture consists of one main datacenter containing 10,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to a Veeam Data Cloud (VDC) customer Vault. Proxies are installed on physical servers and use the network transport (NBD) method.
Ciao, come sappiamo le migliori pratiche sconsigliano di mettere i server Veeam dentro un dominio active directory di produzione: meglio fuori dominio o in uno separato e ad hoc.In ogni caso, se il vostro (o dei vostri client) server è in dominio, bisogna aggiornare abbastanza in fretta perché il punteggio di questa vulnerabilità è “solo” 9.9https://www.veeam.com/kb4743 P.S.: ci sono anche alcuni problemi minori risolti
Hello everyone, I'm continuing my exploration of Veeam v13. Today, I'm sharing with you a presentation of the Web UI and the thick client. In this first section, we will cover:Configuring a component via the WebUI Configuring a component via the thick client Configuring a backup job from the WebUI Performing a restore from the WebUIEnjoy the read!Find my previous article here : 1. Veeam Software Appliance WEB UI / Console⚠️ Reminder: We are testing a beta version here. Some features are still missing, incomplete, or may not be included in the final release.Deployment: In this Beta version, to deploy V13 as a virtual machine, the following prerequisites are required:Two hard drives of at least 256 GB each are mandatory. I have allocated 4 vCPUs and 16 GB of vRAM. Rocky Linux is used as the OS type, as this is what Veeam uses here. A paravirtualized SCSI adapter will be used by default.Additional Information:The design of the WebUI interface is 80% complete. The thick client interface i
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
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
