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.
Page 1 / 1
Was a service account used, or the default LOCAL\SYSTEM account?
And, I assume you’re attempting to upgrade Veeam Backup?...not VeeamONE or other product?
Was a service account used, or the default LOCAL\SYSTEM account?
And, I assume you’re attempting to upgrade Veeam Backup?...not VeeamONE or other product?
Yeah, that’s the point, I don’t know what was used. If his AD account, that account is dead, and will never authenticate. My admin level domain account fails. The service account fails. We even tried the local Administrator account that NASA renames.
Yes, Veeam Backup
What account is shown for the postgresql service? If it’s the account that you no longer have to reset the pwd for, I’d recommend getting ahold of Support to see if they can assist.
What account is shown for the postgresql service? If it’s the account that you no longer have to reset the pwd for, I’d recommend getting ahold of Support to see if they can assist.
If I check the Postgresql Service it says “Network Service” with the password field invisible dots under Log On.
Can I change the PostgreSQL account in Services without totally breaking Veeam?
I've not done that before. I recommend getting ahold of support to see what your options are.
I've not done that before. I recommend getting ahold of support to see what your options are.
Annoyingly, NASA buys through procurement to save a tax payer buck. But often that means no direct access to support. I didn’t buy it, so I don’t have a customer portal login for support. How NASA saves money is vendors don’t have to deal with thousands of individuals. Maybe Veeam is different, but I didn’t go through the purchase process. Not to mention Veeam just laid off 300 workers :-(
You should still be able to get support because they even offer support for the free Community Ed, albeit best effort. You should be able to create a Veeam account & log in. Use the product support ID in the license area of the VBR console when you create the case. Try that & see if you can get assistance.
When you go through the upgrade process, at what point are you getting stuck? What’s the exact step/error message?
When you go through the upgrade process, at what point are you getting stuck? What’s the exact step/error message?
After you are prompted to enter the PostgreSQL credentials. It inherits mine and fails.
When you go through the upgrade process, at what point are you getting stuck? What’s the exact step/error message?
After you are prompted to enter the PostgreSQL credentials. It inherits mine and fails.
This worked for me. My scenario was that I domain joined after initial deployment. I added a line to pg_ident.conf
veeam eUSER]@[domain] postgres
Hi @mntbighker - I’m just following back around on your post here. Are you still having issues? Or, did any of the provided comments help? If so, we ask you mark the one which helped you as ‘Best Answer’ so others who have a similar issue who come across your post may benefit.
Best.
The problem remains. The server is unpatched. The team has not taken any action, so I have no results to report.
Ok, thanks for the update @mntbighker . What I think we’ll do is change your post from a question to a ‘content’ post since there seems to be no foreseeable resolution. If you ever do get this resolved, if you could, it would be great to post here what you did to resolve your issue.
@Madi.Cristil , can we change this post to a “content” post please?
This was perfect. We renamed the server after installing VEEAM, so we had to add the new server name to the file mentioned in this article to have successful authentication.
