Community

I create a file level job backup and only need to backup .xls files like below picture But when the job is running, why my backup consume more than 300GB? Actually when i filter in the machine, all xls files under E:\ is not more than 50 GB.Capacity of my E drive is 7.4TB and now the job say is 5% progress which mean the VBR like backup all entire disk without any file filtering.Anyone know why? 

I’m attempting to backup an entire Ubuntu 24.04 computer with the Veeam Agent for Linux.  The destination is an external USB drive.  I can do this with a Windows 11 computer and the Veeam Agent for Windows with no problem.However, when I try to do the same thing with the Veeam Agent for Linux, I’m given an error message that the destination path is included in the backup.  As far as I can remember this used to work.Why does this work now only in Windows but not Linux?

What happen if we use file level backup then we have connectivity issue and the job is failed, will in next retry the VBR continue the backup or will start from beginning?

Fellow Veeam Legend ​@MarkBoothman shared an interesting post on the VUG UK Community page and I thought it highly relevant to also be shared with the main Community as a whole as well.Today Anton Gostev, Chief Product Officer at Veeam, created a couple posts on the Veeam Forums I think those anxious for the release of Veam Backup & Replication v13 should be aware of. Starting in v13, Veeam is beginning to deprecate some features, as well as streamline system requirements to make their product better, more secure, and performant. The posts can be viewed at the links below:VBR v13 Deprecated Features

Hello Community,I am facing the following problem.We are using an archiving (HSM) solution where the archiving application uses the NetApp Fpolicy Engine for mirgation. After migrating files off a NetApp smb share to s3 storage, the NetApp fpolicy engine leaves a stub at the original location. This "stub" is used to recall the file back to the original location when it is accessed. These stubs cause problems when backing up through veeam. During Nas backup (Share and using the NetApp storage integration) the stubs are not backed up, it causes a recall from the archive. (This is not what you want). On a Windows Fileserver veeam handles these stubs well. These stubs are called NTFS Reparse points. The stub file has the L (Reparse) and O (Offline) attribute set. When doing a Windows Fileserver backup these reparse points are, by default, skipped. No setting needed. This is the correct way to handle stubs. I assume this is because of the "L" attribute of the reparse

Hello, we added file-indexing on our ubuntu 24.04 lts-servers today and started the backup of each workload.Veeam detects all files with extension .sophos and .lynx as malware.The files with extensions .sophos are 100% clean, these is our sophos endpoint detection for linux.The lynx-files looks also normal and not like malware. Can we exclude thee files for each workload? I only see the option to exclude a complete workload. Detected files:/opt/sophos-spl/.sophos/usr/share/doc-base/lynx-common.lynx/usr/share/doc/w3m/keymap.lynx/usr/share/doc/w3m/ja/keymap.lynx/usr/share/doc/w3m/ja/examples/keymap.lynx/usr/share/doc/w3m/examples/keymap.lynx/usr/share/wazuh-dashboard/plugins/wazuh/node_modules/brfs/test/

Hello, In this article, I will talk about Veeam Direct Restore to Azure feature. What is Direct Restore to Azure? Included in Veeam Backup & Replication ™, Veeam Direct Restore to Microsoft Azure allows users to import and restore on-premises VMware and Hyper-V virtual machines, physical servers, and endpoints to Microsoft Azure. Restore Microsoft Windows and Linux-based virtual machines, physical servers, and endpoints with Restore to Microsoft Azure. 

Hello everyone!In this post, I will explain how to utilize one of the key features of Veeam Backup & Replication, which is the ability to test the integrity of created backups. Introduction Creating the Virtual Lab Creating the Application Group Creating the SureBackup Job Testing the SureBackup Job Introduction SureBackup uses created backups to initiate VMs

Dear community, Does anyone have an idea if I can force a threat hunter signature update? I do have 2 different cases: Lab case (NFR license!)I do have a lab with a NFR license activated and my SureBackup fails on a regular base with the error message, that the Threat Hunter signature update is not possible.I already reviewed the firewall rules and updates a rule set for v12.3 so that every requirement should be done. Customer case (prod license)The SureBackup (antivirus) fails with the error message that there is no signature database available. wr already reviewed the FW rules and don’t see issues. Can I force the signature update manually somehow? If nobody has input on this I will of course open a support ticket! Thanks in advance!Lukas

Hi Community,Does anyone know if is possible to define an especifc name during the sureback job execution for vSphere?The surebackup job give a randon name to the VM that is being  tested adding a 32 hexa charecters as suffix  , like the screnshot below  

Dear Veeam community,I am using Veeam Backup & Replication to back up my data and would like to know if it is possible to add Synology NAS to the list of managed servers in Veeam Backup & Replication. I tried to configure Synology NAS as a Linux server, but I encountered an error: ‘Unable to collect hardware info. scp: /var/services/homes/adminDS/.: No such file or directory’. I have checked the path and permissions but the problem persists. Can you give me instructions or recommendations on how to properly configure the Synology NAS as a managed server in Veeam Backup & Replication? I would appreciate any help or advice. Thank you in advance for your assistance.

Hello,I’m unable to stop or disable Office 365 backup jobs, and I keep getting the error message:“Unable to complete the operation. Another job operation is in progress.”I have already tried stopping all Veeam-related services (Veeam*), as well as rebooting the Veeam Backup server, but the job remains stuck and won’t stop.Current version: Veeam Backup for Microsoft 365 8.1.0.331Has anyone encountered this issue before? Any suggestions on how to forcefully stop the job? [13.02.2025 04:14:54.449]     93 (1) Error: Unable to complete the operation. Another job operation is in progress.[13.02.2025 04:14:54.449]     93 (1) Type: System.Exception[13.02.2025 04:14:54.449]     93 (1) Stack:[13.02.2025 04:14:54.449]     93 (1)    at Veeam.Archiver.Engine.Tasks.TaskDictionary.<>c__14`1.<GetTaskResult>b__14_0(Exception inner)[13.02.2025 04:14:54.449]     93 (1)    at System.AggregateException.Handle(Func`2 pred

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.

As a Veeam cloud services provider, your goal is to deliver reliable, secure, and scalable solutions that protect your customers' critical data. While Veeam is already recognized as a leader in backup and disaster recovery, adding Veeam Data Cloud M365 to your service portfolio can provide your clients with a powerful cloud-based solution to safeguard their Microsoft 365 environments. In this blog post, we'll dive into why Veeam cloud services providers should embrace Veeam Data Cloud M365 and how it can benefit both your business and your clients.1. The Growing Need for Microsoft 365 BackupMicrosoft 365 has become an essential platform for businesses across the globe. With tools like Outlook, SharePoint, Teams, and OneDrive, it powers collaboration, communication, and productivity for millions of organizations. However, despite its strong cloud infrastructure, Mic

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?