, thanks for your update. That, indeed, could have been the cause.
Feel free to update the thread if something similar appears again.
Thanks

,
check this video: https://www.youtube.com/watch?v=drMB1PO373g

, do you need to back up the host itself or guest VMs as well?

, ,
I'd add that in order to speed up the process, start a trial for Cloudberry Explorer that supports multithreading.
Also, to speed up the process, you can spin up an instance in Packet that has a direct connection to BackBlaze:
https://www.backblaze.com/b2/solutions/compute/packet.html
https://www.backblaze.com/blog/introducing-cloud-compute-services/
Also, it's free to move data to Packet from B2 (this will be a must when downloading from B2 and then uploading to another bucket in B2)
https://www.packet.com/about/partners/backblaze/

Hope this will help.
Thanks

Hi ,
https://github.com/aws/aws-sdk-net/issues/528
https://aws.amazon.com/premiumsupport/knowledge-center/presigned-url-s3-bucket-expiration/
I did a quick search to give you a link to AWS Docs, but I couldn't find it.
Anyways, according to the link above. V4 signature supports up to 7 days pre-signed URLs.
V2 signature that supports longer period has been deprecated this June.
Thanks

, what connectivity between AWS S3 and your on-prem server do you have?

Hi ,
How big is repository? Maybe it's easier and faster just to rebuild it from scratch (will be performed automatically).
Transferring is possible, but for that, you'll need to stop the backup service, change the location and start the service.
Thanks

, can you please tell a bit more about your use case?
Thanks

Hi, .
You should be fine as long as the SSL checkbox is ticked for the storage account of your choice.

As for the Cloud Service, you have a plenty of choices. We tend not to recommend anyone specific since we call ourselves storage agnostic vendor and we partner with many of them.

Thanks

, yes we do:
https://www.ssllabs.com/ssltest/analyze.html?d=mspbackups.com&latest
You'll see that we use TLS 1.0 (yes, for some users with legacy servers) 1.1, 1.2 with a bunch of ciphers.

I think you should be checking either your endpoint security software, the antivirus or the firewall.
Thanks

, I have just tested it and it seems that you need to have "Rebranding" permission to generate installation packages.
I'll file a feature request to make it separate.
Thanks

Hi, !
Please check out this article:
https://mbshelp.cloudberrylab.com/backup-and-restore/backup-agent/switching-editions

, it turned out, that the page was not supposed to be on the production server, but it ended up there.
I'll add you to the list manually and we'll keep you posted on any developments in this regard..
Thank you!

, don't want to confuse you, but we're working on 404 error. Android agent is not in the works as of now.

, please check here what we have in CLI:
https://help.cloudberrylab.com/cloudberry-backup/command-line-interface/managing-application-settings
Will this work?

, we're really sorry about that.
It's now being worked on.
I'll keep you posted.

Thanks

Hi ,
We decided to make it consistent with local backups (NTFS doesn't support colons in paths) to simplify data seeding and management.
It should work smoothly despite if you have put data to folders with colons before.
Moving forward we'll be introducing the new data format that will put everything into archives and there will be no such structure in the cloud (and it's not clear what's gonna be with Simple mode).

Please let me know if you have any other questions or concerns.

Thanks and have a wonderful weekend!

in addition to that we're adding some more features to lock down a user from changing backup settings and plans. More details to come.

, thanks for the update and the clarification.
Indeed, you can restore with no issues if the version with which you're restoring it is newer or the same as the one that was used for the backup.
Thanks

, how the files were initially backed up?
Looks like it was a backup to a local destination and then that destination was used as a source for cloud backup.
What you see is basically the file structure that we use for storing files on the backup storage. The numbers are a timestamp.
To get rid of this folders you can restore everything from the cloud and then use that folder as a source for one more restore job and restore files from there.

Please let me know if you need more details on how to restore it. And also try avoiding backing up backups.

Thanks