That's how the software currently operates, but a lot of things will change with version 7.0 that should address the situation you mentioned.

Archive mode will be overhauled in version 7.0 and will actually be the main mode of the backup.

As for the file-level restore from an archive, you need to right-click on the data in the archive on the backup storage tab and select "restore" option. Let me know if you have any issues while performing the operation.

The data can only be restored via the corresponding restore plan.

More info on how to create it via CLI can be found here:https://help.msp360.com/cloudberry-backup-mac-linux/cli/creating-restore-plan-via-cli

It checks if your current backup chain is intact via separate "quick sync" functionality without actually scanning all the files in the cloud and warns you if there are any problems with your data.

It's enabled by default in all plans starting from version 6.2, so you no longer need to worry about that or perform any additional actions.

That issue should be fixed in version 6.1 and up. Make sure you're using the latest build. If the problem persist please open a ticket regarding that.

Better to create a ticket regarding that and send us the diagnostic logs, we'll forward them to our Linux team.

Difficult to suggest anything, to be honest. Try using this cost calculator and see if the results are close to what you usually get from AWS: https://calculator.aws/#/estimate

Please select "Amazon Simple Storage Service (S3)" during the procedure.

Make sure you're mounting that share with correct user account that have appropriate access privileges.

For further investigation we need you to open the ticket in our support department, it'll be transferred to our Linux team.

Try this to ensure the files are in the cloud:

1) Specify the prefix of the old machine.

2) It is likely that the software will try to sync the files automatically, so please wait in this case.

3) Create a consistency check plan and make sure you're specifying the correct dencryption password. Please run that consistency check and wait for it to finish.

In general, we don't recommend enabling any kind of versioning or lifecycle policies on cloud containers outside of our software, due to the problems similar to yours, since the software may not be aware of some of the files being deleted in the cloud.

Yes, I understand that, and our Backup software should be suitable for that purpose. Feel free to check out the trial version, it comes with 15 days of full functionality.

Explorer is not designed for autmoatic uploads of large quantities of files, so the best way would be to try out our backup software.

Here's our help section that should be very useful during first-time setup: https://help.msp360.com/cloudberry-backup/installation/setup-wizard

At the moment there is a known issue related to machines having the same UUID , R&D is working on it. The only workaround I can suggest is to change UUID of one of the machines, that should help.

No info on that yet, still in testing. There will be a big announcement when the build is almost ready.

Simply editing the plan and removing the files from Source Selection will be enough. The files will stay on storage side, but the local copies will not be touched by our software anymore during the plan runs.

If it was an image-based restore on a live working HDD then not much can be done here. I can only suggest to try and use some third-party tool to salvage anything you can from that disk.
If it's available from another machine copying the data to a safe location, and returning the files there after initialization should work.

Looks like that was a temporary problem on Google Cloud's side, their services should be up and running now.

That's a known issue our R&D is working on.

For now please use Service Account authentication as a workaround. Here's a guide from Google that should help with the setup.

Here's the part you need.

Note that we do not officially support Google Drive anymore, so this workaround is applicable to Google Cloud and not Drive.

Hm, so do you currently have the latest version of the software installed on this 2016 machine? Checking out the logs would really help in performance-related cases like that, but before opening a support ticket try disabling the file cache:

- Click Drive tray icon and choose Options
- Select a mapped drive and press Edit > Edit advanced options
- Uncheck "Use file cache" option
- Find the cache directory in Options > Advanced
- Navigate to that directory with Windows Explorer and delete all its contents

#1
New UI should be introduced this year, but that's all behind the curtains for now. Added your feedback to the corresponding R&D task.

#2
Found the feature request you were talking about, I'll try to raise it's priority, but can't make any promises on it being implemented soon due to #1.