Skip to main content
Solved

Failed to find the agent certificate. Possible reason: a recent change of hardware could cause the HWID to change as well.

  • September 10, 2025
  • 5 comments
  • 172 views
S
Forum|alt.badge.img+1

Backing up a postgresql database path on a suse linux enterprise vm, using  Backup Job: Backup → Linux Computer -

Error received: 9/10/2025 5:05:53 AM :: Processing suseprod Error: Failed to execute agent management command print. Failed to find the agent certificate. Possible reason: a recent change of hardware could cause the HWID to change as well.

 

Changes i made, i had changed the vm hyperv config version for this vm from 10 to 8, thus changing vm name. I ran this same backup job, got error above, created a brand new backup job/chain  same error, at the manage credentials section i used same root password. This backup worked for me earlier this year and last, but with both success and error due based on reports. Sometimes errors, other times success. right now it fails within 1 minute of trying to backup:

 

Any fix/workaround please, Can Veeam 12 backup postgresql directly from my suse linux server, if so what are the steps?

Best answer by SysEng

Thank you guys for all the help. This is what i did to resolve the issue though:

-Remove Old VM from Inventory

  1. Open the VBR console
  2. Go to Inventory > Manually Added
  3. Locate the old vm entry (likely showing “25 days ago” or offline)
  4. Right-click and select Remove from Inventory

If you see a warning like “Cannot delete because it’s used in a job,” first delete or edit the job to remove the VM, then retry.

-Delete Old Backup Jobs (if applicable)

  1. Go to Home > Jobs > Backup Jobs
  2. Locate any test jobs tied to the old vm
  3. Right-click and choose Delete
  4. Confirm whether to delete associated backup files (optional)

-Reset the Veeam Agent on SUSE Linux VM

-Reset Agent Identity

Run these commands on the Linux VM only:

sudo systemctl stop veeamservice

sudo rm -rf /var/lib/veeam/*

sudo systemctl start veeamservice

This clears the agent’s certificate and identity  It does not affect Hyper-V jobs, repositories, or backup chains

-Verify Agent Status

veeamconfig --version

sudo systemctl status veeamservice

N.B. To ensure the agent is installed and running properly.

-Reconfigure in VBR

-Re-add VM to Protection Group

  1. Go to Inventory > Protection Groups
  2. Edit your existing group (or create a new one)
  3. Click Add > Individual Computer
  4. Enter the hostname or IP of suseprod
  5. Use root or sudo-enabled credentials
  6. Click Rescan to deploy agent components and verify connectivity

-Create New Linux Computer Backup Job

  1. Go to Home > Jobs > Backup Job > Linux Computer
  2. Name the job (e.g., suseprod Linux Backup)
  3. Job Mode: Select Managed by backup server
  4. Type: Choose Server
  5. Computers: Add the Protection Group containing suseprod

-Configure Backup Mode and Objects

5 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 9583 comments
  • September 10, 2025

Yes v12 should be able to back up Postgres from your VM without issue.  Did you check the Inventory tab to see if you need to approve the Linux VM SSL thumbprint?  Just wondering due to the certificate message maybe?

Also check the logs for the backup - C:\ProgramData\Veeam\Backup\Jobname and see if there is anything there that points to the failure.  Other than that support would the last resort.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
Andanet
Forum|alt.badge.img+11
  • Andanet
  • Veeam Legend
  • 422 comments
  • September 10, 2025

Hi ​@SysEng I think your issue is due to Veeam Agent + registered credentials. 

Please try this as per Fabian post on forum

1) Stop the service:
# systemctl stop veeamservice
2) Make database backup:
# mv /var/lib/veeam/veeam_db.sqlite /var/lib/veeam/veeam_db.sqlite.bak
3) Start the service:
# systemctl start veeamservice
4) Wait a few minutes for the database to rebuild
5) Rescan machine in the protection group

But before to do 5th step please check credentials because the new VM create a new uid for the user. 

 

Linux logs can be grabbed with these instructions

Let us know if your job will be completed successfully or not. 

Thanks 

Antonio D'Andrea | VMCE 2021 | VMCA 2022 | VMTSP2024 | Veeam Legend | VUG Italy Leader | Object First Ace | VCP6-DCV | I want it written on my tombstone "Please start a restore to the last valid backup"
S
Forum|alt.badge.img+1
  • SysEng
  • Author
  • Influencer
  • 64 comments
  • Answer
  • September 10, 2025

Thank you guys for all the help. This is what i did to resolve the issue though:

-Remove Old VM from Inventory

  1. Open the VBR console
  2. Go to Inventory > Manually Added
  3. Locate the old vm entry (likely showing “25 days ago” or offline)
  4. Right-click and select Remove from Inventory

If you see a warning like “Cannot delete because it’s used in a job,” first delete or edit the job to remove the VM, then retry.

-Delete Old Backup Jobs (if applicable)

  1. Go to Home > Jobs > Backup Jobs
  2. Locate any test jobs tied to the old vm
  3. Right-click and choose Delete
  4. Confirm whether to delete associated backup files (optional)

-Reset the Veeam Agent on SUSE Linux VM

-Reset Agent Identity

Run these commands on the Linux VM only:

sudo systemctl stop veeamservice

sudo rm -rf /var/lib/veeam/*

sudo systemctl start veeamservice

This clears the agent’s certificate and identity  It does not affect Hyper-V jobs, repositories, or backup chains

-Verify Agent Status

veeamconfig --version

sudo systemctl status veeamservice

N.B. To ensure the agent is installed and running properly.

-Reconfigure in VBR

-Re-add VM to Protection Group

  1. Go to Inventory > Protection Groups
  2. Edit your existing group (or create a new one)
  3. Click Add > Individual Computer
  4. Enter the hostname or IP of suseprod
  5. Use root or sudo-enabled credentials
  6. Click Rescan to deploy agent components and verify connectivity

-Create New Linux Computer Backup Job

  1. Go to Home > Jobs > Backup Job > Linux Computer
  2. Name the job (e.g., suseprod Linux Backup)
  3. Job Mode: Select Managed by backup server
  4. Type: Choose Server
  5. Computers: Add the Protection Group containing suseprod

-Configure Backup Mode and Objects

Andanet
Forum|alt.badge.img+11
  • Andanet
  • Veeam Legend
  • 422 comments
  • September 11, 2025

Great news ​@SysEng 

your Identity reset steps are the same Fabian wrote in his post but whitout remove all veeam folder.

The most important thing is that you got the backup done again.

Thanks for share your solution

Antonio D'Andrea | VMCE 2021 | VMCA 2022 | VMTSP2024 | Veeam Legend | VUG Italy Leader | Object First Ace | VCP6-DCV | I want it written on my tombstone "Please start a restore to the last valid backup"
S
Forum|alt.badge.img+1
  • SysEng
  • Author
  • Influencer
  • 64 comments
  • September 12, 2025

Thanks for the assistance once again guys, this forum is HOT!


Terms & ConditionsAccessibility statement