The Virtualization guided setup guides you through creating a server plan, adding a hypervisor, and adding a VM group.
Caution: Because OpenShift applications do not have a UUID or GUID to uniquely identify each application, the Commvault software indexes each application with an ID in the form project_name-application_name.
If you delete an application and later create a new application for the project that uses the same application name, the backup history for the new application is indexed using the ID that was created for the original application. In that scenario, restoring from a backup job for the original application might overwrite data for the new application, resulting in data loss.
Before You Begin
Complete the Core Setup Wizard.
Review the information in Red Hat OpenShift: System Requirements.
Identify the OpenShift access URL.
Obtain administrator user credentials or a service account and token:
A user account that is used to access OpenShift must have the storage-admin or cluster admin role assigned.
A service account that is used to access OpenShift must have the cluster admin role assigned. If you are using a service account and service token, record those items so that you can enter them when you add the hypervisor.
Obtain Gluster host SSH credentials for Gluster FS endpoints.
To identify Gluster hosts, use the fully qualified domain name (FQDN) or IP address, exactly matching the entries that are returned by the
oc get endpointscommand.
If you are using a passphrase and key to access the Gluster host, copy the key to a location that is accessible from the CommServe system.
The user account that you enter for the Gluster host SSH credentials must have root permissions or be part of the docker group. You can run the following commands to add the backup_user to the docker group:
usermod -a -G docker backup_user
To create an access node (VSA proxy), install the Virtual Server Agent (VSA) package on one or more client computers, which can be outside of OpenShift.
At least one machine must have the VSA installed. For more information, see VSA Proxies and File Recovery Enablers for Linux.
If the setup page is not displayed, from the navigation pane, click Guided setup.
After you complete the core setup, on the Protect tab, click the Virtualization tile.
On the Create server backup plan page, type a name for the plan, then provide information about storage, retention, and backup schedules. For more information, see Creating a Server Plan.
If you configured a server backup plan as part of the Core Setup, the wizard skips this page.
The Add hypervisor page appears.
Provide the following information:
Select vendor: Select Red Hat OpenShift.
Hypervisor display name: Enter a descriptive name for the hypervisor.
Select one of the following authentication methods:
User name and password: Enter the user name and password.
Service name and token: Enter the service account name, and then copy the token into the Service token file path box.
A service account that is used to access OpenShift must have the cluster admin role assigned.
Access node: Select a previously deployed proxy.
For Gluster host SSH credentials, click Add to add a Gluster host and credentials.
The Gluster host SSH credentials dialog box appears.
In the Host name box, enter the fully qualified domain name (FQDN) or IP address of the Gluster host, exactly matching the entries that are returned by the oc get endpoints command.
Under Authentication, select one of the following options to provide credentials:
Username and password: Enter the user name and password.
Username, key and passphrase: Enter the user name and passphrase, and then click Choose File to select the key.
On the Add VM group page, type a descriptive name to identify the VM group, and then select virtual machines to be protected.
To finish, choose one of the following options:
Click Back up Now to perform an immediate backup of the virtual machines in the VM group (without requiring confirmation).
The Job details page appears and displays job status information.
Click Do it later to go to the hypervisor page without performing a backup.