Power outage during initial backup -- starting over at 0%?

Support
#1

Hey all,

I’m new to duplicacy and I had a machine doing an initial backup to B2, but the power went out after a couple of days when it was around 45% complete. I started the backup again and it skipped a bunch of chunks at the beginning, but it still seems to be starting over at 0% and is only very gradually increasing. Does this mean the previous progress was lost, or will it skip the remaining chunks it already uploaded later in the process? I was expecting all of the skipped chunks to be at the beginning.

Thanks!

What happens when you interrupt a backup process?
#2

The skipped chunks represent Duplicacy verifying that that particular chunk is already backed up and does not need to be uploaded again, ie the 45% progress is being considered.

Where are you seeing this? BTW: which version of Duplicacy are you using? CLI or Web-GUI?

#3

I’m using the CLI version, and the low percentage is being shown as part of the progress output:

Uploaded chunk 1984 size 5765638, 245KB/s 6 days 02:50:06 7.1%

Those numbers dont make sense if the 45% is being considered, because there is already ~90GB uploaded of a ~160gb backup set in the B2 bucket. Am I misinterpreting the status?

Thanks!

#4

I interpret this as 7.1% of the files (not chunks) to be backed up, ie those not yet backed up (the remaining files). I think it can also be interpreted as the percentage of current execution.

Take a look at a log of a backup like yours, that was interrupted and then resumed. Note that it starts from 0% even though a portion has already been backed up:

...
09:44:14.490 INFO BACKUP_START No previous backup found
...
09:44:17.572 INFO FILE_SKIP Skipped 286 files from previous incomplete backup
...
09:44:17.615 INFO UPLOAD_PROGRESS Skipped chunk 2 size 503556, 492KB/s 04:18:32 0.0%
...
09:44:18.019 INFO UPLOAD_PROGRESS Skipped chunk 52 size 1086525, 52.11MB/s 00:02:22 0.6%
...
09:44:21.773 INFO UPLOAD_PROGRESS Uploaded chunk 1 size 1463872, 13.38MB/s 00:09:13 0.7%
...

After you finish this first backup, you will notice in the upcoming incremental backup runs that this percentage will always start at 0% in the log.

#5

Cool, thanks a lot for the info.

By the way, I did just happen to catch a very large amount of skipped chunks on another computer that had the initial backup interrupted by the outage…it skipped from 55% to 72%, so it looks like it is possible that it will find chunks that were already backed up late in the operation as opposed to all at the beginning like I was expecting.