Discussion Boards

Greetings. On a Veeam 12.3 install, whether there be an NFS or SBM datastore, and even while trying to hold the [CTRL] key and right-clicking on any datastore, the “Access Permissions...” menu does not show up, nor is there a ribbon icon visible for “Set Access Permissions” option.The logged in user into Veeam is a Veeam Backup Administrator. This option is visible on any other Veeam servers tested.What would be the cause for this effect? Thanks in advance.

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar

Hi everyone,Another week, another little project. 😀I’ve been spending some of my spare time practicing and experimenting with Codex again, and last weekend’s result is AgentBridge. The idea came from something that has bothered me for a while when working with Veeam Agent management in v13 VSA:VBR does a great job managing Agents once a machine is under management — but starting from V13, onboarding Windows machines in non-domain environments is no longer as straightforward as simply pushing via username and password. Linux certification also require SSH-based preparation and manual steps before they can be added cleanly.For one or two machines, that’s fine. But once you start dealing with more hosts, it quickly becomes painful.So I built AgentBridge.It’s a small open-source tool focused specifically on that initial bootstrap and enrollment process.You run AgentBridge as a single application on Windows, Linux, or macOS, open its local Web UI, connect it to your VBR 13.1 server, and us

Hi, we have a Fast LTA with 5 Silent Bricks. We plan to remove them weekly, and have one brick only in the system. We want to have weekly backups rotating offsite for one month (thatswhy 5 bricks). Whats the best strategy? Currently we have one volume and one S3 share per brick, and 5 backup copy jobs, they are running on first saturday, second saturday and so on, copy of the latest backups to the brick for the current week.But what happens if there are only 4 saturdays? I have no other scheduling options to get 5 weeks. How would you implement this? Thanks.Rene

Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra

Hi,I created a full system backup with veeam agent for windows on a dell laptop with Win 11 installed. I boot from Veeam recovery media to a new laptop, select the backup from external usb drive, select bare metal recovery and whatever i do (Entire, volume, manual) i receive the same error message: Restore failed: The stub received bad data

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:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate

Hi,We have a 2-node Microsoft Hyper-V cluster managed by Veeam Backup & Replication Community Edition.The two nodes are:- BETELGEUSE – works normally- SAIPH – affectedThe problem is that Veeam sees SAIPH as a Hyper-V server, but its Physical Host association appears to be broken.Veeam shows:SAIPH → PhysHostId = 00000000-0000-0000-0000-000000000000and:Get-VBRPhysicalHostdoes not return SAIPH, while BETELGEUSE is returned normally.We verified that:- SAIPH is reachable- VeeamHvIntegrationSvc is installed and RUNNING- WinRM/DNS connectivity to SAIPH works- the Hyper-V host itself is operationalThe impact is that VMs hosted on SAIPH are not being backed up correctly. As a temporary workaround, we moved the VMs from SAIPH to BETELGEUSE using Failover Cluster Manager, and the existing backup jobs then work normally.An important detail: the problem appeared after the network interface cards (NICs) were replaced on SAIPH.We also checked the Veeam PostgreSQL configuration database. The hosts

So it's very simple, our backup server (infrastructure appliance) had a proxy server configured for access to Internet (in order to fetch updates etc.)Everything good in 13.0.In 13.1 it seems to be trying to use internet proxy to connect to anything http(s), even “localhost”. Goes without saying that Backup server doesn't even properly start (system services can't connect to local identity service bc that sends them to internet proxy).After defining proxy exceptions for localhost etc., connections to data movers still fail, again because those connections attempt to go through internet proxy.Case is open with support. Reverted to 13.0. Careful!

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain th

Hi everyone, During the execution of a backup in Veeam Backup & Replication version 13.0.1.29 , integrated with Prism Central  pc.2024.3.1.14 the snapshot creates a recovery point, and this recovery point has a retention period of 60 days.I cannot find where this 60-day retention period is configured. I checked the backup job, but I cannot find any information or setting related to this retention.  where this retention is configured? does anybody know?  

Hi everyone,I’m testing the Malware Detection capabilities in Veeam Backup & Replication v12.1 (or latest) and wanted to check if this behavior is expected.Here is what I did step-by-step: Enabled Inline Entropy Analysis under the main menu's Malware Detection settings. Placed .onion links and ransomware notes inside a test VM. Enabled the Malware Detection option within the Backup Job settings as well. Executed the Backup Job. The job completed successfully without throwing any warnings, alerts, or failures.However, when I ran a SureBackup job on the same VM, it successfully flagged and detected both the onion links and the ransomware notes.Is Inline Entropy Analysis intended to catch file-based artifacts like text notes during the live backup process, or is deep artifact/file scanning primarily deferred to SureBackup/YARA scans?Any insights on how these two detection layers interact would be appreciated!Veeam version: 13.1

We manage several VBR deployments through Chef using the Veeam powershell module. In testing Veeam 13, we can’t seem to add groups with the Add-VBRUserRoleAssignment command in powershell. Veeam 12 works fine and in Veeam 13 adding local and domain users works fine, just no local or domain groups. We can add the groups manually through the Veeam BnR console just not with the powershell command. We are currently testing on Version 13.0.1.2067 however the previous versions of 13 seem to have the same problem. Has anyone else experienced this issue? 

I'm doing a full VM restore in Veeam to an HPE VM Essentials host, and I want to understand how the disk provisioning gets decided. Is there a way to force the restored disks to come back as thin-provisioned, or does Veeam just inherit whatever the target VME datastore or storage policy dictates?Trying to work out whether I have any control over this at restore time or if it's entirely determined by the destination.

1. Our environment:Veeam Backup & Replication (Advanced edition), HPE MSL3040 tape library, LTO-9 SAS HH drives, Windows Server 2025. Source data lives on a NAS file share (accessed via SMB/NFS). Processed data gets written to tape via a File to Tape job.2. Our requirement — tape verification:We need our verification to cover two layers:Read-after-write — checking tape parity and block integrity as blocks are written by the tape drive head, to ensure physical tape sectors have no write errors.Content integrity — after writing, reading back the raw file structures from tape, generating a cryptographic MD5 checksum of that data, and matching it against the original source file's MD5 to confirm the two are identical.Ideally this would be something we can run as part of an automated job rather than a manual step.3. Why this matters:Once a file is archived to tape, the source copy gets deleted from the NAS share to reclaim space. That means tape becomes the only copy — there's no going