Let me add that the Windows maximum file name length is 32,767 characters. You can easily enable long filename support with a registry or group policy edit. https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

But I want to confirm with the team this is fully-supported for backups, so stay tuned.

I am not sure why the names are so long. I will log your request and ask the team. Thanks.

It's simply a current limitation in the product. It is scheduled to be released in a future version. I'm checking with the team now to see if it's officially scheduled yet.

If you just want to quickly remove the backups from storage and you're sure you do not need to be able to restore any old versions, then you can quickly delete the main backup folder in B2 from the Storage tab in the agent.

These issues are hard to diagnose over the forums. I'd recommend you open a support case so the team can review the logs to see what's going on. While 3.x has been available for some time, and you can certainly use it to see if it addresses the issue, I think the best option is to speak with Support and get some guidance from them.

Let me add that if you have already moved the data, depending on your backup folder selection and retention settings, the backups may already be deleted or flagged for deletion.

If the original folder were kept in the backup plan, then we would see the movement of the data as deletes of the original files and then file backups would be kept according to your retention settings.

If you moved the files and also changed the folder that is being backed up (and removed the original folder from the backup plan), then the old backups will remain indefinitely in backup storage and you would have to manually remove them when they are no longer needed. Since the original folder is no longer a part of the backup plan, retention for those backup files will never be triggered.

I do not believe that's possible. If you moved the data to a new location, then you'll need to back it up again to Backblaze B2. You can sync any folders with OneDrive if you're using the OneDrive sync client. So you may want to move the data back and add the location to OneDrive for sync. https://support.microsoft.com/en-us/office/choose-which-onedrive-folders-to-sync-to-your-computer-98b8b011-8b94-419b-aa95-a14ff2415e85

Jeff, it's an interesting question without an easy answer.

The backups are in a proprietary format. Any program that needs to restore these files would have to come from MSP360. I realize that some files may be backed up in whole, and you could make the case that a backup of a file that contains the entire file could theoretically be decrypted and decompressed using some technology outside of MSP360. In order to do that we would likely have to use either some open standard / open source method (like a ZIP files) or provide source code to the community. Unfortunately, that's not how the product is engineered. But even that option would not work with block-level backups, filename encryption, or any new backup formats that we are working on (wink wink) to improve the product.

I suppose we could say that should the company ever go out of business we would make available a version of the product that could be used to restore files. And I'm certain we would do that if this doomsday scenario ever played out (despite our growth and having no plans to go away).

I've been in the backup and disaster recovery space for a long time and the companies I've worked for have made restoring easy, despite them having proprietary formats. And it's more than backup and disaster recovery. You're trusting many SaaS companies with your data for hosted applications like O365/G Suite, Salesforce, password managers, private / public clouds, BDR, etc.

One thing you can do is restore any important files, if needed, and then encrypt them yourself and copy them to cloud storage using a product like MSP360 Explorer. Stick them in low-cost, archive storage or on a hard drive you own and keep them for the long haul. Managing this could be prone to its own issues though.

What have you seen, if anything, from other products that helped relieve you of these concerns?

This is a known issue. I'm checking with the team on what version we can expect the fix.

The ID comes up when you launch the product right in the UI. If you're looking to connect to a remote system you'd have to ask the user to give your their ID or if you are managing the computer remotely, then you can connect and note the ID.

Backup Prefixes are not needed in Restore Only Mode. The product scans for all computers backed up and let's you select what you want. In the case of deleting old backups, its best to do that from the Storage tab and not from the storage account directly. If you delete from B2, we don't know about the deletions and you'll need to Sync the repository. But you can have different backups in the bucket. As I mentioned in the previous post, backup types are broken up within the computer prefix in storage.

I'll ask the team about why you were not seeing anything in storage until you switched license types.

If you are not seeing any backups listed, then we need you to check your B2 storage to confirm what you see in the cloud. You would normally see the cloud account in the list, with sub-folders for Images (if they were run) as well as drives that were backed up using file/folder, SQL Server database backups if you used that product, etc. Because you're not seeing anything, we need you to check your storage to verify if anything is there.

Feel free to reply here with any updates.

Can you also confirm the product version you are using?

Are you saying you followed these directions, but did not get a list of computers to restore?
https://help.msp360.com/cloudberry-backup/restore/restore-only-mode

What did was fine (using trial mode) but you should be presented with a list of computers on the backup target without any need to perform a sync.

Should just be an informational message that certain files were skipped as they were excluded from backup. I think if you examine the History for the backup plan and look at the messages, you'll see they were not supposed to be backed up because they did not meet the criteria for backup.

I'll let the team know. Thanks for the update!

Do this instead: Change the Retention to use the Modification Date instead of the Backup Date. Then you can Uncheck the "Always keep the last version" option. Then backups will be kept for only 15 days from the modification date and then removed. I think that's what you want.

What is your old open ticket?

Let me also add that you do not have to use Block-Level Backups. Especially if you either do not have a need or do not want the added complexity in scheduling and retention. They are optional, and if you ignore that scheduling option, then you can think of backups as incremental forever. Every time a file changes it will be backed up in full.

Incremental backs up the entire file each time it is changed. Block level only backs up the changes within the file to save storage and reduce backup time.

your feedback is welcome. Please continue to provide any feedback on the forms regarding the product. Regarding file transfer, there are updates planned for a future release that will provide the functionality you’re looking for.

That's what it is. I agree the terms can be confusing. Some of that has to do with the flexibility in scheduling what we call incremental and block-level backups. We allow you to schedule them, so we have to give them names :-(