Are you certain that is not the name of the folder on the Linux machine? I do not think that is coming from us, but I can ask Support.

So you are saying you followed the directions exactly as detailed in article I posted:
1. Registered the same cloud storage exactly as you used previously
2. Selected the same Bucket
3. Ensured the backup Prefix was the exactly the same
4. Waited for the repository sync to complete (and you are not using AWS S3 Glacier)
5. Verified your old backups were showing up in the Backup Storage tab
6. Created a backup plan with the same folders selected

Last question: Same version and distribution of Linux? If so (or not) what Linux are you using?

It's not Advanced tab in Settings. It's in the Storage configuration. Is that the same place you are saying you checked when you say "Storage tab"? If so, are you positive they are the same prefix? Usually the data in the actual storage will use that prefix in the main folder - you may see something like the following as the main folder in backup storage (CBB_ followed by the PREFIX_NAME).

Each Storage has it's own prefix option, so please check the new machine against the old one and also verify what root folder names were created (if different) on the old and new machine.

Did you give the new machine the same backup prefix as the old one? If not, that's why. If you did, we'll have to look into it further.

https://www.msp360.com/resources/blog/how-to-continue-backup-on-another-computer/

Are you running the download from a local disk? If not, please try that.

Check your Task Manager - Startup tab and see if you have Drive starting. If so, disable it from that screen. Restart the PC and see if the service loads fine without the UI. If that does not address, I recommend opening a Support case. I suspect this is something the support team could figure out easily.

Please continue working through the ticket that's the best way.

That shouldn't be happening, which makes me think that you're trying to run the app somewhere, which would naturally load up the user interface. The app doesn't need to be loaded at startup as it loads as a service. That might be the issue.

Can you also clarify how you purchased Managed Backup? Did you subscribe from us directly or did you subscribe from a partner? I have the sales team looking into your licenses, but any original purchase details you can provide would be appreciated.

I requested an update a couple days ago. But if you have a support case open, please follow up with support. If you're waiting on a reply, email them back for an update.

They should be visible in History. If you're not seeing them , you'll need to post an image of that screen so we can see what settings you have. Also describe what your backup is doing.

Sorry this post went unanswered. I'm guessing you may have already found a solution. But what I would recommend is that you create the Restores using the management console and have them run on installed agents at your customers. As an example, if you have a server that you are backing up, create the recurring restore operation on that agent. Or, if this is a one-off restore, you can also create it from the management console on the agent to run once and then disappear.

Sorry Rich that this post went unanswered. You may have already found a solution. I don't think any of our products fit your use case exactly.

I was going to suggest our CloudBerry Drive, but that product is more geared for exposing the cloud as local storage. And it sounds like what you need is the files really stored locally on each instance for best performance and that is more file replication. I would suggest you look for a product that can replicate your main S3 storage to multiple other locations. While our Explorer product used to have folder sync capability, that feature has since been removed.

If I misunderstood your use case, please let me know.

If you're on maintenance, Support would like to check the logs and config in order to provide as proper answer as possible in this situation.

To send them via GUI:

Please send us diagnostic logs by going to Feedback in the program menu. In the opened window click Send button.
The logs will be sent to our support team automatically. This will help us diagnose and troubleshoot the issue.

Please DON'T send us the log file attached. The log file will be sent automatically.

CLI for Linux standalone:

If that doesn't work please send logs via command line (please note case sensitivity):
"/opt/local/CloudBerry Backup/bin/cbb" sendLog -u "how we should call you" -e "your contact email" -m "Logs for ticket #00060066"

Or create the log archive locally by this command:
"/opt/local/CloudBerry Backup/bin/cbb" saveLog -p ~

The archive file will be placed in the home directory of the user currently logged in.
Please send it to us attached (if it is too large - upload to any file hosting and send us download link)

Does the new share have the same name as the old one? If not, is there a reason it cannot have the same name? If you need to use a new share, then I think what you can do after all the data is copied over to the new share is simply change the storage account to use the location. And make sure to change the old credentials with updated information. If you have already tried that, then what I need you to do is reply back with specific steps you have taken and the result of each step. Thanks.

The product runs as a Service and should be loaded automatically at OS start time and show up in the tray automatically. Are you trying to manually run the product in another manner? Any details would be appreciated.

We have an open request in the system for this feature. I have added your request to the open ticket and someone will get back you if the feature is officially scheduled. I will ask the team for any idea about how you might implement what you need in a different way. Stay tuned.

Hard to diagnose these types of issues on the forum. I recommend if you're using a paid version of the product that you open a support case using the Tools - Diagnostic toolbar option and the Support team can review the logs. If you're using the free version, then I'll reply back if Support has an answer for you on this issue. I do know one customer who reported something similar was able to restore on a second execution of the restore. SO you may want to try that.

We deprecated many of the cloud vendors what were not being used by our customers. I'f you lookng for low, long-term archival storage tier pricing, then your will find many options from AWS, Azure, and Google Cloud. Also consider Wasabi or Backblaze B2 for low cost, hot storage.

Can you verify the Service Account method worked for you?

I’m checking with that team on the release date.

They know it’s the free edition and are waiting for you to open the case. If they tell you otherwise, you let them know I and Anton T requested you get to open a case.