Solved

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.

Veeam Backup and Replication v13 on Windows includes an option to define a custom mirror repository. But what repository should you actually mirror? Is this option even intended for the windows based installation, cause it feels like the offical repos only host updates for the software appliance.

Hi - maybe this is not the correct forum, but asking anyway. I feel there is a disconnect, maybe that is to harsh a word, between people understanding the Kubernete’s ecosystem, and those like me who need to be able to talk about the ecosystem and understand it, without needing to know the nut’s and bolt’s? Hope that makes sense - is there a “Kubernete’s for dummies”, any blogs/information with breaks it down in a simple form for me to truly start understanding it? I see more and more it moving into production at clients, but feel when I present Kasten I’m not able to speak freely “around” the ecosystem the product is designed for.

Hi,Recently I change my job. so that i need to change my email address, any one can help me in this issue?

Hello,I am planning to upgrade Veeam Backup & Replication from v12.3.2 to v13.0.2 and would like to understand the expected downtime and processing time.Current environment:Veeam Backup & Replication: 12.3.2 Target version: 13.0.2 Local backup repository: approximately 150 TB Repository type: Local repository (Windows) Number of backup jobs: 80 Number of restore points: 2560 (if relevant)I have two questions:How long does the VBR application upgrade itself typically take when upgrading from 12.3.2 to 13.0.2? After the upgrade, how long should I expect any backup chain metadata upgrades or repository upgrades to take for a repository containing approximately 150 TB of backup data?I understand the actual duration depends on hardware performance and repository design, but I would appreciate any real-world experiences or guidance from others who have performed a similar upgrade.Thank you.

This is the second time my Veeam 13 console cannot connect and shows the error below.The first time I faced this issue, I reinstalled VBR and it worked normally. However, now that I am facing it for the second time, I feel there might be a bug in this version.After checking the Veeam services, I found that there are three services that cannot start:Veeam Backup Server RESTful API Service Veeam Explorers Recovery Service Veeam Web ServiceHas anyone else experienced the same issue?   

Hello,We are using VSA v13 (linux) and we use powerstrore is there still a integration with Powerstrore, like on v12 windows. There was a installer but this oviously does not work.Even tried it installing on the BR console no luck there

Hi all,I’ve been trying to troubleshoot an issue I’ve been having with the Veeam Windows Agent for a few weeks now, and I’m still stumped. I will try to provide as many relevant details as possible, please correct me if any of this is incorrect.I’ve been using this Veeam product for around 10 months. My use case is that I want to have a secure, offline backup of my laptop’s main SSD. So once a month, I connect a 2TB external HDD (Seagate, NTFS) to one of my laptop’s USB 3.0 ports, and run a volume level backup of just the SSD (this is the drive the OS is installed on). The laptop is running Windows 10 and the latest version of the Veeam Agent.Until recently, everything worked flawlessly. The issue began when I noticed the HDD was quickly filling up, and I realised that I had not specified how long Veeam should keep backups for, so all incremental backups were being stored. So, I edited the job and set that setting to 8 days - reading the online manual, this would mean that since the ex

I try to use Veeam13 appliance version, and need help can/how i can mount the iscsi drive to the veeam13?

Hi,We are just moving customers away from VMWare to HyperV and I have got a problem at one site.I have added a Ubuntu 24 server as a backup proxy onto the DRHost. I then added it in Veeam, and I can see it in the list of Backup Proxies, but I am unable to select it when trying to set it up in the available proxies in the job.It isn’t greyed out, and it went through the setup pretty much okay. I did get this message:veeam cannot find nfs mount tools on the linux machineI am not sure if I need that though, sorry, not an expert on this bit.At the moment the server is not in the box of available proxies.Can anyone help?

 Veeam是否可以直接备份到磁带机中？本地存储的空间不足，请问是否有其他方法，能够直接备份到磁带机中？

I enrolled in a Veeam 13 subscription course, but the lab setup instructions appear to be based on a 2023 recording and an older ESXi licensing model. Because of that, the setup options shown in the course no longer work as presented, which makes it difficult or impossible to complete the home lab as expected. On top of that, I can clearly see the training is v12 = false advertising. The reason for the failure comes when I install VCSA. The error shows the license used in ESXi is invalid however I followed the instructions in the training and the instructor downloaded the same software as I. Conclusion is the material and training is old but sold as some new amazing thing. I contacted support by email, used the chatbot, and reviewed the help section, but I have still not received a response after 78 hours.My concern is not just the delay in support, but that this course is still being sold even though the lab guidance appears outdated. At minimum, this should be clearly disclosed befor

After update to VBR 12.3.2 I am unable to login.The following error:The socket connection was aborted. This could be cause by an error processing your message or a receive timeout being exceeded.  I have restarted all veeam services, specifically veeam backup service.All sql server (veeamxxx_ services have started.However under SQL server config manager the sql server is running but the agent is stopped and I am unable to start that service ( grayed out). TIA

I get this when trying to set up a replication job in Veeam B&R(13.0.2.29).I got the same message when I set up a backup job, I added my Proxmox nodes, set up the backup jobs and they are good. So my virtualization infrastructure is enabled, I can browse my nodes and see all the VMsAny idea why am I getting the same message when setting up a replication job? If I click yes, I obviously get an error when trying to re-add my Proxmox nodes. Clicking No does not take me anywhere.Thank you

Hi there, I am still looking to find the solution out there, but it may be much quicker to ask.Scenario is my old VBR server was on VMWare, and a backup of the config was taken.The backup has been recovered on a brand new VBR server, now on HyperV, different server name and IP. The old server is long gone.Restoring the config worked great, but now I cannot pass any ‘four-eyes’ approvals as the users that were on there, do not exist on this new server. I added the users to this new server, using the same usernames, but they do not have access to this new VBR server.If I add the users to the server as admins, that itself kicks off another four eyes approval.So, how do I get around this? Is there a way to disable that feature when dealing with a new box? Thanks in advance!

Hello guys, I’m using the Calculator on a daily basis, and am pretty sure the calculation is wrong (or maybe I’m?? :D) when you consider Immutable GFS Backups to Object or local storage.If you backup Immutable the Calculator will ask for a immutability Period, this in fact does not matter when using GFS as always one Full Backup will be kept for the configured GFS Retention.Or at least as far as I’m aware.Heres my test:Lets say we have 16TB of source Data, this is the immutability with 14 days and gfs.​​​​​​ As far as I understood it, 16TB is round about the source capacity, of course we will shrink it a bit thanks to compression.Lets say a full backup will then be 10TB which seems surreal already. And lets now turn gfs off in the calculator.Now we only have 14 Dailies immutable but we are missing another 11 Full Backups as stated, GFS will always take full backups. Am i doing something wrong? Is the calculator not able to predict this scenario? 

Simple question, but I don’t think this is possible from reading up about this, there is a great video on migrating, but I think this assumes you still have the old VMWare infrastructure as well as your destination Hyper-V. So, the question is then, can you restore a full backup of a VMWare VM, onto Hyper-V? Assume pre-reqs like removing vmware tools are taken care of, but the actual conversion to Hyper-V can this be done without running your source VMW environment?

Hello everyone I want to take VMCA and VMCE this month. The certificate will say the year 2026, right? Thanks.

We have Veeam B&R 12 on build 12.3.2.4854Our patching software is highlighting we should upgrade agents to 13.0.3.1220Question then is will this continue to work or should we restrict patching and only update agents from the Veeam console?

We have a request to restore approx. 900k files across 2 VM windows server using VBR V12. since selecting individual files is not practical. we are evaluation alternative approaches such as restoring parent directories, mounting restored VMDKs or using instant recovery. Looking for recommendations on the most efficient and reliable method along with any best practices for handling a restore of this scale.

I am testing out deleting and restoring a single email in my Exchange Online mailbox using V365 restore with modern authentication. I keep receiving an error of ‘failed to open mailbox, account doesn’t have permission to impersonate requester.’I found that adding the Impersonation role in exchange is depreciated, so instead I installed Exchange Online Powershell, connected to ExchangeOnline, and granted my 365 admin account full access to my mailbox and I can now see my 365 account as a full delegate in my mailbox settings. I did this because my 365 account was not an option when adding delegate through EAC, I assume because it has no Office license or mailbox so it is not in the list of users to add as delegate.However, even though I can now see my 365 account has full access to mailbox, I continue to get error when going through restore wizard and entering my credentials and 2FA code.Is there anything more I need to do or am missing about granting my 365 admin account access to user

I currently have a Veeam Backup & Replication v12 environment running on Windows Server. I have acquired a new server and plan to migrate my backup infrastructure to Veeam Software Appliance (VSA) v13 in order to benefit from immutability and the enhanced security features provided by the appliance.I would appreciate it if you could share your experience and best practices regarding this migration.Specifically, I am looking for guidance on the recommended procedure to migrate from Veeam Backup & Replication v12 on Windows Server to Veeam Software Appliance (VSA) v13, while preserving existing backup jobs, repositories, configuration, and historical backups.Any feedback, lessons learned, or official migration steps would be greatly appreciated.Thank you in advance for your support.

hello, using VBAR, i exported an agent backup to .vhdx.now, i need to take .vhdx and create a hyper-v virtual machine, so i can boot the image.i checked the veeam docs, this forum and the internet, but i could not find a clear answer.please advice, thanks much, david

Attempts to back up a Wallix Access Manager virtual machine recently deployed at a customer's site on HyperV result in the following error:Processing Acces Manager V5 Error: VHDx:CVhdxDisk.InitialValidation: Incorrect bitmap entry type (PAYLOAD_BLOCK_ZERO): See [MS-VHDX-v1.00-20160128] specification section 3.4.1.2. Agent failed to process method {VHDX.GetDiskInformation}.I edit the virtual disk to made a conversion from vhdx to vhdx from Hyper-v panel, but it doesn’t work.Do you have any ideas on how to fix this problem?Many thanks,Morgan

Hello Expert, I am getting below error during windows agent backup. Basically job was in hung stat on VBR so i stopped the job and restarted the services on agent servers. we tried to recover the backup but its failed with error "Job unexpected failed" in error log i could see below error. These nodes backup was running fine since last few years. Since this node belongs to DB we cant reboot it. Any suggestion or guidance is highly appreciated.Info (3)    [RPC] RPC confirm session has been created. Id: {7a87b}Info (3)    [RPC] Destroying RPC confirm session. Id: {7a87b}Info (3)    [RPC] RPC confirm session has been created. Id: {52fb05}Info (3)    [RPC] Destroying RPC confirm session. Id: {52fb05}Info (3)    [RPC] RPC confirm session has been created. Id: {898fab}Info (3)    [RPC] RPC confirm session has been created. Id: {0fc04}Info (3)    [RPC] Destroying RPC confirm session. Id: {0fc04}