I understand. That is something we currently working on.

Yes, that is correct, but during uploads via our software we create specific folder paths that contain colons. That's the main reason we don't yet support Windows-hosted Minio.

The issue with Minio is related to colon characters being created during backup. Our R&D is working on that.

Currently there's no workaround for that, that's simply how file transfers always worked everywhere.

Yes, if any/all of these options are changed for that plan you would need to re-upload the whole data set.

Do you run Minio Server on a Windows machine? Due to technical limitations we don't currently support such configuration, so if that is the case please use Linux machine instead. We'll change that in the future. I already see your logs in the ticket system. We can continue discussion there and update this thread once the root of the issue is identified.

Yes, I understand the situation and we're working on that option.

Even when copying such amount of files locally such speeds are expected. Encryption and NTFS permissions might not slow the operation down on a small scale, but when dealing with large quantities of files these options affect the upload.

It is better to perform such oprations in the cloud after upload using Cloudberry Explorer to avoid conflicts like that.

Unfortunately issues like that are almost unavoidable when dealing with small files and large data sets. If you're backing up NTFS permissions and additionally use compression/encryption that makes things worse.

Looks like you might have missed something.
Make sure you've replaced all colon symbols in those folders with %3A and the folder structure is the same as on the source.

Those VMs that were excluded from the plan will stay on storage side indefinitely until deleted manually, retention policy will no longer be applied to them.

You can actually do that too, just make sure you're renaming "$" characters with "%3A". This is how we replace colons for storage destinations, since that character is forbidden. So you will see C%3A on cloud storage side instead of C: when looking at the folder path.

In short: colons are replaced with $ for local destinations and with %3A for cloud destinations. If you perform the procedure keeping that in mind everything should be fine.

Yes, you can do that, but after transferring the data from cloud to local destination you would need to rename all of the "%3A"(those are colons for your disk drives) to "$" characters. After that just synchronize the repository for local account via tools > options > repository and you'll be able to see that data on the backup storage tab.

Yes, that can be achieved. Just follow this guide: https://kb.cloudberrylab.com/kb1051/

1) The same rules will be applied here as with an image-based backup.
You need to schedule full backups to make sure purging is performed correctly
These settings will work fine, but note that if you de-select any VM from the plan that data becomes "orphaned" and will stay on storage side, so it's better to plan beforehand and make sure you select only those VMs that you want to back up.

2) The software will always back up the current state of your VMs no matter what snapshot you decide to restore.

3) You can ignore those messages. If your backups are successful then everything should be fine here.

As an additional suggestion I can provide this link with permissions required to properly perform backups using our software: https://kb.cloudberrylab.com/kb1078/

1) You would need to create a separate plan for that.

2) The same rules apply here.

3) If your local drive fails you won't be able to run that backup, so the only option is to make sure everything is in a consistent state and both destinations are reachable.

4)You can safely restore that data from the cloud, since the point of hybrid backups is to have data both on-site and off-site.

5) You would need that only in case you want a specific schedule for your backups according to your company's regulations. Otherwise you can use hybrid plan as it is if it suits your needs.

Hi,

Regarding your questions:

1) Every VM will be fully-re-uploaded if it was selected for that plan

The percentage depends on your preference, so 50% is a well-balanced default choice. It's a safe option if you don't want to manually set up schedule for full backups.

2) Snapshots performed outside of our software shouldn't affect your backup plans.

3) If there are any issues with VSS you will see the corresponding errors and the plan's status will be "failed". Unfinished uploads upon unexpected shutdowns are cleaned by the next plan launch.

Most likely there is still something in the system using VSS besides our software when you run it by schedule. You can try shifting schedule for that plan to non-working hours.

Another possible reason is that previous VSS snapshot has not completed properly and is still running. Try to restart the Volume Shadow Copy service. You can do this by going to Start > Control Panel > Administrative Tools > Services: find Volume Shadow Copy and right click and select Restart.

Event logs could also tell more about issues like that.

In addition I can also suggest to enable "Use System VSS provider" option for that plan.

There's still no ETA for that, although that's a highly popular feature, so it will be introduced soon.