Here in May 2022, I would like to get an update from MSP360 with respect to the filename-to-object naming issues when using S3-compatible storage targets. This includes both the ‘filename too long’ issue and the ‘unsupported symbols’ issue.

I understand this is not a defect or design deficiency with the MSP360 family of products. I understand this is equally not a defect or design deficiency with respect to the various S3 targets like Amazon AWS S3, Wasabi, MinIO, etc. Finally, I understand that MSP360 is not alone in this challenge, in that other backup and data transformation products from many other vendors share this interoperability issue when it comes to object storage.

I know there are *workarounds*, as MSP360 has documented…

https://kb.msp360.com/cloud-vendors/general-topics/unsupported-symbols-in-filenames

I’m posting because I found the following press release dated 2021-10-26…

https://www.prnewswire.com/news-releases/msp360-adds-immutable-storage-for-aws-and-more-than-a-dozen-new-features-to-cloud-backup-solution-for-managed-services-providers-msps-and-it-teams-combating-ransomware-301408310.html

This press release contains the following bullet/statement…

“Support for any filename characters and extra-long filenames. The MSP (and its users) no longer need to care about file names to back them up.”

However, I could not find this same press release within the ‘Press Center’ content area of the MSP360.com website…

https://www.msp360.com/company/media/press-center.aspx

…So, I’m trying to learn if this press release was *retracted*, possibly due to inaccuracies related to this exact feature announcement.

I use and like the MSP360 solution, so this inquiry is not intended to be contentious; I’m just trying to understand our current status with respect to the infamous filename-to-object interoperability issue.

Thank you!