While I confirm at my end, can you confirm what version you are using?

Managed Backup can update the agents automatically. Can you explain how you have things set up in case you're not using that feature by accident?

I'm guessing that's not an option though because of the connection issue. So you can ignore my previous statement. It's late in the day...

Looks like the new build has been published. I would try it on one endpoint. The fix has to do with an issue with some passwords that used extended characters that would prevent proper authentication.

There is a new patch release (7.7.0.109) coming out later today / early tomorrow. It has one fix that might address your issue. If you haven't already contacted Support, please try the new release when it posts.

requirements are minimal. They're on the download page on the website, and you can certainly review them when downloading the trial. But someone will need access to the server to install, manage the backup plans, and be able to run any restores, and you'll need to back up the data somewhere, so that server will need to be able to access the internet to back up to your preferred cloud storage, or have some local storage available in their data center that can be used for local backups. You'll also need to look at the feature matrix on the product page to make sure you purchase the correct edition, as there are limitations on data and shares that can be accessed with the product for different editions. You're probably looking at either server edition or ultimate Edition depending on how much data you need to back up.

Are you saying you want to back up your server that is hosted in the cloud? I guess the answer would depend on whether you have a dedicated server with full administrator access, or a shared server / shared services, Since you say you are using their managed service since you do not have the ability to manage the server at your end, I assume this is a service without full server control and access. You would probably have to ask your hosting provider to see what backup options you have. Generally they will will provide some means to back up your WordPress data - assuming that's what needs to be backed up. But if it's a dedicated server and you can get access to it, then you should be able to install CloudBerry Backup.

I'd recommend you go to support immediately for assistance.

I see an indication in the internal system that this error is addressed in 7.7.1. But that agent release is not been made available yet for managed backup. So, if you can't roll back to the version you were using previously, then I'll recommend you open up a support case. They may be able to provide a workaround or get you an early version of the next agent release.

Or it could be an internet connection issue. Either way, this will be much easier to resolve through support.

I hate to ask, but have you tried uninstalling the agent, restarting the server if possible, and reinstalling the agent. While I'm waiting for that answer, I'll see if I can find anything on that error code for you.

sounds like something happened with the user account you're using. Why don't you try changing it from the agent. Or, if you can see the endpoint in the management console, you can try changing the user account from there as well.

There is extensive coverage of all the benefits over the legacy format in the online help here: https://mspbackups.com/AP/Help/backup/about/backup-format/about-format

Here's an overview of the benefits:

• Grandfather-Father-Son (GFS) retention policy for long-term retention management
• Immutability - for backup data protection in the cloud
• Client-Side Deduplication to reduce backup data and improve backup times
• Consistency Checks to ensure backup data is present and correct
• Synthetic Backup for all backup types: file, image-based, Hyper-V and VMware backups
• Changed Block Tracking for Image-Based Backup
• Restore on Restore Points
• The number of requests to storage is reduced significantly (faster backups and restores)
• Uploading by data parts enables continued upload in case of network issues
• Support for any characters (emoji, 0xFFFF, etc) and extra-long filenames
• Automatic filename encryption (one password for generation)
• Real full backup for file-level backups (for generational retention of complete backup sets)
• Fast synchronization (reduced number of objects in backup storage)
• Plan configuration is always included in a backup
• Backup logs are backed up along with backup data
• Object size is now limited to 256 TB regardless of the storage provider limitations
• Much faster purge operations
• Faster backups and restores for large numbers of small files (file backup)
• Lower cloud storage costs for large numbers of small files for warm and cold storage classes

I would say the only considerations if you're using the legacy formats and will not greatly benefit from the new features:

• File Backup: If you need incremental-forever backups, stay with the legacy format. This may be an issue if you're performing large local file backups (there is no synthetic full support for local storage yet)
• File Backup: If you prefer version-based retention versus generational retention
• If you need hybrid backups - as opposed to running two separate backup plans with the new format
  

You need to run both incrementals and fulls. That's why you can't schedule the incremental when a full is not scheduled. If what you want is to run incremental backups for 7 days and then do a full backup on the weekends, then set it up that way.

Regardless, I would again encourage you to consider moving to the new backup format by creating a brand new backup plan that uses the new image-based format. It has a lot of improvements over the legacy format that you can read about in the online help.

Can I assume you're doing an image backup? If so, you would just schedule the incremental backup on the same schedule tab in the wizard where you scheduled the full backup. If you haven't already done so, I would encourage you to move to the new backup format. That would require you create a new backup plan using that format. You could remove the schedule from the old backup plan and leave backups in storage until they're no longer needed and then manually remove them. You can refer to the schedule section on this help page for more information. Let me know if you have any further questions. https://help.msp360.com/cloudberry-backup/backup/image-based/nbf

I cannot speak to the reason by Support that you move to the new backup format. If it's because of what the KB article talks about (millions of files), then moving to the new backup format may only be needed on those backup plans with a large number of files.

Generally speaking though, for those plans with large numbers of files, the new format has much improved backup and restore performance, plus client-side deduplication, synthetic fulls (new for file backups), GFS Retention, Immutability for Wasabi / Amazon S3 and soon for Backblaze B2, and built-in backup consistency checks.

As you've noted, the backups do require periodic full backups because backups are managed at the generation level - which is a full set of the data. On those systems where the source data is large, you can schedule less frequent full backups. And you may want to consider using GFS retention to keep data longer term, but with less granularity in restore points as the data ages.

Some of these settings are going to be dependent on your negotiated retention and backup contracts with your customers. You say you are keeping 2 years, but did not indicate if you're keeping all versions of every file, including files deleted locally, for 2 years, or you are keeping only a fixed number of file versions.

For example, on your 3 TB data set, you could:
* Run daily incrementals - or more frequently if needed
* Run a full backup every 3 months
* Keep backups for 90 days
* Turn on GFS and set Yearly backups to 2 years

With those settings you'll have all data kept for 90 days (you'll really back up to 180 days before the oldest backup set of 90 days can be removed). After the 90 days, you'll keep full backup snapshots for 2 years. So you may end of up with 4 full backup snapshots in storage plus up to 180 days of incrementals. Obviously, those retention and schedule settings can be adjusted as needed for your particular use case.

When using the new backup format, you'll need to set your schedule for incremental backups, for example daily, and also scheduled the full backup, say monthly. Full backups in the cloud will be run using the synthetic option, and will be created using most of the bits and bytes in the cloud combined with the latest incremental data. They'll run faster than running a full backup. Full backups to local disk will have to run in full. Schedule your full backups with the understanding that you'll have multiple backup sets in storage and weigh that against your retention requirements that will be set on the retention tab - which determine how many days of backups you're going to keep. For example if you're keeping 90 days worth of backups and you run a full backup every 30 days you'll end up with four full backup sets of 120 days, at which point the first backup set of 30 days will be removed from storage leaving you with 90 days. If you do need features like GFS retention or immutability, then you can enable those options as well on the retention tab. If you provide some details about what you're using now for retention, I might be able to provide better guidance on what the ideal options would be with the new backup format.

It looks like the prep step is complete as is the backup step. But in order to diagnose, Support would need to review your logs. If you could submit them to Support from the GUI, we may be able to provide some guidance on how to address. If not, what's I'd suggest is you try a test backup of a single file to your B2 account and see if that works.

For what purpose other than changing the user account? What are you looking to do? Are you asking because you want to be able to restore the backups from the old user account? If so, there is no way to do that explicitly without changing the user account.

Please let them know your results after the version downgrade. They’ll get that info to the engineering team for review and ultimately fix the issue. Thanks for your patience.

The current version of the agent is 7.6. You’re version is long out of support. I would strongly encourage you to upgrade to a newer version and see if the problem is resolved. You can find the Product Lifecycle here: https://www.msp360.com/ProductLifecycle.aspx

You can change the user account more easily from the management console - gear icon - edit user account. Once the user account is changed the existing backups will no longer be accessible on that endpoint. They'll remain in backup storage but they cannot be accessed from a different user account. You will have to go through all existing backup and restore plans and assign a storage account after the user account is changed. You will then have to run a fresh full backup on each plan.