Unable to delete VEEAM from registry at all

Hi @itsupportarmt -

Are you able to reinstall your server OS then reattempt the new install?

I have this idea. But im also cautious that it shouldn’t destroy my creation of those directories. Or should I move to another backup solution?

And, if you have this installed on A Domain Controller server, Veeam really advises against installing on those.

Yes, reinstalling your OS would wipe your AD data if this is your only DC. 

Shall I try AOMEI Backupper?, if im unable to install Veeam B&R

Definitely installing on a DC is not recommended but in this case you may need to play with the registry permissions to get the delete to work.  Suggest a backup first.

As others have mentioned, if this deployment was on a DC, I’d recommend against this.  Like nearly all applications, the best configuration is going to be one role per server.  I’d recommend Veeam be installed on a separate server that is not holding any other roles such as Active Directory.  Not only is this for simplicity and to prevent conflicts between applications, but also from a security perspective.

To answer you question, if this is a standalone server with no other roles, then rebuilding the server is mostly trivial.  Placing the server back in the same OU would apply the same GPO’s.  HOWEVER….

It is not recommended to have a VBR server on your domain.  It is not required, and in the event of a breach of the domain, your backup server which would be almost certainly your last resort against recovering from malware, etc, would now be accessible to the bad actors/malware and backup data could be affected.  I’d highly recommend installing Veeam on a separate server, physical if possible (to prevent console access or encryption of the backup VM in the event of a hypervisor breach), and containing only Veeam roles.

Also, you’ve mentioned a few times changing to another backup product.  Obviously, that’s your prerogative, but you’re going to have a hard time finding a group of Veeam employees, technologists, fans and users recommend moving to another product.  We tend to work through the issues and set up what most of us will consider the best tool for the job rather than hopscotch around between products because of a roadblock encountered that should be able to be resolved.  Consider working through the problem encountered as an opportunity to learn more about the product, and maybe more about the process of troubleshooting in general.  In my opinion, hopping around the issue to something else without putting full effort into troubleshooting the issue, while possibly easier in the sort term, prevents that opportunity to learn and grow your skillset and knowledge.  But as I said, that choice is indeed yours.

Dear @chi-ltd @dloseke @liyakat_versatile ,

Hope you are doing well.

Yes this was a mistake I did. I am terribly sorry for that.

At first the IT vendor installed Windows Server 2016 in it and updated it to Windows Server 2019 Standard with activation.

Then I was usually performing the backups with “WINDOWS SERVER BACKUP”. One day I tried to install WINDOWS UPDATE SERVICES and Uninstalled it later.

After this uninstallation the windows server backup was showing in the system but if I open it shows windows server backup not installed in this computer.

So what I did?, I went to veeam backup and replication. For almost 1.5 years no problem at all, until I found out that veeam backup was generating lot of log txts in the sql server folder. 

But then I resolved it with an automated .bat file to remove the logs.

Recently the update 12.1 message came up so when I downloaded the ISO and tried to install these errors started popping up. 

Reinstalling the OS may fix the issue completely. I have updated active directory backup also. But Im afraid that the machine may lose the activation license.

Now I have installed the veeam B&R in another PC which is not a DC. Now all the tasks are fine except one error popping up in the task report that unable to write meta data.

I tested this backup and the restore was fine. But why this meta data comes I dont know.

Now two things I have in mind troubling. One is the inability to remove the registry entry in DC and the other is this meta data error in my PC veeam B&R

@itsupportarmt - have you tried to contact Veeam Support? They are really best suited to help you.

Yes they will respond just not as quick as standard support.

Dear @coolsport00 @Chris.Childerhose ,

I will definitely give it a try.

Let us know what happens and if you get it resolved.