Ok, I had a test server which I used to test out Windows Agent backups.I’ve now built a more robust server to handle veeam (community edition as we only have a few servers), when I try to backup the same server, I get:I’ve removed the backup jobs, and uninstalled the agent both using the old server and manually going into Add/Remove programs, yet the same problem exists. I’ve also added the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication AgentDiscoveryIgnoreOwnership DWORD=1Still no joy. When I go into the registry editor on the machine in question, I can see why Veeam is having a problem. The values in BackupServerIPAddress, JobSettings, and VBRServerName are all pointing to the wrong server. I’m loathed to start deleting this key. What do I do to ensure this server I wish to backup now has the correct agent installed?RegardsIan
Hallo Zusammen, wir haben für unsere internen Dienste einen kleinen Mail-Server installiert, welcher seine SSL/TLS Zertifikat via Lets-Encrypt bezieht. Auch Veeam B&R versendet darüber seine Benachrichtigungen, wenn man dem “untrusted certificate” vertraut. Da sich die Zertifikate bekanntlich alle 3 Monate erneuern, ist die Fehlermeldung natürlich nicht so gut.Kennt das Problem jemand und wie wurde es gelöst? Vielen Danke
Hi, I created new jobs to organize Exchange groups and Teams groups since my company was previosly configured to backup the whole organization, Now that the backup is set up and backing up for about a month is time to disable the original job, if I disable and delete the job, would that release the previously used licenses for any aditional user that is not on the new jobs ? Thanks in advance.
Just a quick question...I was tasked with restoring OneDrive data from an account for a client that apparently left and the user was deleted, but someone else was accessing the OneDrive data while the user account was still in the Deleted Users status/folder, but once the 30 days elapsed, that data was purged. This client is currently being backed up by Barracuda Cloud-to-Cloud backup (until I get those folks moved over to Veeam) but I noticed that the last backup of the data was before the user account was deleted. Makes sense, but I hadn’t considered that their OneDrive would even be accessible by the other users during that time period if the user/mailbox had been marked as deleted.So my question is, if a user account is marked deleted, does VB365 still backup the deleted mailbox/OneDrive (or can it even do so - assuming that you had that user explicitly specified or had the job set to backup the entire organization, etc) until Microsoft purges that data? I imagine I can test thi
Hi, I have a client that wants to back-up his S3 buckets. Everything I can find talks about backing up to S3 which is great but not what he wants. He has a DR policy that states that he has to have a copy of his cloud files on prem. I’ve gone through the AWS module for Veeam from top to bottom, but I can’t find a solution. I was hoping that EFS would work but it does not.
A new vulnerability in PostgreSQL was published today - CVE-2023-39418https://www.postgresql.org/support/security/CVE-2023-39418/All versions < 15.4 are affected. Version 15.4 was published at August 8th 2023.https://www.postgresql.org/about/news/postgresql-154-149-1312-1216-1121-and-postgresql-16-beta-3-released-2689/ Does Veeam advise to update PostgreSQL on VBR servers to version 15.4?
Hi folks,My wanderings in the wonderful continue. I need to move an M365 repo from a REFS drive (as far as I know this is not good, NTFS is the best practice) to a new drive. I have read on the forums that the Move-VBOEntityData powershell is NOT the way to go. Instead this is the procedure: 1. Disable all backup jobs related to the repository you want to move.2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).4. Start the Veeam Backup for Microsoft Office 365 services.5. Add the new repository with the moved data.6. Open backup job settings and specify to use the new repository Any comments or advice from folks who have been through this. I would like to avoid any pain since I had a wisdom tooth pulled this week and have enough already :) cheers
we currently use azure as object storage and would like to achieve immutability on the backups.veeam does not support “out of the box” immutability to azure. i would like to know if any of these would work or if anyone has better ideas.Immutable blob storage on folder level Enable soft delete for blobs (or container) Enable versioning for blobs (or container) Enable point-in-time restore for containers setup Object replication in azure for the storage account thanks
VBR v12 RTM removed " Install a new instance" selection from Installation setup with the Microsoft SQL Server, bug or normal?
I noticed VBR v12 RTM removed the " Install a new instance" selection from the Installation setup with the Microsoft SQL Server.An error message will pop up if the Microsoft SQL Server or Microsoft SQL Server Express does not install locally or remotely.That means I need to install Microsoft SQL or SQL express before installing Veeam Backup and Replication manager server (I knew v12 supports PostgreSQL) if I would like to work with Microsoft SQL? or is it a bug?
Hi Folks, First off don’t ask 😁 “why do you want to do this” :), I don’t but I have no choice as the customer is going to do this and I can’t convince them otherwise. However, they are asking about consequences :(, So a customer has an M365 multitenant backup. They want to rename the server and give it a new IP. The proxies and repositories will remain the same.They are not leveraging S3 only old style repos and they have no portal my understanding is that there is no database that has recorded the console’s hostname and IP (unlike VBR) so changing the name and IP should not have any affect (only perhaps firewall stuff if they have any rules tied to the old IP).Is this correct? Thanks
Hi all,I have 2 Backup Servers (Veeam B&R v11) running independently from each other with 2 licenses (16 Sockets CPU and 24 Sockets CPU). My goal is that both Backup Servers can backup from disk -> disk(HPE StorgeOne 5200) -> Tape (HPE MSL 3040). I have some questions as follows:- Is it possible to add 1 Window Server (Use it as Tape Server) to 2 Veeam Backup Server?- Can use 2 Window Server (Use it as Tape Server) to manage 1 Tape Library (HPE MSL 3040)? If so, what needs to be done?- Is it possible to add 2 licenses to 1 Backup Server to increase the number of CPU Sockets to 40?Thanks
Veeam Backup for Microsoft 365 proxy disconnects and proxy Windows service dies on every backup. Anyone else seen this?
I had M365 backups working flawlessly and then needed to switch repositories. Somewhere in there, something broke. So I ended up removing the repo, removing Veeam M365 backup, cleaning up all app residue and re-installing from scratch, since this was a new, small instance and I just wanted it to be clean.Now, every time I try to run a backup against the same recreated Org, the job will connect to the org, start resolving the objects, it finds the objects to backup but never actually receives any data. Shortly thereafter (30 seconds or so), the proxy service crashes and the portal shows status “disconnected” and Details “Job was interrupted”.I have even tried putting it on a different VM and the same behavior persists. The only element that I haven’t recreated is the O365 implementation. I have also recreated the Azure apps/certs each time as well.The logs don’t seem to show much. Below is the end of the latest log as well as the console view and some event logs. I am kind of at a loss
Any idea for this? It’s pure Hyper-V with Azure, not AWS. 1/31/2023 10:06:49 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://vbr11:9402/api/v1/account/login' is not supported.
Hi Folks, I am back into the wild and wonderful world of Veeam Service Provider Console after a brief sojourn. I wanted to see if there is a quick answer to this and if my old solution perhaps has a better one now.I have a VBR that is connected to the Service Provider and all backup copy jobs are working fine. In VSPC the company is smiling with a happy green Healthy! However, at the VBR level the when pressing the Management Agent icon it complains that is connecting, and can’t connect after rolling through all the gateways. I tried running through the SP properties again but no luck. Is it time to un-install the pesky agent and redeploy? The ClientAgent_error, Communication and ClientAgent logs have things like CloudGate “No such host is known” and “Endpoint Hanshake Failed” and The write operation failed, see inner exception. ---> System.TimeoutException: Could not finish read operation in timely manner.Now could this be that if they have running backups and have used up the Tena
In an agent job for a WSFC (fileserver role) we see a warning after having switched over to the secondary node. Each job run now finishes with a warning that CBT table has changed.As with VM backups I expected the warning to disappear in the next cycle - but it didn’t. How can I reset the CBT for an agent backup (not hypervisor based CBT but Veeam CBT driver here)?
Trying to migrate Enterprise Manager to a new Server. I stopped the Veeam services on the old server and disconnected it from the network. I installed the EM on the new server and pointed it to an old DB that was used by the old server. There was a dialogue window confirming that the DB was owned by the old EM server and that it would be transferred to the new EM server.What happened next is that the the service account was getting locked out. So I had to roll back the changes. Good thing, I did not uninstall the EM from the old server per the instruction on https://www.veeam.com/kb1889 . Curious what happened here.
Hi,I have a successfull running backup job of 10 vm (which is the limit). I recently moved that vm to another server/datastore and the backup job claimed that this machine wasn’t found the following evening.To correct that problem, I edited the job, removing that vm and re-adding it to the job.Since that time the backup job report that I exceeded the maximum, which is not true!Is that someone can help me with that please? Denis GravelCEGEP de Thetford
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.