Approx., in October, 2018.

Hi Jose,

The upcoming release should fix this issue.

The speeds you see relate to controlling requests only. The real data is transfered inside Amazon thousands times faster.

Hi Fernando,

1) Unless you are using Archive Mode, you can rename backup plans, and you won't have to reupload. To rename, click Edit and pass through the wizard, changing just plan name.
2) To delete files in Glacier, you go to Backup Storage. But, unless you are using Archive Mode, Backup Storage is not connected with backup plans anyway. So, the short answer is "no way".

Circular Logging is a mode not recommended for Exchange server. CloudBerry Backup will work anyway but enabling the circular logging can lead to losing some data put to Exchange after the latest backup in case of subsequent restore. Yes, CloudBerry Backup triggers logs truncation after successful backup.

Glacier job might be "broken", it happens sometimes. In this case, the only solution is wait a day, better two to be sure bad job has gone, and try again.

Unfortunately, the reason of this issue is still unclear. You can try another PowerCLI build, or try to connect to vSphere/vCenter newer than 5.5, if this is an option for you. I this case, the software will use newer DLLs.

Hi xlntech,

If you have the PowerCLI installed, please try removing it and reinstall Backup again.