The beta version is from april, if you are using the beta you are using the OneDrive v1 (aka the MS Live API), which should have stopped working on the 1st. The newer OneDrive v2 (aka the Graph API) is working now, but not include in the current beta.
You can tell which backend you are using in the “Storage Type” dropdown. The v1 version is labelled “Microsoft OneDrive” and the v2 version labelled “Microsoft OneDrive v2”.
Based on the discussion here, I think the slash issue will be fixed once the beta is created. Planned release some time next week.
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.
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 184.108.40.206 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.
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.