Solved

Hello All,  I need to take backup from postgres cluster using Veeam, the postgres is deployed in clustered nodes (3-nodes).As I know and did it before, we can use Veeam Agent for Linux to backup single node holding the postgres database, then I can perform the restore for the file using Linux FLR.  Here I have some points to be discussed :1- I know we can perform image-level backup for the VM holding the postgres, and ask the DB admin to provide us pre or post-thau script. In this cause, would it be better to use Linux agent backup on the VM instead of VM-backup? What is the pros and cons for using Agent or VM back with postgres? 2- can we create a script from our end as backup admin as simple script if the customer does not have his own script? In this case appreciate if someone explained how the script works? 3- how can we backup clustered machines, do we have to install Linux agent on all cluster nodes? How can I point the nodes to take backup and restore? Comparing to Microsoft SQL

Hello community, Can someone provide instructions for the recent patch? I am looking to upgrade from 12.3.2.3617 to 12.3.2.4165. This is my first patch upgrade via ISO and I want to confirm I am installing correctly.  Thanks!!

Veeam Backup & Replication includes several built-in credentials: Helper appliance credentials Tenant-side network extension appliance credentials Provider-side network extension appliance credentials Azure helper appliance credentials  I understand that the documentation recommends changing the Azure helper appliance credentials before deploying Azure helpers.However, I would like to change all four built-in passwords (for security and compliance reasons), even though I’m not using Azure or Cloud Connect helpers. Is it supported and safe to change these built-in credentials (in the Credentials Manager), or could this cause issues with helper appliance deployment or communication?

Scenario: A user submits an urgent ticket - a very important folder has been deleted from the file server.IT will ask ‘when is the last time you saw that folder?’ and they usually don’t know.So, I fire up Veeam Backup and Replication. Click Restore > Microsoft Hyper-V > From backup > Guest file restore > Microsoft Windows.I’ll (randomly) pick a backup from 2 days ago. Wait (forever) for the backup to spin up; then navigate to where the folder should be, only to find it’s not there. So I close it and spin up a different backup set. I’ll keep doing this until I eventually find the folder and restore it. This takes forever.Is there a faster way to do this?

Hello Community Members, I am just trying to figure following scenario but unable to put into action.Scenario:-I want to copy a SMB Share/SAN Intergration Full Backup job from last day of previous month i.e 29th of 30th etc. I cannot find an option to handpick a specific restore point from last day of previous month. I want to retain this job with two-year retention on tapes. VBR just offers to copy Full Backups via Copy to Tape but does allow to handpick specific full backups from a list of previous backup jobs/restore points etc. Is this functionality only available via PowerShell?       

Is there a way to search the Veeam database to see if a particular file is in a backup and which backup/s its stored in? I was taught to just go to disk, search the server name and then hunt & peck through backup dates until I find the backup that has that file in it. 

Hello Veeam Team and Community,I’d like to clarify something about partner and certification requirements.If my company plans to: Provide managed services to customers who use Veeam Data Platform (for backup and recovery management), and Also act as a reseller of Veeam licenses (via authorized distributor), do we need to hold any specific Veeam certification (e.g. VMSP, VMTSP, VMCE) or reach a certain partner tier in the ProPartner program?Or is being a registered ProPartner and sourcing licenses from an authorized distributor sufficient?Appreciate your guidance so we can ensure full compliance with Veeam’s partner requirements.

Current LAB setup(all settings inherited from previous host): HypervHostB with a private switch 2 virtual machines on this private switch VM1 - ClientPC with windows 10 iso installedVM2 - PrimaryDC (Veeam restored from HypervHostA to HypervHostB - Session Type is Full VM Restore) - this server has roles(ad fs mgmt, dhcp, dns and gpo repectively)    - has 2 vm switches, Data: ip 192.168.50.1, subnet 255.255.255.0, gw - 192.168.50.150, preferred dns:192.168.60.240(DC2) and secondary dns:192.168.50.1                         Voice: 20.20.20.5 subnet:same, gw:20.20.20.1, dns1:PDC, dns2:DC2Observation:1.VM2 fired up nicely, AD components such as aduc, domains and trusts, gpo etc all open fine, able to logon with my local and domain AD accounts successfully 2. Fired up VM1, VM1 picked up IP via dhcp successfully, showing domain name schools.local on VM net adapter3. Both vm1 and vm2 can successfully ping each other via ip and dns name, nslookup works as well.4. vm1 is listed in dns on vm2Chec

We are running a VMWare environment.We created a new iSCSI datastore for some of our VMs due to the previous Fastclass Fibrechannel datastore having issues.All of our VMs are running well on this new datastore but every Veeam backup job fails for VMs housed on it. All backups for VMs running on other datastores are fine. The VMs show up in Veeam and are able to be added to jobs and show their file sizes, but fail when the job is run.Any ideas? I’ve pasted the typical error message below that we get, with some of our info redacted. Note that some of the files do actually back up, namely the smaller files like the .vmx, .vmxf, and .nvram, but the .vmdk file seems to be where the error occurs. 10/1/2025 3:18:59 PM :: Processing ******** Error: Failed to open VDDK disk [[***NAME OF ISCSI DATASTORE***] ***NAMEOFVM***.vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [***VMWare HOST IP***];Port: 443;Login: [***USERNAME***];VMX Spec: [moref=9];Snapshot mor: [9-snapsho

So I’ve been trying to restore a VM to my Proxmox cluster and I keep getting an error `Failed to reach the hypervisor. Error output: can’t open ‘ssh-public-key-string’ - File name too Long`. I tried recreating the workers, testing the connections and rechecking all the configs I can think of and I can’t get past this point. Every host is configured with IP and ‘root’ credentials. Each is available and the workers start up seemingly fine. Running ‘Veeam Backup and Replication 12 Build : 12.3.2.3617` on Windows Server 2022 Standard

Hey everyone! Happy Friday 😃I had a quick question regarding Per-VM Backup chains. If I remember rightly, I think I read somewhere that in V12 it would be enabled by default. Are Per-VM backup chains now best practice? Anything to be aware of when transitioning to them on already existing backup jobs that do not utilise Per-VM backup jobs currently?Thank you!

I am running a daily configuration backup, as I should. :-) It is saving to my default repository, which in my case is a locally attached drive on my VBR server. (in fact, I had to do a configuration restore once, so I know that process works).But I just realized I don’t have a tape job, that copies the configuration backup to tape, in case of full on disaster and the building burns down to slag. And I guess I am drawing a blank, because I am a bit unsure how to set that up.Do I just need  to do a Tape job, choose a “Files” backup, go to my VBR server, and choose the “VeeamConfigBackup” folder? What about the “VBRCatalog” folder? Anything else I need?A better way to do this? Obviously I would want this run every day, so it goes onto a tape every day, and once a week, we send all tapes that are FULL offsite for storage.Sorry if these seem like stupid questions.

Hello all, I don't know if this is the right place to ask for help but we have been running into a brick wall for 2 days now. We have only recently gotten back into using Veeam and we succesfully rolled out VSPC to a VM in our DC. We also have another VM in our DC running VBR (neither of these servers are part of a domain), first we had this installed without Cloud Connect purely to mess around a bit. But after that stage we decided to up the license to include Cloud Connect. The VBR obviously had the management agent from VSPC installed and everything was working as intended.However when we wanted to connect the newly added Cloud Connect service via VSPC we ran into an issue where we would go to Configuration > Catalog > Veeam Cloud Connect > Servers > New. We would then enter all the correct information, we will get a pop up stating we need to take ownership of the already installed agent. Which sounds reasonable but after that we just get a prompt saying “Access Denied”.

I keep getting the error when with the Windows Backup Agent:“Veeam Endpoint Backup is already running for user *MyUsernameImCurrentlyLoggetInWith* “When I try to edit the job currently running. But no other users are logged in or accessing the app. I have tried deleting the job. Now I can’t make a new one. Rebooting, of course. Shutting down the App and the Service. Uninstalling and reinstalling. Resetting the DB. Deleting the config folders in ProgramData and Windows Program Files. And I keep getting the error. Like something is still left on the machine, with a setting that is causing he fault. Ideas?? How do I completely remove everything from the Veeam Agent from the machine and start over?  

Hello,i was trying to register linux server, but certificate file exists.I have deleted /opt/Veeambut still is echo about “File exists” Do you have any hints, where could be located for redhat? I have checked all logs, but cannot find even on VBR or linux itself. Its Veeam 12

Hi there,Veeam B&R 12 is installed on a Windows 2022 Server, which is installed on VMWare ESXi 6.5 U3. From there I backup our produtvie Server, which is a VMWare ESXi 6.7 with a Windows Server 2016 and a Windows Server 2012 R2 (Exchange Server) installed on it. Everything works fine, exept the backup of the Windows 2012 R2 Server. It does backup, but I receive the Warning “Failed to index guest file system. VSS Control: Index failed". Is there any way to fix this, except disabling the file indexing?

Does Veeam VBR 12.1 cover Server 2008 and 2008 R2 Virtual guests…? Thanks in advance.

I am doing a fresh install of Veeam Backup & Replication 12.3 on Server 2019. The process gets to step 6 and I get a popup stating: “failed to start Veeam backupcdpsvc service”. I checked the error logs and one that I noticed was “a call to sspi failed see inner exception”. Has anyone seen these issues before. I have erased everything and tried to reinstall. I'm using the local account not a Domain account if that helps. 

HotAdd Manual Testing (kb1184) only works when VM is powered off. I did this test but only works if I turn off the VM. There is no text in the article saying that the VM has to be powered down in order to attach the snapshot vmdk but I would think this is normal where the snapshot vmdks are locked thus can not be attached to another VM. What did I miss in the KB?  

I’m working with Veeam SureBackup and I have 5 Virtual Lab running on one ESXi host. Now I need to move it to a different ESXi host.Is there a way to change the assigned host for the existing Virtual Lab, or do I need to create a new Virtual Lab on the new host and reconfigure everything?

Hello. I have a request to restore files from a specific host from a tape made earlier this year (2025-01-01). And I am not sure how to determine which tape it is that I need. Here’s the problem. At the time, the VM I need files from was running on vSphere. Since then, we’ve moved to Nutanix. If I try and do a Restore, choose VMware, I don’t see the jobs from that long ago. (which I kinda expected). But what I don’t know, is how to determine which tape made on (or around) 2025-01-01 has the backups from this VM. So I can recall the tape from offsite storage and do the restore.I realize this is probably a silly question, but I’ve never had to do a restore from so far back, it’s only on tape, and not still on disk storage.I tried to do a Restore,  If I select “Files and folders”, I can scroll down to my server, and I can see the VM I want, but the backups listed only go back about 60 days. I need longer than that. Which means I’m looking in the wrong area. But I don’t know what the right

Hello forum, We have an existing physical 12.3 VBR Enteprise server with local default repository (E:\) and local attached tape drive.Need to move to a new physical VBR Enterprise server, also with a local default repository and a new tape drive. We don’t want to connect the old tape library to the new server.Ideally the old server remains available for eventual restores from the old tapes.Backups on the local repository have only 2 weeks retention, so not really required to copy them to the new local repository.Is a simple configuration restore from the old VBR ES to the new one OK?I suppose the old catalog does not need to be copied to the new VBR ES and can be left out of the configuration restore?I’ll need to configure the new tapel ibrary and new media pools on the new ES and then point the copied Job definitions to the new media pools?Can the old VBR remain online for at least 6 months?Thanks, Francis 

I have been using VMWare 6 Essentials Kit for over a decade.   Broadcom hates us now.   I can’t upgrade to anything under $1600 a year.   I don’t want to go with Windows Server Hyper-V.   What free Open Source Hypervisor is supported by VEEAM?   I am stuck on VEEAM 11 community because I can’t upgrade.   

Hi community, While waiting for Veeam Backup for MS365 to release a tool for migrating backup data from one bucket to another, I was thinking what could be another way of doing it. On the forum I saw that there are several options by using other tools, which are currently not supported by Veeam, as they might change the structure of files, but seems to work, and I thought of Veeam object storage backup feature. Has anyone used object storage backup job to archive Veeam for MS365 backups? It won’t help with backup mapping and will only be ok for smaller environments, but purely for archival purposes it doesn’t look to bad for me.  Thank you!

Hi all,I finally found time to deploy the most recent version of v13 (final first release) within my lab and I quickly ran into the issue that the Web GUI shows "failed to check for updates" even after I ran through the process and updates the appliance.The host management GUI shows that the system is up-to-date, so I assume that the update was installed successfully - the VSA even rebooted during that process.  I already restarted the VSA (and the whole lab environment tbh) so there can't be any caching issue as far as I can tell. Veeam Support Case is already open. R&D: https://forums.veeam.com/veeam-backup-replication-f2/v13-failed-to-update-but-system-is-up-to-date-t100160.html Any ideas on that? Best regardsLukas