Consistent failure of one backup set (log enclosed)

wasabi
backup

#1

I’m new to duplicacy (using the web GUI) and on one of my backup sets it’s consistently failing (tried 4 times). Here’s the log. Since I’m new to duplicacy, this set has never had a successful finish yet.
Any advice on how to troubleshoot?

Running backup command from /Users/joe/.duplicacy-web/repositories/localhost/2 to back up /Volumes/files
Options: [-log backup -storage Duplicacy.Wasabi -stats]
2019-01-15 14:58:16.983 INFO REPOSITORY_SET Repository set to /Volumes/files
2019-01-15 14:58:16.983 INFO STORAGE_SET Storage set to wasabi://wasabi[redacted]
2019-01-15 14:58:17.905 INFO BACKUP_START No previous backup found
2019-01-15 14:58:17.905 INFO BACKUP_INDEXING Indexing /Volumes/files
2019-01-15 14:58:17.905 INFO SNAPSHOT_FILTER Loaded 3 include/exclude pattern(s)
2019-01-15 15:02:26.439 INFO INCOMPLETE_LOAD Incomplete snapshot loaded from /Users/joe/.duplicacy-web/repositories/localhost/2/.duplicacy/incomplete
2019-01-15 15:02:26.439 INFO BACKUP_LIST Listing all chunks
2019-01-15 15:03:21.011 INFO FILE_SKIP Skipped 50031 files from previous incomplete backup
2019-01-15 17:06:12.355 ERROR UPLOAD_CHUNK Failed to upload the chunk aafe3cb0f42b0d936105c5827564d4bd9795a45dc1990ffb1693936cfe8a0b76: TemporarilyUnavailable: Resources for this operation are temporarily unavailable.  Please try again later.
	status code: 503, request id: EA92E7238D0AE254, host id: 7U/Ha0SwrSF0dzTP56D2xbYtNSO+mVzmJwRoGpys94NyIGQ35D5Fm9TKleUI6gZEsSCeK7bbKO1A
2019-01-15 17:06:13.249 INFO INCOMPLETE_SAVE Incomplete snapshot saved to /Users/joe/.duplicacy-web/repositories/localhost/2/.duplicacy/incomplete

#2

I’m sad to see this since I just switched to wasabi from B2, but it looks like wasabi is sending back a 503 error code.

Which wasabi region are you using? I have daily backups to the us-west-1 region and haven’t had any failed backups so far.


#3

us-east

However, I have three other backup sets that completed successfully so it’s weird how just this one is having problems.


#4

Unless I’m reading the log incorrectly, it would probably be a good idea to contact wasabi support and send them the log output since it seems to have some wasabi-specific troubleshooting info.


#5

Thanks, I’ve reached out to Wasabi support to see if they can help.

I’ve been pondering a switch to B2… does one work better than the other with Duplicacy in general?


#6

Last year I migrated from Wasabi to B2. I had recurring problems with Wasabi when dealing with buckets. Their support is also terribly slow.

With B2 everything is 110% perfect, for more than 6 months now.


#7

I generally had a good experience with B2 as well even before I migrated away from it. I haven’t noticed any functional issues with either when using Duplicacy – at least not yet.

The main reason I switched from B2 to Wasabi was the free egress, better performance, and not having to worry about API calls. The psychological cost of knowing that my data is locked behind a paywall with B2 was annoying and costly for periodic backup integrity checking and replication elsewhere; but that might not be a factor for others.


#8

@joe did it always fail at the same chunk?


#9

I just checked and it was different chunks each time.

It started working successfully though. I’ve engaged Wasabi support but since it’s working they’re having difficulty with helping. No worries, several backups have completed successfully!

@gchen if I buy a GUI license, can I use it for the web version? My “trial” of the web version is about to expire. Thx!


#10

@joe yes you can activate the GUI license in the web version.