Restoring PIM Endpoints


Article ID: 36135


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)



What are the files that I need to consider when backing up a CA PIM endpoint?

How do I do this procedure?


On *nix OS systems, it would be absolutely ideal to backup the entire top level directory, /opt/CA/AccessControl, or whichever directory you installed /AccessControl in.  Typically, a copy or a 'cp' command will accomplish this task.  Please make sure PIM is stopped before doing this procedure:

# cp /opt/CA/AccessControl /your/network_share/here

Next, ou will want to copy the seos.ini configuration, along with your PAM configuration native to the local system - typically found in /etc/pam.d/system-auth.

# cp /opt/CA/AccessControl/seos.ini /your/network_share/here

# cp /etc/pam.d/system-auth /your/network_share/here

Create a script that will duplicate the rule set by running the dbmgr utility on the temp database:
# cd /opt/CA/AccessControl/seosdb.tmp
# dbmgr -export -l -f /tmp/lang_script  

Execute the dbmgr utility to create a flat file containing data from the old database:
# cd /opt/CA/AccessControl/seosdb.tmp
# dbmgr -migrate -r /tmp/flat_file

Import the script generated previously to populate the new database:
# cd /opt/CA/AccessControl/seosdb
# selang -l -f /tmp/lang_script  

Load the data from the flat file into the new Access Control database:
# cd /opt/CA/AccessControl/seosdb
# dbmgr -migrate -w /tmp/flat_file 



Release: ACP1M005900-12.9-Privileged Identity Manager