Setting up OneDrive (personal)

Now I am confused. :smile: The Beta I am using seemed to be backing up to OneDrive okay. Well, the machine I was using yesterday seemed to complete a backup. Odd.

I’ll try and get access to a couple of these OneDrive setups later today and check exactly which version is in place. I’ll also watch out for next week’s Beta release and do a test install around it.

For any willing to do test installs to see if OneDrive v2 works well (important because we’re past the date when Microsoft has said the earlier version would go unavailable), please consider testing Experimental before Beta. This will also be an opportunity to gain some experience migrating backups to v2. I don’t think it’ll be automatic. Obviously don’t use Experimental for important backups, and also don’t count on returning to prior Beta easily.

@ts678 you are worrying me. Are you saying that all of my OneDrive backups are now useless? These are not installed in Test Environments. These are in fully working small companies. I have two of them setup backing up to the cloud so can’t really play games with them. They have to be run on the most stable versions.

And if you are saying that this upgrade will trash the old backups that doesn’t really make sense to me. I know I have swapped the delivery method of backups between Local files and SMB and FTP before and was impressed as to how resilient Duplicati was at that swapping around. So it surprises me to hear you say that it will not migrate from OneDrive v1 to v2

You are correct that changing the method of connecting to the backend destination shouldn’t “reset” your backups.

I think he meant installing the new experimental or beta version that supports v2 won’t automatically update your job to use v2 - you’ll have to do that manually.

While unlikely, it’s POSSIBLE the v2 API does something silly like connecting at a different folder level than v1 (which would cause Duplicati to THINK your backup was missing, when really it’s just in another folder path).

That’s the sort of thing we’re looking to confirm does NOT happen via the experimental release. :slight_smile:

I suspect it won’t be a problem at all since Canary users have been able to us v2 for a few months now and I don’t recall hearing about any such problems.

@JonMikelV The places I have OneDrive as a destination are small. So easy to do a manual check first. So I’ll spot if it is connecting at a different level. @ts678 has basically scared me off from going near the experimental releases. So I’ll wait for that beta and then do some manual checks when upgrading.

Absolutely not, It’s an Application Programming Interface (API) change as described by Microsoft in my link, however when this forced migration happens, they will be inaccessible until you reconnect using the v2 API.

Absolutely not, and you don’t even need to move files around (as other destination changes might require).

Not saying that. I mean Duplicati just won’t change the destination type for you. You must do that yourself, however for the small companies you support, I guess you’ll offer directions (see “gain some experience”).

These are standard precautions, and the difficulty of downgrades applies to Beta as well. It’s difficult, so it’s important that Beta be good quality. Achieving that is especially important given forced OneDrive migration.

So basically this Experimental could be last test call before Beta. Canary user base is probably far less than Beta (even though v2 came out on April 2 in canary, exposure is limited), so I’m trying to encourage (not scare off) testers of Experimental. There are risks, thus precautions, but better to discover issues early. Not everyone is willing and able to do a test install and meaningful test, but here’s a chance for any who are.

1 Like

FYI, I had a backup that used the old OneDrive API that I migrated to the v2 API. The only things I had to do were to change the storage type and generate a new authentication key. I did not have to change any paths, and the existing backup sets were recognized without any problems.

@warwickmm thank you for that confirmation. I know I am running a Beta version here so I don’t expect perfection. Though I do feedback anything I can about my experiences.

I have done plenty of beta testing of all kinds of odd products in my years. So understand the risks. This is why I am not using the Canary editions.

Hi everyone, I tried to change my current backups of Duplicati from OneDrive to OneDrive V2. Unfortunately this doesn’t work and I get the following error:

Failed to connect: BadRequest: Bad Request error from request Method: GET, RequestUri: ‘’, Version: 1.1, Content: <null>, Headers: { User-Agent: Duplicati/ Authorization: Bearer ABC…XYZ } StatusCode: 400, ReasonPhrase: ‘Bad Request’, Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Cache-Control: private Transfer-Encoding: chunked request-id: 69f2e8f5-1da4-46ba-8bbc-60e758d4558c client-request-id: 69f2e8f5-1da4-46ba-8bbc-60e758d4558c x-ms-ags-diagnostic: {“ServerInfo”:{“DataCenter”:“West Europe”,“Slice”:“SliceC”,“Ring”:“5”,“ScaleUnit”:“002”,“Host”:“AGSFE_IN_61”,“ADSiteName”:“WEU”}} Duration: 3.7835 Strict-Transport-Security: max-age=31536000 Date: Fri, 21 Dec 2018 12:07:27 GMT Content-Type: application/json } { “error”: { “code”: “BadRequest”, “message”: “Resource not found for the segment ‘root:’.”, “innerError”: { “request-id”: “69f2e8f5-1da4-46ba-8bbc-60e758d4558c”, “date”: “2018-12-21T12:07:27” } } }

Does anyone know what I can do? I’ve already tried the slash, but unfortunately no success.


Does that refer to the temporary workaround mentioned in Release: (canary) 2018-10-23 pointing to Path on server needs / at beginning when configurations are edited #3460? If not, could you clarify it please?

Microsoft Graph error responses and resource types says

400 Bad Request Cannot process the request because it is malformed or incorrect.

Addressing resources in a drive on OneDrive explains its format. I’m not sure if a double slash is helping any, and what’s the # for (and is that character allowed)? I’m not a OneDrive expert, and can’t help more in depth.

The # looks suspect to me (my configuration doesn’t appear to have one). Also, did you generate a new AuthID when changing to OneDrive v2?

Yes, it refers to that workaround But that didn’t help. I’ve tried one slash in front and two slashes.

The # is for pure organization so that the folder stands at the beginning. With the old one drive setting it was no problem at all.

Yes I did. But that seems not to be the problem. Does anyone else have an idea on that?

Try removing the # from the folder name?

Maybe pick a different folder, or make a new one. Try to get something going, then study the differences.

I’ve tried everything and the OneDrive v2 doesn’t work with the # in front…v1 does, though. Sucks big time. I’ve got to backup all my Backups again to migrate to v2. But thanks to you guys anyways.

Found a workaround for my problem. I’ve just copied all backups from “#Backups/” to “_Backups” and changed the backup paths and everything works fine.

Thank you guys for the input.

I’m trying to migrate to OneDrive v2 in and am getting an “Unauthorized” error message myself. Here are my Backup destination Storage Type and Path on server values:


And here’s the error message I’m getting:

Failed to connect: Unauthorized: Unauthorized error from request Backup/DELLXPS8500 Method: GET, RequestUri: ' Backup/DELLXPS8500', 
Version: 1.1, 
Content: <null>, 
Headers: { 
User-Agent: Duplicati/ Authorization: Bearer ABC...XYZ } 
StatusCode: 401, 
ReasonPhrase: 'Unauthorized', 
Version: 1.1, 
Content: System.Net.Http.StreamContent, 
Headers: { request-id: b3605381-e3d0-4c0c-b9a3-8b92c91c4019 client-request-id: b3605381-e3d0-4c0c-b9a3-8b92c91c4019 x-ms-ags-diagnostic: {
"DataCenter":"North Central US",
Strict-Transport-Security: max-age=31536000 Date: Thu, 27 Dec 2018 21:32:13 GMT WWW-Authenticate: Bearer realm="", 
client_id="00000003-0000-0000-c000-000000000000" Content-Length: 265 Content-Type: application/json; charset=utf-8 
} { "error": { 
"code": "InvalidAuthenticationToken", 
"message": "CompactToken parsing failed with error code: 8004920A", 
"innerError": { 
"request-id": "b3605381-e3d0-4c0c-b9a3-8b92c91c4019", 
"date": "2018-12-27T21:32:13" 
} } } 

Based on the above, is the OneDrive v2 authentication link working properly? Every time I go to it, the autocomplete email address in my browser is the same one I used for Enterprise testing, not the personal one associated with my Office 365 Home OneDrive storage. This leads me to suspect that the v2 token portal might not cover consumer 365 subscriptions.

Also, do we have to revoke the previous OneDrive v1 token before using a new v2 one? If we do, I’m not sure how that would work as I didn’t store that token anywhere outside Duplicati.

Lastly, are there Advanced options that might help?

Any ideas?

Bump. Anyone at all?

If the auth link was broken in general others wouldn’t have been reporting successful transitions so I’m guessing it’s something specific to your situation.

Did you try getting another auth key since your current one isn’t working?