That's true. But the full backups are synthetic fullls using all the bits and bytes already in the cloud to create the next set. So if you create a full backup every week then you'll have a new immutable backup weekly. Does that help? If not please describe your retention settings and a little more detail and maybe I can offer an alternative solution.

have you inquired with pCloud to see if they plan on adding an S3 compatible API interface? Most of the cloud storage providers we work with like Wasabi and Backblaze B2 offer S3 compatible APIs and since we have an S3 compatible connector that makes it easy to integrate. At this time I don't think there are plans, firm anyway, to support PCloud. Can I ask in what region you're located?

Can you confirm you are creating a Restore Plan from CloudBerry Backup to restore the files? You can see the backups and when you run the restore plan, you get the error noted above?

What type of backup were you running, file or image?

CBL are archive files and must be processed by the restore engine. That may also contain incremental backups of files, which makes restoring more involved than a simple extraction.

I meant the version of our software.

What type of backup are you running? File, Image, etc.?

I have done some research and see a similar issue reported by a customer in version 7.2.1.49 with a fix scheduled for the next patch release. I don't have a date but it will likely be around November 9th or 10th. I would recommend you open a support case to verify if it's the same issue and if Support has a work-around or if a pre-release agent is available for testing.

If you're restoring from another computer, you'll need to follow the instructions in this Help article: https://help.msp360.com/cloudberry-backup/restore/about-restore/restore-from-another-computer

thanks Steve. Here's the original post. https://forum.msp360.com/discussion/2386/could-not-create-ssltls-secure-channel-backblaze-b2

Version?

what's your backup target for these backups? Also can you clarify the version of the agent and the type of backup you're running. Thanks

The new backup format has now been integrated into the console so you can start using it in remote deploy if needed.

Can you explain what an ALOUM object is? I was not sure, tried Goggling and found nothing.

Doing a little research, I do not see an issue with backing up the local OneDrive folder.

I think you'll need to keep your Setting to "Always keep on this device" if that addresses the issue.

We back everything up by default. We leave it to the customer to decide what does not need to be backed up. There are no default exclusions unless you have the don't back up system and hidden files option checked in the backup wizard. You can Google what file types and locations are not likely needed for backup and you'll probably get a bunch of resources that will list out Windows folders and the like that may help assist. I've been speaking to the team about whether or not we should post a list ourselves, but I haven't made a final decision yet - it's under discussion.

Not that I'm aware of. Normally I would just suggest you use our Office 365 product to back up data in OneDrive. I'll do a little more digging this afternoon see if I can find a solution for you, but right now I don't know of any.

I think that makes sense given that onedrive is a cloud-based storage service with some locally cached data and pointers to the cloud data. If the file is not persisted locally, then there would be nothing to copy to S3.

I think the answer to that is, it depends. It's going to depend on how large the OST files are in relation to the rest of the data being backed up. But before you exclude any files please make sure that they're OST files which are just cached copies of emails and calendar and contacts from the server versus a PST file which is an actual email archive or may even be used as the main mailbox when using POP3 email servers. But I think you'll have more luck excluding other folders that are absolutely not needed for backup, whether that backup is a file folder or image backup.

if you no longer need that service account because you're decommissioning all backups for that customer on all endpoints that use it, then you can use that option You mentioned. Or are you just looking to delete specific endpoints? I'll have to double check the option you're talking about cuz maybe it can do what you want if it's just specific endpoints, but let me know.

For File Backup, you can go to Reporting - Backup History and search for the endpoint and find the backup execution in question. Click the execution on the date in question. Once the sidebar opens, click the Details tab for a list of files that were backed up.

If you're referring to Image backup, then we are not backing up files, so there's nothing to report in that regard. The best you can do is to exclude files / folders that are not needed for the restore. Temp folders, Cache Folders for browsers, log folders, hibernation and pagefile / swapfile (if not needed), etc.

Nov 1 is the planned release date.

officially, windows 11 will be supported in the 7.2.2 release. I'm working on a release date for you right now, but it should be soon.