Looks like the problem has been caused by a bug which is already fixed in the latest version, so in case anyone suddenly starts to experience the same software behavior make sure you're on the latest build.

The change is likely caused by the update, a lot of things changed since version 3/[(I believe that was about 5 years ago), so the repository work has also been changed.

Here's what I suggest:
1. Make sure that repository sync is finished.
2. Re-create the plan from scratch with the same identical parameters.
3. Run the plan like usual.

The problem with the warning about file deletion is actually most likely related to repository being out of sync after update and some of the files no longer requiring purge.

What you described is not really supported in any of our products. You can use our API to verify your settings in Managed backup and no RDP required once you install the software, everything can be changed by logging in to a centralized web dashboard.
Remote deploy of configurations is also available in managed backup application.
You can schedule a personal demo here if you're interested.

Not for the standalone version. Our managed product allows you to change all parameters remotely without logging in to any of your machines directly, so perhaps it would be more efficient to try that out.

Currently you can only use Powershell as a pre-post action script. More info on that can be found here.

Check purge operations on the history tab(you can switch view to "files") and compare with what you actually have on storage side(outside of our software), maybe the problem is in that option.

You mentioned that the software is "deleting every single file before running the plan". Purge only happens upon successful backups, never before any operation, so that's unusual. Do you have "delete files that have been deleted locally" enabled for this plan? Have you tried syncing the repository?

If the cloud portion of data is still intact try syncing the repository via tools > options > repository. After that retry running the plan.

Thanks for pointing that out! Hope this method helps users who are having troubles creating bootable usb using native functionality.

Yep, I saw the ticket. Just reverted your notification settings to default.

Yes, we're aware of this problem and have a separate task to support o365 SMTP. Currently I can't recommend using that until we officially introduce this type of notification service.

Do you see any unusual activity in the event logs?
For further investigation we need diagnostic logs from the software(Main menu > diagnostic). Be sure to add that these logs are for Sergey N in the issue description and past the link to this forum thread.
Once the ticket is created please also attach event logs from the machine and continue communication in the ticket system.

I've informed the engineer responsible for handling your ticket about this. If you have any more info like that please provide updates in your ticket.

A lot of options will be introduced with the new archive mode, so stay tuned for the updates.

Not yet, this is something our R&D is working on.

I need to bring "Object reference" error message to the attention of our developers. Could you please send us the logs with step-by-step instructions on reproducing the problem?
Oh, and make sure you're doing all that on version 6.1.3.11.

Old folder structure currently stays as it is for now. If you want it to be mirrored right away you'd need to start your backups from scratch of remove some of the data that is under the old delimiter.

Will pass that to our R&D, just created a feature request in our issue tracker regarding this.

Everything you described in your post is quite expected, since we're talking about GDA. The sole purpose of this storage class is to archive data and then store it for a long time.
Just to warn you if you plan on restoring large volumes of data from GDA: it is likely to cost you a lot, so check their documentation first.

Just want to add that we'd need everyone with issues like that to contact support. Your particular case is under investigation by R&D.