Community

Hello, I currently have an R740 with a NetApp E Series directly attached and am looking to use it as a hardened repo (rocky os). I am concerned that the 740 is near end of life, so wondering how difficult and what would the steps be if I was to replace the server with a new one in a year or two down the line? 

  Three management modes at a glance.  Mode Managed In Best Fit Reality Check Standalone Local server Isolated hosts or segments without VBR reachability Easy to forget until restore day VBR-managed VBR console Most internal infrastructure teams Best default when central visibility matters VSPC-managed VSPC via tenant VBR Service provider and multi-tenant designs Adds tenant visibility and service-provider controls  Linux boxes still end up doing a lot of the jobs nobody wants to virtualize.File servers. Monitoring nodes. Database hosts. NTP servers. Application servers that got built once and never moved again. They are everywhere in Veeam environments, but the Linux Agent still gets less attention than the Windows one. That matters, because some of the things that are easy to gloss over on Windows become real design choices on Linux.This is the part that actually

Last week I attended my first RSAC in San Francisco. To say it was a great experience would be the understatement of the year.The conference is enormous, and you can tell just by walking around downtown as the streets were filled with people sporting their RSAC badges. I quietly slipped mine off whenever I ventured outside the convention center. Wearing it felt like broadcasting to the city: "I'm from out of town — please rob, scam, or at least aggressively inconvenience me." Better to blend in with the local hipster cyclists. More on that later.AI Everywhere (And I Mean Everywhere)AI dominated the conference floor. Nearly every booth referenced it, the street advertisements were themed around it, and by day two I half-expected to find an AI-powered fixture in the restroom. (In some parts of North America they call it a "restroom" — in Toronto we say "washroom." My theory is that in some locations companies work their employees so hard that the restroom is the only place they can hide

I recently wrote a blog about VSA HA Clustering, which you can find below (link to my site is below as well).Veeam VSA HA Cluster Setup With the release of Veeam Backup & Replication 13 there is a new feature that you can use to set up two nodes in an HA Cluster configuration for high availability.  I am going to outline the process below and keep in mind that you will need to have a VDP Premium license in order to do this as that is a hard requirement.  Now let’s look at HA Clustering with Veeam VSA.Configuring a Veeam VSA HA ClusterThe HA cluster configuration process involves two major phases: enabling the HA feature on both nodes via the Host Management Console, and then assembling the cluster through the Veeam Backup & Replication Console.Enable High Availability on Both Nodes via MGMT UIBefore the cluster can be assembled, the HA capability must be enabled on each Veeam Software Appliance independently through the Host Management Console (Web interface on port 10443).Acce

 Microsoft’s position on your Microsoft 365 data has not really changed: they keep the service running, but they do not give you backup in the way most admins mean it.Yes, deleted data may hang around for a while. Exchange has retention behavior. SharePoint and OneDrive have versioning. Teams data can still exist in awkward places even after it disappears from the user view. None of that gives you a real backup timeline, a clean point-in-time restore, or a recovery workflow you would want to bet an outage on.That is the gap Veeam Backup for Microsoft 365 fills, and v8 is not just another incremental release. The architecture changed enough that you need to think about deployment differently than you did in v7. Start with the big change: v8 is built around PostgreSQL If you are coming from v7, the first thing to understand is that SQLite is gone from the design that mattered before.Older builds used SQLite for the configuration database and for per-proxy cache data. In v8, that moves in

HiI am planning to deploy Veeam Backup & Replication v13 using the Veeam Infrastructure Appliance with a Hardened Repository configuration.My question is about capacity expansion during production operation.If the backup storage becomes insufficient after the appliance has been deployed and is already in use,is it a supported operation to add an additional virtual disk to the appliance VM and expand the backup storage capacity (for example, extending the repository storage)?Specifically, I would like to understand:Whether adding a new virtual disk to the Veeam Infrastructure Appliance VM is officially supportedWhether this applies to a Hardened Repository configurationIf there are any restrictions, best practices, or unsupported scenarios we should be aware ofThe goal is to increase backup capacity without redeploying the appliance.If there is any official documentation or guidance from Veeam regarding this scenario, I would appreciate it.Thank you in advance for your help.

Hi all, Sorry if this has been covered, I couldn’t find it in the search. I have a HyperV host and I want to use VAW to backup the D drive containing the HyperV VM files.  I have 2 USB disks I plan to rotate.  I’ve read the guides and I have registered both the USB disks as storage devices.  Last night it failed and I am suspecting it was due to the drive letter not being assigned when it got reconnected.  In theory, am I OK to simply leave one disk plugged in and VAW will do the backup to that disk, if there is a drive letter assigned?   Thanks.  

Hi, I tried using Veeam Agent for Windows on my 2025 Server to backup a D drive.  The backup destination was a couple of USB disks which I registered with VAW and I wanted to use the disks on rotation.  That backup job failed with some problem about VAW insisting on using the same USB disk each time, plus my colleague convinced me to use the community version of Veeam Backup & Replication, so I started again. I’ve installed VBR, created a repository using one of the USB disks and did my first backup.  All ok.  Then I re-ran the job 5 mins later with the same USB disk still plugged in, so no disk change/no rotation, as I wanted to see if it created the VIB file.  Nope!  I got this: Processing New Backup_Job_1 Error: Update of the storage [E:\Backups\SRV02\New SRV02.c5c62b19-d1f0-4e8e-864d-3da8e38f3D2026-03-30T222815_7C96.vib] is not supported. Storage version: [0]. Failed to open storage for read/write access. Storage: [E:\Backups\SRV02\New SRV02.c5c62b19-d1f0-4e8e-864d-3da8e38f3D20

Every time I try to open a case in my Veeam portal, I get a permission error that I can’t:Which is odd as I am the admin for our license, and I can’t raise a ticket to say I can’t raise a ticket as it always goes back to this error. Can’t use phone support as you need a case number from raising a case. Could someone from Veeam help sort this out? RegadsDamien

Hi Team,I am getting this warning during a Veeam Agent backup: Warning: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instance XYZ. The backup completes successfully and application aware processing is enabled, but the SQL logs are not truncating. Any idea what could cause this or what I should check next? Thanks.  

How we can make exclusion for virus warning when backup m365 using VBO? 

It was a holiday weekend here in Brazil, Carnival, and I was off when I got the call around noon.A client had been hit by a ransomware attack.The entry point was a phishing email that compromised a workstation. From there, the attacker managed to move laterally, reach Active Directory, and eventually gain access to the entire environment.By the time I was involved, most of the damage was already done.Around 50TB of Windows-based VMs were encrypted. Production was down.The environment did have antivirus in place, but it wasn’t properly configured to stop that kind of behavior. In the end, it wasn’t enough.  At that moment, the biggest challenge wasn’t just restoring the environment, it was figuring out when it had actually been compromised. Without that, choosing a restore point becomes a risk.You might bring everything back… already infected.That’s where Veeam Software made all the difference. It wasn’t a straight path, each restore point helped us understand how far the compromise had

Hello everyone,I am currently configuring Veeam Backup for Microsoft 365 (VBM365) for our company, and I have a question about the disk cache to optimise performance.According to the documentation, the standard installation does not allow the cache to be stored on another drive on the VBM365 server (it is located by default in the local PostgreSQL database on the C drive or on a dedicated PostgreSQL server). However, I would like to avoid deploying an additional PostgreSQL server for simplicity and maintenance reasons. My question:Does anybody use a dedicated cache disk on the VBM365 server? If so, how did you configure it (custom path, script, etc.)? Have you encountered any limitations or performance issues? I would appreciate your feedback or alternative solutions (without external PostgreSQL).Thank you in advance for your advice!Morgan

In this article, I'll take you through five different restore scenarios I've tested in my lab, and you should do the same.You’ve got green checkmarks.Your jobs are running.Storage looks fine.Everything seems good.But here’s the uncomfortable truth I’ve learned the hard way:A successful backup job does not mean a successful recovery.Day 2 operations is where this really hits. This is the phase where you stop asking “Did it back up?” and start asking:“Can I actually get my data back when it matters?”If you’re not actively testing restores, you’re running on assumptions—and assumptions don’t survive outages, corruption, or ransomware.Here are five restore scenarios you should be testing regularly (but most people don’t). 1. Full VM Restore (The “Everything Is Gone” Scenario)This is the big one.The “we lost the entire server” moment.It sounds obvious, but a lot of environments never test a full VM restore end-to-end.What to validate:Can you restore to the original location? Can you restore

Repost of topic on the RND forums, but figured to share this here as well: Sharing this tidbit here as there are quite a few topics on how to do session reporting on all job types including the plugin-based Hypervisors (aka PlatformBackups, for example Proxmox, Nutanix, HPE Morpheus, etc)Normally you would pass a CJob object from Get-VBRJob to Get-VBRSession -Job, but regrettably this will currently error with many job types:Get-VBRSession: Cannot bind parameter 'Job'. Cannot convert value "Veeam.Backup.Core.CBackupJob" to type "Veeam.Backup.PowerShell.Infos.VBRJob". Error: "The given key 'VmbApiPolicyTempJob' was not present in the dictionary."However, we can do a little magic trick with Get-VBRSession on the -Type parameter to get all PlatformBackup jobs; Get-VBRSession returns "light" information on the session data, so we will do another magic trick to get full session data from Get-VBRBackupSession, which in turn can be passed to Get-VBRTaskSession for full session reporting with

Not sure how useful this will be for anyone else, but should you need to parse through your logs on all gateway servers for S3 errors returned during Veeam operations with Object Storage, this script is for you.Script requires ripgrep to be installed on the Backup Server: https://github.com/BurntSushi/ripgrep?tab=readme-ov-file#installationIf you cannot install / use chocolately in your environment, download the ripgrep binary appropriate for your OS, and edit the script as noted in comment [2]. What it does:Collect all Object Storage Repsositories Get Ids for all assigned gateways Collect all gateways with Get-VBRServer cmdlet to create array of gateways Iterate over each gateway and do the following: Export logs JUST for that gateway server to the VBR server, uncompressed grep the logs for the relevant S3 error string with ripgrep (rg command) Write all found errors in full to a .log file Pares all found errors and write in human friendly format to CSV Clean up the exported logs,

We are currently using Amazon S3 Standard as the Capacity Tier and S3 Glacier as the Archive Tier for offsite backups in the AWS region.We are now looking to implement Capacity Tier replication to another AWS region.Backup configuration:Daily incremental backups and weekly synthetic full backups Backups are retained in the Capacity Tier for 15 days After 15 days, weekly backups are moved to the Archive Tier (Glacier)Please advise on the best approach to configure replication of backup data between AWS regions for capacity tier

Hi Team, We are updating VBR from version 12.3.2.4165 to 12.3.2.4465 and we VAL and RMAN which are in version 6.3.2.1207 and 12.3.1.1139 My Question is after the VBR upgrade will RMAN and Linux agent backup works with existing version or do we need to update agents as well immediately 

I already have a ticket open on this, but while Im waiting does anyone have any suggestions on things to try. Unfortunately, to make things complicated this only started happening after we upgraded to V13 and also upgraded the firmware on our exagrids. We are using storage integrated backups with Pure. I have not updated the Storage Array plugin yet. I have rescanned everything I could possibly rescan and all backups still sit at 0% 

 We recently completed an upgrade of Veeam Service Provider Console (VSPC) from version 8.1 to version 9.1 in a large-scale, multi-tenant service provider environment. From an infrastructure standpoint, the upgrade was uneventful in the best possible way. All core services came online cleanly, communication between components remained stable, and backup operations continued without disruption. Pre and post-upgrade validation confirmed that the platform was operating as expected. During routine post-upgrade review, particularly within the Managed Computers section, we observed that a subset of endpoints had management agent upgrades that were not completing successfully. After reviewing task logs across multiple tenants, it became clear that these were not platform-related issues, but conditions specific to individual endpoints that surfaced during the agent upgrade cycle. Given the scale and diversity typical in service provider environments, sharing these observations may be useful fo

I am trying to restore Ubuntu VM to Azure but never got any success. We had issue with ver 12.3 where it never create helper appliance for the region so we upgraded to ver 13. It now try to create helper appliance but never complete succesfully. When restore process starts, it creates helper appliance in Azure with status running but never get pass that stage. Internet access is restricted to outbound access to windows update, azure & Veeam.I even tried restoring the Azure environment where we have ipsec tunnel but not luck, still fail with same error.  

TLDR;set up a linux server as a veeam repository on a proxmox server for local VBR proxmox proxy target? I searched around the community for a bit, so if I missed a good post can you point me at it? We stood up a new site last year and I initially deployed Hyper-V server to run a DC and a file share server at the remote site/branch. Using Hyper-V and Veeam I was happily surprised that Veeam deploys a proxy to back up Hyper-V (mostly was using vmware).I had a local disk attached to the Hyper-V server which acted as a Veeam backup repository. This as a pretty awesome surprise how easily and fast the Veeam backups and restores happened on the Hyper-V server using a USB 3 external hard drive.So Veeam would run jobs to hopefully back up the Hyper-V servers locally and then I would run a disk copy job to pull those backups back to the main site periodically for just in case scenarios, and would also copy the disk copy jobs to a rotating offline backup.I recently decided to migrate away from