Backup runs longer than 24 hours, “cancelled” when clock rolls around

Support
1

Sorry if I’ve missed a duplicate post I did search… scenario:

Backing up to DropBox
Collection is about 8k albums
Scheduled backup to run every 4 days at 2:00 AM
Backup starts normally after configuring backup and forcing start… but when the clock hits 2:00 AM, backup is “cancelled” at 2:00 AM (not by me)…

Logic bug in program? Or in user?

TIA

2

Sounds like maybe you should try a backup to a local resource, usb drive, NAS or just a local folder on the computer. As Dropbox is a remote location it’s probably something to do with network delays outside of your home.

3

I work at n enterprise IT.
I’ve backed up 8 TB of media f8les to AWS without issues…
I’ve copied a local backup to DropBox without issues.

The automated Dropbox backup always fails at exactly the time it is scheduled to start if a forced backup is already running. Even if the forced backup is the same backup that is scheduled.

@support anything? Lifetime customer here thanks…

4

That’s an expected behavior, Roon does only one backup procedure at a time and this means that if you have a backup running when a scheduled should be kicked in - scheduled backup will be canceled. But if such happens Roon will retry its attempt to make a scheduled backup the next day at the same time.
As for the time it takes to make a backup to Dropbox - it will always be much longer than making a local one. If this is your first backup to Dropbox and your library is big, 8k albums is about ~90-100k of tracks, I consider this to be a big library, it will take a while. Basically, Roon will be sending one by one tens of thousands of tiny files.

5

For that 24h+ case does Roon report you a backup progress ( we should show you % number) ? Does it change overtime ?

6

How about not scheduling backups for every 24 hours? Every other day?

7

Thanks for checking in - I get what you are saying. Just FYI the user experience is confusing… here’s what that is:

  1. Sitting on the couch at 7:14 PM, set up a scheduled backup to kick off at 2:00 AM. Force start that exact same backup.
  2. Its 8:03 PM, look at Roon… view backups, looks good, 7% done, I can tell something’s going on, looks good!
  3. Go to sleep :wink:
  4. Next morning, see red message “backup cancelled at 2:00 AM”
  5. No indication if the “force started” backup from last nite completed, failed, is still in progress, what? The only message the user sees is that the 2:00 AM scheduled is cancelled… no more percentage. No way as user I know I’m good or not good, just “cancelled”.

Anyway I will leave the scheduled backup in place and see if it kicks off again or if there is any indication when/if it actually finishes.

My expectation BTW (not happening obviously) is that the “force started” backup would run to completion, the 2:00 AM scheduled backup would respect that and start the next time there wasn’t another backup running, and some nice message would tell me those things.

Thanks again anyway. I’ll let you know how it all ends up.

8

Thanks for the report, we will verify this behavior and let you know the status.

9

FYI, we were able to reproduce. Issue was reported to the dev team.

10

Backup completed normally when I just left the scheduled backup run without trying to force it, so I’m good. A little edge case I guess. Thanks for the great support, I appreciate it.

1 Like
11

Closed due to inactivity. If you are still seeing this issue, please open a new support thread.