First refer to the following article on how to create the replacement primary policy server:
What options do I have to recover a failed primary policy server?
Then follow these steps to copy the revision history to the new policy server:
On the old policy server run:
/opt/quest/qpm4u/bin/svnadmin dump /var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos > /tmp/sudo_repos.dump
Copy /tmp/sudo_repos.dump to the new policy server.
On the new policy server:
Move the original repository aside:
mv /var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos /var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos.orig
Create a new repository with the same name:
/opt/quest/qpm4u/bin/svnadmin create /var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos
Load the dump to the newly created repository:
/opt/quest/qpm4u/bin/svnadmin load /var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos < /tmp/sudo_repos.dump
Change the file ownerships on the repository files:
chown -R pmpolicy:pmpolicy sudo_repos
Note that the Privilege Manager for Unix repository will be named pmpolicy_repos instead of sudo_repos.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center