Can't backup or rescan server: "backup is in progress"

[mvanrenssen]

Support Case #04378553

We cannot add a server to our backup job. This server was backed up previously, but due to a repository change we had to make a full backup. The backup took too long, which caused the server to freeze during the morning. We had to cold boot the server, since then we've tried everything to reinstall the agent / readd the server.

The troubleshooting steps we took were:
- Remove the backup job and protection group
- Remove agent and all other Veeam bits from the server, such as all Veeam folders under program files and program data
- Restart the server
- Create new protection group and backup job

Whenever we rescan this server or try to apply the backup configuration, Veeam keeps reporting:
"Skipping [servername]: backup is in progress"
"Failed to install package: backup is in progress on target host"

This is similar behavior as in veeam-agent-for-windows-f33/failed-to-i ... 53786.html
For us, however, setting up new Protection Groups or doing a Manual Rescan doesn't do anything to solve the issue.

[PetrM]

Hi Marc,

Perhaps, it happens due to an obsolete entry of backup session in Veeam configuration database, most likely is has not been properly updated because of server reboot.
I would recommend to attach a backup of configuration database to the support case via customer portal.

Anyway, let's wait for findings of our support engineers.

Thanks!

[Dima P.]

Hello,

Small update: I've asked support team to review the case details, so stay tuned. Cheers!

[tejko30]

Hello,

Were you able to figure it out?

I have the same problem: Failed to install package: backup is in progress on target host

I recreated Backup job, recreated PG with new name, rebooted server, reinstalled agent, nothing works.

Dima P. I can reach out to Veeam support but it would be great to share solution here for others too.

Thanks!

[Dima P.]

Hello Matej,

The original case was closed without resolution, so we don't have any details to share. Please reach our support team to investigate the issue and let us know the case ID. Cheers!