HBS 3.0 scheduler issues
-
- Starting out
- Posts: 19
- Joined: Tue Sep 29, 2015 8:30 pm
HBS 3.0 scheduler issues
Hi,
I'm running HBS 3.0 191016 and need to resync a largish (538GB) amount of data to my Onedrive. I've previously used my Synology NAS to perform this task but have decided to use the more powerful QNAP. At the moment this is appearing to be a mistake.
I'm experiencing multiple issues:
1) The upload process from HBS appears to be far slower and less reliable than that from the Synology. There are no ADSL issues. My Synology synced the 538GB in around 9 days whereas after 4 days the QNAP has only managed to sync around 50GB
2) The scheduler options are rather strange. I want the sync to run daily from 1am to 8am and I believe that by configuring a Start Time of 1am and Inactive Hours from between 8am and 1am that this should be the case. Why can't I set a daily End Time in a Daily schedule? The option of having a Start Time and End Date is bizarre
3) Even thought the settings above appear to prevent the sync from running after 8am (through the Inactive Hours setting) the sync is still running when I check the QNAP at 9am. It doesn't stop until I manually stop the process.
The HBS package needs a review as it's clunky, performs poorly and needs a more logical interface.
I'm running HBS 3.0 191016 and need to resync a largish (538GB) amount of data to my Onedrive. I've previously used my Synology NAS to perform this task but have decided to use the more powerful QNAP. At the moment this is appearing to be a mistake.
I'm experiencing multiple issues:
1) The upload process from HBS appears to be far slower and less reliable than that from the Synology. There are no ADSL issues. My Synology synced the 538GB in around 9 days whereas after 4 days the QNAP has only managed to sync around 50GB
2) The scheduler options are rather strange. I want the sync to run daily from 1am to 8am and I believe that by configuring a Start Time of 1am and Inactive Hours from between 8am and 1am that this should be the case. Why can't I set a daily End Time in a Daily schedule? The option of having a Start Time and End Date is bizarre
3) Even thought the settings above appear to prevent the sync from running after 8am (through the Inactive Hours setting) the sync is still running when I check the QNAP at 9am. It doesn't stop until I manually stop the process.
The HBS package needs a review as it's clunky, performs poorly and needs a more logical interface.
-
- Guru
- Posts: 13192
- Joined: Sat Dec 29, 2007 1:39 am
- Location: Stockholm, Sweden (UTC+01:00)
Re: HBS 3.0 scheduler issues
- In this user community we can discuss the interface and hopefully help each other with things that may not be correctly understood.
- Only Qnap can change their software and if you want to have a change in it you should make a request to Qnap about that.
Some protocols include caching which may improve performance over time. I have no idea what protocol Onedrive uses so it may not be an explanation in this case though.1) The upload process from HBS appears to be far slower and less reliable than that from the Synology. There are no ADSL issues. My Synology synced the 538GB in around 9 days whereas after 4 days the QNAP has only managed to sync around 50GB
I would avoid having exactly the same time set in both schedules (if you have that).I want the sync to run daily from 1am to 8am and I believe that by configuring a Start Time of 1am and Inactive Hours from between 8am and 1am that this should be the case.
I think that maybe there's a misunderstanding here so could you please try to explain more what you mean? A screenshot can often be very useful when explaining.Why can't I set a daily End Time in a Daily schedule? The option of having a Start Time and End Date is bizarre
The user interface says that the job should be inactive, so why do you expect it to stop?3) Even thought the settings above appear to prevent the sync from running after 8am (through the Inactive Hours setting) the sync is still running when I check the QNAP at 9am. It doesn't stop until I manually stop the process.
The important question should in my opinion be if the job still is sending any data or not at 9am. If it send data I would consider it a bug, if it doesn't send data it's working like I would expect.
HBS was recently massively overhauled and given among other things a new user interface.The HBS package needs a review as it's clunky, performs poorly and needs a more logical interface.
I'm very critical to some changes and positive to some (the new scheduling for example). The old scheduling was extremely limited...
I haven't decided yet what I think about the user interface as I'm very conservative about that and normally always prefer the previous version but with time I understand their thinking and can appreciate the changes as well.
Last edited by P3R on Wed Nov 13, 2019 9:33 pm, edited 1 time in total.
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!
A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.
All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!
A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.
All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!
-
- New here
- Posts: 2
- Joined: Sun Aug 30, 2015 6:18 pm
Re: HBS 3.0 scheduler issues
Hi sbpond,
I'm sorry, I can´t help, but 2) and 3) is exactly my problem and would be my remark to the software.
I inform you, if I should find a solution.
I'm sorry, I can´t help, but 2) and 3) is exactly my problem and would be my remark to the software.
I inform you, if I should find a solution.
- Toxic17
- Ask me anything
- Posts: 6477
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: HBS 3.0 scheduler issues
I take you have contacted QNAP regarding these issue but had no reply?spbond wrote: ↑Wed Nov 13, 2019 5:29 pm Hi,
I'm experiencing multiple issues:
1) The upload process from HBS appears to be far slower and less reliable than that from the Synology. There are no ADSL issues. My Synology synced the 538GB in around 9 days whereas after 4 days the QNAP has only managed to sync around 50GB
.......
Regards Simon
Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following
NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following
NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
-
- Starting out
- Posts: 19
- Joined: Tue Sep 29, 2015 8:30 pm
Re: HBS 3.0 scheduler issues
OK - to make this easier can someone tell me how I can configure a daily sync task to Onedrive that only syncs between the hours of 1am to 8am.
I thought that my configuration would do this but the fact that it's still syncing at 9am suggests either I'm misunderstood the configuration options or HBS isn't working correctly.
I thought that my configuration would do this but the fact that it's still syncing at 9am suggests either I'm misunderstood the configuration options or HBS isn't working correctly.
-
- Starting out
- Posts: 19
- Joined: Tue Sep 29, 2015 8:30 pm
Re: HBS 3.0 scheduler issues
Here's the Daily schedule interface - see attached. There's an option for Start Time and an option for End Date.
I don't want an End Date, I want an End Time which allows me to configure a daily schedule from between Start Time and End Time.
You can also see the Inactive Hours option which, I assume, allows the sync job to run only between these times. My sync job is set to start daily at 1am so with an Inactive Hours setting configured for 8am to 00pm I would expect the sync job to start at 1am but stop at 8am.
Is this correct?
So, two things:
1) Why can't QNAP provide the option to have a Start Time and End Time for a sync\backup?
2) Why doesn't the sync job stop at 8am when the Inactive Hours config kicks it?
I don't want an End Date, I want an End Time which allows me to configure a daily schedule from between Start Time and End Time.
You can also see the Inactive Hours option which, I assume, allows the sync job to run only between these times. My sync job is set to start daily at 1am so with an Inactive Hours setting configured for 8am to 00pm I would expect the sync job to start at 1am but stop at 8am.
Is this correct?
So, two things:
1) Why can't QNAP provide the option to have a Start Time and End Time for a sync\backup?
2) Why doesn't the sync job stop at 8am when the Inactive Hours config kicks it?
You do not have the required permissions to view the files attached to this post.
-
- Guru
- Posts: 13192
- Joined: Sat Dec 29, 2007 1:39 am
- Location: Stockholm, Sweden (UTC+01:00)
Re: HBS 3.0 scheduler issues
Okay but it appear that Qnap choose to do it differently.
Instead of setting a fixed end time in each schedule, Qnap choose an inactive time window for all schedules (there could be multiple schedules) on the same job.
The End date within a schedule offers a possibility to set up a scheduled reoccuring job that's only supposed to be scheduled for a limited number of times (for example a daily schedule for the coming 10 days only).
Now that I test it with a small job syncing to another NAS, I actually have that behaviour with HBS version 3.0.191016. The job stop on whatever inactive starting time I set.My sync job is set to start daily at 1am so with an Inactive Hours setting configured for 8am to 00pm I would expect the sync job to start at 1am but stop at 8am.
If you run the same HBS version as I and your's doesn't work the same way, I think that you've discovered a bug. Maybe it's limited to when using OneDrive as destination as I don't suffer from it?
As only Qnap will fix bugs please report it to them, either through this link or in the Helpdesk app that you can install in App Center.
I'm not Qnap so I wouldn't know and they usually aren't very communicative about their design decisions but you could ask them when you open the support ticket.1) Why can't QNAP provide the option to have a Start Time and End Time for a sync\backup?
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!
A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.
All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!
A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.
All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!
-
- New here
- Posts: 2
- Joined: Sun Aug 30, 2015 6:18 pm
Re: HBS 3.0 scheduler issues
I have a vague guess: The job do not stop or maybe stop to a different time, because of situations when the QNAP and the Servers of the "Storage Space" services are in different time zones...Maybe it's a Bug?spbond wrote: ↑Thu Nov 14, 2019 1:46 am You can also see the Inactive Hours option which, I assume, allows the sync job to run only between these times. My sync job is set to start daily at 1am so with an Inactive Hours setting configured for 8am to 00pm I would expect the sync job to start at 1am but stop at 8am.
-
- Starting out
- Posts: 19
- Joined: Tue Sep 29, 2015 8:30 pm
Re: HBS 3.0 scheduler issues
I removed and reinstalled HBS and configured the sync jobs using the exact same settings.
The sync jobs now stop at the time provided in the Inactive Hours setting as expected so I assume this functionality was broken by a previous HBS update.
All seems fine.
The sync jobs now stop at the time provided in the Inactive Hours setting as expected so I assume this functionality was broken by a previous HBS update.
All seems fine.
-
- Starting out
- Posts: 28
- Joined: Mon Sep 18, 2017 1:04 am
Re: HBS 3.0 scheduler issues
I was finding that jobs stopped at the inactive time I specified, but that is now a sporadic or completely broken feature. The same jobs that used to behave this way now do not. This was happening before the early Feb. 2021 update to HBS 3 and it is also happening after the update. Anyone else struggling with this setting now?
Screenshot shows my settings. Jobs used to stop at 9am but now don't.
Screenshot shows my settings. Jobs used to stop at 9am but now don't.
You do not have the required permissions to view the files attached to this post.
-
- First post
- Posts: 1
- Joined: Tue Feb 23, 2021 12:30 am
Re: HBS 3.0 scheduler issues
Same problem for me - have you found a workaround?
-
- New here
- Posts: 9
- Joined: Thu Nov 10, 2011 4:03 am
Re: HBS 3.0 scheduler issues
Same problem here. Jobs are ok with correct schedule but don´t start anymore!!!
Please fix this QNAP!
Please fix this QNAP!