Long "Compacting Backup"-Activity after Upgrading to v10

[Ibeme]

After upgrading a few customers to v10, last weekend some "Compacting Full Backup" Activity was running the first time after upgrading.
I updated 3 customers so far.

2 of those 3 customers did have jobs with "Compacting Backup" enabled.
All 2 customers did have an issue this weekend with Compacting Backup.

One was still running after 14 hours and I canceled the Job.
Next day it happened again, so I disabled "Compacting Backup" and cancled the Job again.

The other customer hat this running from Saturday through Monday.

Normally and with v9 it completed after a few hours. Now It writes nearly the whole new full backup file and stalls at some point at which it doesn't make any noticable progress.

I already opened a support ticket this morning.

Ticket ID is 04036931

[HannesK]

Hello,

Now It writes nearly the whole new full backup file

compact full always writes a complete new full backup

Please continue working with support. In the comments I see, that you might lack hardware resources.

Best regards,
Hannes

[Ibeme]

Sure it writes the complete full backup but it doesn't nearly stall normally.

I did have a second customer that had the same issue. (The only 2 that are on v10 and have compact full backup activated)

I'm further investigating it with support.

[Ibeme]

Update:

The problem is currently escalated and support is working with RnD on it.

It seems that, when compacting full backup is completed it starts again and again and again...

[Gostev]

Yesterday, I saw an email from builder indicating that the hotfix was created for this issue. So support should have it soon. Based on the description, it seems that the issue is specific to NON-per-VM backup chains.

[sasilik]

I searched something else and happened to find this thread. My experience was exactly the same after upgrading to v10 on july 2020. I wonder why I did not find this thread then... I opened also a case with support but they did not say anything helpful about it or that there were similar cases or that there my be hotfix for that. And as this problem went away after a month or so then case was closed.

[Gostev]

The fix was included in a later v10 update, so may be this is why the issue just "went away" for you.