The new backup format is not compatible. If you want to use the new backup format to take advantage of any of its features with file, image, or VMware backups, you’ll need to create a new backup plan. You can keep the old backup data around as long as needed and then manually remove. If you prefer, you can stay with the legacy format if you're happy with it.

The new backup format has a some advantages, especially for image and virtual machine backups and file backups that have a large number of files. There's support for client-side deduplication, automatic consistency checks, Change Block Tracking for Image/VMware, Restore Verification for Image, generational backup retention with GFS-style Retention, immutability options with Amazon S3 and Wasabi, and synthetic full backups for all backup types when backing up to supported clouds (Google is not yet supported for synthetic fulls).

The new backup format does not yet support hybrid backups and does not perform synthetic fulls for local backups. It also requires periodic full backups of all data, unlike the legacy file backup format which is incremental forever. So this may not make it a good option for you if synthetic fulls are not supported on your desired storage target.

You can read more about it in the online help:
https://mspbackups.com/AP/Help/backup-and-restore/about-backup/backup-format
https://mspbackups.com/AP/Help/backup-and-restore/about-backup/compare-formats

Let me know if you have any questions.

If you tried calling and everyone was tied up, then leaving a message is the best way to proceed. This will get resolved. The other option is to open a support case on the web site here: https://support.msp360.com/

Yes. When 7.2 came out the console hadn't been updated yet. And 7.3 is out now as the latest agent version so you may want to consider looking into that version.

https://mbs.cloudberrylab.com/AP/Help/whats-new

You must be looking at old information from an early release. You can edit and manage the new backup format from the console.

That request is already in the system. In the meantime, you can simply right click the help item and open in a new tab to avoid the current implementation.

I sent this over to Support, but please reach out. If you signed up for maintenance, then you will automatically be charged the next term unless you cancel the maintenance renewal. If you forgot to cancel, then reach out to the team and they will assist you.

Michael please contact Support or your Account Manager immediately and they will remedy this for you . This is not something I can do for you from the forums. I will pass this to Sales, but they'll need a call from you.

You should be able to create a rule for this within the product. The issue with rules was addressed with the 180 version sometime ago. Can you verify what version you're running and if there was a reboot after the upgrade to 1.8? Also check your rules because if there are multiple rules for that file type, then only the first rule is applied on upload.

if you're using the legacy format for file folder backups, then they are incremental forever. The only time we do a full is the very first time. After that only new and change files are backed up. If you use the new backup format for file folder, then yes you will have to run a periodic full of the data, and the same thing applies to image backups with the new backup format. That is, synthetic full backups will be performed on the cloud storage providers I mentioned and will not be performed yet for local backups. For that reason, you may prefer using the legacy backup format for file folder backups if that's what your need is. I do not recommend performing image-based backups if you only need file backups, but some customers do that and if that's your case and that's what you prefer then that's fine.

Can you confirm you are performing Image backups and not File/Folder backups? If so, then synthetic full backups are only currently supported with cloud storage (Amazon S3, Wasabi, Backblaze B2, and Azure) when using the new backup format. The legacy image backup format does also support synthetic fulls to a few cloud storage vendors.

For local backups on the free version you can store up to 1TB in backup storage. If that's not enough you'll have to move to a paid version.

Are you a managed backup customer? If so, you can use the online help. https://mbs.cloudberrylab.com/AP/Help/gapps-office365/get-started

If stand-alone, use that Help site: https://help.msp360.com/cloudberry-backup-for-ms-office-365

There are also detailed configuration instructions here (some of the info might be dated in this PDF but still provides a good overview): https://www.msp360.com/download/Configuration-Guide-CloudBerry-Office365-Backup.pdf

is what you're asking for is the ability to use Linux to connect to remote systems like Windows and Mac? Or you looking to connect to a Linux system remotely?

if you're only doing file backups, then the legacy format would work for you. There's no such thing as a full backup when doing file backups with the legacy format other than the initial full. Everything is incremental forever. You'd miss out on some of the newer features like GFS immutability client side duplication automatic consistency checking etc. But some customers find the legacy format works just fine for them for file-based backups.

Well... moving all the metadata for every backup to the portal would be a complex process with security implications. We could have search in the portal at the endpoint level though. But moving details for hundreds of millions of files to the portal and securely managing that data would be a big undertaking, despite the flexibility it might offer.

this went out today.

Log4j Vulnerability does not affect MSP360 users

Dear Customer,
Maintaining your security and business continuity has always been MSP360’s top priority. 
Yesterday the Apache Foundation released an emergency update for a critical zero-day vulnerability in Log4j, a logging tool included in almost every Java application. 
The problem revolves around a bug in the Log4j library that can allow an attacker to execute arbitrary code on a system that is using Log4j to write out log messages. This security vulnerability has a broad impact and is something anyone with an application containing Log4j needs to immediately pay attention to. 
This vulnerability does not affect MSP360 or Cloudberry users.
If you have any additional questions or concerns, please contact securityatmsp360dotcom.
We appreciate your continued partnership.

Thank you,
The MSP360 InfoSec Team  |  MSP360

My understanding from the team is that Searching is not yet supported when using the new backup format for file backups. We could have done a better job communicating this in the UI. There is a feature request in the system already, but I don’t have a date at this time for when it might be released.

it's a known issue and will be fixed in the next build. But the option really has no effect if you're using VSS with the backup.

depends on many factors. Source file size, compression, broadband speed, etc…

I’ll have to ask Support. There are no specific settings.