Solved

Hey there, we need Offsite-Backups of our Unstructured Data. Since the Backup Files are roughly 3,5 TB in Size, its impossible to get that Data to the Site directly due to slow Internet Connections. So i first configured a Secondary Target NAS for the Backup Job Onsite to get that Backup Copy onto it. I then moved that NAS to the Offsite Location, changed it’s IP and added it back into Veeam as a new Repository. Did a Rescan of that new Repo and Veeam found the Backup Data and added it. I now added that new Repo to the secondary Target in the Veeam File Backup Job and removed the first one (which was the same NAS with the Onsite IP which is now invalid). I then restarted the actual Backup Job. It created some data, finished teh Job and the new Backup Copy Job started. But here’s the problem: It completely ignores the Backup Copy already in existence on that (now) Offsite NAS and instead starts creating a whole new Backup Copy. This is absolutely inacceptable. How can i tell Veeam, that

In Veeam13 how we can move existing job to other repository?I try to edit the job and change the repository then when click next i got this prompt.In earlier version as i remember there are option to move or create new. 

Hello - I am running Veaam Backup and Replication V.12 and am attempting to configure email notifications using Microsoft 365 modern authentication. I authorized the connection via the MSFT 365 signin dialogue and when complete I can see the indicator that the token is valid, but when I send a test email I get a general exception error message (see screenshot). The error doesn’t give allot to go on, has anyone else seen this and can recommend a solution?  

HI..I create user account for myself in Enterprise Managerbut when i logon using my account why i got error ‘Cannot find backed up machines where the user belongs to Local Administrators group’ 

I have installed Veeam Software Appliance on fresh hardware. My intent is to recreate my backup infrastructure around it and then deprecate my current Windows server that handles the jobs. I am not finding anywhere to download a license key for version 13. It does not show in my account portal as an option for generating a key.

With the newly released Veeam v13, we need to install it at two sites, perform primary backups, and then cross-replicate the backup data from each site as a secondary step.Is this a feasible scenario? 1. Backup Server Configuration- Site1: Dell R760 + VSA (Three backup target servers; agent connection and backup completed)- Site2: Dell R760 + VSA (Five backup target servers; agent connection and backup completed) 2. Additional Configuration Required- Backup Copy from Site1 VSA's backup data to Site2 VSA's backup repository (with Veeam WAN Accelerator enabled)- Backup Copy from Site2 VSA's backup data to Site1 VSA's backup repository (with Veeam WAN Accelerator enabled) 3. Questions- I'm unsure how to register the Site2_VSA_Repository on Site1_VSA. I attempted to register it via the Veeam UI below, but I don't know how to handle the Linux authentication part.Backup Infrastructure→ Backup Repositories→ Add Repository→ Direct Attached / Network / Linux - Is there any documentation that co

I have one VBR server with tape installed in main office.Then i also have VBR on other branch in different city and can i use tape on main office to store the backup?I try to add tape server on branch VBR server and pointing to VBR server on main office and should i take the ownership? 

Hi there,I have a question to which i haven’t found any satisfying answer so far.I manage an IT-Infrastructure with three distinct sites and locations.In the past we have used Acronis Cyber Protect but are now switching over to Veeam.Every site is supposed to have its own Veeam B&R Server managing its clients and servers, but only one of them should have a dedicated hardware Tape-Server connected that writes the backups of all three to tape.While I loathe Acronis, WHEN it worked at all (big when), it didn’t care where the backups originated from and simply wrote everything in its SMB-share to tape.Veeam doesn’t like this, cause apparently you can’t set up a tape-job for “imported” backups.From what I gathered, I have three options that are all either worse than with our old solution or will outright not work, haven’t tried all of it so far.We could simply do the tapes as “file to tape” jobs and copy the backup files of all three sites. But that would probably double recovery time c

Does anybody know if in the VEM 13 REST API, the JSON responses have been changed to follow a more accepted naming notation (sorry the notation name escapes me)So e.g. in version 12 a json element that used to be called Entities, it is now called entities, BackupJobSession becomes backupJobSession etc which is enough to make Javascript scripts fail.It seems every element starts with a lowercase letterAm I right that this is something that has changed between versions?Is there anyway to get a v12 style JSON from v13 VEM? ThanksCostas

One of my VBR use rental license and i’m not understand about the calulcation.Total I have 25 endpoint backup by VBR, 1 is windows agent, 21 is hyper-v, 3 is vmware where i split into 2 job.The qty of my rent license is 275.In the license information we can see I have 22 VMs and total used point is 242 (22 * 11).  In the license report the qty used is 242 and in the bottom of report sya this report is not include 2 new VM. My question is :Totally i have 25 endpoint, but wht the license only counted for 22 endpoints? What is +33 in the license information? And why in the license instance only showing 23 endpoints? Why the windows agent showing 0 likely this not consume the license? in the license report why not included 2 new VM? Is there any delay? 

Hello guys,Having a problem with one of our Repo.I upgraded the VBR from v12.0 to v12.3.2 before I upgrade it to v13 since it’s required.After that I have problem with this repo. How to check which account VBR is using when trying to do the upgrade and is there a way of manually upgrading the repos?Thank you. 

Hi Everybody,a Customer of mine posted the following in R&D forum because we have some issues with his M365 Backup. They have a Case open since May adressing this issue but there is only litte to none progress. I thought that maybe anybody here might had a similar issue in the past and maby even a solution or workaround:We’re currently facing a critical issue involving both Veeam Backup for Microsoft 365 and Veeam Backup & Replication (VBR), and we’re hoping to hear from others who may have encountered something similar.Background: After restoring Office files (Word, Excel, PowerPoint) — whether from Veeam Backup for Microsoft 365 or via VBR from local backups — the files can no longer be opened. They appear to be corrupted, even though they were fully functional in their original state on SharePoint or in the file system. Restoring to different SharePoint sites or local paths didn’t help. One notable detail: the restored files are smaller in size than the originals.Suspected C

Hi everyone,We’re running Veeam Backup & Replication 12.3.2.3617 Community Edition and during the Backup Copy job that copies to a USB drive the “Backup Copy USB.vbm” is not saving backup meta.Error message:Failed to save backup meta to [\\ServerName|usb|Backup Copy USB|Backup Copy USB.vbm] Error: Failed to call RPC function 'FcRenameFile': An unexpected network error occurred. Failed to rename file from [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm_13_tmp] to [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm].I went through several troubleshooting steps in Veeam Backup to try to fix the recurring error with the VBM file.Troubleshooting steps taken were firstly to disable Indexing on the USB external hard drive.I also forced Veeam to rebuild the .VBM file on the external USB hard drive.I copied existing VBM file, deleted it off USB hard drive, then resynced the Disk (Copy) to USB backup job. Veeam then automatically rebuilt the .VBM. This worked, but the same error is s

Hello, please give me suggestions to solve this problem. I have a problem regarding backup recovery which makes me stressed. I want to replicate or restore data from one baremetal to another baremetal in the scheme below without vSphere.Baremetal A supermicro, esxi 8.0 host (master node) Baremetal B Intel, esxi 8.0 host (node ​​replication) Baremetal C Dell R760, esxi 8.0 host (node ​​replication)I ran some replication and recovery testsVM test 1restored from baremetal A to baremetal B, successful without any problemsrestored from baremetal A to baremetal C, success, no problemsVM test 2restored from baremetal A to baremetal B, successful without any problemsrestoration from baremetal A to baremetal C, there were many problems (I will attach it below)VM test 2restoration from baremetal B to baremetal C, there were many problems (I will attach it below) I have also done a file copy test for "vm test 2" but it still has problems, for some reason it refuses to run on the baremetal Dell R7

EDIT: Title is misleading.  File2 is connecting fine but File1 is not.(Inventory right now)______________________________Veeam backup server (backup1) running enterprise plus 13.0.1.180. Windows Server 2022File1 and File2 on Windows Server 2022.  All three servers are joined to the domain. ______________________________(Story)Backup1 was running 12.3.2.3617, upgraded it to 12.3.2.4165.  After the upgrade I was able to successfully run backups on both file servers fine.  Decided to take the plunge and upgrade to v13.  This is where things started to fall apart.File2 is connecting to Backup1 and taking backups fine.File1 is not.  (Where I am at now)The issue with File1 one is Failed File1: Failed to upgrade host components. Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.' (0:01:04)The credentials used to connect to both File1 and File2 are the sa

Hello guys,I’m planning to do the upgrade to v13.Is there any recommended way of doing it, documentation that I can follow?Thank you in advance.

Hi,  We currently have VBR 12.3.1 Windows installed with VHR 2.0. When I ugrpade the VBR server to V13, do I immediately have to upgrade VHR too or can I do that a few days later?ThanksEdy  

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. 

I get the error “30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'                             b4634265-9228-4a5e-9d95-2c12313e89c6”This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… How do I fix this? 

Hi Community, We have a Synology NAS storage in our environment and would like to confirm the following: Is there any possible way to add Synology NAS storage to Veeam Backup? After adding Synology NAS storage to Veeam, is there an option to send data from Synology storage to Google Cloud Storage (Object Storage) through Veeam? Please advise if this approach is supported and share any best practices or documentation that can help us implement this. Thank you for your assistance.

I get the next error to tried to configure a VEEAM Location Profile in KastenStatus:  Error:    {"message":"Location profile validation failed","function":"kasten.io/k10/kio/configcontroller/profile.validateProfile","linenumber":49,"file":"kasten.io/k10/kio/configcontroller/profile/profile_validation.go:49","cause":{"message":"No supported infrastructure profile is defined","function":"kasten.io/k10/kio/configcontroller/profile/internal/locationprofile.checkLocationVBR","linenumber":56,"file":"kasten.io/k10/kio/configcontroller/profile/internal/locationprofile/vbr_validation.go:56"}} My K10 instance is deployed in my Openshift cluster Regards,

Can we get backup status for VDC M365 using powershell like in VBR?

Backup Job using Storage Snapshot Unable to Find Ontap SnapMirror Relationship for Secondary Target. Backup finished with Warning: Cannot find any relevant ONTAP SnapMirror and SnapVault relationships   Storage Replication between the Source and Target destinations is working. I was looking at the job log and saw that Veeam was able to identify Primary SnapProtections.   There were lines showing WARNING: Replication of all disk snapshots of vm asdasdfasf is not possible for ‘Snapshot Replication’. Thanks again for your input as to possible reasons why this is happening.  

Hi everyone,I’ve noticed something potentially incorrect in the Veeam Calculator results: When sizing for VMs or Agents, if I set a forecast period of 1 year or more, the result returned is always identical, regardless of how many years are selected, even when a growth rate is applied. I also compared the results with a sizing I completed a few months ago, and the values now returned for a 1-year forecast + growth rate appear to match what used to be calculated as a 3-year forecast at that time. This behavior seems inconsistent, and it makes me wonder if there could be an issue in the calculation logicHas anyone else noticed the same behavior?Would it be possible for to review the calculation logic or code to validate if this could be a bug?Thanks in advance for your feedback!  

I upgraded my vmware (esxi and vcenter) from v7 to v8. What i do is install esxi8 and vcenter8 then i migrate the vm under v7 to v8.After migrated to v8 i run the existing job and get error, i can see the vm size is 0 in the backup job. Then i remove the exising vm in the backup job and select same vm in vcenter8. The backup job is running but vbr make full backup, likely vbr see this is new vm.How i can retain existing backup chain so when vbr backup same vm but in the different vcenter the vbr will continue by doing incremental backup?