For cases when the whole environment where the JetPatch server is located can become inaccessible, or for situations when the JetPatch server crashes, there are simple steps that can be done previously, to accomplish a recovery if one happens.
For situations, when JetPatch can become inaccessible, and there is a need to quickly switch to another JetPatch instance, please check Disaster Recovery Solution Overview
We recommend performing the following activities as part of the disaster recovery process
Preparing for a crash
On-Going Backup Activities
1. Backup DB weekly (or daily)
2. Backup weekly (or daily) the content of directory /usr/share/tomcat/default/conf
3. Backup weekly (or daily) the content of directory /usr/share/intigua
4. Backup your WSUS as recommended by MSFT and explained in the following article
See DB backup KC: How do I generate a PostgreSQL DB Dump?
For directory backup - use your preferred choice of backup.
In case of a crash:
1. Perform a new install of JetPatch as explained in the article Installing JetPatch RPMs in accordance with sizing specifications.
2. Restore from your backup the DB backup
3. Restore from your backup the contents of directories:
/usr/share/tomcat/default/conf
/usr/share/intigua
4. In the WSUS backup article, follow the steps described in the subsections explaining how to restore your WSUS from a backup (WSUS file server and WSUS Database): 'To restore the update file storage folder' & 'To restore the WSUS database'
5. Start the system
The whole recovery process should last 1-3 hours.
In case of more help is required, get in touch with JetPatch support.
Comments
0 comments
Please sign in to leave a comment.