Discussion Boards

Hello All I am reconfiguring my Backups, and trying to achieve disaster recovery, i want to backup local VMs,Microsoft 365 and Entra ID, for that i am using Veeam Backup and replication V13 (VM) Veeam Microsoft 365 for Email, OneDrive and SharePoint. look to add Entra ID but not sure which Veeam product will be best.for repositories i am thinking one local (immutable backup), Azure Blob (immutable backup) now my question is which product i should use for Entra ID backup, what i should use for local immutable backup, is “Object First” devices good? my backup will be under 8 TB, and what i should use for remote backup Azure or i think Veeam have product cloud vault? what will be best.  

Hi,Is anyone able to assist here? I’m trying to upgrade to Veeam 13, as part of the overall upgrade I have to upgrade V Orc from my current version 7.1 to 7.2. However, all that I can see in the previous versions is:But the pre-req explicitly says:Upgrade to Orchestrator version 7.2.1 is supported from Orchestrator version 7.2 only; upgrade from Orchestrator versions 7.1, 7, 6, 5 and 4 to version 7.2.1 is not supported:To learn how to manually upgrade from Orchestrator version 7.1 to 7.2, see Veeam Recovery Orchestrator 7.2 User Guide.  However, I’m unable to find the 7.2 version I need to upgrade to 7.2.1. Any help would be appreciated as the Veeam downloads are clearly not fit for purpose. Many thanks,LGH.

Hi all,It seems that today is vulnerability day! https://www.veeam.com/kb4830https://www.veeam.com/kb4831Let's start planning the updates!

I would like to know from you, gentlemen, if anyone here happens to use this NIST document. It dates back to 2010, but it seems to me to be an excellent source of information. What references have you been using in your projects?   

Malware detection scanned  a suspicious file from backup but the file is actually legit and so I marked it as clean and Exclude. If I modify the same file for testing purposes, will the malware detection flag it as safe, legit file since I marked it Clean and Exclude? Or it will be detected as suspicious again? Thanks. 

I am preparing to update Veeam for Microsoft 365 from 8.1.2.180 to 8.3.0.2201 and I just want to make sure I am all set in case there are any issue after the update. I don’t believe I have any PostgreSQL or NATS setup that I can recall from when I set this up. I suppose if I do it is all default. It also appears there is no config backup option in this program. We do back up this server, but it does hold both V365 and VBR, so not sure if that complicates things from a restore standpoint if there is a problem with the V365 update.I’m probably overthinking it, but it is the first time I will be updating V365 and just want to make sure my jobs and repositories don’t break or need adjustments after the update.The main reason for this update other than the prompt for an update was that we received a one time email last week saying “License update interrupted: License contract has been terminated” even though subscription and user licenses are active as far as we can tell. Possibly a glitch

SQL Transaction Log Backup fails due to temp staging disk full (Veeam Agent for Windows) EnvironmentProduct: Veeam Agent for Microsoft WindowsWorkload: SQL Server databasesBackup Type: SQL Transaction Log Backup (Application-aware processing)Error ReceivedThe following error appears during the SQL transaction log backup job: Log backup job: Backup Job for SQL Server Transaction Log BackupCollected SQL Server transaction logs do not match any existing database backup.Failed to perform internal backup:Code = 0x80040e14Source = Microsoft OLE DB Driver 19 for SQL ServerDescription = Write on "C:\ProgramData\Veeam\Endpoint\SqlLogBackup\{GUID}.bak"failed: 112 (There is not enough space on the disk.)Database hide_name_db        Status    UnprotectedFailed to perform internal backup (hide_name_db): Code = 0x80040e14 Code meaning = IDispatch error #3092 Source = Microsoft OLE DB Driver 19 for SQL Server Description = Write on "C:\ProgramData\Veeam\Endpoint\SqlLogBackup\{18aa4e5f-9ef9-45f8-ad9a-

(running Veeam 13, Community/Free edition on Win 11).I did a bunch of migrations and updates a month ago. Before doing so I set aside the existing Veeam backups, so I have them. When I try to import a backup for one server from it (just to browse and retrieve a couple files) it tells me "Path contains invalid symbols...",. But it doesn’t. I have a path with no special characters or trailing spaces or anything like that. The message isn’t any more specific.I’ve tried mounting the file share where it exists as a mapped drive and a network location. I would copy it into the local machine to try that, but there isn’t room.Also, the import dialog says “Specify a backup to import. You can import backups from a backup repository or any managed server.” but the dropdown menu only lists the local machine and my two hyper-V hosts, not the repository (which is on a network share).Thanks.

We use AWS VTL for backing up some of our larger SMB file shares (mainly AWS FSx for Windows) that run into a few terabytes each.When running a tape backup job we’d run a powershell script to check there were at least 10 free tapes before starting each job (there’s around four or five chained jobs).The script worked fine on VBR v12, but always returns “TooManyRequests” on v13.I have found various “retry” scripts, but the VBR commands ALWAYS return “TooManyRequests” so never complete.Is there now an alternative method to auto load blank tapes that didn’t exist in v12?Our script that worked in v12:# Get Library$NOVA_Tape_Library = Get-VBRTapeLibrary -Name "Novasol Gateway-VTL V3"# Get Number of Free Tapes$NOVA_Free_Tapes = (Get-VBRTapeMediaPool -Name "Free").medium | where {$_.LibraryId -eq $NOVA_Tape_Library.Id}# if number of free tapes < 10 import tapes and format for use?if ($NOVA_Free_Tapes.length -lt 10) { write-host "Import Tapes" Import-VBRTapeMedium -Library $NOVA_Tape_L

Hi teamA hardened repo using the VEEAM Hardened ISO experienced a power cycle and upon reboot its out of band interface lit up like a x-mas tree.Upon further investigation it appeared that the virtual disk was just gone. A message indicated that RAID6 detected foreign configuration.Been working with vendor and they have asked to install storcli on to the server.Would this be possible, being a hardened repo? They have a non-recommended method alternative too.Can’t believe that a power cycle did this and not sure what the root cause is but would be good if we could get it back. Otherwise will have to rebuild and sync primary backups againcheers

Hello,i would like to ask, if somebody is not experiencing that issue, that big environments have issue with SSL connection? we have all in one boxes - VBR, VEM and postgresql is on the same machine at the end of postgresql.conf #------------------------------------------------------------------------------# CUSTOMIZED OPTIONS#------------------------------------------------------------------------------# Add settings for extensions heressl = onssl_cert_file = 'backup_server.crt'ssl_key_file = 'backup_server.key'ssl_ca_file = 'backup_root.crt' in svc_veeambackup.log we see[02.03.2026 11:40:10.307]    <35>   Error (3)    0: Breaking connector[02.03.2026 11:40:10.307]    <35> Warning (3)    Failed to obtain connection: [Failed to connect to [::1]:5432]. Attempt 1 of 20. in pg_hba.conf is preferred connextion via ssl# IPv4 local connections:hostssl    all             all             127.0.0.1/32            scram-sha-256host    all             all             127.0.0.1/32      

Hi,we are planning to use the Veeam Data Cloud for Salesforce Backup. We need to keep backups for 2 years. What, if we decide to switch the backup-partner. For example Salesforce native backup? We cancle our subscription. Fair-Use-Policy will delete the backups after 30 days, correct? What options do we have, to keep  the backups as long as our requirements are? The same question would be, if we decide to use veeam backup for m365 in the data cloud. Here we would have onedrive files, with a retention time of 2-10 years.  We do not plan to quit anything, but we need a valid exit strategie if we decide to use a cloud product. 

Hi everyone,I am currently reviewing the design of our Veeam Backup & Replication server and would like to follow best practices for disk layout.At the moment our VBR server is a VM with the following specs: 8 vCPU 32 GB RAM Windows Server Local SQL instance Only one virtual disk (C:) which is a VHDX located on HDD storage Currently everything is located on this single disk, including: Veeam installation SQL database Veeam logs Veeam catalog configuration backup Windows OS I am considering adding an additional virtual disk located on SSD storage and moving the Veeam-related components there to improve performance and follow recommended architecture.My questions are: What is the recommended way to migrate components from the existing C: disk to the new disk without breaking the installation? Which components should ideally be moved to the new disk (SQL DB, catalog, logs, etc.)? Is it necessary to stop Veeam services during the migration? Are there any known p

Hello everyone,For several days now, I have been receiving the following error message during our backup copy job:“Failed to perform backup verification Error: Unable to get block digest: block is not initialized. Skipped arguments: [0]; Agent failed to process method {Signature.FullRecheckBackup}.”I performed a full backup, but unfortunately the same error message appeared again. The copy job does not conflict with the backup job.How can I fix this error?Thanks in advance!Version: Backup & Replication 12, Build: 12.3.2.4165

Hello guys,After a basic restart of the VM I can't no longer access our VBR console.All services are up and running.Any recommendations?

Hi all. Running Windows Server 2019 as a standalone Hyper-V server. The server is in a workgroup.I have installed the community edition of VBR 12, and configured my backup repository.When trying to configure a new Hyper-V backup job, Veeam gives me a message to say that it cannot connect to the ADMIN$ share. However, if I type \\localhost\ADMIN$ into the run box, then the folder does open.I’ve tried setting my host name to localhost, to the server name and to it’s IP address. I’ve also tried with the current logged in credentials, and have tried by enabling the administrator account.Any help would be appreciated.Thanks, and have a great weekend!

I read in the news recently that Veeam has bought Securiti AI, which is going to have a direct impact on its data protection offering. This deal is a game-changer for Veeam's strategy, combining data resilience with data security.But what does Securiti AI do, and why did Veeam decide to buy it?Securiti AI is a big name in the industry, and they focus on Data Security Posture Management (DSPM), privacy and data governance. With a spent about £1.725 billion in total Veeam's big plan is to bring together their data resilience (which they're really good at – backup and recovery) with data security (Securiti AI's thing).So, why's this important for Veeam?I think this purchase is meant to create one command centre where they can use DSPM on data in use and on backup files as well. This means that sensitive data (PII, GDPR-compliant data) can be easily identified in backups, and the compliance and security posture of the backup data itself can also be verified.So not only can customers restor

Good day Running Veeam Community v12 with a VMWare environment. I am running a backup of 3 VMs. Since I installed Veeam I cannot do a backup copy of a job for one of my servers. The 2 other servers that I run a backup copy and send it in a remote location works but that server I always get this error: Processing [server name] Error: Times out waiting for NFS async IO block callback. Timeout: 180000 msec Failed to download disk 'filenameofserver-flat.vmdk'. Shared memory connection was closed. Failed to upload disk 'filenameofserver-flat.vmdk' Agent failed to process method {DataTransfer.SyncDisk}.Some restore points were not processed The local backup works but I cannot get the backup copy to workI created a different backup job for this server alone but I also get that error. The option I was thinking to do is to do a backup job just for this but i’d like to figure out why only that server on the same host as the 2 other servers is causing me this problem. Thanks for the help

When i tried to restore my database using veeam explorer for oracle from a backup created using application aware processing i got :Failed to resolve path : /h01/oracle/agent/agent_13.4.0.0.0.  

Hello Community,I would like to check if anyone has practical experience or official guidance regarding the following scenario.Has anyone successfully presented a LUN from a Dell Unity array via Fibre Channel to either: Veeam Backup Appliance v13, or Veeam Hardened Repository (JeOS) with the intention of using that LUN as: a backup repository, or an additional backup disk for the repository? My main concern is related to the fact that both the Veeam Software Appliance and VHR (JeOS) are locked down by default for security and immutability purposes. I could not find clear documentation or a community thread that explicitly discusses: Whether FC-based block storage is supported in this scenario Any limitations or restrictions when attaching external SAN LUNs Potential security or immutability implications Required configuration steps (if supported) or reasons why it may not be recommended Most available documentation and examples focus on local disks or direct-attached storage,

Hi All,Can you backup normal vms in Red Hat Openshift with VBR or do you need to use Veeam Kasten?Thanks,Benny

we are veeamawsbackup                   7.1.0.8                                 amd64        Veeam Backup for AWS. we want to upgrade veeamaws 10. can some one please provide the procedure for the same.

Hi All,  Has anyone seen hotadd Linux (Rocky 9.7) VM proxies go sideways and not mount after upgrading to v13? I also added a new v13 appliance proxy and the result were the same. Changing transports to net work fine. On this client side logging it shows: Error: Access to [/dev/sdb] is denied.Failed to check whether access to path is grantedFailed to open disk for write.Failed to download disk 'snapshot-909174XXXX'. CC tenant job logging has: <842>    Info (3)    Skipping VcdDatastore (VcdRef=[urn:vcloud:datastore:GUIDXXXXXX], Name=[*CLIENT_DS*]) because it does not have valid underlying vCenter resources VCSA 8.3VCD 10.4xVBR 13Rocky 9.7 latest Kernel.  We have a Sev1 open but its currently pending logging reviews.  

Hello everyone,After upgrading Veeam Backup & Replication from version 12.3.2.4165 to 13.0.1.1071, we also upgraded Veeam Plug-In for Microsoft SQL Server using the ISO 13.0.1.1071, which installed Veeam Plug-In version 13.0.1.180.The upgrade process completed successfully without any visible errors.However, after the upgrade, SQL Server backups are no longer running successfully.All SQL backup jobs are now failing with the following error:Error: [Microsoft][ODBC Driver 17 for SQL Server] Database is invalid or cannot be accessed Before the upgrade, backups were working correctly with no issues.Has anyone experienced a similar issue after upgrading to Veeam 13?Any suggestions on what to check would be greatly appreciated.Thank you in advance for your help.