Discussion Boards

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,

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

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? 

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. Smaller companies often have limited time to dedicate to cybersecurity.For larger infras

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

Hello everyone!Veeam 12.3.2.3617, Community Edition, Workstation Backup by veeam agentI’m having an issue with one of my home PCs. When I try to back it up, an error appears.29.09.2025 21:31:17 :: Error: Unable to resend traffic block '15863' because traffic history doesn't contain this block. History low block id '15869'.Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>];Agent failed to process method {DataTransfer.SyncDisk}.Exception from server: There is no traffic block '15863' on the source side.Unable to retrieve next block transmission command. Number of already processed blocks: [25496].Failed to download disk 'bdd448f6-e7b0-4f2b-93b3-6eb675ad51c3'   Backups of two other PCs to the same storage complete without any problems. What could be causing this behavior?I tried replacing the target HDD — it didn’t help; the error can also appear when backing up the SSD (the drive’s health is normal, no errors).I tried different backup types (volume, file-level, entire PC) —

NetApp ONTAP S3 with Immutability (ONTAP 9.14 and higher) is currently not (or no longer) supported by Veeam. This means that Veeam backups on a NetApp ONTAP S3 bucket with activated Object Lock (Immutability) are currently not considered “immutable” in the sense of Veeam functionality. The main reason is that ONTAP S3 with activated Object Lock no longer fulfills all the requirements that Veeam needs for immutability.  Veeam currently only lists ONTAP S3 as “not immutable” in its own compatibility directory. The use of Immutability is therefore not officially approved NetApp is working on a solution with the support of Veeam (you may be able to get information via the NetApp Partner Manager).  --> This is ONTAP S3 (on ONTAP machines (FAS/AFF), not a NetApp Storage GRID)! Links to this:NetApp ONTAP S3 with immutability - R&D ForumsNetApp ONTAP S3 

This is a great day Community!At VeeamON in San Diego back in April, Anton shared how Veeam is looking to add more hypervisor support to their product. Late last year, they began answering customers’ call to do so by implementing support for Proxmox. In more recent months, Veeam announced support for both Scale Computing SC/Hypercore and HPE on VM Essentials. But, that’s not all….Some of us in the Veeam100 Community were approached about a month ago to test out a Veeam Plugin for XCP-ng. Based on our testing & feedback Veeam has been hard at it getting the Plugin updated, and just today released a new Public Beta ripe for you all to test out! That’s pretty amazing considering something else pretty significant was released a couple weeks ago (has anyone heard about the Veeam Software Appliance on v13??? 😉 )For testing instructions, download link, and password go to the following Forums post by Anton Gostev:https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/veeam-plug-in-for-xcp-ng-

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

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 listed on Veeam here https://helpcenter.veeam.com/docs/backup/vsphere/trusted_root_certificates.html?ver=120.After installing all CA still got same issue here. Are i missing something here? Any insight would be appreciated! 

The IdeaWhen the weather is bad on weekends, I listen to music and vacuum, and then I can become creative. This weekend, an unusual idea came to my mind:What if Monopoly was not about money and hotels but backups and recovery? And when I get creative, the idea doesn’t let me go; I start doing stuff. Here is the result:BackupOpolyA playful way to explore Veeam’s ecosystem, while still keeping the fun and strategy of the classic board game. The player tokens would be a tape cartridge, a notebook, a server, and more. I sketched a board design in Excel (Drawing with Excel relaxes me).Design for the game boardAnd then I put together some basic rules. Here's what came out of it.ObjectiveBuild the strongest data protection environment by acquiring Veeam products, storage systems, and advanced features. Collect VUL licenses, charge opponents when using your technologies, and avoid penalties for ransomware or audit. The last player not bankrupt wins.Instead of dollars, players pay and earn Veea

I’d like to share my current backup infrastructure and get feedback on best practices when using Synology NAS with iSCSI LUNs as Veeam repositories.🔹 Current Setup Main Site Backup Jobs → Repository on Synology NAS (connected via iSCSI LUN to VM). Secondary Site Backup Copy Jobs → Repository on Synology NAS (iSCSI LUN). Immutable Backups Another Synology NAS configured as a Hardened Repository (WORM / immutability). Backup Jobs First Backup is Full Backup, then after then we do incrementals and Synthetic Full Backups on Fridatys. Disks are configured as ReFS with 64KB block sizes since that was recommended when I was configuring this. Aprox 2 years agoAny recommnedations would help. 

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

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(*)After to installed manually veeamsnap-kmp-default-6.3.2.1207_k4.12.14_94.41-sles12.4.x86_64.rpm and cons

Hi, I created “Backup Copy” and somehow is working if the Object Type is “Agents For Window Job” but not on “Repository”. Is there something I missed out ?   

Hi,A newbie here with using Veeam for Oracle RMAN backups.I am trying to understand/visualize whether the RMAN retention and Veeam Immutability are independent of each other or are they related in some way.We run our backups on the Oracle DB server using shell scripts and cron and using a RMAN catalog.We have set  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 35 days.We do RMAN delete obsolete as well.The Veeam Immutability is 7 days.Does Veeam delete the backup files if they are 7 days old or does it delete the files if RMAN fails to delete them after 35 days? Or does Veeam do nothing unless we uses the force-delete?Kinda hoping someone has a presentation of some sort to show how this works. Have read thru the documentation and can’t find any that explains this. Or maybe it is explained more clearly/visually in any Veeam documentation and I just can’t find it.Any reply will be much appreciated. Thanks in advice. 

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