Discussion Boards

I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.

Hello,Yesterday I had to re-install Veeam Backup for Microsoft 365.  I now lost my ability to restore from previous backups.  When I try to do a test restore, I can only choose backups from yesterday.  Is there a way to fix this?

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:

Hello Expert,I am looking for advice on the best way to protect our Veeam VBR/DB. Our environment is currently set up as follows:Veeam VBR Server: Running as a VM on VMware.Database Server: Running as a separate, dedicated VM (MS SQL).Current Backup: We are currently including both the VBR VM and the DB VM in a standard VMware snapshot-based backup job.Is this considered a "good" or "supported" configuration? I am concerned about:Stun/Freeze: Will the VMware snapshot "stun" cause the VBR server to lose its connection to the remote database during jobs?Consistency: Does a standard VM backup ensure the VBR server and the separate DB VM stay in sync if a restore is needed?Circular Dependency: If our VMware cluster goes down, we lose our backup server.Should I exclude these VMs from our regular backup jobs and rely solely on the Configuration Backup tool, or is there a benefit to using Veeam Agent for these specific servers

After moving from v12 to v13 we have started seeing:Backup copy RPO violation: [server] was not copied within 165 days 23 hours 6 minutesThese seem to occur at semi-regular intervals to VM’s residing on a Proxmox server, maybe every14 days. What is odd is regular backups and offsite copies run daily and without error, even these jobsreporting RPO violations. Just in case, when these errors popup we run an active full and a copy. Werun tests to ensure they are working and can be restored.Any ideas why the error is occurring?

Hello Expert, I am getting below error during windows agent backup. Basically job was in hung stat on VBR so i stopped the job and restarted the services on agent servers. we tried to recover the backup but its failed with error "Job unexpected failed" in error log i could see below error. These nodes backup was running fine since last few years. Since this node belongs to DB we cant reboot it. Any suggestion or guidance is highly appreciated.Info (3)    [RPC] RPC confirm session has been created. Id: {7a87b}Info (3)    [RPC] Destroying RPC confirm session. Id: {7a87b}Info (3)    [RPC] RPC confirm session has been created. Id: {52fb05}Info (3)    [RPC] Destroying RPC confirm session. Id: {52fb05}Info (3)    [RPC] RPC confirm session has been created. Id: {898fab}Info (3)    [RPC] RPC confirm session has been created. Id: {0fc04}Info (3)    [RPC] Destroying RPC confirm session. Id: {0fc04}

I have A DC that is being backed up, the backups complete successfully, but when I try to test it with surebackup it errors out with “Results: unable to perform Domain Controller restore from a crash-consistent backup. Be sure application-aware processing is enabled in the backup job settings”For the backup job on the server I have “Enable Application Aware Processing” ticked under guest processing. Is there some place else I need to look? I’ve tried unchecking the application aware processing, saving the job, and the re-checking it and saving then re-running the backup, but the surebackup still fails with the same error message.   

Hello everyone,I would like to validate a design scenario in Veeam Backup & Replication.The customer wants the following backup architecture: A primary backup repository without immutability A secondary immutable repository in the same datacenter A third immutable repository in the DR site My first thought is to use: 1 primary backup job to the non-immutable repository 2 Backup Copy Jobs using that same primary backup as source: one Backup Copy Job to the local immutable repository one Backup Copy Job to the DR immutable repository My main question is whether this is the right and recommended approach in Veeam.More specifically, I would like to confirm: Is it supported and considered best practi

We  are  unable to access the Veeam Backup Enterprise Manager Web UI, receiving a "localhost refused to connect" error. Initial troubleshooting steps included checking firewall rules and verifying if port 9443 was listening, but the service was not running. We identified that the Veeam Backup Enterprise Manager service was not present or visible on the server.VBR ver is 12.3.2 localhost refused to connect.Try:Checking the connectionChecking the proxy and the firewallERR_CONNECTION_REFUSEDC:\Windows\system32>netsh advfirewall firewall add rule name="veeam.xy.com 9443" dir=in action=allow protocol=TCP localport=9443Ok. Veeam Backup Enterprise Manager' service does not appear in the services.msc. I just joined in the team and don’t know if previous engineer has done anything.EM is local as per logs.Integration] EnterpriseManager: { IsAddedToEM: True, IsEnterpriseManagerLocal: True } (ti

PS C:\Windows\system32> Get-Service -Name *Veeam* | Select Name, Status, StartType Name                       Status StartType----                       ------ ---------VeeamAHVSvc               Running AutomaticVeeamAWSSvc               Running AutomaticVeeamAzureSvc             Running AutomaticVeeamBackupCdpSvc         Stopped AutomaticVeeamBackupRESTSvc        Running AutomaticVeeamBackupSvc            Stopped AutomaticVeeamBackupUpdateSvc      Running AutomaticVeeamBrokerSvc            Stopped AutomaticVeeamCatalogSvc           Running AutomaticVeeamCloudSvc             Stopped AutomaticVeeamDataAnalyzerSvc      Stopped AutomaticVeeamDeploySvc            Running AutomaticVeeamDistributionSvc      Running AutomaticVeeamExplorersRecoverySvc Running AutomaticVeeamFilesysVssSvc        Ru

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.

I have backup job with forever forward incremenal and the retention set to 7 days.I also have backup copy to Azure Blob where immutable set to 30 days.When we use forever forward incremental then full backup will be merged with last increment, then how this work in immutable storage?If the immutable set to 30 days then full backup only for 1st day and rest 29 days is incremental and no full backup merged every day?

Here my configuration for azure blob where i set the immutable duration for 7 days. How we can make sure that we can’t delete any backup files inside this blob?I try connect to azure blob storage then upload new file and then i try to delete and i can deleted the file. Is the immutable not work since i can delete test file what i upload manually? 

Hi teamI was wondering if anyone has noticed some strange behavior when configuring network during ISO installer workflow?I have done two installs now. When I go into the network portion and I select the connection toggle, it stays in the connecting state and eventually disconnects.For one repo, one nic actually connected.From a switch perspective, all is up and connectedI made the changes as per documentationInstalling from Veeam Hardened Repository ISO - Veeam Backup & Replication User Guide for VMware vSphereFor the repo that manages to connect to one nic, I configured LACP as per document but only with one nic. This got the repo on the network and I manually added added the second nic the bond from the CLI.The second repo, in the netwo

Hi, I’m trying to use a Veeam proxy on a satellite location to backup local resources to a configured VDC Vault. It fails with the error:4/22/2026 9:32:28 AM Failed : Processing [server-to-backup] Error: NFC storage connection is unavailable. Storage: [stg:datastore-355002,nfchost:host-354978,conn:vcenter-fqdn]. Storage display name: [VUSA-VMFS02]. Failed to create NFC download stream. NFC path: [nfc://conn:vcenter-fqdn,nfchost:host-354978,stg:datastore-355002@server-to-backup/server-to-backup.vmx]. Agent failed to process method {Transfer.FileToText}.  (NFC storage connection is unavailable. Storage: [stg:datastore-355002,nfchost:host-354978,conn: vcenter-fqdn]. Storage display name: [SAN-storage].) (Failed to create NFC download stream. NFC path: [nfc://conn:vcsa.voortman.local,nfchost:host-354978,stg:datastore-355002@ server-to-backup/server-to-backup.vmx].) (Agent failed to process method {Transfer.FileToText}.) (0:08:25) I can, off

Hello Community, We have two DC’s and running Veeam 13 for Backup and Replication of VMware Virtual Infrastructure. In previous versions we have backup server VM running in the secondary DC and replicated to the primary DC. In case of loss of secondary DC, we can recover the VM on the Primary DC by simply powering it ON and then recovering any other VMs. However with Veeam 13 we have observed that the Veeam policy doe snot allow the Veeam Server to be replicated. What should be the recovery steps for the Veeam backup server (we have deployed the Veeam software appliance)?My thoughts:Deploy a new Veeam backup server appliance with same network IP as the previous server. Import the config backup Rescan all the backup components.Is this the right approach or should we deploy the server appliance with a different IP and import the previous backup config? BR,Sudhir 

Network Mapping in Veeam Orchestrator  Recover Locations can not be deleted.Checking if any of you guys have experience this. I can delete the network mappings. However if I go back, the network mappings reappear. The only way I can make the mappings go away is to delete the Recover Location and re-add the Recovery Location. Is this normal behavior on VRO v13? 

Hi, I’m considering supporting cross-platform recovery on a large production scale /w CC. I’m aware of the limitations presented with this. I’m really interested in hearing about experiences with recovering Prox backups into VM or Hyper-V and accounting for driver removal/install. What was your experience? Were you able to automate the workflow?  What was more problematic, Windows or Linux? What about boot loaders/Grub & Kernel drivers?  Thanks!

Please help, We are trying to backup large number of laptops, ± 400 using 1 proxy server to backup to S3 type of storage. We are experiencing performance issues. Laptops are using wi fi to connect to the cooperate network. We used a CSV file to configure protection group and our backup are scheduled during working hours. Please advise on the way forward for the best practice or recommendations. 

I have a migration from Veeam on Windows to Veeam on Linux, and I need to make sure there are no problems after the migration

I'm getting in my own way right now.I've set up an organization in Veeam M365. I want to edit it, but when I go to the connection settings, I'm asked for the application ID and a certificate.Which certificate should I select here? Veeam only suggests three options:1. Self-Service Patch Certificate2. Restful API3. (without friendly name) I didn’t have to specify a certificate during setup; I just followed the wizard.How can i choose the correct certificate?Maybe I'm just being stupid today. 

Hi since upgrading my PVe to version 9.1 and the VBR to 13, the backup performance have degraded a lot. We have 1 worker per pve host, storage is Ceph. Did someone encounter this issue?

Hi,I am going over DR scenarios and have a query on improving our procedure.We have two sitesPrimary site Hosts all production servers (5x physical & 30ish virtual) Hosts the VSA virtual server Primary & immutable storage repositories Secondary DR Site Off-site storage repository 2x spare physical servers for use in DR scenarioBoth sites connected via VPN. Everything on Hyper-V Now my query - lets say the primary site is destroyed. We want to restore everything to the secondary site.First step I can’t login to Veeam console because it was hosted in the primary site. Therefore current procedure is to setup a new instance of VSA and import a backup of the config. Not a difficult task but it takes time which I’d rather not have to spend during an emergency scenario.Is there a better way? Does it make sense to replicate our VSA virtual machine to the secondary site? Maybe hi

Are there anything besides the tape that need to be preserved before removing the old tape library? What are the steps to add the new tape library?https://helpcenter.veeam.com/docs/backup/vsphere/connecting_tape_devices.html?ver=120Following this the drive will automatically appear and how about the media? If the tapes are added to the tape library they will automatically appear in the media.Last step will be to create a Tape job