VeeamON 2025 San Diego, California
Join discussions around Veeam community projects, Veeam events, industry and technology news
Recently active
I upgraded from 12.0 to 12.3.0.310. No other change.VBR runs fine, but now I cannot logon from my local console using the machine’s domain name; i can, however, using its IP address.I’ve tried:Remove the VBR server machine from the domain, then rejoin it - no change Ping the server with success NsLookup the server name with success Flush the DNS with IpConfig - no change Tried to rerun the VBR installer, but it can’t repair, only suggests to remove(!) VBRNothing about this in the release notes.Anything else to attempt? Or, has some bug been introduced with VBR 12.3 or its installer?
I have more than 2000 Entra ID users but only have 900 M365 subscription licenses.When we setting the VDC to backup all tenant, will the VDC only take any user who have active license in M365?
We have B&R 12.3 running on a physical Windows 10 Pro system. Does anyone have experience with an inplace upgrade to Windows 11 in relation to B&R. Should B&R be uninstalled beforehand?
I am currently trying to backup 2 physical servers with Veeam.The target servers are running RHEL 6.6 (2.6.32-504.1.3.el6.x86_64).When I try to include them in a Protection Group to create a backup job, I am encountering an issue where one server succeeds and the other fails.In the Veeam Console UI, it shows up as failed with the message "The server has closed the connection." When checking the log related to the Rescan Task, the main error message is "Failed to upload package file from "D:\veeam\Backup\Packages\veeamdeployment-12.2.0.334-1.x86_64.rpm" to "/tmp/veeamdeployment-12.2.0.334-1.x86_64.rpm". Timeout: 10800 sec, mode: 644 (Veeam.Backup.Common.CRegeneratedTraceException)".It seems unrelated to the fact that the file upload to the server is not possible.This is because the situation is as follows:- Use root account when backing up Veeam- Veeam backup server and backup target server are located on the same network- SELinux and firewall are both disabled on the target server- No
Dear Expert!I need your assistance with the Veeam Backup issue. I tried numerous times to resolve this issue, but none of my ideas appear to be effective. Could you please provide any suggestions for resolving this problem?Error Message: Unexpected packet type: [%1]. Unable to retrieve next block transmission command. Number of already processed blocks: [997]. Failed to download disk. read: An existing connection was forcibly closed by the remote host Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.Thank you for help!!
I’m using the Veeam Agent for Windows (Free Edition) and 6.3.0.177. My primary drive is a 4TB NVMe SSD (NTFS / backup source) and my backup drive is a 4TB USB 3.0 SSD (ReFS / backup target).For a long time now I see performance issues with backups. My first thread about this wasSince then, I replaced my external USB drive (backup target) three times. I initially had a 1TB WD HDD, replaced it first with the same drive (guarantee/RMA), then with a different 1TB WD HDD and eventually moved to a 4TB SSD.From experienced I noticed three things:The drives became slower with time. With time the backup size increased and formatting or replacing the drive seemed to solve the problem, but the issue would eventually return. I suspected that the performance degradation was due to SMR, so I eventually switched from a HDD to a SSD. The SSD proved very fast read and write speeds, but soon I experience the same performance issues -- even worse. The issue started after adding a bunch of additional dat
I try to restore my bare metal server using veeam recovery media to VMware esxi.When i try to restore i got warning ‘OS disk in backup uses MBR disk’, then i check the created VM using EFI.I try change from EFI to BIOS then do same thing, then the recovery media say different warning. The waring now say ‘OS disk in backup use GPT disk.So why with same backup file, the warning message is different?
Over the years we have encountered lots of situations where other engineers disable a job with the intention of returning later of after a day or so to enable the job, but this never happens.There are 100+ reasons to disable a job but lots of times, a job is disabled with the intention of enabling it shortly after. We just do not have the correct option to use.It would be nice if instead of disabling a job we had the option to PAUSE FOR 30m, 60m, 90m, 1day, 2days, 1week, custom length. -MarioPS. No need to expand on what happens when disaster hits and a job had been disabled weeks ago…
Hi Veeam community, is it possible to backup AWS Storage Gateway Volume Gateway EBS volumes using Veeam for AWS 8.0 or Veeam BR 12 or any Veeam product for that matter?
i am trying free tier of Veeam, Proxmox and AWSI have a Proxmox VE community edition installed on an old PC 5TB Hard drive, I would like to try to backup a ec2 instance from AWS Free tier and store all data to my Proxmox, Veam VM is installed in my proxmoxis this possible 100% no cost ?any document, links or suggestion for me to test this situation is appreciated.
Is it possible using Veeam to create a bootable clone of a system disk to a second local drive? I don’t want to have to use recovery media to restore the OS.I have a server with two physical spinning disks that are not RAIDed (can’t rebuild the server to do this) so I want to create a bootable clone. There are numerous free tools out there, but as we already use Veeam I thought I’d find out if it can do this first. Thanks
When we add user from Entra ID, how long this user will be shown in VDC?I try add new created uses on Entra ID as VDC admin user but even wait more than 10 minutes, the new user still not showing.
Dear Community, Anyone face this issue if yes kindly guide how to fix this. Failed to upgrade host components. Error: 'Exception of type 'Veeam.Backup.Common.CAppException' was thrown.'
Trying to upgrade Veeam from 12.0 to 12.1, and the original installer has left. How would we reset the credentials so we can perform the update? We thought our service account was used but apparently not. All attempts to update have failed so far. Part of the issue is most NASA accounts require PIV card authentication, and I don’t know if that plays well with a Veeam update. The service account is PIV exempt. The current version is pushing an old version of the kmod veeamsnap that won’t work with the current RH kernel. Why don’t we just rebuild the kmod in the fly every time a new kernel arrives like other kmods seem to work? Like CUDA for example.
Hello guy,When i use veeam backup & replication 12 has error Selected server is unavailable.How do i fix it ?Thank you
Hi, I’m planning to upgrade VBR towards 12.3 and facing an issue regarding Failed to stop service ‘VeeamRESTSvc'. with the below commands i try to stop the service get-service veeambackuprestsvc | stop-service -force But it not impact on VBR server as well. All services are stopped but not impact did any one face this issue during upgrade?
