If the CloudBoost appliance encounters a failure you must deploy a second CloudBoost appliance to restore the metadata from backups in the cloud.
This article lists the system requirements for running CloudBoost, giving details of supported public and private clouds and NetWorker server versions
You must configure the shared data store immediately after you have deloyed the CloudBoost virtual appliance.
Verify that CloudBoost is receiving clones from NetWorker.
Connect NetWorker to CloudBoost to send a NetWorker backup clone to CloudBoost.
After you configure the CloudBoost virtual app via vSphere cli you can login the CloudBoost management console to configure its deployment settings.
After you have installed CloudBoost virtual appliance, you must next configure the IP settings and hostname for CloudBoost from the VM console.
This simple post provides the steps needed to install the CloudBoost virtual appliance in vSphere
Always download your Cloudboost Encryption keys at your earliest possible time as there is no way to retrieve them after a system failure.
The following table provides a list of firewall port requirements for CloudBoost for NetWorker.
The CloudBoost virtual appliance presents itself as a NetWorker AFTD. The enabled workflow is a clone operation to the cloud.
You can monitor the health of the systems and obtain basic statistics such as the amount of de-duplicated data, number of users, etc.
On the Support page, you can see what version of CloudBoost is currently running, and you can upgrade the CloudBoost virtual appliance.
NetWorker with CloudBoost enables long term storage provisioning via the cloud.