Discussion Boards

Hello,I have a very small environment consisting a of 1 Hyper-V server.  I have direct attached storage, a QNAP NAS with NFS & Object Store capabilities and a subscription with Wasabi.  Ideally I’d like to configure a backup which creates a copy on the direct attached storage, copy on the QNAP and a copy in Wasabi.  I’m seeking recommendation on how to configure the backup job.  So far I’ve created a SOBR consisting of the direct attached storage + QNAP.  I also have a Backup Copy job which uploads the SOBR to Wasabi but I’m not certain if any of this is a best practice.   The Backup Copy job is configured as a secondary location for the primary backup job.  Thanks

Hi all. I’ve got a Veeam backup & replication CE that backup some VM on VMware ESXi.This backups are copied offsite to another site using a IPSEC VPN, a proxy is placed on other site and storage is a NAS.At least once a week, randomly, backup copy job fail because can’t connect to Veeam proxy.At this this I’m using Linux as a proxy but also with Windows we’ve issue. What found in logs are this rows: [26.08.2024 08:31:56.875]    <24>   Error (3)    [ReconnectableSocket][PacketAsyncReceiver] Exception on [af09e7b0-f7ed-4e85-969f-96d3cff82943].[26.08.2024 08:31:56.875]    <24>   Error (3)    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond (System.Net.Sockets.SocketException)[26.08.2024 08:31:56.875]    <24>   Error (3)       at Veeam.Backup.Common.Reconnect.CPacketAsyncRe

Anyone had experience of using Veritas 5250/5x50 appliances with Veeam? I believe the appliances can support SMB/NFS so as long as that is available then yes….if anyone has any thoughts or experiences please let me know.

Hello together, I have the following Problem.I want to migrate a Workstation to am VM in Proxmox.I found the following Thread with nearly the same questionNow my Problem:When I start the VM it boots into the Veeam restore option but the Agent shows the Error “Failed to resolve ClientID. Machine doesn´t have identifiers”.Like in the Thread above I switched the VM-Bios from SeaBios to Uefi but then the VM doesn´t boot into Veeam.Is there a possibility to solve the Error Thank you for your help. Markus

Good day!Hi All, Experiencing this error after the successful created of the protection domain.after the rescan. got this error. 8/1/2024 2:33:59 PM Warning Failed to connect to 172.16.0.31 Details: Failed to call RPC function 'EpAgentCollectSystemInfo': Machine doesn't have identifiers.

Hi all,Anybody faced issues with the usage of certain TIERs from a SOBR on another VBR server ? Here’s what we want to achieve:Customer is upgrading to brand new VBR server (new hardware)Together with this shift, he want’s to move from S3 provider.All configured well, but what with the existing SOBR were we only want to keep the archive tier. Both Capacity and Archive tier are S3 compatible repo’s (encrypted). We just want to break up the SOBR and mount the S3 Archive tier to the new VBR and perfrom a rescan. All backup points should then be visible as ‘imported’ backups.This gives the customer the opportunity to keep the possibility to restore from his previous archive tier when necessary and get rid of the costly capacity tier. Any things we should keep in mind ? I guess a rescan of the repo will populate the internal DB with the necessary info to perform restores via the new VBR.   

Hello everyone,For those who don't know, I'm the creator of the website Ransomware.live, and I'm excited to share some major updates and improvements I've been working on over the past few months:  Major Code Overhaul: I’ve rewritten 80% of the code to enhance efficiency and performance. This should result in a smoother and faster experience for everyone using the platform. Integration of TTPs: I’ve integrated Tactics, Techniques, and Procedures (TTPs) from the Ransomware Tool Box, thanks to the valuable contributions from my friend Will. This addition provides more comprehensive insights into ransomware oper

I haven’t found an answer to this, so asking here.I was asked if we can change the retention on an existing backup to keep it longer than the original retention time.For example, we are running forward incrementals daily with a synthetic full every Saturday. The retention is set to 30 days. We are using Veeam 12.1 with immutable Linux repository.If someone comes to me and asks for us to keep last Wednesday’s backup for 90 days due to an ongoing project they have, can I retroactively change the retention on that backup to 90 days? (I understand that the prior Saturday-Wednesday files would/should also be retained to keep the chain intact).Thanks.

Hi guys,First, I’m not sure if I should be posting here or forums.veeam.com?  Either way, here’s my setup: Hyper-V host domain-joined to customer infrastructure, running Windows Server 2022, patched with July 2024 cumulative patches.  Security software includes S1, Threatlocker, and Huntress.  Threatlocker is in “learning” mode and is not blocking anything. Backup server is also running Windows Server 2022 patched with the latest July 2024 cumulative update.  Security software includes SentinelOne and Duo authentication to enable MFA for local user logins. Backup box is *not* domain joined at all.I’ve been told this is a UAC issue, but using a domain user bypasses this problem. I feel like I’m taking crazy pills. No matter what I do, I can’t get the backup server to authenticate with the Hyper-V host using a domain account.  I can get it to authenticate, browse \\hypervip\ADMIN$ share, and connect w

We have had an error message when backing up Office365 for 2 days  JetError -528, JET_errMissingLogFile, Current log file missingWe backup to a NASThe backup repository has the same error message, but the NAS is fully accessible and our normal Veeam Backup & Repository continues to back up to the same NASDoes anyone have an idea?

Hi,I try to add VBR server to Veeam EM, there is no problem. But sessions tab I see “Database Replication” failed.And the logs like that;“The SQL Server machine hosting the configuration database is currently unavailable. Possible reasons are a network connectivity issue, server reboot, heavy load or hot backup.Please try again later.Error:relation "licensing.cc.ınstancestobackupslinks" does not exist”VBR build is 12.1.0.2131, is not community license, and db is postgre.Thanks,  

Veeam to backup Openmediavault hostI try to backup with veeam my openmediavault host. It's installed barmetal.Downloaded and installed it with apt-get install veeam-nosnap. But if I try to backup my volume lvl, i get this error: Item nvme0n1 cannot be backed up without veeam snapshot kernel modul.Hiw I can get the modul?

So I am on Veeam community edition 11.01.1261 and decided to look into immutable backups. I created a Ubtunu 22.04.2 VM and followed the guide. I added the repo to Veeam. When I do a backup and check on the Linux system I am not seeing the immutable tag set, what am I missing? I’m looking in the data directory of the backupset. The backup is there, looks fine, it is not immutable.  lsattr---------------------- ./0000.vblob The Linux FS is XFS, and I set the checkbox to say it should be immutable for 7 days. 

Does anyone have the Lego build instructions from the July 18th build event?

How to deal with the situation where the tape name is mislabeled and does not match the actual tape sequence? Manually modifying and restoring the sequence recognized by the system, which is inconsistent with reality, is very troublesome

Host backup is a day backup, which runs a tape backup after the backup is completed; But today I found out that all the backup days of the tape were for the backup data on July 31st, but it prompted that the backup data did not exist. I don't know why the data on July 31st was backed up. I saw that the backup tape number on July 31st in the tape backup record is empty

Hello, How can I force VBAR to send email after the completion of a backup.As it is now, seems can only get a daily email?I have not yet tested, but not sure what VBAR does if a backup job fails?I checked the forum, veeam docs andhttps://helpcenter.veeam.com/docs/backup/powershell/email_notification_settings.html?ver=120

Hello, I’m new here, so forgive me if I’m doing this wrong.I’m having trouble configuring a SOBR to a client. The client wants to send an Agent File level backup job directly to S3 Standard on AWS and keep only the recent 7 days worth of data and then proceed to archive a weekly full backup. How would I go about and do this? There is no capacity tier as it would make no sense…    

Hi, we have TBs of data in our on-prem Veeam repositories that we would like to move to Azure (archive tier). We added object storage repo and choose Archive Tier but when we try to use copy /move data option to migrate off this data from our on-prem repos to this archive repo, this doesn't show up in the available target locations. We would like to get some advice on some of the available options that we can use to move our data to azure. We will hardly need this data to restore from but as a business requirement, we need to keep this for a few years. Thanks

Is anybody here having problems with Tape Library control through Veeam lately? I have jobs that have run for years and that even survived the V12 update a couple of weeks ago, but have now started throwing a fit every time a tape needs to be loaded/unloaded/inventoried etc. Every error is a variation of the “Failed to call RPC function” message, but with different specifics: LoadMediumByScsi, GetElementsStatusesByScsi etc. This only started on Friday, and is puzzling because it only affects our Dell ML3 (LTO6/LTO8) interchanger, but not the Dell TL2000 (LTO6).  I have tried the usual update of Firmware (Drives and Libraries, SCSI Controllers etc) to no avail. Removing and recreating the Library made little difference either (it loaded a tape ONCE then returned to the errors).  Rebooted the Backup Server AND the Library.  Has anyone dealt with this successfully or am I looking at new incident?

I have been looking at some information within the Veeam documentation, but it could not move forward due to some errors according to images. 

I’m sure I’m overlooking something obvious -- Veeam is running on a Windows 2022 server on the domain.When adding my non-domain Hyper-V host (Windows 2022) to the Veeam managed servers, the only credentials that work are hostname\administrator. Any other account on the Hyper-V host with full administrative rights is failing with --“Failed to connect to host XX.XX.XX.XXAccess denied or timeout expired.Check if you you have local administrator privileges on computer ‘XX.XX.XX.XX’.Possible reasons.1. Invalid credentials.2. Specified host is not a Hyper-V server.” I’d prefer to disable the .\administrator account on the Hyper-V host, so I’d love to know what I need to do to get my non .\administrator accounts working with Veeam. Thanks, Chris 

Hi, I have a backup copy job which runs forever. There are two VMs and I see the backup copy is backing up  the hard disk with no progress. How do I best troubleshoot it and I don’t see an option to cancel the job. I use VBR 12.1. I believe in earlier version it was possible to cancel a job. I use the immediate copy mode.Thanks,Edy 

Hello,I have 900 M365 users and now i communicate with our veeam partner to purchase VDC license.The vendor say we must make groups of our 900 users. Here i want to know it’s mandatory we should make some group for my 900 users? If yes, is there any best practice what kind of groups (should i make group by internal department or by any object will be backup)?

After doing a cold boot of the host server, the Veeam backup service has failed to run or come back online. When trying to connect through the client we receive the error message of “No connection could be made because the target machine actively refused it 127.0.0.1:9392”After checking the logs, we’ve found an error stating that it failed to fetch logical page (1:21805) in database 5 failed. It belongs to allocation unit 72057594191544320 not to 72057594190823424