To enable an alternate host recovery, you must copy the required user configuration file and auto configuration file from the source host to the destination host. If the target asset is in a different protection policy than the source asset, then you must also store the password of the source storage unit in the lockbox on the destination host.
Replicate the directory path of the configuration files on the destination host by using either of the following methods:
Create the directory path on the destination host by creating each subdirectory in the path separately with the same permissions, user, and group as the destination SID. For example, create the following directory path, where the source instance is SID:
/usr/sap/SID/SYS/global/ppdmconfig
Create the directory path on the destination host, and assign full permissions. For example:
Go to the
/usr/sap directory:
cd /usr/sap
Create the required directory path, where the source instance is SID:
mkdir -p SID/SYS/global/ppdmconfig
Assign full permissions to the directory path:
chmod -R 777 SID/
Copy the user and auto configuration files from the source host to the directory path on the destination host.
If the target asset is in a different protection policy than the source asset, store the password of the source storage unit in the lockbox on the destination host:
To obtain the password of the source storage unit, run the required script from the
PowerProtect Data Manager server. You can fetch the MTree pathname details from the source
.utl files:
Connect to the
PowerProtect Data Manager console as an admin user.
Navigate to the
/usr/local/brs/puppet/scripts directory.
Obtain the storage unit password by typing the following command:
python get_dd_mtree_credential.py MTree-name
For example:
python get_dd_mtree_credential.py mtree1
==============PowerProtect DD MTree credential==============
Full MTree path: /data/col1/mtree1
User name: user1
Password: pass1
============================================================
Store the source credentials in the lockbox on the destination host:
Create a separate file
lockbox_reg.utl.
Add the following lines in the
lockbox_reg.utl file:
To store the source lockbox password, run the command
ddbmadmin -P -z lockbox_reg.utl on the destination host. When prompted for the password, enter the password from step 3a.
To store any additional credentials, such as for secondary storage, modify the
lockbox_reg.utl file with the following lines and then run the command
ddbmadmin -P -z lockbox_reg.utl again:
When the configuration files are in place and any required credentials are stored, perform the alternate host recovery by using the same steps as for the restore of a database to the same host.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\