Community

Veeam 12In v12 is not so sensitive via WMI/DCOM connection Veeam 13Upgrade to v13 was successful.All services are runningPS C:\Users\user01> Get-Service | Where-Object { $_.Name -like "Veeam*" }Status Name DisplayName ------ ---- -----------Running VeeamAHVSvc Veeam AHV ServiceRunning VeeamAWSSvc Veeam AWS ServiceRunning VeeamAzureSvc Veeam Azure ServiceRunning VeeamBackupCdpSvc Veeam CDP Coordinator ServiceRunning VeeamBackupRESTSvc Veeam Backup Server RESTful API Ser…Running VeeamBackupSvc Veeam Backup ServiceRunning VeeamBackupUpda… Veeam Backup Update ServiceRunning VeeamBrokerSvc Veeam Broker ServiceRunning VeeamCatalogSvc Veeam Guest Catalog ServiceRunning VeeamCloudSvc Veeam Cloud Connect ServiceRunning VeeamDataAnalyz… Veeam Data Analyzer ServiceRunning VeeamDeploySvc Veeam Installer ServiceRunning VeeamDistributi… Veeam Distribut

Hi Folks,Next week we will be launching our new Fleet Manager and we have a true star joining us! See if you can guess who that is 😁! There will also be some other cool folks present. If you have time please join us. https://objectfirst.com/fleet-manager-launch-event/  

We have a Veeam Backup Enterprise Manager that connects to several Veeam B&R servers at our remote sites and child companies. As we’ve been upgrading to V13, the requirement to use HTTPS to connect to the VBR server is causing endless issues. Most of these sites are smaller, and only have one external IP that’s used for something user-facing, such as client VPN. (You know, because default ports are good for end users that wouldn’t know how to specify them.)V12 used Veeam-specific custom ports that we could forward to the VBR servers and there was no issue whatsoever, but the upgrade to V13 has ruined this. It is necessary to be able to specify a custom port for BEM to collect data from VBR servers. We’re not pointing a web browser at this, and backup software is an ideal place for knowledgeable IT staff to use and document custom ports, or even just a single nonstandard port that Veeam uses by default (like is used to with 9392). I don’t know who deci

Hi, Today I have another issue with a hardened repository The VHR is in emergency mode with the message “cannot open access to the console - the root account is locked”I followed the step from this document https://www.veeam.com/kb4663 but unfortunately the root account remains locked. Any further advise? Thanks  

doing a trial version as thinking of switch to the linux hosted server but have run into an issue while testing. While setting up the backup it said preferred method was certificate for authentication for backups which I did and the backup works just fine. Now comes the fun part I cannot restore back to the windows PC, the browse and OK buttons are greyed out. If I choose other location I have to pick SSH for authentication which I am confused about, anyway I can restore the file to the veeam server and copy it back but that's a very ugly way to do things. What am I missing here or failed to setup properly?

Hi,Today I upgrade in my homelab (with NFR license) from Veam 12.3 to 13. I have 3 Proxmox node and three Proxmox backup job, Everything was running fine before the upgrade. Now with 13 I discovered that Proxmox is missing, when I click “add new server” and virtualization platform Proxmox is not there. Proxmox plug in is installed version 13.3.1.7 No idea what has happened with the upgrade. The upgrade process ran without an issue. Any idea? What I already did is uninstall the Veeam Proxmox plug-in and reinstalled installed after a restart of each step.

While upgrading to Veeam Backup for Microsoft 365 8.4, you might notice the following message: Connection to PostgreSQL is not encrypted. Enable TLS in PostgreSQL for secure communication.  VB365 checks whether the connection to the PostgreSQL database uses TLS.If TLS is not explicitly enabled, the warning is shown regardless of whether PostgreSQL is local or remote. If the PostgreSQL database is locally hosted on the vb365 server itself, this traffic does not leave the host. But if you have multiple proxies, those proxies also connect to the database, and this traffic leaves the network. So in those scenarios, it might be good to have this traffic encrypted. I will describe here how you can enable this traffic to be encrypted. Step

I am not sure if this has been posted somewhere before but I thought I would post my experience of setting up Linux proxies for our VMware backups and the one issue I ran into. I deployed a couple of Ubuntu 22.04 VMs, as I will be using hot-add for the VM backups. I added them to the VBR server and created a test backup of one VM. First backup attempt and I got this error:Error: Cannot get service content. Soap fault. Temporary failure in name resolution Detail: 'getaddrinfo failed in tcp_connect()', endpoint: 'https://vc.domain.local:443/sdk' SOAP connection is not available. Connection ID: [vc.domain.local]. Failed to create NFC download stream. NFC path: [nfc://conn:vc.domaint.local,nfchost:host-1310340,stg:datastore-1310378@TEST/TEST.vmx]. --tr:Unable to open source file [nfc://conn:vc.domain.local,nfchost:host-1310340,stg: So the key to the problem is “failure in name resolution”. Specifically name resolution from my new Linux pr

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Ansible + Veeam + AI + Monitoring and Observability Tools = AIOps Everything starts with a signal.A sudden spike detected by Dynatrace.Suspicious behavior flagged by CrowdStrike.A failed backup showing up in Splunk.Before, this meant just another ticket.Someone had to notice it.Someone had to analyze it.Someone had to act.Time lost.Today, the flow is different.Observability detects.AI evaluates.The system decides.And that’s where everything changes.👉 Ansible Automation Platform executes automatically:isolates the workload adjusts the infrastructure triggers remediation workflowsMeanwhile…👉 Veeam ensures there is always a clean recovery point:immutable backups validated re

So Andy you did Magic tricks some time ago right? Can you tell me how security and ransomeware scanning is done by veeam with a card trick? Im a little rusty with it, but sure Challenge accepted, I will give it a try…   Can you tell me how security and ransomware scanning is done by veeam?SureSo lets do an abstraction. So we’ve got your files. Let’s think about 52 files inside a card deck.Each card in this deck, represents your workload, your database, your VMs, your server, your fileservers, your hardware servers.Each card is one of them and of course they all have a lot of data inside of them.Now one of your files,  one of your file servers is gettin

Hi All,I’m encountering an error when attempting a restore from VBR version 13.1.2064 (recently upgraded):“ResourceExhausted: Sending message exceeds the maximum configured message size.”Does anyone know if this is a known issue or bug in the newer VBR versions?

I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.

Hello,Yesterday I had to re-install Veeam Backup for Microsoft 365.  I now lost my ability to restore from previous backups.  When I try to do a test restore, I can only choose backups from yesterday.  Is there a way to fix this?

I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:

Hello Expert,I am looking for advice on the best way to protect our Veeam VBR/DB. Our environment is currently set up as follows:Veeam VBR Server: Running as a VM on VMware.Database Server: Running as a separate, dedicated VM (MS SQL).Current Backup: We are currently including both the VBR VM and the DB VM in a standard VMware snapshot-based backup job.Is this considered a "good" or "supported" configuration? I am concerned about:Stun/Freeze: Will the VMware snapshot "stun" cause the VBR server to lose its connection to the remote database during jobs?Consistency: Does a standard VM backup ensure the VBR server and the separate DB VM stay in sync if a restore is needed?Circular Dependency: If our VMware cluster goes down, we lose our backup server.Should I exclude these VMs from our regular backup jobs and rely solely on the Configuration Backup tool, or is there a benefit to using Veeam Agent for these specific servers

 Given the complexity and critical nature of this transition, I have created Part 2 of this guide to focus specifically on updating WinPE boot images to support the Windows UEFI CA 2023 Secure Boot certificates.The previous guide was published nine months ago and continues to generate significant traffic. This follow-up article addresses the missing component: updating WinPE boot images to ensure compatibility with Windows Deployment and the Windows UEFI CA 2023 Secure Boot trust chain.The complete Part 1 guide is available here, followed by Part 2 covering “

After moving from v12 to v13 we have started seeing:Backup copy RPO violation: [server] was not copied within 165 days 23 hours 6 minutesThese seem to occur at semi-regular intervals to VM’s residing on a Proxmox server, maybe every14 days. What is odd is regular backups and offsite copies run daily and without error, even these jobsreporting RPO violations. Just in case, when these errors popup we run an active full and a copy. Werun tests to ensure they are working and can be restored.Any ideas why the error is occurring?

​It was a technical milestone last week for me in the lab after successfully migrating my Veeam v13.0.1 backup server from Windows to a Linux VSA. The purpose of this migration was to improve system efficiency and showcase the v13 product enhancements to my customers. This was a joint effort with Veeam support and the Partner team. Below are the steps I followed during the migration. The first step was obtaining approval from Veeam support and having a dedicated engineer available if any issues arose. All the migration steps are below Step 1 - engage Veeam support and open a migration ticketStep 2 - follow the pre-requisites from Veeam supportConfirm the latest P1 is installed Remove all the storage integrations from the Veeam server Remove the google plugin from the installation Collect and send the VMC log to support for verificationStep 3 - engage wit

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}

I have A DC that is being backed up, the backups complete successfully, but when I try to test it with surebackup it errors out with “Results: unable to perform Domain Controller restore from a crash-consistent backup. Be sure application-aware processing is enabled in the backup job settings”For the backup job on the server I have “Enable Application Aware Processing” ticked under guest processing. Is there some place else I need to look? I’ve tried unchecking the application aware processing, saving the job, and the re-checking it and saving then re-running the backup, but the surebackup still fails with the same error message.   

Hello everyone,I would like to validate a design scenario in Veeam Backup & Replication.The customer wants the following backup architecture: A primary backup repository without immutability A secondary immutable repository in the same datacenter A third immutable repository in the DR site My first thought is to use: 1 primary backup job to the non-immutable repository 2 Backup Copy Jobs using that same primary backup as source: one Backup Copy Job to the local immutable repository one Backup Copy Job to the DR immutable repository My main question is whether this is the right and recommended approach in Veeam.More specifically, I would like to confirm: Is it supported and considered best practi

TL,DRAfter upgrading to Veeam Backup and Replication v13, in one of our customer environments SAP HANA application backups started failing because the plug in tried to reach the repository on TCP 6162 first, timed out, and did not automatically fall back to the classic 2500 to 3300 range in our scenario as it should have done according to documentation.Opening 6162 fixed the connectivity requirement as confirmed by Veeam Support.  Our issueBackups that had been stable on v12 suddenly failed right after moving to v13, specifically SAP HANA application backups using the Veeam Enterprise plug in for SAP HANA. SymptomOur HANA jobs spent a long time “trying to connect” and then died with a timeout. In the logs it was obvious that the plug in was repeatedly attempting to connect to the

Hello, everyoneIn this article, we will explore Veeam Universal CDP (Continuous Data Protection), an advanced disaster recovery technology designed to provide critical levels of protection with minimal data loss.Unlike traditional backups, which run every few hours, Universal CDP operates continuously, enabling companies to protect their most critical applications with a Recovery Point Objective (RPO) of just a few seconds.What makes it “Universal” is its versatility. While Veeam's standard CDP is typically limited to virtual machines within VMware vSphere environments, Universal CDP extends this capability to protect a variety of workloads (such as physical servers or different platforms) and replicate them directly to a VMware vSphere infrastructure at a disaster recovery site. Backup infrastructure for Universal CDP The following backup infrastructure components are required to use Universal CDP: