Discussion Boards

I am currently going through the network segmentation best practices (Segmentation | Veeam Backup & Replication Security Best Practice Guide) and I’m wondering where would be the best zone to place my VB365 server.  Part of me thinks Management since it’s a backup server, and part of me thinks Restricted since I am backing up to a local disk.Anyone care to share their thoughts?Thanks!

As some of the Veeam staff probably know, I am definitely NOT Veeam's biggest fan. One reason is because there always seems to be a need to sort of build an environment to suit Veeam. As a service provider, I've always looked for solutions that best fit existing environments with little to no modifications. I've also been very big on ease of installation, ongoing administration, and intuitive interfaces for managing everything, I wouldn't rate Veeam as the best at any of that.However I do continue to see a lot of people who say "Veeam is the best" and "Veeam is great" and "Veeam solved all of our problems", and also threads like this veeam-backup-replication-f2/broadcom-vm ... 91924.html where there's plenty of people discussing needing to find a way to build their entire infrastructure around "what works with Veeam

Good morning community,just a quick question regarding the Linux hosts authentication. Regarding Security & Compliance Analyzer, it’s best practice to set this to manually.Is the only option, to get information about the current acknowledged systems so far, by exporting them, and check the exported file? Is there an option to get these informations from the config-database or from anything else?Couldn’t find anything int the user guide: Adding Computers to Trusted Hosts List - Veeam Plug-ins for Enterprise Applications thanks in advance, best regards Markus  

Good day. Our enterprise manager server has crashed and we wish to create a new server. How do we go about that.

Hi Folks,I would appreciate if someone can offer a suggestion on how to troubleshoot the following error: Error: Failed to create snapshot: Backup job failed.Cannot create a shadow copy of the volumes containing writer's data.VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].   This is the result of an attempt to backup a Windows folder, which is on an ReFS disk F: (the folder has about 5 GB of content and the disk F: has 150+ TB of free space).  The backup repository has about 28 TB of remaining capacity.  The repository is on a ReFS disk mounted as disk E:.Stuff that I already tried:Rescanned the backup repository Recreated the backup repository Restarted the backup server Tried to backup other folders on drive F: with same resultsAppreciate any input.Thank you!-sul.

We are setting up a test backup job for a VM.  After creating and running the backup it fails with the following error:  “Failed to create processing task for VM Error:  No such host is known”  I’m also a newbie to the Veeam environment.  I logged into the Veeam server to ping the VM in question and was able to get a response.  Any suggestions?Thanks,

We started sending backup copies to S3 (backblaze) and I noticed that I had to configure the backblaze repositories to use Direct connection type or specify the vbr server as the proxy. Since this is a new configuration to Backblaze is there something else that needs to be done configuration wise on VBR or Backblaze to use a Gateway server or is it better to use Direct?

When decommissioning a Veeam Backup & Replication server instance, the log collection in Backup Enterprise Manager continues to run for those Veeam servers.   Due to this, the collection logs always show as failed because the server is no longer in existence.  Since I need to retain the backup logs for audit purposes, I cannot remove these Veeam instances from the BEM console since that also removes all audit logs for that Veeam instance.  I’d like to request a feature to disable log collection for Veeam instances that no longer are functioning but still need to be retained in the console for audit purposes.  This way I know if the log collection is successful on existing servers that still need it. 

I don’t know what to do anymore, perhaps somebody knows to help.There were a minor problem on the local target RAID6, which was solved by the RAID controllers patrol read.Before i noticed the issue the 3 chained B2D job were already running, failing and stopping. I remember hard stopping one because it was hanging in infinite loops.From that time i was trying since a few days now to get those 3 chained B2D jobs running again.But doesn’t matter what i do, if i try to run the job(s), run a health check, try to use the repair option which is given for the 1st of the chained group, if i try to disable the job and try all again…. it always ends very fast with the error:”Some metadata sections are missing or corrupted”.It’s the same on all 3 jobs in the chained B2D group.The source isn’t the problem, cause a backup to tape job running without any issue.From my understanding since i didn’t find any other repair option in Veeam, the only rout

Hi ALLWe got hit with FOG Ransomware and i am looking for tools that can help Decrypt the VBK file.  Please post any suggestions. 

When I add and rescan the server in VEEAM backup and replication communication, error is appear : 4/7/2025 5:47:12 PM Warning Failed to connect to xxx.xxx.xxx.3 Details: Failed to call RPC function 'EpAgentCollectSystemInfo': [WMI] Empty result.   I was enable all services and inbound firewall related RPC such as WMI ; RPC ; WRM on domain. (server in domain active directory)Log file : [07.04.2025 17:45:47.498]    <17>    Info (3)    -------------------------------------------------------------------------------------[07.04.2025 17:45:47.498]    <17>    Info (3)    STARTEPAGENTDISCOVERYJOB[07.04.2025 17:45:47.498]    <17>    Info (3)    b1977272-5e9e-47bd-bdae-e91d23f5506a[07.04.2025 17:45:47.498]    <17>    Info (3)    58612558-af3f-4225-a21c-72c77993cae5[07.04

So i have a SQL server that wanted to have a backup of. Today i setup veeam BandR console on another machine with a portable ssd as repository. Right now i have the job running a full windows backup thinking in case i need to restore the whole server i can restort to a VM or another physical server is SQL-1 goes down ..correct? Now my job has appl aware on for SQL and trunking trans log. Would that be correct?  Or should i change to SQL veeam plugin and Windows Agent server edition instead of using console. Im looking at the fastest recovery process. Now im getting another server to mirror SQL-1 so would be   SQL-1  < < > > veeam console < < > > SQL-2  so the backup its just a precaution. Is it my current job correct? Thanks.

Hello, As of this morning one of my Veeam consoles is having jobs with Guest Processing enabled fail.Veeam Version 12.3.1.1139Failed Connecting to guest OS via RPC Error: Retrieving the COM class factory for component with CLSID {Removed} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).  Steps I’ve tried:Rebooted server with Veeam Console installed. Rebooted source VM whose replication & backup jobs have guest processing enabled. Confirmed that the credentials in use are still accurate by signing directly into the VM using them. Verified neither Veeam console nor VM being backed up had Windows updates installed last night or this morning. Tested guest processing using a different domain admin account to rule out profile corruption. Ping from Veeam device to VM works with no dropped packets. Verified

I have a problem with a baremetal restore with veaam freeware.Destination is a M2 hard disk.After complete restore and a reboot.. blue screen with this message:“Your device ran into a problem and needs to restart.Wie will restart for you.Stop code: INACCESSIBLE BOOT DEVICE. I have done a fresh installation of windows 11 (and kubuntu) without any problem so i think that my new M2 do not have hardware problem. A restore on a sata drive it’s OK (no problem) The dimension of the original drive and M2 is the same (256 giga).So how can i restore my drive? It is possible?Thank you…. 

I’ve been a long-time critic of Veeam’s lack of functionality and overall clunkiness compared to other software, mainly Acronis, but I am always looking for what situations any product might be best suited for, so I’m curious what everyone’s favorite things about Veeam are, especially if you migrated an environment to using Veeam from any other product, what product was it and what made Veeam the better choice?

Hi Community,In anticipation of #VeeamON2025, ​@Dynamic , ​@lukas.k, and I recorded a video where we share the story of how we met, our friendship,beer, our passion for #Veeam, and all the exciting developments in the IT-Universe and our lives since we first met at #VeeamON2024.We are excited to continue our journey and hope to meet as many of you as possible in person in San Diego this year.  

Good afternoon, just thought I’d ask the question alongside speaking with our FW MSP and Veeam themselves…I’m trailing Wasabi right now. So far, a backup copy job running for a couple of my smaller VMs is not even completing, and the speed is showing a 6MB/s doing its initial seed.I have a 1Gbps leased line and the VCC jobs for the same VM’s run at around 110MB/s. I very much doubt this is the difference between great value cloud object storage and a VCC partners inhouse infrastructure, but I suppose I need to ask now before I waste more time on this…Any insights? There is nothing on the Veeam server throttling this, the FW MSP has been asked and has said all wasabi endpoints are not subject to inspection so I am starting to wonder.TIA!

I have a physical Zabbix server, which I’ve added to a Veeam Protection Group in order to back it up. I'm backing it up using the "Linux Agent" backup type. Recently, during the backup process, the Zabbix agent on that server becomes unreachable.While the backup job is running, I receive continuous Telegram alerts indicating that all hosts in the infrastructure are unreachable. However, there are no actual issues in the environment — everything is functioning normally.When I check the Zabbix server itself during the backup, the zabbix_agentd service appears to be active (running). Once the backup job finishes, the agent becomes reachable again and everything returns to normal.I’ve been unable to find a solution to this issue anywhere. I would really appreciate any help or guidance on how to resolve this problem.Thank you in advance!

Our current VM farm is backed to a local Linux Immutable Repo and then BCJ to another Linux Immutable Repo in DR site. Both site are L2 connected with metro cluster formed on storage level.VBR server is installed on VM farm. What if: the production site is down, my VBR server is rebooted on DR site; while my primary backup repo and production VM farm is gone. During this period, I will leverage of resources on DR site and backup is still required before failback to production. I have to stop all existing backup policy and create new backup policy because backup path is changed?The initial backup during that moment will be incremental or full? (wondering because all backup file are there, but there are no LUN level replication before)Will the map backup function can help?

We need to have the earliest restore points, how can I safely delete the old restore points so that we can retain the last x restore points? Where can I have the old restore points automatically deleted?For backup jobFor Replication job 

Hi everyone,I’m currently in the process of setting up the Veeam Data Platform for the first time, and while the installation seemed to go smoothly at first, I’ve started running into some challenges during the configuration stage. I’m finding myself a little stuck when it comes to integrating Veeam with some of my existing backup solutions. I’m unsure if there’s a best practice or recommended approach for ensuring everything works seamlessly together.Additionally, as I work through the setup, I feel like I might be overlooking some important configuration settings that could be crucial for optimizing the platform’s performance. Are there any key steps or specific settings that I should pay closer attention to during the configuration process?Lastly, I’m curious if anyone here has faced similar challenges during their first deployment of the platform. What are some of the common issues that new users tend to run into, and how did you go about troubleshooting the

Hi everyone,I have two Veeam proxy servers that max out their RAM (20GB) once or twice a week for about an hour. I’m trying to find out which jobs are running on the proxy at the time of the spike. I know the affected VM's name but need to identify the specific job running when memory usage is high.Proxy details:VMware VM With 20GB RAM (recently added 4GB, but still seeing spike)OS WindowsMax concurrent tasks: 16Is there a way to track this from the proxy server or within Veeam Backup & Replication? Any insights would be appreciated

Hi!We have an ESXi 7 host with some VM on and want to replace it with a new host with ESXi 8.We have Veeam backup & Repliaction Enterprise 12.3 on a standalone server.The backup is going to a NAS, and then out to a cloud backup.I want to migrate all my VM to the new ESXi host but without losing the backupchain.Not sure what method that I should use.Can anyone here please give me som input what path is the best way to go?We rather not start from the beginning with all our backups.

I'm in the process of migrating our hosts and VMs from vCenter 7 to 8, maintaining the same EVC and cluster layout. During this migration, I understand there is a risk of breaking the backup chains due to potential new MOREF IDs. Is there a way to preserve the backup chains? Our jobs are mapped using vSphere Tags.I will be carrying out this migration without powering off any VMs or hosts, and I want to ensure the backup chains continue without issues.If I go to each job and remap or re-browse the VM objects by tags, will this preserve the backup chain and retention? If the backup chain isn't preserved and a new full backup is required, will the retention policy continue from where it left off?