Unanswered questions

Hi everyone,We're currently using the new Veeam Backup & Replication v13 Appliance and have a question regarding post-backup automation.In our previous Windows-based Veeam installation, we had a scheduled task that would automatically shut down the backup server after the backup job had completed successfully. This worked well for our 3-2-1 backup strategy, as the backup server only needed to be online during the backup window.After migrating to the v13 Appliance, we can't seem to find a similar option or supported method to automatically power off the appliance once all backup jobs have finished.Has anyone implemented this on the v13 Appliance? Is there a built-in feature, or is there a recommended approach for scheduling an automatic shutdown after all backup jobs have completed?Any suggestions or best practices would be appreciated.

Hi everyone,I'm running into a strange issue with a Veeam Backup & Replication Appliance v13.0.2.29 on a physical HPE Gen10 server with iLO 5 (firmware 3.13).The appliance boots normally and displays the Veeam Host Management screen, but I can't access the network configuration because the keyboard input doesn't seem to work correctly.ENTER to change the network config!What I've tried:HTML5 Remote Console Java Integrated Remote Console (v252) Different browsers Hotkey programming Ctrl+X Ctrl+Shift+X Fn combinations Java updated to the latest versionThe problem is that Enter does not activate the "Sign in" button, so I can't get into the Host Management menu to change the appliance IP address. The appliance currently has an incorrect IP configured, so I can't access the web interface or SSH.The server is in a remote datacenter, so connecting a physical keyboard isn't an easy option.Has anyone experienced this with the Veeam Appliance or iLO 5?Is there a known workaround to get Enter

Setup:On-prem VBR 12.3.2 Veeam Backup for Microsoft Azure appliance, connected via External Repository Goal: Instant Recovery to VMware vSphere, restoring Azure VMs back to on-prem vCenter (testing DR failback scenario)What I've confirmed:Restore points ARE visible in VBR under Home → Backups → External Repository → Failback storage Each VM already shows 5 restore points. Platform shows correctly as Microsoft Azure, repository FailbackThe issue:When I right-click a restore point to start the recovery, "Instant Recovery to VMware vSphere" is not available / grayed out in the menu, even though the restore point is clearly present and shows 5 valid points.Questions:What conditions cause Instant Recovery to VMware vSphere to be unavailable even when a valid restore point is shown in the console? Does an active/running backup job on the same policy (I currently have other jobs running in parallel) block Instant Recovery for these VMs? Are there specific requirements for restore points impor

Hello,We are facing a backup issue with Veeam Agent for Microsoft Windows on one specific Windows 11 Pro workstation.We have two Windows 11 Pro PCs, both fully updated and both backing up to the same SMB share.On PC #2, backups work fine.On PC #1, backups always fail.The job starts normally and goes through: Initializing Preparing for backup Creating VSS snapshot Calculating digests Reading EFI partition Reading OS (C:) The failure occurs during Finalizing with the following errors: Application is shutting down. Unable to retrieve next block transmission command Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown What we already tried: Reinstalled the agent Recreated the backup job Updated the agent to 13.0.2.1102 Disabled antivirus for testing Confirmed SMB 3.1.1 Added this registry key:HKLM\SOFTWARE\Veeam\Veeam Endpoint BackupForceBufferedAccess (DWORD 32-bit) = 1 We also checked VSS earlier: writers are stable and the backup does not

I have been having problems with Veeam community edition failing to complete backups and giving the error “Application is shutting down. Unable to retrieve next block transmission command” at different points in long running backups.  This happened for local backups as well as remote system backups (on my network).  This error was from Veeam 12 although 11 was having consistent issues as well.  I tried new backup repo hardware, a new motherboard/USB controller, all the drive/os fixes/scans...there are no 3rd party antivirus scanners, and tried checking for volume snapshot errors.What seems to have fixed it is explicitly blocking all internet traffic (outbound) for the Veeam server executables.  What could my local backups have to do with the internet?  I have a fairly complex set of internet firewall rules with MiTM cert inspection, so I’m not surprised if Veeam gets unexpected certificate errors or failures to reach servers in background processes, but would it affect my local backup

I have a customer environment that was running Veeam 12 and we now upgraded to veeam 13. we have to backup the laptops and previous setting was fine but now the problem is that we cannot ping most of the laptops from the VBR13, but we can ping from the laptops the VBR13 server using ip and dns name. We have disabled the firewall on the workstations and the problems still persists, whereby we cannot ping and nslookup fails from the VBR13 server side.

I'm running the latest version of Windows 25H2 version, and Veeam version 13.0.3.1220.  I installed Veeam Agent for Microsoft Windows Free version, and created the USB Recovery Media. I then did a test Bare Metal Restore.  I immediately get the error: Authentication failed, see inner exception.If I use old Recovery media created on an different PC, that is running an older Windows version with an older version of Veeam, the restore process works just fine. I don’t get the Authentication error. I found a post on Reddit, where everyone was having this same problem. One poster said he opened a support ticket with Veeam, and they acknowledged the problem. But I can’t find any information on what Veeam is doing about this very significant bug. Does anyone have an update on this bug? Is Veeam planning a fix, and where can I find a timeline? I’m not updating my Veeam version on the older PC, as I don’t want to introduce the bug on that PC. Thank you.

Hi everyone,I have a question about using the proxy appliance as an internet proxy for VMs running inside a Veeam Virtual Lab.I enabled the internet access feature and configured HTTPS traffic on port 443. On a VM within the isolated network, I then configured the isolated-network IP address of the proxy appliance and the corresponding port as a proxy server in the web browser.However, internet access is not working.While troubleshooting, I started wondering how DNS resolution is supposed to work in this scenario. Typically, the VM sends DNS queries to an internal DNS server. If the requested hostname cannot be resolved locally, the DNS server forwards the query to an external DNS forwarder.Since the proxy appliance only proxies the web traffic, how are DNS queries from the isolated environment handled? Does the internal DNS server require a separate route or masquerading rule for external DNS resolution, or is DNS resolution handled by the proxy appliance as part of the proxy connecti

Hi everyone,I noticed an interesting behavior during DataLab testing. Multiple runs of the same DataLab test are producing different restore outcomes.For example, in one run, VM A completes with an error, while in the next run the same VM completes successfully. I have also seen the opposite behavior with another VM.I would have expected the test results to be consistent and repeatable, especially since nothing has changed in the environment between the runs.Most of the VMs involved are running older versions of Oracle Linux Server.Has anyone else observed this behavior before?Kind regards,Chris

Hi,did anyone or maybe Veeam itself worked on skill for Claude Code (and others)? For diferenet API endpoint, but mainly VPSC.I found (but not tried) this one https://github.com/Servosity/msp-skills/tree/main/skills/veeam  Best regards

Dear Community, As we transition to Veeam 13 I may be getting a bit lost on the usage/purpose of the above Appliance.I have deployed the VSA ver 13 as in-house demo to explore the features and usage. I also deployed the Veeam Hardened Repository 2.0.0.8 and I like how it makes things easier.However the Usage of the Veeam Infrastructure Appliance which can also be used to deploy the Linux VHR has other roles/features that may not be clear on how they plug-in to the entire deployment. I am reading this part https://helpcenter.veeam.com/docs/vbr/userguide/linux_infrastructure_appliance_byb.html?ver=13 and I would like to understand which components that we used to integrate and configure in VBR ver 12 can be compared. Hope its clear. Though I hope for some more Videos on deployment of the same, on the Veeam Youtube channel on the same with demos.

Hi everyone,I'm looking for some advice regarding an urgent VMCE+ certification requirement.We have a customer who is currently attending Veeam training and needs to obtain the VMCE+ certification as soon as possible because they have a project starting in the 4th week of July, where the VMCE+ certification is a mandatory requirement.However, we are still waiting for access to the Veeam ProPartner Portal, which is required to access the VMCE+ course materials.I'd like to ask:Is there any way to expedite ProPartner Portal access? Is there an alternative method to access the VMCE+ training materials while waiting for the portal access? Has anyone experienced a similar situation, and if so, how was it resolved?Any guidance or recommendations would be greatly appreciated, as we're trying to help our customer meet a very tight project deadline.Thank you in advance for your help!

I am a first time Veeam customer trying to set up a new test environment using a trial license in hopes to purchase it but unfortunately have had a lot of trouble setting things up and restores have been a nightmare. I have one physical HPE server that is running the Veeam VSA installed from the latest ISO file.  I am able to run a backup of unstructured data but am unable to restore.  When I try I get no mount server is available.  I have a second physical HPE server that is running Windows Server 2022.  I also have a laptop that I’m using just for management with the console installed. The issue is when I go to Backup infrastructure and click on Managed Servers/Microsoft Windows, I see the windows server, we’ll call it backup1.testdomain.com and next to it says “Microsoft Windows server (default Windows mount server).”  When I go to Backup repositories, I see Default Backup Repository and the linux VSA box, we’ll call it VSA1 (not joined to a domain).  If I go to the properties of VS

Hi All,Does anyone know how to kill off a stuck job.  I have a windows agent job that runs on a physical machine.  The job itself runs fine and is still working according to the agent on the physical machine itself.  However, in my veeam backup and replication console, there is always this job running.  Its not the scheduled one as when that runs, I then get 2 instances of the job.  The proper one finishes but there is always this stuck one.  So it always looks like I have 1 job running.I logged a veeam ticket but they just directed me to https://www.veeam.com/kb1727 this page which ive already done.its not a massive drama, just annoying.  I’ve restarted the services\jobs several times and rebooted the physical backup server. Any ideas?ThanksJames

What are the prerequisites for using Changed Block Tracking (CBT) with VM backups in Veeam Kasten on OpenShift Virtualization 4.21? How can we validate that CBT is enabled and being used during backup operations?If the CSI driver does not provide native CBT support, is there any workaround that combines the CSI driver with KubeVirt, libvirt, or QEMU modifications or configuration changes to enable incremental backups based on changed blocks?

Hello Everyone,My name is Khadar, and I am from India. I have been working as a Storage and Backup Administrator for the past 4 years.I have received a requirement from a customer to onboard 4 Virtual Machines and 1 Microsoft SQL Server into the Veeam Backup & Replication solution.Note: I am very new to this backup tool or solution.I would appreciate your guidance regarding the complete implementation approach, specifically on the following points: Licensing Requirements Which Veeam license should be purchased for this environment? How many licenses will be required for 4 VMs and 1 SQL Server? Would Veeam Universal License (VUL) be the recommended option? Backup Storage Sizing How should I calculate the backup repository storage requirement? What information is needed to estimate the backup storage size accurately? Are there any best practices for retention, compression, and growth planning? Implementation Details Recommended architecture for Veeam Backup & Replication.

I’m playing with the VHR ISO and wonder how we can add a second LVM volume to the VHR.We do this for RHEL and Ubuntu builds so I’m interested if we can do this with VHR.The sort of scenario would be where you add another bunch of disks or disk shelf into a physical server (and possibly controller) so we can have a physically separate second set of storage rather than buy a new server.Some use cases:You also might want to separate remote site backups onto separate Repo’s for specific regulatory or governance requirements Getting the most value from the physical hardware

Environment:- Veeam Backup & Replication 13.0.2.29 (Premium, evaluation)- Backup source: Veeam Agent backup (Windows) of a file server, ~16TB data disk (D:)- Repository: QNAP NAS (TS-433) via SMB, share \\192.168.0.253\Veeam_Repo- Original restore target: Hyper-V VM (SRV-FS01) hosted on physical host SRV-APP01- Backup type in console: shows as "Disk (Imported)"Issue:Volume Restore (Restoring FILES D:) consistently fails partway through with:"An unexpected network error occurred. Asynchronous request operation has failed. [requestsize = X] [offset = Y] Unable to retrieve next block transmission command. Number of already processed blocks: [N]. Failed to download disk 'Volume ...'"Troubleshooting so far:1. Initial attempts failed almost immediately (~10 min) with    "Failed to use DB:GetRepository in restore mode (UnauthorizedAccessException)"    — traced this to using the VM being restored (SRV-FS01) as its own Windows mount    server (circular dependency). Fixed by adding the physi

When creating a backup job with VMs in a ovirt cluster, you are not allowed to select all VMs associated to that cluster.  You have to individually select each one for that job.  This is not ideal if your VM inventory changes and you are not aware.  Why can’t ovirt we have the same function as VMW cluster backups.

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain th

Hello Im very new to Veeam and i installed on a server Veeam Backup and Replication. Now i get this error message: (it never worked)  I read that the API Service needs to be started, but this is not working and an error occurs.  Also its not possible do uninstall the Veeam Software with the Error → Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. It is the adiminstrator user. The new Update i was able to install but also after this update from march i get the same error message. Does anyone have a idea how i can fix this issue?

Hi all, I'm stuck on this and hoping someone has faced it before.Setup: On-prem VBR 12.3.2 (10.91.5.243). In Azure there's a Veeam Backup for Azure appliance v6 with private IP only (no public IP allowed by the customer). Connected via IPSec site-to-site VPN. I need to register the appliance in the VBR console to do a failback of an Azure VM back to on-prem vSphere.What I've tried:Add Server wizard -> Veeam cloud-native backup appliance -> connect to existing appliance, using the appliance private IP -> fails Test-NetConnection to the appliance IP on 443 shows True, but I later noticed the latency is <1ms and there's an ARP entry for it on our LAN. So I think my tests were reaching some local device, not the appliance in Azure Browser from the VBR server to the appliance IP gets redirected to :4343 and refused (Veeam support told me 4343 is not even a Veeam port) Checked proxy on the VBR server (winhttp, IE settings, env variables). All clean, no interception Veeam support

Hello , We are planning to migrate our infrastructure from an on-premises Hyper-V environment to Microsoft Azure. Our current environment consists of: Hyper-V virtual machines protected by Veeam Backup & Replication.The Veeam Backup & Replication server is currently running as a Hyper-V virtual machine. A NAS device is used as the backup repository, which will also be decommissioned as part of the migration. We would like your guidance on the following: Does Veeam offer a cloud-hosted or SaaS-based backup management solution that can replace our on-premises Veeam Backup & Replication server? If such a solution is available, can it manage and protect Azure virtual machines while providing the same or similar functionality as Veeam Backup & Replication? ​​​​​​​If a cloud-hosted Veeam solution is not available, what is the recommended architecture for customers migrating entirely to Azure? Additionally, regarding our backup repository: We plan to decommission our existing

Hi All,I’m wondering if there is a more widespread issue with Veeam Backup for Microsoft 365?A customer has recently noticed the processing speed for their M365 jobs is grinding to a halt and not finishing at all. They have tried many things including provisioning a physical server with SSD but the job processing rate remains very low.Are there any suggestions to improve this? They are on the latest version and only noticed the issue within the last few weeks.Setup - One Server, One organisation. 4 jobs to process - Mailboxes, SharePoint, OneDrive and Teams.Using one account for all jobs. Any guidance would be appreciated. Thanks, Peter.