I'm checking with support to see if there's a limitation on the trial I just wasn't aware of. I'll report back when I hear back from them

also make sure that you don't use the customer build on the admin PC. That computer should just have RDsetup.exe installed. You can also check add remove programs in Windows and see if there are multiple versions installed and uninstall them all and install the main executable on the admin PC..

Are you saying on that last computer you have the agent installed but it's not recognized? Can you try reinstalling it?

What do you mean when you say one was recognized with multiple versions? Can you post any images to clarify what you’re seeing?Can you verify how you’re creating the remote installs for your customers? Please refer to this video: https://www.youtube.com/watch?app=desktop&v=nupwq6cvDZY

What about increasing their cloud storage. It's $23/TB/Mo on average in the US for S3-Standard and they'd only pay a portion of its use which sounds like a few dollars based on current use.

Which product? Managed Remote Desktop or the free version? I am unaware of any limitations in Managed Remote Desktop. There is a 5 Address Book limit in the free version.

I'm wondering if it would just be easier to ask the end user to scan their hard drive for very large files from Windows Explorer. With retention settings and multiple file versions stored for each file it's increasingly difficult to figure out which files are actually taking up the most space. There might be some single very large files, but there might also be 10 copies depending on retention of a slightly smaller file that collectively is storing more data in the cloud. Can I ask why remoting into the system is not an option?

let me semi-correct myself. You could go to reporting - backup history in the management console and review the backup plans for that particular endpoint. You'll see the files that were backed up with each plan and their file sizes, but that might require you review a few different backups to get a sense of what the big files are. You still need to remove them from the client itself on the agent.

there's no catalog stored in the management console, so you'll have to connect remotely to see what's being backed up and delete any files you no longer need from the storage tab. If you're not using file name encryption with S3, then you may be able to review the bucket on the S3 side to get a sense of file sizes, but you should not delete them from there anyway since you'll have to resync the repository and block level backups can make that difficult anyway.

I would also check to verify if you're on the latest version.

I'm going to recommend you open up a support case. The only reference to that I error I see in the system is one about virtual machine backups. Nothing specific to Wasabi or image based backups. It could be related to a VSS issue, and the support team could help you resolve it if that's the case.

Can you tell us what type of backup you are running and what your target is? Is there anything visible in the history screen for that particular backup plan that would indicate more about the error or the file in question?

That's correct. Cost depends entirely on how much data you have. By integrating with public cloud storage, you get to own your own cloud storage and are not bound by a persistent subscription to a service. You also get choice, which is great for our international customer base so they can select a cloud storage provider in their region without the need, for example, to send data from the EU to the US. And they get a variety of pricing models and cloud storage options, like storage classes in Amazon's AWS. Data is compressed and only file changes are backed up after the initial backup. If you had less than 1 TB of compressed backup data, your cost would be $6 / month with Wasabi, as an example.

To your other point. Cloud storage is not backup in of itself. Copies of data are subject to deletion and removal by the cloud provider if you use a product like OneDrive, which is only copies of production data. If you get hit by ransomware, the cloud would likely delete all the data as it's deleted locally, renamed, and you'd end up with a copy of ransomware encrypted files in cloud storage. Our product is true backup. You can keep any number of versions of your data and for as long as you need. If you're working on files actively for a job and want to keep 10 copies of your data, you can do that, and do so for 180 days while retaining the oldest copy so it can be restored any time past your retention period. Plus, all the data is encrypted using AES-256 encryption to prevent someone from getting into your cloud account and accessing your data.

Keep in mind we work with Managed Service Providers and internal IT teams with our managed backup product. We also work with a lot of small businesses and consumers with the paid CloudBerry Backup products - and these customers need true backup.

It may not be a good fit for you, but since there's a free version, you can play around with it, ask questions here, and see if it meets your requirements for what you need.

We integrate with public cloud storage providers. If you want your data protected off-site, in secure cloud storage, then you need to select a cloud storage provider and would need to pay for the storage. If you're concerned about cost, using a provider like Wasabi or Backblaze B2 would provide cloud storage at $5-6 / TB per month. If you only want local backups, then you can register a File System account and back up to a NAS or external hard drive at no additional cost. But we recommend cloud storage for most use cases to ensure your data is protected off-site.

You should disable the agent from Global Agent Options and protect the agent and CLI with a master password from Remote Deploy.

cloudberry drive is designed to expose cloud storage as local storage or a network share. We don't mirror the entire cloud environment. There is a cache and some files might be local, but the product will adjust the cache as needed. I'll have to check with the team to see if there's any way to leverage files that are already stored in the cloud.

you'll rarely get maximum downstream bandwidth speed when restoring from cloud storage. I haven't seen speeds that approach anywhere near gigabit speeds. The internet seems to have a lack of information on what the maximum download speed even could be. I'll have a conversation with the team about Glacier restores to see if they have any other information I can share with you.

trial license view is coming back in the next release, which should be out in the next week or two. It was a mistake removing it.

hard to figure out without looking at the logs. You can look at the logs to see which file is in question. You may also be able to look at the backup details right from the user interface to see which file threw the error to see if there's something about that file that's different.

I'm not aware of a feature to do that. I'll add your request to the system for the engineering test to review. You may be able to use a product like this to bulk change the dates. This is not an official endorsement of the product, but I believe I've used it in the past to do what you need. https://www.nirsoft.net/utils/bulk_file_changer.html