Well, honestly, it's not really supposed to work with the closed lid. At least for now.

I'll need input from the devs on that. Will provide a reply soon on your case.

Let me consult with R&D first, and we'll provide more info on that as soon as possible.

Yes, that's correct.

It's the latter, the files are sent to Wasabi from your NAS device after local upload.

That's not really how it works. As I mentioned previously, the data is moved within your S3 bucket, this type of backup does not use vaults at all.

The lifecycle will be applied automatically in this case. Lifecycle rules option exists to give you an ability to set up more granular transitions between storage classes(e.g. Infrequent access).

There's no support for the so called "pure Glacier" in Linux version, backups are performed via lifecycle rules in S3 by enabling "archive to Glacier" option when creating a plan.

As for the "access denied" message, you need to assign "S3fullaccess" policy to your credentials on AWS side to resolve that.

iCloud has its own closed infrastructure which we don't have access to, that means implementation of this feature is quite complicated, but afaik our R&D is working on this.

Currently I can only suggest to use standard backup plans to back up that data to your local NAS destination.

You can generate a link a provide it to a person you're connecting to via any means, that will install the software automatically and launch the remote session.

As for the second point you mentioned:
You can setup unattended access which requires Windows password, so you're correct here. The procedure can be done in both ways.

Thanks for the feedback, I'll transfer it to our developers.

We do not support Windows XP, so we can't guarantee proper functionality on this OS, sorry.

Consistency checks work per destination, not per plan. Currently they can only be created remotely, but not deployed via "remote deploy" functionality.

Make sure you're on the latest version and send us the logs from both machines via diagnostic menu, please. Don't forget to mention this forum thread in the issue description.

The first thing to try is to update both machines to 2.2 and retry the operation. This is likely to fix your problem.

Make sure you're on the latest version and send us the logs from both machines via diagnostic menu, please. Don't forget to mention this forum thread in the issue description.

We need the logs from both machines sent via diagnostic menu, please. Don't forget to mention this forum thread in the issue description.

Configurations are not cross-compatible between Windows and Linux machines. You need to re-create the plan from scratch.

Are you on the latest version of the software? What are the Operating Systems on both machines?

That depends on what you mean by "documents folder". That log record is expected to appear if some temp files are in the data set, maybe some of the documents are opened during the backup procedure.