Community

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.

Hi.If someone had completed the training of Veeam Backup & Replication v12.3: Configure, Manage, and Recover (VMCE), Can they just attempt the exam for the same or they can also attempt the exam for VMCE 13 as well or they have to attend the VMCE 13 training to attend the v13 exam. TIA

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

Having updated to Proxmox VE 9.0 below. There is a need to upgrade from  Veeam Plug-in for Proxmox VE build 12.1.3.217 to plug-In build number 12.1.5.17 to support it.The Proxmox VE Plug-in integrates the backup server with the Proxmox VE server and enables worker deployment. From version 12.3.1 and above, you do not have to manually install this plugin.You can download the Plugin for Proxmox VE directly from the referenced link, or navigate to the release Information for Veeam Plug-in for Proxmox VE v12.1.5.17 in the following KB article.

IntroductionThis blog provides a practical guide to deploying a single-node Kubernetes cluster and integrating the Veeam Kasten K10 solution.The objective is to offer a clear reference that facilitates the exploration of Kasten’s features and benefits. EnvironmentTo carry out this env, the following components are required (depending on the defined scope):One or more servers forming a Kubernetes cluster. An instance of Veeam Kasten K10.Kubernetes Service (k3s)For the installation of K3s, a server (or more, depending on the needs of the lab) was deployed to simultaneously fulfill the roles of master node and worker node.The chosen operating system was Ubuntu 22.04 LTS, due to its stability and compatibility with K3s.Note: The provisioning of the virtual machine and the operating system instal

My recent discovery so it could help someone not to loose time. And maybe if there is a solution I’ll be most thankful.So with Proxmox version 9 you need to set Machine type to version 9.2 instead of Default as it defaults to 10 and that causes Veeam backup to fail.  That will insure that your backup will be sucesful and restore will work too. I have issue, where I am migrating servers from Hyper-v to Proxmox and usual and most painless solution was to use Veeam Backup&Restore as intermediary as we are already using it.But in this case restore to proxmox fails as when VM is created is created with default version for machine type and this defaults to 10 and this results in: Failed to prepare disks for restore. (If anybody knows how to convince the process to default to 9.2 Mychine type I’

VMCE v12 trainingA brand new VMCE v12 training course was launched in September. The 3-day training now includes many of the great things that have been implemented in this version.Find your training here: Veeam Certified Engineer (VMCE) Training VMCE v12 examThe associated VMCE v12 exam has been available since 1 October. As a Veeam certified trainer myself, I have to be compliant within the next 60 days. That's why I planned a tough schedule and scheduled the exam just one day after this year’s Veeam100 summit in Prague 😀.Schedule your exam here: Get Veeam Certified Now! Exam flavorsThis time I took an online protored exam with PearsonVUE. I used to like on-site exams better, but since Covid

Because of the new v11-feature of immutable backups on XFS filesystem, I am looking for real-world experiences with XFS as Repository.I just read through this forum entry:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.htmland the closing experience of user ferrus:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.html#p388579 Sounds very good to me so far. I can remember first implementations of ReFS Block Cloning. Lets say, it does not work that fine at the beginning.Would you share some of your experiences with XFS as Veea

Hey everyone,As we prepare for the upcoming update that introduces support for Veeam v13 on Windows, I wanted to ask:What migration strategy are you planning to adopt and why ?Will you simply upgrade your existing Veeam Windows server to v13? Or do you plan to migrate to v13 and then transition to the Veeam Software Appliance?So far, I haven't found any official discussion about the migration process from Windows to Linux. Ideally, I'm looking for a solution that allows me to back up and restore my settings during this migration. Personally, for all new projects, I’m planning to propose the new Linux-based appliance, even though some aspects still require optimization and improvement. In cases where migration is possible, I would tend to recommend switching to the appliance for smaller infrastructures as well — mainly to benefit from the native hardening layer and eliminate Windows licensing costs. Smal

Hi all,the in place upgrade of Veeam ONE 12.3.x to 13.x doesn’t work. The MSI packet for the monitor client won’t be found. The path to the MSI file is shown as “1” and giving the correct path to the mounted ISO ends in an error message that the MSI doesn’t fit to the system (Windows 10 22H2).What can I do? At the moment I do not plan to update my Windows machine. My way is to go away from Windows in the next months.Kind Regards

You might have found the same information when you upgrade the previous version of Veeam Backup and Replication server to v12.3.2.4165.The version shows 12.3.2.3617, not 12.3.2.4165.After the upgrade is complete, verify the Veeam Backup & Replication version from the Veeam Backup & Replication console (Help | About). It shows the correct version information.