Discussion Boards

Hey folks,I work for a Veeam Reseller/MSP and have a quick question about per-VM backup chains.We have a tenant who's switching their local backups from legacy to per-VM format. On our end, all of our Cloud Connect repos are already set up for per-VM.Once they make the switch locally, will their backup copy jobs to us just keep going with incrementals since our side is already per-VM? Or will this trigger a new full backup on the service provider side?Ideally, we’re hoping the chain just continues without needing a new full. Just wanted to check if anyone’s been through this and can confirm.Thanks!

Hi Everyone, Last week at VeeamON I was asking people about SIEMS, if they are using them and if so which ones?I got a myriad of answers. So I wanted to put up a poll here asking if you use and which one?  

Hello everybody,I could not find any Solution in VEEAM Backup and Replication Console, neither searching on the Internet.But I want to request a Feature, so we are able to create Folders in the Backup-Job-View to organzie Backup-Jobs. For example:Daily Jobs SQL Jobsetc.Thanks in advance.

When running multiple backups at the same time backups fail with this error stack. How can I solve this? RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 05/06/2025 22:46:41ORA-27191: sbtinfo2 returned errorAdditional information: 3475ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Broken pipe--tr:Cannot write data to the socket. Data size: [18636].--tr:Failed to write data into throttled device.--tr:Failed to asynchronously execute command [plugin.findRMANBackupFilesForSbtInfo] on backup server [xxx.xx.x.xx:10006].--tr:Cannot find RMAN bac

Hi,I’m using VBR 12.3.1.1139 and have already successfully migrated the configuration database to a local PostgreSQL server (which was installed during the VBR update/setup).Now I’d like to move from the local db server to a centralized one. Therefore I started the configuration “Restore” process and again chose”migrate”. Typed in hostname, database name, name and password of native authorization. But when clickin on “connect”, I get a dialog (from the db server?) that the connection is refused, the phrase is “no pg_hpa.conf entry for host <hhhh>, user <uuuu>, database <dddd>, SSL off”The problem seems to be “...database <dddd>...” whereas <dddd> is NOT what I entered into the migration dialog under “database name”. The centralized pg server only permits a certain database for each of their users.Our pg server tells me that VBR wants to connect to <dddd> where <dddd> is in fact the name of the user VBR is running with!? e.g. “BCKSRV2\horst”.Thi

Team,My SAP HANA DB are failing with below error. VEEAM Ver 12 hdbsql error: * 447: backup could not be completed: [110512] Backint reported 'BACKINT backup job into /usr/sap/KSD/SYS/global/hdb/backint/SYSTEMDB/COMPLETE_DATA_BACKUP_databackup_0_1 failed with error code ERROR' in file '/var/tmp/hdbbackint_KSD.wI4S0A', [110203] Not all data could be written: Expected 4096 but transferred 0 SQLSTATE: HY000 Your support is highly appreciated

Hi all,I have a feature request: can it be made possible to offload backups of Azure SQL databases created with Veeam for Microsoft Azure from VBR to Wasabi or other object storage using a copy job?At the moment this is possible for Azure VM's of which backups are made on blob storage. For Azure SQL it is only possible to make backups on blob storage so there is actually no offsite backup possible… 

Hello I am running into this issue; any idea what could  caused it  

I’ve got an Ubuntu 24.04 VM running in Proxmox VE which is backed up using Backup & Recovery Community edition.  The VM failed recently and I restored the VM back to Proxmox VE, but it just boots to Grub recovery. From what I understand, the problem is the VM is encrypted with LUKS which is transparent to Veeam.  I’ve read a few posts and guides on getting this to work, but I’m not having any luck.  I’m able to decrypt and mount the volume in a live environment, but I cannot get it to permanently mount in order to boot. Is there anything special that needs to be done for encrypted Ubuntu VMs in Proxmox or any guide for restoring LUKS VMs? 

I have moved VBR 12.3 to a Hyper-V VM as recommended. I would like to continue to use a set of USB drives for the backup copies. Is this possible?

Does anyone have recommendations for time settings on a Veeam hardened repo?  After researching, I’m seeing conflicting recommendations from use the internal CMOS clock, use an internal NTP server, or use an external NTP server.  Just wanted to see what some of the Veeam experts recommend.

As of the 27th March we have seen a significant increase in incremental backup size for our Microsoft 365 backup… Peaking at 800GB+ on the 31st! We have different jobs configured for different sources, for example we have separate jobs for:User Mailboxes Shared Mailboxes SharePoint Sites OneDrive SitesLooking at the size of each backup job, I think the increase in backup size is primarily due to the user mailbox jobs; the other jobs look ‘normal’ in terms of their size. Is anyone else seeing a sudden increase in backup size in the last couple of weeks?  Does anyone have any tips for pinpointing where the increase is coming from? 

Products:Veeam B&R Community Edition 12.3.1.1139 (Windows Server 2022) Windows Agent 6.3.1.1074 (Windows 11 Pro for Workstations, version 24H2)Using B&R Console I accidentally uninstalled CBT Driver from the Windows 11 PC, and now I cannot reinstall it anymore.The CBT driver is also missing from installed Windows apps and program list in the legacy Control panel.I tried to uninstall completely all components on that client, I removed it from my B&R Protection group, restarted it many times, but no avail.I also tried to install the standalone Agent, but the CBT driver install/uninstall option is missing from settings.Even command line method fails:Veeam.Agent.Configurator.exe -uninstallCBTDriverExitCode: 0Veeam.Agent.Configurator.exe -installCBTDriverExitCode: 20Errors:Failed to perform the operation.File existsThe only way I haven't tried yet is with command line by booting the PC from Veeam Recovery Media.In attachment: log file.Any ideas on how to solve?BTW, I’m wondering

Following on from my previous post, I am now in a pickle because after uninstalling a failed install of VBR 12.3 and reinstalling 12.1 the system is incapable of backing up my VMs. Need to completely uninstall all 12.1 stuff and do a clean install and forget about importing the config. Stay tuned.

Hello,When we have rental license how we can calculate how many VM can be protected by the available license?  

Someone on the Community reported the error of this post - “All backup proxies are offline or outdated” here -https://community.veeam.com/topic/show?tid=6645&fid=66I ran in to this issue in my HomeLab and opened a ticket with Veeam Support about it.  I was able to figure out the issue myself and wanted to post the fix steps here so that if you run in to this issue you can take the steps needed to address it yourself.This error does not seem to report anything in the log files which was the first thing I checked.  So, the steps to fix it are as follows -Remove the Proxy from the Veeam console using Delete. Remove the server from Managed Servers section - this will uninstall the components from the server. Log in to the Proxy server to ensure all components for Veeam are gone - if not remove them in the Control Panel Reboot the Proxy server Add the server back in to the Veeam Console as a Proxy server which will reinstall the components again. Validate your failed jobs by running the

Hi everyone, I have again encountered a problem related to backup using veeam backup, the error message is below.“Processing VM Linux Error: An error occurred while saving the snapshot: Too many levels of redo logs. (An error occurred while saving the snapshot: Too many levels of redo logs., An error occurred while taking a snapshot: Too many levels of redo logs.)Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef 11, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce FalseError: An error occurred while saving the snapshot: Too many levels of redo logs. (An error occurred while saving the snapshot: Too many levels of redo logs., An error occurred while taking a snapshot: Too many levels of redo logs.)” Detail diskVM Disk : 1 TBDatastore Free : 300 GB I really appreciate the advice given.. 

Dears, Greetings,I got an issue in my server as i am adding the machines as physical infrastructure.the issue is the job stuck at phase of storage initialized  then it fails after a while for windows with given error: and for linux machine it fails quickly with error  the thing is the network is fine and the connection to the NAS storage also so could you please help me in this error?Thanks,

Dear All,Let me ask for advice regarding the significant difference between the backup size and the repository size, which is causing inefficient storage usage and making it seem like deletions are not working properly. Below is my configuration: Source Backup: vMWare vCenter Destination Repository: Cloudian Object Storage Backup Frequency: Once per day Full Backup: Once per week Rettention: 7 Days Immutability: 5 days + 0 days (I modified the registry to set block generation to 0 days Capture:Rettention Policy (Job Configuration)Immutability (Repository Configuration)Results:Backup Size 5,20 TBRepository Size 15,6 TB My Opinion:Could the deletion be failing because the data is still locked by immutability at the time of the deletion? If so, what would be the correct configuration to avoid this issue? Could it be due to a failed checkpoint removal, as shown below:    Thank you for your attention. I truly appreciate your suggestions and assistance. 

 I currently have three separate data centers (DCs), each with its own Linux Proxy Server and Backup Repository. A single Veeam Backup & Replication (B&R) server, located in a fourth data center, manages all backup jobs across the three DCs.If this central Veeam B&R server becomes unavailable, all backup jobs across the environment would fail. To eliminate this single point of failure, I’m planning to deploy a dedicated Veeam B&R server in each data center. This way, each site will operate independently with its own Veeam B&R Server, Linux Proxy, and Backup Repository.  What is the recommended approach for implementing this setup? Will additional Veeam licenses be required for running multiple B&R servers? Once implemented, how can I migrate existing backup jobs and managed hosts from the central Veeam server to the new local Veeam servers in each data center? What is the other option for High Availability in this scenario ?

My HelpDesk staff is in charge of removing tapes from our library. I have a Powershell script that emails them the tapes to be removed. They don’t have the Veeam B&R Console installed on their workstations. But they do have access to Enterprise Manager, from a web browser. Is there a way to export tapes from Enterprise Manager? I don’t see one. And since this is all they do with Veeam, installing the whole console is kind of overkill for them. Right now, they’re logging directly onto the B&R server itself, to do this. And I’d really like them to not log onto a server directly.

The install drive for Veeam B&R has 7.3 GB free space and there is nothing left that I can do to recover or extend the partition. I was wondering if I uninstall 12.1 would there be enough disk space to then install 12.3? I am running Community edition.

My understanding it that the best practice is to run Veeam B&R on a stand alone server, not domain joined.  It should have rdp disabled.  Veeam console should be installed on another server.  Our B&R server is domain joined.  I haven’t found any documentation on doing this type of migration.  The processes run under the local system account.  The credentials for things like vmware and storage arrays are stored in Veeam.  What am I missing that would blow up when doing this migration?  I would like to move it to a new server, not just remove the current one from the domain.  Our repository servers are windows and domain joined as well.  Should they be removed from the domain?  Seems like yes and that might be biggest issue.  Any insights appreciated.