Deploy the software needed to setup the Distributed Storage servers and the proxies.
Edit the Ansible Configuration file, located in /opt/hedvig/samples.
A sample Ansible Configuration file for rack un-aware configuration is shown below:
If necessary, contact Commvault to get an Ansible Configuration File customized for your environment.
tmux(terminal multiplexer) session. This will ensure that the deployment process will continue if it is disconnected.
Set the root password using one of the following methods:
In the Ansible configuration file:
Using an exported environment variable:
export HV_ROOTPASS=<root password>
If the root passwords are different between the storage nodes and the proxy, then export the password as follows:
Where: ^^^ is the separator, and the deployment process will try all passwords.
Start the deployment.
hv_deploy -–deploy_new_cluster <path to ansible file>
hv_deploy -–deploy_new_cluster /home/admin/cluster.ansi
The following prompts will be displayed:
Specify an input method to define the cluster: 1) Load an Ansible inventory configuration file 2) View Ansible configuration file formatting information
Enter 1, as the Ansible Configuration file has already been prepared.
Specify the absolute path to Ansible inventory file:
Enter /home/admin/<Ansible Configuration File> or the location in which the Ansible Configuration file is saved.
Please enter the SSH password for <cluster name>
The SSH password must be the same for all Distributed Storage servers nodes and proxies.
Would you like to wipeout Hedvig Pages if any of these machines have been used in a Hedvig cluster in the past? (y/N)
Enter Y, if this is a new cluster, or if you do not want to preserve the existing data.
Enter N, if this is an existing cluster with data, and you want to preserve the existing data.
Would you like to enable mid-playbook restarting on this deployment? (Y/N):
Enter Y to enable this option, or N to disable it. This option allows you to skip the completed steps if the deployment is restarted later.
The deployment will be started. Depending on available resources, the deployment process might take 30-60 minutes.