Please open a case so Support can review and provide the details to the engineering team for a fix. Thanks.

Can you verify you're using the same version, and the latest version of the product, on all computers involved?

great.. let us know if you have any other questions.

I've seen other posts on the AWS forums around this message that indicate it can happen when you sign up for AWS but do not sign up for S3 specifically.

Please check the steps detailed in this article. If you've already done so, then we'll probably need more information in order to provide assistance. https://help.msp360.com/cloudberry-backup/backup-destinations/cloud-specific-settings/amazon/sign-up-for-amazon-s3

Just so you know, I had the same exact question I asked myself when I looked at GFS which is why isn't there a weekly option. So you're not alone. I'll reply in more detail to your recent question when I settle into the office in about an hour. I've been traveling to the ASCII conference in Chicago this week so I'm just getting back.

What you can do is select Daily and check off the one day of the week that you want to run the full. That's effectively weekly.

I spoke with Support and they are waiting for the logs to be sent. I've also passed on the info you provided in the previous post.

It's best to work with support on this as there's an open case already with another customer reporting similar false positives with sentinel one. Please submit the logs and work with the support team on a resolution if you're unable to whitelist the application using the posted sentinel one articles.

Are you saying when you look at the remote machine, you are seeing an alpha-numeric code instead of a numeric one like this?

Immutability / WORM support is coming - currently scheduled for August. I'll reply back with more details once I have them.

there's another customer with the same report in the system. I think the best thing for you to do would be to open up a support case directly with the support team. I've added your comments to that particular case. You can submit logs from that machine using the tools diagnostic toolbar option to get things started.

What is the program reporting? I think you'll need to follow whitelisting procedures with that product and you may be able to submit the binary to sentinel one for exclusion, but I'm not sure exactly what the report is. If you want to provide more details you can do so here

we'd have to examine the logs to see if there's anything relevant in there to indicate what's going on. Do you see any relevant information in backup history for that backup plan to indicate what might be going on? If not you can have a look at the logs to see if you can find anything in there. Or you can send the logs to us for examination if you have maintenance. Can you verify what Mac edition of backup you are using and version?

have you followed all the directions, including drivers, in this article? https://help.msp360.com/cloudberry-backup/backup/create-a-recovery-disk-flash-drive

So you are installing to the G: drive? Can you try an install to the Program Files folder? I'm wondering if you're having a security rights issue with that folder.

Please open a support case. If the support team asks, tell them that I was the one that instructed you to open the case. You can easily send the logs to support to kick off this process by using the tools diagnostic option and the toolbar.

Is the G: drive a local drive on the server or a mapped drive? Where are you grabbing that "execute" command from? Are you reading the msi install log?

Just to confirm, you are using MSP360 Managed Backup and have set up these storage accounts from the management console. You are using the Amazon S3 and Wasabi storage connectors and not the generic S3 connector. When you run a backup to either storage account, you see the error posted, correct?

Are you using a Windows agent? If so, is it a server or desktop? Version?

I think you'll have a much easier time working with Support on this one. I see only one reference to this error for Google Cloud that was addressed some time ago. It could be a TLS version issue, but in order to understand the error, the Support team is going to need to see the logs and system configuration. I would use the Tools - Diagnostic toolbar option on the agent or the RMM - Remote Management - gear icon on the endpoint in question - Send Logs option from the management console to get the support ticket created.

when you change the encryption password, we require that all the data be backed up in full again. Old backups remain in storage with the older encryption passwords unless removed by retention settings. We did this to make it easier to restore by avoiding having two or more encryption passwords in use simultaneously in the most recent backup of each file.