What if storage is full/ disk full?

Support
#1

My storage is almost full and I would like to know what happens in that case?
How is (CLI version) log message in such a case? Is the backup run immediately quitting? Will I notice this in the exit code? Is there a retry on the next backup run?

Thanks for the great product and support!!

#2

I would expect the backup to fail with a non zero exit code. I think the exact symptoms and lines in the logging will vary depending on what protocol you’re using to backup to the storage.

Next time you run the backup I think it will act as though the failed backup never happened, unless it’s an initial backup.

1 Like
#3

Got this message today:

Failed to upload the chunk <chunk id>: Maximum number of retries reached

Unfortunately there is no further logging after this line - so I guess it has just quit service?

I believe there was no special exit code (cause my task manager should report if non zero exit code). At least it would be very nice to see some more logging, e.g. “exitting with code x”

#4

Which storage are you using?

#5

In this case the exit code should be 100 (see Exit codes details). If you go back a few lines in the log you can see the actual upload error.

#6

Hmmm…

my Storage is OneDrive, OneDrive reported to me that the storage is full.
I am on version 2.2.3 (58387C) and this is my command:

./duplicacy backup -stats

and this is my complete logfile of the backup run tonight:

Storage set to one://thisandthat
Last backup at revision 345 found
Indexing /volume1/duplicacy-repo1
Parsing filter file /volume1/duplicacy-repo1/.duplicacy/filters
Loaded 9 include/exclude pattern(s)
Response code: 507; retry after 433 milliseconds
Response code: 507; retry after 1387 milliseconds
Response code: 507; retry after 2846 milliseconds
Response code: 507; retry after 2691 milliseconds
Response code: 503; retry after 11505 milliseconds
Response code: 507; retry after 16878 milliseconds
Response code: 507; retry after 49074 milliseconds
Response code: 507; retry after 121265 milliseconds
Failed to upload the chunk <someremovedchunkid>: Maximum number of retries reached

There is no more output.

If i run ./duplicacy -log -verbose backup i get not more than
…

    2019-12-18 22:36:40.630 INFO ONEDRIVE_RETRY Response code: 507; retry after 802 milliseconds
    2019-12-18 22:36:45.759 INFO ONEDRIVE_RETRY Response code: 507; retry after 1680 milliseconds
    2019-12-18 22:36:51.925 INFO ONEDRIVE_RETRY Response code: 507; retry after 2272 milliseconds
    2019-12-18 22:36:58.539 INFO ONEDRIVE_RETRY Response code: 507; retry after 2807 milliseconds
    2019-12-18 22:37:05.814 INFO ONEDRIVE_RETRY Response code: 507; retry after 15773 milliseconds
    2019-12-18 22:37:25.934 INFO ONEDRIVE_RETRY Response code: 507; retry after 31020 milliseconds
    2019-12-18 22:38:01.239 INFO ONEDRIVE_RETRY Response code: 507; retry after 29532 milliseconds
    2019-12-18 22:38:35.543 INFO ONEDRIVE_RETRY Response code: 507; retry after 45733 milliseconds
    2019-12-18 22:39:21.276 ERROR UPLOAD_CHUNK Failed to upload the chunk <somechunkid>: Maximum number of retries reached

By the way: If i run ./duplicacy backup -log -verbose (mind the sequence) i get “incorrect usage” although I saw some examples like this in this forum.