Solved

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? 

HiWe have Fortinet Fortimanager and Fortianalyzer running as VMs. Up until last week, these got backup up absolutely fine. We upgraded these from 7.2.11 to v.7.4.8. Since then, the backups have been marked as suspicous with potential malware activity detected.I’m wondering what is going on. It may just be a coincidence but I don’t believe there is any malware.If I mark the backups as clean, the next backup just gets flagged as suspicious. This only happens on these 2 VMs. All other backups are running fine.  Has anyone come across this sort of issue before? Or am I missing something somewhere?ThanksRoy   

Hi everyone,I believe I’ve encountered a bug in Kasten K10 version 8.0.6. When creating a backup policy using a preset that includes block mode export, I noticed that the system automatically forces "Export snapshot references only", even though the preset explicitly specifies full volume export and a PersistentVolume (PV) is present.To test this, I created a policy that should export the full volume. However, once applied, the policy is transformed into "Export snapshot references only", and even after removing the policy, the export behavior remains unchanged.Has anyone else experienced this issue?Thanks in advance!

Has anyone set up an HA Cluster with Veeam 13 and figured out how to update the SSL for the FQDN that is used when managing a cluster?  When I go to my FQDN the SSL being is used is the Primary Node SSL so the browser shows unsecure.I would have thought this would have been done automagically when setting up the cluster.  Any ideas or thoughts from those that have done this?

Hello, I am trying to simulate retention for Veeam Agent Linux with this information:So it's a “Forever Forward Incremental” retention mode.The problem is that there is no periodic full backup with this retention, and it seems that the calculator does it by default:  I find 1.3TB, whereas if I calculate manually:   1 full backup (300GB source, 50% compression) = 150GB 29 incrementals (5% daily change, 50% compression) = 15GB × 29 = 435GB Total estimated storage: 150GB + 435GB = 585GB  Is it possible to simulate this type of retention? Best regards,Thomas

I have setup a new server on our network. Connected to domain, network, hyper-v installed and I am unable to add this server to the Virtual Infrastructure > Microsoft Hyper-V > Standalone Hosts > (server).  I have my Veeam server trying to contact our new server and there seems to be a road block. I am running Veeam V11a trying to setup a new 2019 windows server. During the hyper-v setup process I have added the name and/or IP address, I have selected the last option (standalone) which matches the description of the new server.  My credentials do work because I ran a test to setup a VM running server 2019 and I was able to set that up right away. For some reason the physical server is blocking the Veeam connection.  Is there a firewall exception I need to add?  I did attempt to manually add the physical server to Veeam so the agent might create its own firewall exceptions. I was unsuccessful at that as well.

When trying to add a Hyper-V host to VBR 13 from either the web console or GUI, we receive the error ‘Samba failed with error: NT_STATUS_ACCESS_DENIED - Can’t load /etc/samba/smb.conf.  The same error occurs when trying to add MS Server 2022 and 2025.  The MS server has it’s firewall disabled.Anyone else experienced this issue?Dave 

Hi Community,Does anyone knows if the calculator is under maintenance for CPD replication?I’m getting the error below. 

Hello everyone,I am new to this community and have already tried my luck in a closed thread about the Veeam VM Migrator Utility.However, I currently have a question about this utility.Are there any experience reports on migrating individual vSphere VMs using the Migrator Utility?Is individual migration with this tool even intended? Thank you in advance for your feedback!

Since yesterday all our existing configured backup jobs to Azure Blob storage are failing and attempts to create new object storage repository are failing on Validating Credentials.  Error: Unable to access object storage (reason: 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. (xstorageaccountnamex.blob.core.windows.net:443))Any ideas?  I’ve tried rotating the access key in Azure and updating that in the Cloud account in Veeam m365 backup.  This has started to occur a week after upgrading to v8 which was ok initially.

Hi all,I want to update Veeam Agent for Windows from 6.3.2.1205 to 6.3.2.1302. The in place upgrade doesnt’t work:  Will my backup job settings be safe when I uninstall the current installed agent and reinstall the new version of Veeam Agent for Windows?Kind Regards

I started my first backup on the 9th. I have retention set to 12 days and Synthetic on Saturdays (default)  . No files have yet been removed from my NAS. I have attached details 9kinow there are extra backups on some days) but its over 12 days now. When will deletion start ? Tony

Does VAMWF support scheduled backup jobs?  I was able to create one with the GUI, but it didn’t run, probably because there was no entry in Task Scheduler.