Version?

Is the NAS setting up the target as a network share from the NAS software for access? Or are you using something like an IP address to connect?

This may need a support case since I'm unable to find any open issues with that error in the system. But reply back with the information requested and I'll see what I can find.

Did you install according to the directions in the article? Can you post the command you ran and also please note the OS and platform (x86 / x64). Thanks.

We have seen that product in the past report managed backup agents incorrectly; false positives. My recommendation is to open a support case with our team and submit the logs so they can review. They may be able to provide a method to whitelist the product in sentinel one.

which backup format are you using? Are using the legacy format or the new backup format? If using the legacy format then those backups are incremental forever. There's no such thing as a full backup with the legacy backup. All files are backed up with one-to-one correspondence between the file and object storage. If you're using the new backup format then you do need to run periodic fulls, and in the case of local backups currently, there are no synthetic full backups supported yet.

You can use Simple Backup Mode with CloudBerry Backup as described here. https://help.msp360.com/cloudberry-backup/backup/cloud-to-local/step-5-specify-backup-mode

That's not possible. Can I assume this is an image backup? Where are you backing up to? Cloud or local? The new backup format supports synthetic full backups to all clouds (sans Google currently). A synthetic full uses the incremental backup data to construct a new full.

I'm not really sure what you're asking. You can restore if you have an internet connection regardless of where that data is stored. Can you elaborate?

Linux is on the roadmap. Not sure of release dates at this time.

somehow I pasted the wrong URL. Please refer to this page on registering the powershell snap-in. https://www.msp360.com/resources/documentation/cli-api/msp360-explorer/powershell/amp/

Currently, the backup agent requires an internet connection to perform a restore.

Thsi is what Support reported to me (internally):

Have the customer sync repositories for both storage accounts (local and cloud) to make sure the information about the files stored is up to date. Then, run another backup and make sure the backup completes successfully. Technically, that should be enough.

If the customer still has issues after syncing both repositories and completing a new backup successfully, ask them to create a Support ticket.

Let me offer an alternative for you. You have 8 licenses now. You would find using our Managed Backup product much easier to manage and upgrade, and it comes without any storage limitations.

Subscriptions are available both monthly and annually (with an additional 20% discount) off the normal discounted price. You said you are backing up servers, but if you are using the product, or need to use the managed product, on desktops and you use our Integrated AWS Storage instead of B2 and Azure, you can get desktop licenses for $1/month ($2 for non-MSPs).

In order to make the transition easier for you, we would provide you some credits based on your original CloudBerry Server Backup licenses so you do not feel like you're losing your original purchase spend.

If you would like to speak to Sales for more information about Managed Backup and get a quote based on your needs, please use this link: https://www.msp360.com/contact.aspx/?category=sales

I also do weekly webinars on Managed Backup. There is one scheduled tomorrow at 12 PM ET. You can register to learn more about the product and see the advantages over the manually managed product you're using today: https://get.msp360.com/webinar/getting-started-with-msp360-managed-backup

Let me know if you have any questions.

I'm not saying that. It's only aggregate on the agent. I'll double check with the team to make sure it's not doing what you're suggesting, but I don't think it does. It uses the backup plans on that agent and aggregates all the data that's backed up based on the local data dictionary that's being kept. You mentioned earlier that you're backing up on alternate weeks to Azure and to B2, so my suggestion was to make sure that the total for all backup plans on each agent across both cloud storage providers is not over the one terabyte limit.

Each agent has a total storage limit of 1 TB for that license. That means, all backup data for all backup plans on each agent, have an aggregate 1 TB limit. If you're saying that one or more of the Backblaze B2 buckets for an agent has less than the 1 TB limit, then it's possible your storage need to be synchronized. A mismatch can happen if you delete B2 data from anywhere other than the agent's Storage tab. To run a consistency check, please refer to this help text: https://help.msp360.com/cloudberry-backup/backup-destinations/adding-a-cloud-storage/consistency-checks

You should know which agents are reporting the problem from the error messages.

And it's the total of B2 + Azure for each agent. Total across all cloud storage accounts for each agent. So, if you're alternating weeks, then you need to account for both storage targets. My guess are the plans that you showed in the screenshot that are both over 500 GB.

It's a collective limit across all backups for that agent. You can reduce storage by eliminating any folders from backup that you do not really need backed up. You can also selectively remove large file backups from the Storage tab that are no longer needed in order to create temporary space to allow backups to continue. You can also change retention as needed by reducing the number of versions you are keeping, reduce total retention time, as well as possibly removing deleted files from backup storage after a delay. If you need help, then please post your backup details for guidance.

You have it reversed. The managed products do not have any storage limits. However, all but the Ultimate edition of CloudBerry Backup have storage limits according to the product licenses. Please refer to this page for details: https://www.msp360.com/backup/windows.aspx

If you need additional storage, you should contact Sales or Support as they may still have add-ons available to purchase for the Server SKUs that can add additional storage for you.

I would request that you wait until the 7.4.0 release before you start using chained backups. The current implementation will always run an incremental backup on the chained plan. The 7.4 release will include a new option to execute the same type of backup that is being run on the main plan. You'll also have to make sure that your GFS settings are compatible between the two plans based on the main plan's schedule if you use GFS. You should also make sure that the chained plan has no schedule assigned to it.

please refer to the installation section of this article near the end:
https://www.msp360.com/resources/documentation/cli-api/msp360-explorer/powershell/amp/

I checked with engineering, and the changes are already in the planning stage and should be released with the 7.4.1 agent release. No exact dates for release yet. I will let you know when I have a date. The next release is 7.4.0 - 7.4.1 follows.

So, this is not O365/M365? We do have a solution for M/O365.