Community

Hi all. Running Windows Server 2019 as a standalone Hyper-V server. The server is in a workgroup.I have installed the community edition of VBR 12, and configured my backup repository.When trying to configure a new Hyper-V backup job, Veeam gives me a message to say that it cannot connect to the ADMIN$ share. However, if I type \\localhost\ADMIN$ into the run box, then the folder does open.I’ve tried setting my host name to localhost, to the server name and to it’s IP address. I’ve also tried with the current logged in credentials, and have tried by enabling the administrator account.Any help would be appreciated.Thanks, and have a great weekend!

I read in the news recently that Veeam has bought Securiti AI, which is going to have a direct impact on its data protection offering. This deal is a game-changer for Veeam's strategy, combining data resilience with data security.But what does Securiti AI do, and why did Veeam decide to buy it?Securiti AI is a big name in the industry, and they focus on Data Security Posture Management (DSPM), privacy and data governance. With a spent about £1.725 billion in total Veeam's big plan is to bring together their data resilience (which they're really good at – backup and recovery) with data security (Securiti AI's thing).So, why's this important for Veeam?I think this purchase is meant to create one command centre where they can use DSPM on data in use and on backup files as well. This means that sensitive data (PII, GDPR-compliant data) can be easily identified in backups, and the compliance and security posture of the backup data itself can also be verified.So not only can customers restor

Two weeks have passed since the Veeam 100 Summit in Berlin. This time the grateful members of this select community were given facts about the upcoming version 13 of VBR and also the opportunity to test the Linux version via an OVA ready to install in a VMware environment. ​@HunterLAFR already showed us some initial screenshots here:LAB- Deploying VBR13 – on Linux – OVA! | Veeam Community Resource HubI’d like to add a summary of what I found most interesting.Before you ask: No, we don’t have a release date yet. There is still some 12.x version(s) to go before. 😎But, what we see with v13 seems already quite complete when looking at the interface.As ​@HunterLAFR has already shown in his screenshots, we have to options to access the GUI. There will be a new WebUI. This directly greets us with a nice and colorful dashboard. Obviously, this is all static demo date right now. But looks very promising still and will finally deliver the single pane-of-glass view onto your backup infrastructur

I shared with the Community last week how to configure Veeam HA in the new VDP v13 BETA Preview. If you'd like to see those posts, here is Part 1 and Part 2.I want to switch gears a bit and now take a look at Veeam's new ability to create Custom Roles in the Remote Console. Before diving into this topic, as with my other posts…let me share a few disclaimers:> As is stated in my blog title, the build I'm using is a VDP v13 BETA build. Buttons, topics, functionality, feature location, role types, etc may change when this version reaches GA> Because of the above, how I show you how to configure custom roles now may be a little different in the GA versionWith those out of the way, let’s now configure a couple custom roles.Introduction Before showing you how to configure custom roles, let me go over a few talking points about roles in the new VDP v13. In this new version there is a newly added Security Officer role. This is not a role configurable in the Web UI or Remote Console (RC).

 It's been a bit quiet around me the last few weeks. I am currently active in several projects, including two different customer infrastructures that start in the greenfield with V13 based on the Veeam Software Appliance and are in the fortunate starting position of having premium licenses in use. Thus, nothing stands in the way of the use of the High Availability / HA function.Important to know: Only the Linux Veeam Software Appliance can provide the HA feature and only in conjunction with the Veeam Data Platform Premium license!See Considerations and Limitations - Veeam Backup & Replication User Guide for general considerations and limitations when using HA. I strongly recommend that you read this page carefully and follow the guidelines.Marvin "Marveeam" ​@MarvinMichalski recently reported on his blog about providing the HA feature, you can find the article at How To: Veeam High Availability (HA) Cluster, take a look.So, the basics are clarified and the initial setup is done...

Good day Running Veeam Community v12 with a VMWare environment. I am running a backup of 3 VMs. Since I installed Veeam I cannot do a backup copy of a job for one of my servers. The 2 other servers that I run a backup copy and send it in a remote location works but that server I always get this error: Processing [server name] Error: Times out waiting for NFS async IO block callback. Timeout: 180000 msec Failed to download disk 'filenameofserver-flat.vmdk'. Shared memory connection was closed. Failed to upload disk 'filenameofserver-flat.vmdk' Agent failed to process method {DataTransfer.SyncDisk}.Some restore points were not processed The local backup works but I cannot get the backup copy to workI created a different backup job for this server alone but I also get that error. The option I was thinking to do is to do a backup job just for this but i’d like to figure out why only that server on the same host as the 2 other servers is causing me this problem. Thanks for the help

When i tried to restore my database using veeam explorer for oracle from a backup created using application aware processing i got :Failed to resolve path : /h01/oracle/agent/agent_13.4.0.0.0.  

Hello Community,I would like to check if anyone has practical experience or official guidance regarding the following scenario.Has anyone successfully presented a LUN from a Dell Unity array via Fibre Channel to either: Veeam Backup Appliance v13, or Veeam Hardened Repository (JeOS) with the intention of using that LUN as: a backup repository, or an additional backup disk for the repository? My main concern is related to the fact that both the Veeam Software Appliance and VHR (JeOS) are locked down by default for security and immutability purposes. I could not find clear documentation or a community thread that explicitly discusses: Whether FC-based block storage is supported in this scenario Any limitations or restrictions when attaching external SAN LUNs Potential security or immutability implications Required configuration steps (if supported) or reasons why it may not be recommended Most available documentation and examples focus on local disks or direct-attached storage,

Hi All,Can you backup normal vms in Red Hat Openshift with VBR or do you need to use Veeam Kasten?Thanks,Benny

we are veeamawsbackup                   7.1.0.8                                 amd64        Veeam Backup for AWS. we want to upgrade veeamaws 10. can some one please provide the procedure for the same.

A question came up during a recent customer demo of Veeam I was hosting == Is a snapshot enough for a backup or do you need an actual backup. My answer was you should have both. In this post, we'll break down exactly what snapshots and backups are, where each excels, where each fails, and how Veeam ties them together into a strategy that actually protects you. Some will say snapshots are good enough. Others will say they're a disaster waiting to happen. The truth, as usual, is somewhere in between — but with an important nuance: "snapshots and backups are not the same thing, and you need both."Misunderstanding the difference between these two technologies has led to real data loss events at real organizations. What is a Snapshot?A snapshot is a "point-in-time capture of a storage state". It records the state of a VM, volume, or dataset at a specific moment — not by copying all the data, but by tracking *what has changed* since the snapshot was taken.Most snapshots work using one of two

Special thanks to our dear Veeam Support Team Members Cosmin Ciobanu and Marius Nita for the following trick! Veeam Support is _always_ looking for ways to make everyone’s lives easier.Currently, to generate an HTML report for many sessions at once you need to go to the Session tab in the UI and ctrl / shift + click on desired sessions; not always convenient, and for Transaction Log backup sessions in particular you may have hundreds (if not thousands) of sessions.With Powershell and a bit of prep work, you can do this automagically: Preparatory Step:From a Windows-based backup server, copy the following filesCopyC:\Program Files\Veeam\Backup and Replication\Backup\SessionReport.xsltC:\Program Files\Veeam\Backup and Replication\Backup\SqlSessionReport.xsltto the following path on the machine where you will generate the report with Powershell:Windows:C:\Program Files\PowerShell\7\Linux:/opt/microsoft/powershell/7/Both xslt files should be in the powershell/7 directory. Then run the foll

Hi All,  Has anyone seen hotadd Linux (Rocky 9.7) VM proxies go sideways and not mount after upgrading to v13? I also added a new v13 appliance proxy and the result were the same. Changing transports to net work fine. On this client side logging it shows: Error: Access to [/dev/sdb] is denied.Failed to check whether access to path is grantedFailed to open disk for write.Failed to download disk 'snapshot-909174XXXX'. CC tenant job logging has: <842>    Info (3)    Skipping VcdDatastore (VcdRef=[urn:vcloud:datastore:GUIDXXXXXX], Name=[*CLIENT_DS*]) because it does not have valid underlying vCenter resources VCSA 8.3VCD 10.4xVBR 13Rocky 9.7 latest Kernel.  We have a Sev1 open but its currently pending logging reviews.  

Hello everyone,After upgrading Veeam Backup & Replication from version 12.3.2.4165 to 13.0.1.1071, we also upgraded Veeam Plug-In for Microsoft SQL Server using the ISO 13.0.1.1071, which installed Veeam Plug-In version 13.0.1.180.The upgrade process completed successfully without any visible errors.However, after the upgrade, SQL Server backups are no longer running successfully.All SQL backup jobs are now failing with the following error:Error: [Microsoft][ODBC Driver 17 for SQL Server] Database is invalid or cannot be accessed Before the upgrade, backups were working correctly with no issues.Has anyone experienced a similar issue after upgrading to Veeam 13?Any suggestions on what to check would be greatly appreciated.Thank you in advance for your help.

Hello everyone,I would like to get some advice regarding the optimal Veeam architecture for a two-site environment.Infrastructure Hyper-V environment Two locations: Vienna Novi Sad Sites connected with 1 Gbps IPSec tunnel Repository available in both locations Current components: Backup Server Hyper-V hosts acting as on-host proxies Repository Vienna Repository Novi Sad Current designRight now the backup jobs run like this:VMs from both locations → backup to Vienna repositoryThen we run Backup Copy jobs from:Vienna Repository → Novi Sad RepositoryThis means that VMs located in Novi Sad follow this path:Novi Sad VM → Vienna Repo → Backup Copy → Novi Sad RepoSo effectively the data crosses the WAN twice.ExampleVM located in Novi Sad: Backup goes NS → Vienna Backup Copy goes Vienna → NS ObservationDuring the first full backup we see relatively low throughput (~7 MB/s) and Veeam reports Network bottleneck.This is expected since the traffic goes through an IPSec tunne

Hello,I have to configure S3 Wasabi for the first time and I would like to be sure about the configuration.I will use it as backup copy repository with immutability.1) I create the bucket on Wasabi with versionning + object lock enabled2) I create a policy on Wasabi based on https://helpcenter.veeam.com/docs/backu ... positoriesI need the policy "Immutability Enabled and Helper Appliance Configured Beforehand" right ?How could I limit the policy only to the bucket "backupbucket" ? Because if I understand correctly, the policy in Veeam documentation has permission on all buckets.3) I create a new user and assign the policy4) I create the repository to veeam and set the desired immutability.I think I need some help on part 2 to be sure the user can only write to the "backupbucket".Thanks for your help

 Original post: Veeam Plug-in for HPE Morpheus VM Essentials Explained - CloudnRoll Veeam and HPE are further strengthening their partnership, with many new features and integrations expected in 2026.Veeam introduced a new native integration plug-in for HPE Morpheus VM Essentials (VME). It´s currently in beta version, with general availability anticipated shortly. This new plug-in provides hypervisor-based image-level backup for virtual machines (VMs) running on HPE Morpheus VM Essentials, ensuring secure and reliable protection for a wide range of workloads.Next, the architecture of the Veeam Plug-in for HPE Morpheus VM Essentials, the installation steps, and the backup/restore configuration process are presented.  Architecture The architecture of the Veeam plug-in for HPE Morpheus VM Essentials (VME), shown in the previous figure, consists of two key componentsThe plug-in module deploys natively on the Veeam Backup & Replication server without requiring a separate virtual applian

Trying to get Veeam Agent for Windows to run, installs without error using:VeeamAgentWindows_13.0.1.1009.exeI get the following error when trying to run anything…Could not load file or assembly 'System.Diagnostics.EventLog, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.I installed .net 8.0.24, here’s the list of runtimes…C:\>dotnet --list-runtimesMicrosoft.AspNetCore.App 8.0.24 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]Microsoft.NETCore.App 8.0.24 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]Microsoft.WindowsDesktop.App 8.0.24 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]After installing the runtimes, I’ve removed the agent software, rebooted, reinstalled but the same issue continues.Anybody have any ideas?

Hi,Do we need to open ports manually on every vm acting as backup proxy,gateway server,mount server vm for dell dd(backup repository) and vbr server when these vms are in vcenter added in vbr infrastruxture along with other vms who will be backed up.customer has fortinet firewall installed in their environment.they have to use dell dd for backup jobs and tape for archiving.

Hello,Using Veeam 365 community edition, backing up our Sharepoint site always end with warnings of: Processing site: https://**********.**** completed with warning: Failed to backup item version: /********/********/********/.****, version: 2.0, Download timeout exceeded (last error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..). All retry attempts failed. Re-run the backup job to proceed. Total count of failed items: 17The file it stops on changes each time and the number of files, still backs up most data but it is never fully successful. We have 20 backup applications, the backup is running and downloading data but it’s average processing rate is only around 500kbpsAnyone else seen this, what other logs to check in Veeam or Office 365 or a fix? Running version 8.3.0.2201 P20251212 

Running Veeam agent for Linux, v. 6.3.2.1207_x86_64. OS is Mint MATE 22.  Been making weekly backups for a year or more, just now trying a test recovery on spare computer- loaded some files, ran b/u to ext. drive, deleted files.  Have Recovery Media on stick, using steps in user guide.  All good thru several menus until “Mount Local Disc” which brings up a menu “Select Local Disc” but there are no items from which to select.  Backup drive lights up, so recognized by system.  What am I missing?  

As we know VMCE will be retired and VMCA was retired, so anyone know what the new certication path now?

Hi teamCan someone shed some light on this and how best to go about it.We have Nutanix cluster A and Nutanix cluster B.VM have been moved from cluster A with Nutanix Move, which creates a new VM on cluster B and syncs data. My guess is that it creates a new UUIDThere is an existing backup to a Wasabi Repo from cluster A.How can I re-create/re-point the backups that are on the repo so that the copied VM on cluster B can continue to use the backups already there?I am not so sure if there is a remap function for this. I also cannot add vm from the new cluster to the existing job as it only allows me to select existing one. It appears that you select cluster first when creating the job.My guess is I may have to create a new job and let old one age out?

I have company policy to not use port 80 and i can see Veeam GatewayAPI was listen on port 80.Can we change this port?