Veeam Data Cloud for Microsoft Entra ID
I’m trying to investigate the levels of Veeam dedup/compression thats typically seen when using a non deduplication appliance. Is it really between 2:1 and 3:1? Again I’m thinking about typical VM workloads.Also if using XFS and fast clone it works in a similar fashion to dedup.Be interested if anyone has any data on data reduction thats “real world”thanks
We need to analyze why the error message is appearing during the backup window. The alerts are being triggered due to the replication process between the T and O servers. Specifically, these alerts occur during the backup window of the T server, which runs from 9:00 PM to 10:00 PM PST. During this period, replication from T to O is paused, resulting in theError 9036: "Paused for backup or restore."However, the alerts are only seen on alternate days, not consistently every day, which requires further investigation. T Server – File1 O Server – File2 Primary Concern:The question raised is why the production server experiences impact—such as replication delays or user access issues—during the backup window. While domain controller replication is standard across all servers, it appears only the file server is affected during its backup schedule.Currently, the file server is backed up using an Application-Aware Processing policy.Veeam’s Application-Aware Processing ensures backup consiste
我尝试卸载相应的主机，然后重新添加它;但还是无法解决
Hi All, I am trying to configure backup alerts for the Nutanix backups same as VMware in the Nutanix proxies using Azure by creating the App registration process, we have configured everting as per Veeam article but now while sending test email we are getting some SSL error also it is showing not authorized with Microsoft even though it is showing authorized during configuration. In Azure app registration for the same we have selected platform as single page application only, is that correct or we need to select platform as web? please help to resolve this issue as I am not getting much support from Veeam support. Need your help and advice for the same as for Mail configuration we are using Microsoft with modern authentication using port 587.
升级到 12.3.1 后，客户端代理已更新，但 Linux 加密存储主机仍然无法连接和更新;我手动重置了加密的库帐户密码，但仍然无法连接。我该如何解决这个问题？ 我尝试刷新，但仍然不起作用
Hi,The Tenable Nessus report for PostgreSQL 12.x < 12.18 / 13.x < 13.14 / 14.x < 14.11 / 15.x < 15.6 SQL Injection . Output from most recent scan Path : C:\Program Files\PostgreSQL\15 Installed version : 15.1 Fixed version : 15.6Any patch or update guide from Veeam Backup & Replication 12 Build 12.3.1139 ? Thanks
I’m unable to run any backups on Veeam Agent for Windows (6.3.1.1074, free edition). While my setup was working previously, I now get the error “Failed to create VSS snapshot” when attempting to run a backup.My destination is an SMB share on a local Debian host. Other devices on my network (In identical configurations, “Entire Computer” and encrypted backups) are able to back up to that share successfully, it’s just this one machine that’s failing.I’ve tried the usual suspects: Restarting the machine, removing/re-adding the backup job. I also tried the steps outlined in this post:Opened an Command Prompt (Run as Administrator)Ran the following commands:net stop vss net start vssYou can also restart these services in services.msc:Volume Shadow Copy Microsoft Software Shadow Copy Provider Without success. The log from my backup attempt is:6/4/2025 09:14:13 :: Initializing 6/4/2025 09:14:20 :: Preparing for backup 6/4/2025 09:14:26 :: Backup file will be encrypted 6/4/2025 09:15:07 :: Fai
Dear Community, Anyone face this issue if yes kindly guide how to fix this. Failed to upgrade host components. Error: 'Exception of type 'Veeam.Backup.Common.CAppException' was thrown.'
When updating a vcenter server appliance, part of the process is to replace the old vcenter VM with a new VM that has the same name.The problem I encounter is that the Veeam backup job fails because it seems like it’s trying to continue to backup the old VM which was deleted.…Processing vcenter Error: Cannot find Linux guest credentialsUnable to connect to guest OS for guest processing. Cannot find Linux guest credentialsError: Cannot find Linux guest credentials …Keep in mind that this VM was previously excluded from guest processing and indexing. I even removed the vcenter exclusions and re-added them to the job but when you run the guest credentials test, vcenter is listed twice and fails the tests even though its excluded. That VM shouldn’t even be tested since guest processing and indexing are disabled for Windows and Linux.Below are the errors from the guest credentials test:…6/5/2025 5:03:47 AM Failed Photon OS guest OS requires Linux credentials or a transport service installed
Hi,A newbie here with using Veeam for Oracle RMAN backups.I am trying to understand/visualize whether the RMAN retention and Veeam Immutability are independent of each other or are they related in some way.We run our backups on the Oracle DB server using shell scripts and cron and using a RMAN catalog.We have set CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 35 days.We do RMAN delete obsolete as well.The Veeam Immutability is 7 days.Does Veeam delete the backup files if they are 7 days old or does it delete the files if RMAN fails to delete them after 35 days? Or does Veeam do nothing unless we uses the force-delete?Kinda hoping someone has a presentation of some sort to show how this works. Have read thru the documentation and can’t find any that explains this. Or maybe it is explained more clearly/visually in any Veeam documentation and I just can’t find it.Any reply will be much appreciated. Thanks in advice.
Hello. Looking for feedback on installing the Veeam Windows agent on a desktop machine that’s managed by Microsoft CoPilot We have a service account with a known good password. VBR requires that the credential be entered as “DOMAIN\username” . But since the target machine is managed with CoPilot, it seems to need logins to use “username@DOMAIN” When we try to use the “DOMAIN\username” credentials to push the agent, we are getting a “invalid username or password” error from the VBR console, even though we’ve tested the account and we know the password is good Is there any way around this account format issue? we did try entering the credentials in VBR as “user@DOMAIN” but that didn’t work either.
Result of my attempted backupHello again, As you can see from the image above, there was an issue with my backup and none of it saved, the rest of the error info that I could copy is: 22/05/2025 10:45:03 :: Error: Cannot process pending I/O request (offset: 598344892416, size: 65536): async reader terminated Corrupted block processing thread failed unexpectedly Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>]; Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Cannot process pending I/O request (offset: 598344892416, size: 65536): async reader terminated Unable to retrieve next block transmission command. Number of already processed blocks: [453602]. Failed to download disk 'FA96EA97' Any advice on how to proceed? Thanks!
We have created a backup job for SQL Server, to generate Full + Incremental backup and transaction log backups, and configured GFS for all the database backups (physical servers with GFS policies as well).In the environment there are three SQL Servers as part of an Always On Availability Group cluster.The backup of the DB run and then finishes OK.The Transaction Logs portion, says that all the 44 DB has been skipped.What could be the posible causes that makes the transaction logs not been backed up?On the documentation I've found that to became subject to log backups there are some conditions: - Databases in the Always On Availability Groups for this node were successfully backed up for the last two processing intervals.The backups has been executed for the last 10 days, and no transaction logs has been backed up.Does the backups and transaction logs has to be run on the primary SQL Server?
Olá a todos estou enfrentando o seguindo problema em meu windows 2025 server:Esse servidor foi recem adquirido da Dell e ele foi entregue com o windows server 2025 standard, instalei o veeam backup agent for windows, criei minha job de backup diario, configurei o meu servidord de arquivos e meu Active directorio, instalei o antivírus kaspersky endpoint security cloud, rodei minhas primeiras job corretamente, depois de dois windows updates e de alguns reinicio do sistema operacional meus backups param de funcionar. Não encontrei nada nos logs que me dessem uma pista, apenas a mensagem de erro falha inesperada, terei criar outras jobs e a mesma falha apareceu.Alguém poderia me dar uma ajuda de como contornar essa situação ?obrigado
Estimados:Tengo una duda sobre el backup copy… Resulta que tengo un job basado en agente que funciona correctamente. Cuando se crea el backup copy sobre ese job para un repositorio que está fuera de oficina (este está en una red a través de un enlace MPLS y no tiene perdidas de paquetes) su velocidad y rendimiento baja y se vuelve lenta la tarea. Leí sobre poner un servidor Gateway para que sea más eficiente. Es correcto eso y si pueden dar una explicación más en detalle sobre ello? Saludos,
Replication Job issues, unable to replicate virtual machine from the source to destination host. Error: VDDK error: 1 (Unknown error). Value: 0x0000000000000001 Failed to download disk 'VDDK:vddk://[Datastore-Replication] GTBHELP01_replica02/GTBHELP01.vmdk'. Shared memory connection was closed. Failed to upload disk 'vddkConnSpec>' Agent failed to process method {DataTransfer.SyncDisk}.
Hey guys,I have the same random problem with my Proxies (Windows), VMDK are still attached to my proxies randomly once the job finish. The proxies are not backuped during the different backup jobs. The Vms that Veeam processed is found to require consolidation.On the vmware side I found a log " Unable to access file since it is locked An error occurred while consolidating disks: Failed to lock the file. Consolidation failed for disk node 'scsi0:0': Failed to lock the file." at the end of the backup job.But I don’t find the root cause. Have any of you ever encountered this problem?
I’m encounter error when I adding the linux server for immutable repository. Anyone can help?
Hi everyoneI'm experiencing an issue with one of our Veeam backup jobs where the process fails consistently with the following error:Error: Failed to do TLS handshake.Possible cause: Unknown errorDetailed info: Reconnectable protocol device was closed.Context: Veeam Backup & Replication is being used for a daily VM backup job. The failure occurs for a single VM. The backup job retries multiple times, but ends with 0 bytes transferred and a final error after approximately 2 minutes. TLS handshake failure seems to prevent the backup from initializing. No successful backup was performed (0 B read, 0 B transferred). What we’ve tried so far: Verified basic network connectivity. Restarted both the Veeam Backup server and the affected VM. Confirmed that the VM is reachable and responsive. No recent configuration changes were made to the VM or the infrastructure. Questions: What could be causing the TLS handshake to fail in this context? Could this be related to certificate
Hello everyone,My Veeam B&R server is running on a Windows 10 VM and I’m about to migrate it to a Windows Server VM. I’m going to take the opportunity to migrate to PostgreSQL for the backend at the same time. I’m more comfortable with PostgreSQL than SQL Server and it will reduce our licensing costs.I recently went through a VMWare to Hyper-V migration (thanks to Veeam it was very straightforward).The downside is that I must maintain the legacy VMWare backups until the end of the retention period and maintain the new Hyper-V backups in parallel. I can’t afford a reset on block tracking or whatever references are maintained for XFS reflink usage.With a migration to a new server and new database engine, relying only on the Veeam B&R backup .bco file, is there any danger of losing changed block tracking data or resetting the reflink index, triggering a requirement for a full backup? With thanks,Simon
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
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!
Looking for validation and/or alternate direction here. I've got a customer looking to deploy VRO. We are at a stand still because of SQL licensing. Straight from our documentation, VBR doesn't support SQL managed Instances, Veeam ONE supports RDS. VRO doesn't specify anything in the guide regarding SQL managed instance support. Obviously given the limitation with VBR not supporting SQL managed instances, renders deployment unsupported. As all (3) VBR, VONE, and VRO databases are deployed onto the same SQL server at the time of wizard deployment. This has come up a few times now, customer upgrading to VDPP then being locked in with SQL licensing costs. Each customer has a bit different scenarios. No DR. Cloud is DR, no native SQL cluster in Cloud.
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
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.
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.
