OneDrive storage location format

Hello,
I am following your guide to setup a OneDrive storage location. The token I have downloaded OK. Your guide says to enter the directory on OneDrive. I tried different variants based on Windows theme, but it does not work.

So in what format do you need to enter the backup storage location and I want to store it in a subdirectory.

Thanks

Something like storage or test/storage should work. Make sure you create the directory in OneDrive first.

Hi… Thanks for the response.

I tried with “Backups/Duplicacy” but I could not get into accept it. Always a “failed to retrieve storage” error.

I then tried a local storage location and I could get that to work.

I then tried dropbox with “Backups/Duplicacy” but the Duplicacy put the backup under “Apps/Duplicacy/BackupsDuplicacy”

In summary; I could not connect to OneDrive but I could connect to Dropbox but not at the storage location I wanted.
Will keep trying with OneDrive and may have to get back to you on this thread.

Anyway, just trialling at the moment, looking for a Crashplan alternative but it looks very promising, much potential. Hope you include multiple repositories and multiple storage location with the new GUI you are currently working on.

Thanks

I tried with “Backups/Duplicacy” but I could not get into accept it. Always a “failed to retrieve storage” error.

This looks more like a sign-in problem. Is your OneDrive account a business one? Duplicacy only support OneDrive Personal.

I then tried dropbox with “Backups/Duplicacy” but the Duplicacy put the backup under “Apps/Duplicacy/BackupsDuplicacy”

I tried it myself and yes, if there wasn’t a “Backups/Duplicacy” directory then the storage directory would be “Apps/Duplicacy/BackupsDuplicacy”. But if “Backups/Duplicacy” is created first, then it will correctly go into “Apps/Duplicacy/Backups/Duplicacy”.

Hi… Thanks for the info.
My OneDrive account is a personal account (family).
I tried again on my 2nd laptop with OneDrive and received the same error “failed to load OneDrive storage”.

I will leave Dropbox storage location as it is as I am only using Dropbox for testing since I could not get OneDrive to work.
I really need to get OneDrive working as OneDrive will be my main storage location.

I would try to initialise with CLI but I have no idea what the Storage URL would look like,

Any ideas what I can do to see why it is not working?

Thanks

Can you paste the full log line that says the “failed to retrieve storage” error?

Ok… I just tried again so I could get the log info. The first time I tired I received the error as said before after a timeout. However there was no log information to copy except, time responses.
I then turned on verbose logging and tried again. This time is connected and it then asked for the encryption password. I then entered the encryption password and after that it timeout out with “fail to retrieve storage” error again. Below is log info.

10:03:19.000 Command: duplicacy -background -log -d info -repository “C:\Backups” “one://Backups/Duplicacy”
10:03:19.100 Reading the environment variable DUPLICACY_ONE_TOKEN
10:03:19.102 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:03:19.630 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy/chunks?select=id,name,size,folder
10:03:19.974 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy/fossils?select=id,name,size,folder
10:03:21.337 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy/snapshots?select=id,name,size,folder
10:03:21.673 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy/config?select=id,name,size,folder
10:03:21.979 The storage has not been initialized
10:15:27.000 Command: duplicacy -background -log -d init SAMSUNGLAPTOP-Craig-Backups “one://Backups/Duplicacy” -e
10:15:27.253 Reading the environment variable DUPLICACY_ONE_TOKEN
10:15:27.255 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:27.519 Response code: 503; retry after 604 milliseconds
10:15:28.123 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:28.185 Response code: 503; retry after 1881 milliseconds
10:15:30.067 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:30.124 Response code: 503; retry after 2658 milliseconds
10:15:32.782 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:32.836 Response code: 503; retry after 3501 milliseconds
10:15:36.338 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:36.452 Response code: 503; retry after 6794 milliseconds
10:15:43.246 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:15:43.298 Response code: 503; retry after 21978 milliseconds
10:16:05.276 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:16:05.331 Response code: 503; retry after 4200 milliseconds
10:16:09.531 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder
10:16:09.673 Response code: 503; retry after 20034 milliseconds

This is puzzling. The api call to list the directory issued by the info command succeeded:

10:03:19.102 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder 10:03:19.630 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy/chunks?select=id,name,size,folder

But the same call by the init command failed with a 503 error:

10:15:27.255 GET https://api.onedrive.com/v1.0/drive/root:/Backups/Duplicacy?select=id,name,size,folder 10:15:27.519 Response code: 503; retry after 604 milliseconds

Can you try running it from the command line:

cd c:\Backups
duplicacy -log -d init SAMSUNGLAPTOP-Craig-Backups one://Backups/Duplicacy

I ran;
cd c:\Backups
duplicacy -log -d init SAMSUNGLAPTOP-Craig-Backups one://Backups/Duplicacy

then message;
C:\Backups>duplicacy -log -d init SAMSUNGLAPTOP-Craig-Backups one://Backups/Duplicacy
2017-08-29 18:03:34.265 ERROR REPOSITORY_INIT The repository C:\Backups has already been initialized

I then tried;
C:\Backups>duplicacy backup

then message;
Storage set to P:\BakDuplicacy
The storage has not been initialized

I then tried;
C:\Backups>duplicacy -log -d backup

then message;
2017-08-29 18:04:30.306 INFO STORAGE_SET Storage set to P:\BakDuplicacy
2017-08-29 18:04:30.307 ERROR STORAGE_NOT_CONFIGURED The storage has not been initialized

Seems like it is confused!

Thanks

It looks like the repository (c:\Backups) has been already initialized with storage P:\BakDuplicacy.

You can remove c:\Backups.duplicacy and run the init command again.

My nightly build started to get the same 503 error since last night. The message returned with the error is:

Our services aren't available right now
We're working to restore all services as soon as possible. Please check back soon.

This is definitely something wrong with their servers. Not sure this affects all Duplicacy users. I’ll contact their support.

I removed the .duplicacy folder and tried to initialized again and kept getting the error 503.

Ok… thanks for your support.
For your info, I also use Cyberduck and I can log in and transfer files up to this OneDrive account without any problems, so it does not look like a general log in issue,

Thanks

Starting from August 28 all operations (backup, prune, list) have failed with error 503. The OneDrive website seems to be working normally and getting a new access token hasn’t helped.

I submited a ticket in Wed and they haven’t responded yet.

OK, that’s unfortunate, but thanks for the update!

Any update on 503 errors with one drive ?

This is all I got from them:

Your issue is related to development on OneDrive and we have a dedicated team to handle Development/API related issues. Here is the link to get in touch with them https://dev.onedrive.com

The page on https://dev.onedrive.com doesn’t state clearly how to contact their development team. I just submitted a github issue anyway:

The 503 errors have been fixed in version 2.0.9.

Thanks! Everything is working again.