HDP -allow multiple backups to run

Feature Request
1

I’ve notice that HDP will block other backups from running when one backup is doing some kind of process at 100%

image
image358×174 2.89 KB

HDP needs to allow multiple backups to run. I also don’t know why the processing at 100 can sit there for a while. It holds up the pc since hdp client is also stuck running. If there is a some kind of cleanup going on with the process it should be done without holding up other backups and keeping the client forced online.

2

Thanks for the feedback, let me clarify how HDP handles concurrent backups.
HDP does run multiple backups in parallel, one job does not block another.

  • If a job shows a “Queued” state, that’s the only case where it’s waiting for another job to release resources.
  • If it’s not in the Queued state, it’s already running concurrently.
1 Like
3

Thanks for the reply, i do see at times the jobs will run in parallel, but the issue is when one job sits forever in finishing state. it blocks all the other jobs from running. The client job should just upload the data to the server. The server should have off time processing to address cleanup and dedup etc..

Keeping the client tied up with finishing process and other clients from backing up is a problem when there are a lot of PC backups running. It causes all the PCs waiting to backup to wait online while the first client finished up.

4

Hi marcoi,

Let me give you a more precise breakdown of the stages, because I think the percentages are hiding what’s actually going on:

“Running 0%” doesn’t mean the job is idle. At that stage HDP is taking a snapshot of the source and calculating the changed areas — it’s actively working.

About the finishing stage (100%): data synthesis is not post-job cleanup — it’s the final stage of the backup task itself. Until synthesis completes, the backup isn’t finished. That’s why a queued task can’t be released while another job is still in this stage.

So what looks like “one job sitting at 100% blocking everything” is really one backup still completing its final stage.

That said, we recognize the real problem: when a job sits at 0% or 100% for a long time, you have no way to tell what it’s actually doing or whether it’s healthy.
The improvement we’re planning is to break the progress display into stages, so each phase is shown with what it’s doing, instead of leaving you staring at an ambiguous percentage.

Thanks for staying engaged on this.

1 Like
5

To help us analyze the situation further, could you please let us know how many devices are syncing simultaneously? Also, how long does the progress typically get stuck at 0% and 100% respectively? Thank you!

6

I had patched about 7 PCs on Wednesday morning after a large windows updates came out. I have most of my backup jobs set to run on startup first log on. So when i started all the PCs, I ran the updates, then the backup jobs started a few mins after logged in. First PC that was turned on and backing up was then staying at 100% for a long time, During that Finalizing process, no other backup ran. I don’t know if its finalization doing finishing the backup or a cleanup task to delete an old backup is holding things up.

7

Thanks for the explanation! We will also work on optimizing the UI and related mechanism prompts. Thanks!