Discussion Boards

Hello,We have a Backup Copy on S3 containing multiple backup jobs, and we have noticed that VMs removed from the jobs are not being deleted from the S3 repository, even after exceeding the defined retention period. Full and incremental backup images are still being retained.I would like to understand how retention works in this scenario. Does the fact that the backup chain is incomplete prevent the deletion of old restore points?What are the best practices to ensure the automatic expiration of obsolete backups?Thank you in advance for your help.Best regards,

Hi ​@Madi.Cristil, I have a request for a Webinar topic and ​@Pybarra in the R&D Forums suggested I reach out to you. I would -really- like to see an in-depth webinar & demo session discussing section 2.9 Hardening in the VBR Best Practices Guide (link below), with the subjects of proper segmentation (2.9.1) and “management domains” (2.9.3) being of particular interest. Seeing this in action in a demo environment where the different server & network configurations (both physical and virtual) would be absolutely invaluable since it's almost never discussed in Veeam Best Practices videos beyond the topic of Linux Hardened Repositories.https://bp.veeam.com/security/Design-an ... Hardening/

I’m using the Veeam Agent for Windows (Free Edition) and 6.3.0.177. My primary drive is a 4TB NVMe SSD (NTFS / backup source) and my backup drive is a 4TB USB 3.0 SSD (ReFS / backup target).For a long time now I see performance issues with backups. My first thread about this wasSince then, I replaced my external  USB drive (backup target) three times. I initially had a 1TB WD HDD, replaced it first with the same drive (guarantee/RMA), then with a different 1TB WD HDD and eventually moved to a 4TB SSD.From experienced I noticed three things:The drives became slower with time. With time the backup size increased and formatting or replacing the drive seemed to solve the problem, but the issue would eventually return. I suspected that the performance degradation was due to SMR, so I eventually switched from a HDD to a SSD.

Hi All, I have this weird error happening on my Veeam server.“Host is unreachable. Unable to install backup agent: cannot connect to 192.168.0.100 Error: The parameter is incorrect.”The weird thing is, I’ve checked through all nodes of my Veeam installation and can’t find anything erroring or relating to this error (see pic).In the ‘Name’ section below, those IP addresses do not relate to anything on the LAN, they aren’t even the same subnet. I have no idea where they are coming from.  

Veeam Backup for AWS - Restore Instance or EBS Volumes Failed with timeout We are trying to restore an Ec2 instance or the EBS volume itself but we are getting a timeout error. The get id of the volume to be restored is generated, but the resource is not created.The following messages are displayed in the logs 11.02.2025 11:53:00.375] <10ac> Info         Creating temp resource: [CCloudTempResource] Id: '4c089da9-12ee-45ed-8cba-9d8e16b43d8a' ResourceId: 'vol-0a70a25fdf6e95f61' ResourceType: 'Disk' LocationId: '7111a4d7-2c16-4f08-ad44-29da76fcc61e' CloudAccountId: '5c4fd4b6-79a8-4b0b-a85d-e03ad3a6cb3a' LeaseId: '6f9cdea5-3611-4e32-902c-4eaf7d780d22'[11.02.2025 11:53:00.382] <10ac> Info         [AmazonStateAwaiter] Awaiting volume 'vol-0a70a25fdf6e95f61' for states ['Available']. Timeout: 1800 sec.[11.02.2025 11:53:00.385] <10ac> Info         [CDefaultEc2VolumesManager] Getting volumes by ID: 'vol-0a70a25fdf6e95f61'.[11.02.2025 1

Our Veeam Backup and Enterprise Manager were both hosted on the same server, but I've now relocated the Enterprise Manager to a different server. Should I keep the guest catalog folder (VBRCatalog) on the old server?I know VBRCatalog uses Backup server and it replicates to EM ( if it is, any additional steps required ). Please advise   

Dear Community,Did anyone achieve the below task from Google by Using Veeam Backup?Question:Do we have a solution to take backup from Data stored in GCP Filestore? 

Hello Community and good day,bringing the conversation here as well to further discuss on this topic. First of all, apologies for the long thread but I wanted to provide as much context as possible.I totally agree that using physical boxes exclusively as VHRs and putting the VBR server role alone somewhere else (as long as backup data is physically separated from the VBR server itself) should be the way to go from now on.Looking at our install base, we still have some customers using physical Windows boxes hosting both the primary backup repository and the VBR server role at the same time. To be completely honest, in a scenario where backup data is not physically separated from the VBR server itself I see little point to enabling two-factor authentication for Veeam Backup and Replication users without applying some hardening on these boxes, such as preventing some users from logging onto the operating system.Although the first goal should be to put the VB

I have a fairly simple site, where I have vCenter, 2 ESXi’s, a baremetal veeam backup server and 2 QNAPs for backups storage, also 2 proxies each residing on one of the ESXi (for hot-add).Up until now, when proxies were windows ones and we didn’t use the hardened setup we had the QNAPs attached via iscsi to the proxies, where the proxies would be 1:1 nated via a linux firewall, so they would have a production reachable IP but then translated into non-production network, with different vlans and the traffic would be heavily filtered - this worked very well.I’m redesigning this and moving the repos to linux hardened repositories now, also want to switch over the proxies to run on linux. Is there a way, to keep the repos unreachable for the backup server itself? So the repos would be reachable only by the proxies? I imagine proxies having 2 nics, one towards the backup server and the other in the backup storage network. The backup server needs to be within t

We have a VMware backup tag which contains 16 servers, is there a way to configure the order in which they are backed up?

Can we migrate VM from VMware to Azure Stack HCI/ Azure Local using VBR?Is the steps same with migrating VMware to Hyper-V?

I have one job that started failing to create synthetic fulls on weekends.   The job runs just fine M-F creating incremental backups. I have another job that also creates synthetic full backups over the weekend.  And that job finishes with no errors.  So I know it’s not my NAS (Qnap) that is having issues.So why is it doing this for only the one job?   Error log below. 02.02.2025 16:57:48.444]    <43>   Error (3)    Failed to execute full transform task[02.02.2025 16:57:48.444]    <43>   Error (3)    Agent: Failed to process method {Transform.CompileFIB}: The semaphore timeout period has expired.[02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed. [requestsize = 700416] [offset = 1242582327296][02.02.2025 16:57:48.444]    <43>   Error (3)    The semaphore timeout period has expired.[02.02.2025 16:57:48.444]    <43>   Error (3)    Async

I would like to verify the data in my backup copy job from my Veeam Backup for Microsoft 365 however I cannot find a place where I can select restoring from the copy job instead of the backup job itself. Is it possible to select the data to be restore from the Backup Copy Job?

I’ve been using Veeam for a while now. I was under the impression that I was performing a full backup every week. The way I have been doing this is I have 4 USB hard drives which I rotate. I plug one in on a Friday, wipe it, it backs up over the weekend (no errors), then Monday I unplug it. Friday I plug in the next one and repeat the process.I’ve just had need to restore from a backup, I wanted to restore the entire VM, and it’s errored saying the .vib file is missing. Having had a Google, everything seems to say this is a file for incrementals. Have I rendered all my backups useless up to this point by wiping the disk each week? The backup files it is creating are always a similar size to the VM I’m backing up so I’d assumed it was indeed “Full”. Is there anything I can do to restore my back up, and which setting have I missed in the backup job to make it do actual, proper, full backups?Thank youStuart

Hello,I am looking to recover some files of interest that were backed up to tape over a year ago.  The files were on a Hyper V VM running windows server.  The files were part of a backup job that was run on VEEAM at that time.  I obtained the tapes and imported the entire tape job to our backup server, which is a 5 tape media set around 50 TB.  When I attempt to "Restore guest files" from the imported tape, I get an error message that some of the files are missing and then get the following errors, indicating that "Mount wasn't found".  Of note, the previous backup/tape job was on a different domain that has been since decommissioned, so we are now running our backups under a new domain controller.  Would the old domain be the mount it is looking for?  I'm wondering if it is unable to mount because it is trying to do so on the old domain (which doesn't exist)?  Of note, I utilized the same process in the past to recover files on tape with no issue, but that was on the previou

Hi all,I would like to use Quantum DXi V5000 as deduplication storage appliance  Unfortunately, when adding deduplication storage appliance, there is an error message, that there is no Veeam Data Mover service enabled on the virtual storage appliance To enable Veeam Data Mover service I need to install Veeam Data Mover on the appliance…. The issue is that I do not know default root password for Quantum DXi V5000 and adding non-root user to sudoers file didnt help.Is there any option to manually install Veeam Data Mover on linux based machine? 

Good morning. I usually perform backup jobs using the Oracle RMAN plugin for a primary repository.When creating a copy job of this backup job for a second repository, I receive several errors saying "File does not exist. File: [XXXX.vab].Where is Veeam looking for these files that no longer exist in the primary repository?We have an immutability configuration of 30 days in our primary repository. Since this is our first contact with Veeam, we were mistakenly deleting Oracle RMAN backup files older than 30 days directly in the repository file system. However, we were instructed by Veeam support to just rescan the repository so that possible invalid files in the Veeam database catalog could be resynchronized, but this did not solve the problem.I have an open case about this but still no response. Has anyone had this problem and solved it?

 Hello.Tell me, is veeam backup version 11 installed, ASP NET and NETCore version 3 installed, how can I update the NET versions, does veeam backup 11 support newer NET versions.

I have one Windows physical endpoint which has the Veeam agent installed, and a backup is taken to the BackipRepository1 every few hours. I also need to take a backup of that machine once a week (midnight on Saturday) and retain 52 copies, but those backups need to go to BackupRepository2.I have tried to create the second job but get the following message.Skipping WINWORK0256548; workstation is already assigned to the backup policy Workstation1 Nothing to process. Failed to apply backup job configuration at date and timeIs there a way for me to have two different backup jobs for a single endpoint like this, please?

Missing application permissions: Exchange.ManageAsApp. Public folder and discovery search mailboxes will be skipped from processing, and a shared mailbox type will not be identified.I have a fully licensed version of Veeam Backup for Microsoft 365 (not the community edition) which I recently upgradded to version 8.1.  Since then I’m getting this message.  I tried to put in a support ticket but that doesn’t work so I thought I’d try here.I have already followed the instructions on https://helpcenter.veeam.com/docs/vbo365/guide/ad_app_permissions_sd.html?ver=80 where I assigned Global Reader to the Veeam App ID but I still get the error message.Useful suggestions gratefully received.

I’d like to gather as much information on hardening Windows Repos and Proxies, and have it all posted below to help others if they are looking for information on this topic.We all know the Veeam B&R Server has a security checklist which gives you very clear concise things to do for security.  There is also the LHR.  Following the DISA STIG, or using the ISO is a great way to make sure the software portion of your LHR is safe.With the above, you still have to protect the underlying hardware. Everything from physically getting at the Disk, Server Bios/UEFI, destroying the hardware, to SSH ports on a SAN, and use of MFA for logins to a SAN to prevent access. Turning on immutable snapshots and 4-eyes features on the storage pools are also great to implement. Lets not forget the VLAN for your management networks and who is allowed to see those IP’s. Even with all of this, I still don’t see specific documents for hardening a Windows Repository or Proxy server. Man

I am working on a deployment of Veeam 12.3 on Windows Server 2025 as I see there is now official support.  I am planning to use PostgreSQL, and I was wondering which version to choose.  The 12.3 ISO comes with v15.10-1.  Is that Veeam’s recommendation for Server 2025?The latest version of PostgreSQL is 17.2.  Try as I might, I can’t find any statements regarding PostgreSQL’s support for Windows Server 2025, but if Veeam support is willing to stand behind it, that’s good enough for me.Also, am I correct to assume the only way to run the DB on its own drive (D:) is a manual install of PostgreSQL before the Veeam install?

Hello All,I'm testing Veeam with my homelab Proxmox cluster. I have an issue with a worker on a node that is not reachable every other day. The backup gives a warning message. When I test the worker in the Veeam console I'm getting this message <<<<<<19/01/2025 20:42:53 Error Failed to synchronize configuration settings of the worker XXX-worker can't lock file '/var/lock/qemu-server/lock-101.conf' - got timeout19/01/2025 20:42:53 Error Worker XXXworker test failed: can't lock file '/var/lock/qemu-server/lock-101.conf' - got timeoutHere is the warning message from the emailFailed to prepare the worker XXX-worker: Failed to power on the worker VM: Failed to wait for the task UPID:XXX:0006259E:0080C27A:678CCD30:qmstart:101:root@pam: to complete; There are no available workers in the cluster. Performance may be affected; Failed to prepare the worker worker: Failed to power on the worker VM: storage 'datastore' does not e

I am trying this one more time and have had this work in the past but just wasted hours on a restore that would not boot. I have a replacement laptop a little newer and I installed veeam on the new laptop and created the usb drive. I then booted the usb and went into bare metal selected, connected to my veeam backup and recovery and selected the restore point, removed the partitions and did the restore. The restore said it completed successfully but would not boot even with secure boot off. Tried start up repair and unable to repair. I selected command prompt and I could see all of the files were there and tried some bcdrec stuff but nothing worked. I can restore a clean image and then restore my files that way but the bare metal recovery is supposed to work and obviously it is not in my case. Currently running endpoint backup version 6.2. Trying again but pretty sure it will give me the same result.