Hi , please check out this thread: https://forum.cloudberrylab.com/discussion/474/full-backups-refuse-to-run , the same thing is explained there.

In a nutshell, our "full" backup is incremental and "block level" backup is block-incremental.

, in fact, you don't need to use PIN for Unattended Access. That's poor graphics (we have improved the look in beta builds already). The right button is the arrow button, or just press Enter.

The credentials are for the user from the remote PC (or domain credentials, if you connect to a machine in domain). We will also make it more obvious by the next major release.

Thanks for your feedback!

, wow, thanks for the details! Noted.

We plan to include pre-backup and post-backup scripts execution by December (depending on how the testing stage goes, of course).
For the sake of experiment, you might want to start backup manually using the CLI, here's the guide for it.
This way you can't really pass variables from the backup process to the script itself, but it's something.

fixed the image above

Hi , this is how it is supposed to work - the "full" backup is incremental. It makes full versions of files that have changed since last full backup.
As in,
day1 - Full version of the file A
day2 - Block version of the file A
day3 - new Full version of the file A
day4 - no Block version because the file has not changed
day5 - no Full version because the file has not changed compared to the last Full

and so on.

A good write-up here, please check it: https://www.cloudberrylab.com/blog/backup-types-explained-incremental-vs-differential-vs-full-vs-synthetic/

Hi . Sounds like a good idea. I will take it to the developers for discussion.

May I ask you what your environment(s) is(are) and what is the distribution of different filesystems you have?
As in, if you have 1 server with ZFS and 10 servers with BtrFS - that's valuable information.
You can also PM me (click my nickname -> Send a message) if you want to keep this info private.
Thanks in advance!

Hi , while indeed the question is not Linux specific, the option is available on Windows but not on Linux (yet).

Here is how it looks in Backup for Windows



We will support it in Backup for Linux too, although I cannot share an ETA for it now.
Adding your request to the list!

Hello , please check out my screenshots below, the wildcard seems to work perfectly for files - folder exclusions by filters will be supported in future.

Setting up a backup filter in GUI - back up anything that contains [trans] as a part of file name.


Same screenshot from the WebUI.


The folder selected for backup contains 2 files that match the filter.


Backup storage after the plan ran successfully.



It also works in CLI for addBackupPlan (editBackupPlan should allow it too, but apparently there's a bug). Related CLI guide

Hi , the error may still occur in rare occasions, we only fixed the most frequent case. A big fix for it will be implemented in the mid-term future, most likely by the end of the year

That's a CloudBerry error. Please use Feedback menu in the top panel to send the diagnostics - it will automatically open a support ticket.

check out this article, it's based on the Windows version but the Google Cloud part is the same: https://help.cloudberrylab.com/cloudberry-backup/signing-up-for-the-cloud/google-cloud/signing-up-for-google

Hi . We recommend using Google Cloud Storage, it is far better in terms of data safety and availability, and it proved to provide better experience to our customers in Backup for Windows.
Google Drive is not supported in CloudBerry Backup for Mac. It is a consumer-grade storage and we are making a business-grade solution (which later we might expand to satisfy the consumer too). Sorry, that's just not our priority at this point.

, you might also want to check out these two sources:
General Help - https://help.cloudberrylab.com/ - not much info about specific problems, but quite a bit of how-to's and explanations. If you use Backup for Linux or Mac - the link is different.
Knowledge Base - https://kb.cloudberry.online/ - it's heavily under construction now and might miss important things, but it seems to be closer to what you're looking for.

Let us know if there are specific troubles or questions that are not described in either of these sources.

Hi , thanks. Adding you to the lists.

We plan to add multiple-to-one (aka conference calls) in the next major release, and then one-to-multiple at some point in the future

Hi .

So the reason the resolution does not go back is that the default resolution was not passed from the remote host to the client machine.
It is supposed to be fixed in the next major update (v 1.7.5), you'll be getting "time to upgrade" notifications in the application.

Sorry for the inconvenience!

Hi , thanks for your detailed explanation!

It is not an expected behavior. We will most likely fix it by the next update.

Sorry for the inconvenience

Hi . It seems the Glacier Inventory in Explorer is outdated. You can trigger a manual update by using the Get Inventory button, see the screenshot

sorry wrong link. Try this one: https://help.msp360.com/cloudberry-backup-mac-linux/settings/backup-settings

Hello . We disagree, there should not be a reason for that. At least in the ideal world where bugs/performance degradation never slip into the versions available for download.
It's not me to make such decisions - but I doubt we will change the way it currently works (it would take quite some work to).
You can always contact Support and they will get you the version you need.

Also, if there is a specific reason you have on your mind - please share it with us.

Hello . Thanks for your kind feedback.

As a matter of fact, we strongly consider multiple-to-one connection in the nearest future releases. One-to-multiple is another thing we will probably implement at some point in future.

May I ask you to specify what the use cases are for both?
As in, what are the processes that require one-to-multiple and multiple-to-one connections?
Just for us to get a better understanding and think through the whole cases searching for important details.

Thanks in advance.