# Incoming HBS 3 back-up hanging on remote server

**URL:** <https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447>\
**Category:** Backup and data protection\
**Created:** [November 4, 2026, 1:10pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447 "2026-11-04T13:10:52Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 4, 2026, 1:10pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/1 "2026-11-04T13:10:52Z")

</div>

Hello. I have for some time been backing my live QNAP server to my second QNAP server using HBS 3. My latest back-up failed (which it does sometimes, usually due to me running out of space on my second server). The failed back-up cannot be stopped via the HBS interface on my live server as the button is greyed out. On my second server the back-up is recorded as 97% complete and still running. How do I kill/stop the back-up on my second server? A reboot of my second server makes no change. I cannot run any more back-ups until I stop this process.

Thank you.

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 4, 2026, 1:31pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/2 "2026-11-04T13:31:18Z")

</div>

Yeah, the management of backups in HBS when one side gets full is not really good. You can’t alter how many copies are kept in the backup, etc.

So what I think you need to do it shut both NAS units down. A shut down stops all current processes. A reboot will bring the processes back up where they were when the machine was rebooted.

So shutting down and then restarting should solve your issue (at least the one where you need to stop the backups!). 😃

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 4, 2026, 2:36pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/3 "2026-11-04T14:36:51Z")

</div>

Thank you! That sounds like a simple thing to do, which it is. Unfortunately the tenacious back-up is still hanging at 97% ☹. Any other suggestions (like kill the process)?

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 4, 2026, 2:53pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/4 "2026-11-04T14:53:52Z")

</div>

So you shut down the machine completely? And then restarted? That should have killed it.

Try this.

With the machine running, stop HBS in the App Center.

Shut down the machine.

Restart the Machine

Start HBS again.

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 4, 2026, 3:31pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/5 "2026-11-04T15:31:37Z")

</div>

Yup, I shut down bother servers completely and restarted them. I’ll try that suggestion, which sounds to me like a very good one. Again, thank you.

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 4, 2026, 3:59pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/6 "2026-11-04T15:59:58Z")

</div>

Yikes - this back-up is like a zombie! Still running at 97% after stopping/shutting down/starting…

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 4, 2026, 4:45pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/7 "2026-11-04T16:45:26Z")

</div>

So did you get the process stopped?

It’s possible that it is transferring data very slowly. Have you clicked on the job to see what it is doing and then viewing what the transfer rate is at? Maybe it’s backing up a large number of small files. That takes quite a while.

If your remote machine is totally out of space, then you will likely need to stop everything. Clone the backup job, delete the remote backups and basically start over.

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 4, 2026, 5:16pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/8 "2026-11-04T17:16:30Z")

</div>

Thank you.

I am used to having start over as my storage is almost full, but that’s not the cause this time round - my second server has space to spare (although I’ll have to clear it out again soon). I can’t see progress on this server as the job is incoming. On the live server the job is recorded as failed after some 30 minutes so no progress available and no record of why. The CSV log reveals nothing of any use (that I can see). The back-ups are all pretty much the same as it is my personal media store (Plex). Any other helpful thoughts? Any idea what process I should look for in Resource Monitor to kill?

---

<div class="post-metadata">

**Author:** ![SteveKo](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@SteveKo](https://community.qnap.com/u/SteveKo)\
**Post date:** [November 6, 2026, 9:53am UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/9 "2026-11-06T09:53:49Z")

</div>

Thanks for the report! You could try either of the following to clear the stuck incoming job:

1. Run the backup job again from the source NAS. Once it completes successfully, the progress on the destination NAS will update and the stuck job will end.
2. In HBS 3 on the destination NAS, deny the connection from the source NAS to clear the stuck job, and then allow the connection again.

We’ll also look into this issue internally. Thanks!

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 6, 2026, 10:11am UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/10 "2026-11-06T10:11:50Z")

</div>

Thank you - trying that. I’ll report back.

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 6, 2026, 3:50pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/11 "2026-11-06T15:50:16Z")

</div>

That worked, in that both source and destination failed but the processes have ceased on each. I shall delete some stuff off destination and re-run in the hope that was the problem. Thank you very much, @SteveKo (and @NA9D). I shall report back for closure in a week or so when I have done what I need to do and run a successful back-up.

---

<div class="post-metadata">

**Author:** ![Streaky](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Streaky](https://community.qnap.com/u/Streaky)\
**Post date:** [November 13, 2026, 5:44pm UTC](https://community.qnap.com/t/incoming-hbs-3-back-up-hanging-on-remote-server/7447/12 "2026-11-13T17:44:36Z")

</div>

The back-up was going fine once I cleared space on the destination but we had a brief power cut this morning which caused my ethernet network to drop so I’ve had to start all over, BUT looking good so thanks again you two.
