there should be details including the screenshot in the notification email. Are you sending notification emails? If not where are you reviewing the warning?

I don't think what you're asking for is possible to do with the product. If you unselect the files/folders, then nothing will be checked for retention, since only selected files and folders will be checked against the repository of what's in backup storage. I'll check with this team to see if there are any settings that can get close to what you need by avoiding backing up additional files.

What I'd probably recommend you do is just disable the backup schedule, and then manually remove the backups once you no longer need them.

I'll reply back if I get some additional guidance from the engineering team.

this is a known issue some customers are reporting with that version. It's expected to be corrected in version 3.3.1, but I don't have a release date for it yet. I would recommend you open a support case so the team can review the diagnostic logs. I've added your forum post to the open item.

I don't have a firm release date yet. It should be this quarter. I'll reply back when I know more.

I would say that you'll need to wait for the 7.5 agent release for the planned major improvements. In the interim, please continue to work with the Support team as they may be able to provide some options for improving performance over what you are seeing.

I normally would not suggest deleting versions older than 1 day. That does not provide much versioning for restore points. I guess it all depends on your negotiated RPOs with your customers. But if your customer changes a file and realizes they made a mistake and need to restore an old version, they may not be able to with those settings. In addition, if your customer is hit by some ransomware that encrypts the files in place, rather than renaming, encrypting, and deleting the originals, they may not be able to restore. I realize you have a 90 day delay on the purge, but I would rather see you use a 90 Day Retention, a specified number of versions to keep for each file, a shorter purge delay, and possibly a longer retention for locally stored files (you can have different retention settings for local and cloud).

Always Keep the Last Version will always keep the last version of every file. This is important in case a file has not been edited in 90 days, you do not want it removed from backup storage (usually).

If you are backing up volatile folders like browser cache folders and the like because they happen to be sub-folders, then my recommendation is to simply remove them from backup if not needed. Most customers do not run into issues where files deleted as a normal part of business results in noticeable changes to storage.

Support is going to get back to you in that open ticket - the team will continue the investigation.

Thanks for the update. 20 Mbit is slow. Was this an image or file backup? And are you using the new backup format or the legacy one?

They will be deleted according to the retention policy, separate from that setting. You can still select the Mark Objects as Deleted in Backups option in Advanced Options and any deleted files will be marked as such in storage. That way, you can avoid restoring deleted files. And those files that are deleted locally will be kept according to retention requirements like other files.

The option to which you are referring is not used by many customers for a couple reasons: 1. Most customers do not know when one of their customers (or themselves) will notice that they accidentally deleted a file and need it restored. So, they choose to not accelerate that deletion in backup storage. And 2. Ransomware - most customers do not want to delete files in backup storage in case a customer is hit my ransomware.

James, my understanding is that the 7.5 Windows Agent release will include additional restore performance improvements. Is your download speed running at 20 MegaByte or 20 MegaBit per Second?

I would open a Support case. I am unaware of any limitations on object names. You could try a test on a folder without a space and see if that has the same issue. As an alternative, you can copy the object locally and then back to the new B2 folder.

My understanding it that the Support is working on this with the engineering team. They will reply to you shortly with a suggestion. If you do not hear from them today, let me know.

Can you reply or DM me with your support case number?

Yes, that's it. So, you can get Desktop pricing for $2 / Month (instead of $10) if you use the MSP360 AWS storage option. But you have a choice in storage providers if one of the others provides the features / pricing that works better for you. In that case, you'll pay the retail price (before discount) for the Desktop licenses, but you may pay less for storage - depending on your storage needs (region, features, etc.)

Can I assume that maybe you are not a Managed Service Provider? MSPs get special reseller pricing. For internal IT use (non-MSPs) the cost is higher. If you are an MSP, then your Account Manager can help fix the issue.

if you've signed up for the service, the first time you click on storage you need to select the MSP360 powered by AWS option. At that point you should get a message that desktop licenses will be charged at $1 per month. If you then go ahead and select a different type of storage you'll get a message that the desktop licenses are going back to the normal price. I don't know where you're seeing the $2 price, so posting a screenshot would probably be best. If you signed up for the service however you should be in contact with an account manager who would be best to help you.

I would say to make sure you are backing up the needed system volumes for the image backup. You can also schedule periodic Restore Verification from the backup plan if you have an available Hyper-V instance. More information here: https://mspbackups.com/AP/Help/backup-and-restore/about-backup/restore-verification

As far as retention, set the Retention Policy for however long you need to keep backups. If you do not need GFS, then you can use the "Keep backup For" option to keep backups for as long as needed. Use GFS if you need longer term GFS retention or need Immutability support for the backups.

Synthetic fulls are supported on all clouds currently except Google Cloud. If you're backing up to a local target, then you'll have to run period fulls, but that's no different than the legacy format for image backups.

As far as the File Backup goes, the same applies for retention needs. For the Full backups, synthetic support is best to avoid having to back up all the data every full backup. If you do need local support and none of the GFS options are needed, then you can stick with the legacy file backups that have version-based retention and no need to run any subsequent full backups.

That's your server name and password. We do not manage any credentials for the stand-alone backup product's web interface.

can you post a screenshot please or what you're looking at?

It sounds like you're using our standalone cloudberry backup product, when you probably should be using our MSP360 managed backup. Managed backup does everything you need, including automatic agent upgrades and centralized management through our SaaS console. I would check it out on the website and reach out for a demo and do a trial. If you're going to stick with the standalone product, then there are silent MSI install options. I would check the help for that information.