To restore OpenStack data on the same location as your backup location

1. Log on as an Administrator or root user based on windows or UNIX system respectively.
2. Run the following command on the NetBackup master server by providing appropriate values:

   bprestore -S master_server -D backup_host -C client -t 44 -L progress log -f listfile

   Where,

   -S master_server

   Specifies the name of the NetBackup master server.

   -D backup host

   Specifies the name of the backup host.

   -C client

   Specifies a controller node as a source to use for finding backups or archives from which to restore files. This name must be as it appears in the NetBackup catalog.

   -f listfile

   Specifies a file (listfile) that contains a list of files to be restored and can be used instead of the file names option. In listfile, each file path must be on a separate line.

   -L progress_log

   Specifies the name of whitelisted file path in which to write progress information.

   -t 44

   Specifies BigData as the policy type.

To perform redirected restore for OpenStack

1. Modify the values for rename_file and listfile as follows:

   Parameter	Value
   rename_file	ALT_APPLICATION_SERVER=<alternate name node> The rename file must also contain the changed NetworkID entry. For example, change: /project_name/instance_name/Metadata/NetworkID=value to /destination_project_name/instance_name/Metadata/NetworkID=value Note: Alternate restore is supported only to same project name.
   listfile	List of all the OpenStack files and metadata files to be restored. The file paths must start with / (slash).

2. To fetch the credentials information for the alternate OpenStack controller:

   • Add a tpconfig entry for the new OpenStack controller.

   • Change the name of the generated encrypted file in /usr/openv/var/global to match the name of the source client encrypted credentials file.

     For example, if hostname1.conf is the encrypted source client file and hostname2.conf is the encrypted alternate client file. You need to rename hostname2.conf to hostname1.conf before running the bprestore command.

3. Run the bprestore -S master_server -D backup_host-C client -R rename_file -t 44 -L progress log -f listfile command on the NetBackup master server using the modified values for the mentioned parameters in step 1.

   Where,

   -S master_server

   Specifies the name of the NetBackup master server.

   -D backup_host

   Specifies the name of the backup host.

   -C client

   Specifies an OpenStack controller as a source to use for finding backups or archives from which to restore files. This name must be as it appears in the NetBackup catalog.

   -f listfile

   Specifies a file (listfile) that contains a list of files to be restored and can be used instead of the file names option. In listfile, each file path must be on a separate line.

   -L progress_log

   Specifies the name of whitelisted file path in which to write progress information.

   -t 44

   Specifies BigData as the policy type.

   -R rename_file

   Specifies the name of a file with name changes for alternate-path restores.

   Use the following form for entries in the rename file:

   ALT_APPLICATION_SERVER=<Application Server Name>

   To change the volume type at the destination OpenStack environment, add the following line with the proper values for old and new volume types:

   change /project/instance/Metadata/Src_VolumeType to /project/instance/Metadata/Dest_VolumeType

   Note:

   Ensure that you have whitelisted all the file paths such as <rename_file_path>, <progress_log_path> that are already not included as a part of NetBackup install path.