Absent Member.. bzdafro Absent Member..
Absent Member..
355 views

How do you handle disaster recovery for your PPM server?

Hi

 

We recently setup another PPM prod 9.14 environment running on Linux.     We ran a disaster recovery test recently and encountered a small issue with the environment passwords.    Our plan was to copy the PROD Oracle DB/schema to our non prod PPM server.   While this does work, the envionment passwords did not due to encryption key differences.  Reading Ch 10 in the Installation guide, suggests different options to migrate to another server.    We had planned on the option below.    Has anyone ran into this problem?  Re-entering all the environment passwords manualy duing a disaster is not an opion as we have hundreds of different passwords.   Suggestions?

 

 

Migrate the database schemas, but maintain the existing PPM Server.

Migrating only the database schema does not require a new license key.

0 Likes
3 Replies
Absent Member.. AlfredoMonasi Absent Member..
Absent Member..

Re: How do you handle disaster recovery for your PPM server?

You need to copy the keys located on our prod PPM folder to your non Prod environment. If is use for non replication purpouse I recommend you too change all users passwords by one default and update your environments also.

0 Likes
Absent Member.. bzdafro Absent Member..
Absent Member..

Re: How do you handle disaster recovery for your PPM server?

So I would move the keys stored on our PROD server $PPM_HOME/security to our QV SERVER $PPM_HOME/security ?

Would environment passwords work without re-entering them?



0 Likes
Absent Member.. AlfredoMonasi Absent Member..
Absent Member..

Re: How do you handle disaster recovery for your PPM server?

Hi bzdafro,

 

Yes id ou only copy the environments keys should be enough but you have to be careful with your environments settings, we have 4 environments by default.

 

KINTANA_SERVER (Current PPM Server)

DEVELOPMENT

TESTING

PRODUCTION

 

If in one of your workflows you are using the incorrect environment values will do the action on the incorrect system. Thats why you have to update your KINTANA environment as soon you update.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.