Community

Hello community,I've seen many customers using Veeam Backup Replication to back up vCenter Server Appliance VMs via image level backup.According to this KB https://www.veeam.com/kb2328  "vCenter Server Appliance - Backup/Restore Recommendations" Veeam do not reccomends you to run image level backups againts VCSA. You should use:  So, I created this procedure to show how simple it is to back up a vCenter Server Appliance using VMware's own backup tool, which we call "vCenter Native File-Based Backup and Restore."Check out this link f

We have licensed Veeam via Socket License and want to Backup our Windows DCs from a different Console than the Rest.They are running on the same ESXI Hosts as the other VMs we already Backup.Is this possible with our license?

Hi, I’m trying to make room in my backup repository for new backups.  My previous retention was set to 90 days and the oldest backup is from 45 days ago.  I changed the retention to 30 days, thinking that Veeam will then delete the backups between 31 and 45 days ago to make room, but it’s not doing that.  Is there a way to prompt it to do that?  I’ve tried to rescan the repository and also re-running the Backup Job, but neither seems to work.  Thank you!

Since this product is part of the Veeam family now I headed over to checkout what there was on the website. Very interesting courses. I did the ones that they offer to non customers and wrote for the other two requests to be allowed in given the fact that they really could use some Veeam evangelists on their side now 😁. We will see if they give in. Either way head over to their site and check out the courses, very interesting stuff https://education.securiti.ai/certifications/ai-governance/ 

Hi,Previous I have turn on backup notification but now after turn off, email is still send ? Any idea where I can turn off ? Sample email notification 

I decided today to publish blog #3 for the Object First (OOTBI) series I am doing.  You can find my blog at the following link as well as in this post.https://just-virtualization.tech/2024/09/06/object-first-ootbi-veeam-integration-backup-stats/ Object First (OOTBI) – Veeam Integration & Backup Stats Today, I am going to discuss the integration of Object First OOTBI into the Veeam Console and show you some backup statistics on the appliance’s performance. Again, I am part of the inaugural Object First Aces program, which has afforded me the opportunity to test both the physical hardware appliance and the virtual VSA for OOTBI.To begin, we must integrate the OOTBI appliance into the Veeam B&R Console by adding it as a Repository under the B

Hello Community!  I am new to Veeam (last used 7 years ago, so might as well be new). Here is my current setup:  I have two Mini PC’s running Proxmox as the “Compute”.They are connected over 10GB  to a different server running TrueNAS, via iSCSI.So the VM “Data” does not actually reside on the Proxmox machine, it just acts as the compute side. Now, I have installed Veeam on a Barebones Windows machine.  I configured the Veeam software to connect to the Proxmox servers (success) and it installed the proxy’s.First backup tested was successful, but the others failed.They show “succeeded” but with “Warnings” and no actual data has been backed up.“disk scsi0 has been skipped due to unsupported storage type” I find this odd since the storage type on the successful backup is the same as the other VM’s I am running, (Three Ubuntu VM’s & Home Assistant OS). Any insight would be appreciated!

I just updated the Veeam Agent version to 6.3.2.1302 on my home computer. I don't use a server because it's a single machine with a single backup job, although I do use the Community Edition in other environments.I re-burned the recovery agent to a USB drive, and when I tested it, neither the keyboard nor the mouse worked. The BIOS recognizes them fine, but when the agent starts loading, it disconnects them.I've tried having up to three different keyboards connected to different USB drives, and re-burning the USB drive four times, making sure the option to copy drivers is enabled, but nothing seems to work. I've never had this problem on this computer before.With this and the previous bug that prevented me from recovering backups from a network drive, which has since been fixed, I'm starting to think I spend more time trying to fix Veeam errors than actually using it.Any ideas on how to fix this?

​Hi Community, time to talk a bit of RAID level, today I will bring to you some number when using R0, R1, R5 and R6, the goal fo this part it is to show how important is to use R6 configured on your RAID controller when you need to use some storage volumes as a DAS repository (using server internal disks, not one external Array)   RAID level 0 - No Fault ToleranceA RAID 0 configuration provides data striping, but there is no protection against data loss when a drive fails. However, it is useful for rapid storage of large amounts of noncritical data (for printing or image editing, for example).

Hi,I would like to backup with Veeam backup and replication 12 my new physical NAS with TrueNas Core.How can I proceed ?Do I need to add my TrueNas like an “unstructured data source” ?If so, what option should I choose in next window? File server, File share or NAS filer ?Thanks for your helpRegards,

Hi, new install of veeam with a dell poweredge server and powerstore connected via iSCSI. this will be a hardened repo.Has anyone tested the optimal settings for Veeam including immutability against the powerstore so the powerstore can still perform the data reduction tasks? 

Hi Community,Recently i install Veeam Agent on Windows Server 2008 R2 via VBR 12 Inventory and got an error  Failed to Verify C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll Signature I found this page https://www.veeam.com/kb4677 and explain 2 possible causesAntivirus Block → Root and Intermediate CA is missingTo confim the issue we look at C:\ProgramData\Veeam\Backup\Svc.VeeamInstaller.log and gotFailed to verify file using the Authenticode provider. Verification status: A certificate chain could not be built to a trusted root authority. (-2146762486), last error: A certificate chain could not be built to a trusted root authority. All are pointing to Certificate Issue, so i install all CA l

Hi All, I have a VBR 12.3.2 server running in AWS as an EC2 instance.  Use Windows agent on other EC2s to back them up to an S3 scale-out repository.  The backups work as expected.  I am able to do file level restores with no problems.  When I try to do a restore to EC2 (create a new EC2) I get the following error “Unable to import the instance from an encrypted volume snapshot” when I click Next on the Reason screen.  I do have it set up to use a helper appliance.  Do you have any thoughts on how to get this working?  The volumes of EC2 that are backed up are encrypted with an AWS-managed key (aws/ebs).  But shouldn’t it be pulling from S3 for the restore? Thanks for any help you can provide.Scott

once i try to install VeeamBackup&Replication the setup refuse to complete it just once started it gives  that The error "unknown exception occurred vmaGetpropertiesFromRegistry"and close the setup and refuse to continue i am sure that happes related to uncorrect uninstalled veeam application is that mean i look for another application ?

Query related a IAM user and IAM role:  Suppose if any customer has a Multiple AWS Accounts  with Control Tower Environment AWS setup, approx. 50+ account and want to take a backup of instance and DB backup using veeam backup for aws appliance,  is it possible using single IAM user and single IAM role to take backup of all workload of this separate account .  Require a IAM role permissions for Control Tower Environment AWS setup, In veeam documentation it is not available. 

Additional Details: Veeam Agent for Linux backup job fails with the following errors:[error] Failed to create volume snapshot[error] Failed to take volume snapshot[error] Failed to perform backup [error]Veeam snapshot kernel module not foundSystem informationSO: SUSE Linux Enterprise Server 12 SP4Kernel: Linux version 4.12.14-95.32-defaultkernel-default: kernel-default-devel-4.12.14-95.24.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.32.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.128.1.x86_64dkms version: dkms-2.6.1-9.1.noarchveeamsnap: veeamsnap-kmp-default 6.3.2.1207_k4.12.14_94.41VBR Console: 12.3.2.3617VAL: v6.3.2.1207I read ready the list of compatibility with extended Linux distributions of veeamsnap and blksnap https://www.veeam.com/kb2804 couldn´t see the compatibility for a 4.12.14-95.24 or 32 or 128 also on rpm veeam repository I don't see a version(*

I have VBR installed in Site-B to backup VM under hyper-v and vmware in Site-A.Connection from Site-B to Site-A using ipsec vpn site to site with 2 internet link for redundant.The VPN have same policy for both connections. When the link use primary link then the VBR can backup the VM but if the primary link and connection switched to the backup link then i got error only for Vmware when using backup proxy.I try to ping from the backup proxy in Site-A then the proxy is able to reach HS-W2019.This error mean the backup proxy is not able to connect to the HS-W2K19 on port 2503? Error: Failed to connect to the endpoint [HS-W2K19:2503]. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 

I have recently installed the Scale Computing plugin into our Veeam B&R 12.3.2 server. If we are currently using Microsoft Agent Backups, is there a migration path to moving to direct VM guest backups via the Scale plugin? If not, can I utilize VM guest backups via Scale plugins for 'new' guest servers and also back up pre-existing servers using the Microsoft Agent method?

Veeam Service Provider Console v9 has been released recently, and it’s one of the most impactful updates we’ve seen in years for VCSP partners. The new version focuses on simplifying MSP operations, expanding compatibility across the Veeam ecosystem, and giving service providers more control with less infrastructure overhead. No More Dependency on Veeam Cloud ConnectThe biggest shift in v9 is operational simplicity. The dependency on Veeam Cloud Connect for managing tenants is now optional. Partners can directly handle tenants, workloads, and agents within the Console. This reduces complexity, speeds up onboarding, and lowers infrastructure costs.All existing connected Veeam Cloud Connect servers will be moved to the Veeam Cloud Connect plugin Tenant Consolidation Under One Company

IntroductionBackups are the last line of defense when cyberattacks strike. Veeam users rely on the platform to restore data quickly and reliably in critical situations. However, availability alone is not enough, backups must be trustworthy. To address this challenge, I created a Python script that uses the Veeam Data Integration API and runs the THOR APT Scanner against the presented restore point(s).Who is Nextron, and what is THOR?Nextron Systems specializes in forensic threat detection. Their flagship product, THOR, is widely used by incident response and security teams to uncover attacker tools and traces that traditional solutions may miss. Unlike classic antivirus integrations, T

Migration from MS-SQL to PostgreSQL is way of preference or license topic.For small environment no one will provide tuning of PostgreSQL configuration.But for bigger backup environment is tuning necessary.Most of issues is possible to fix with 2 things:exclude PostgreSQL from antivirus change 3 values in postgresql.confExcluding from antivirus will prevent to exclude of scanning communication with database. After migration into PostgreSQLCPU usage is too high, even with high number of cpu (32 vCPU in this case) Enterprise Manager is unresponsive (in my case is installed together with VBR)

 Importantly, administrators are responsible for enabling and configuring the fencing mechanism after cluster deployment. Without the fencing configuration, node remediation and VM restarts will not happen as expected. In virtualized environments, high availability (HA) is essential to keep workloads running even when a node fails. In OpenShift Virtualization, HA leverages Kubernetes-native mechanisms combined with OpenShift’s self-healing infrastructure.A key element is fencing, the process of isolating a failed node to prevent issues like split-brain—a scenario where nodes lose communication but continue running independently, causing data inconsistencies and conflicts.When a node goes down, restarting virtual machines (VMs) ha

If you have not upgraded your Promox node yet due to dependencies on Veeam Backup and Replication (VBR). The wait is over as Proxmox Virtual Environment (PVE) 9.0 is now fully supported. It is packed with powerful new capabilities for modern virtualisation and software-defined data centres. Whether you are running a home lab or managing enterprise-scale clusters, this release is a game-changer.Recently, I created some blogposts on how to setup Proxmox VE and also how to Backup and Restore Proxmox VE virtual machines with Veeam.

When Veeam Recovery Orchestrator (VRO for short) is used, it is usually an infrastructure with a VDP Premium license. Alternatively, the use of VDP Advanced and additional 10 instance packs for the Orchestrator would also be possible.In the Orchestrator itself, there are various ways to map recovery plans.In this article, I would like to show a way to first shut down the productive workloads when using replication jobs, transfer the delta data to the DR-site and then boot it up there. This corresponds to a native planned failover within Veeam Backup & Replication (with more options and reporting functionalities).  Replication Jobs in VBR In my lab, I work with various VMware vSphere tags, which map SLAs here (Gold, Silver, Bronze). My replication jobs wi