Data Loss Prevention

 View Only
  • 1.  Creating a Enforce server as a secondary/ DR option?

    Posted Jan 23, 2018 01:42 PM

    Is there any type of guide for creating a secondary enforce server to stay in a type of passive/inactive mode? Based on the stuff ive been reading there cannot be two active Enforce servers connected to the Oracle DB for a variety of different reasons. Looking through the maintenance guide ive  found documentation for backing up and recovering an enforce server.  But my goal is to create 2 identical enforce servers, and have only one active. if something were to happen to the primary server, I would easily be able to switch over to the secondary from the first. Is this being done at all?

     

    I have read a bit about the VCS but is seems like it isnt that commonly implemented. 

     

    Some one the forum responses that have been given on the subject have missing and dead article links. Any help would be appreciated.

     

    thanks

     

     



  • 2.  RE: Creating a Enforce server as a secondary/ DR option?
    Best Answer

    Trusted Advisor
    Posted Jan 23, 2018 09:39 PM

    Paul,

    I've worked with a few customers that like this idea. It was required by some customers, but eventually they stopped doing the COLD  DR enforce server. It ultimaley was more of a pain than it is worth. Especially if the server is just sitting there cold.. waste of energy and allocated power.

    Things to think about.. 

    1. 95% of the DLP data is in the DB, so backing that up is more imprtant than anything
    2. On the enforce server the only thing to really back up is the config dir (Cryto file etc), scripts, keystore etc.

    Here are the options:

    1. Keep Enforce on a VM - If there was ever an outage on the Enforce server, it is easier in most cases to spin back up the VM on another host. - no installation or modification needed.
    2. Keep a Cold DR - If you had a cold DR server, you wold need to make sure the files have been duplicated to the DR one. - more work.
    3. Reinstall the SW on a new Server - Install the SW takes less than 5 minutes and just need to have a backup of the Config Files. - Not too much work especially with VM's

    The BIG issue is the life cycle of keeping that COLD DR upto date when it comes to UPGRADES. When you upgrade to a newer Version/Patch, you will need to update the LIVE SYSTEM. This will update the DB and then the Enforce Console. When you need to update the COLD DR, you will need to install that SYSTEM from scratch, along with applying the patch. In some cases this may be tricky if the DB has already been upgraded.

    So in reality you will be doing #3 on a regular basis in order to maitain the COLD DR. Might as well ONLY do that when you have an outage and need to rebuild.

    Just my thoughts..

     

    Good Luck

    Ronak

    PLEASE MARKED SOLVED WHEN POSSIBLE.



  • 3.  RE: Creating a Enforce server as a secondary/ DR option?

    Trusted Advisor
    Posted Jan 24, 2018 01:20 PM

    Paul.. 

    Emailed your DM.. 

    Good Luck

    Ronak

    PLEASE MARKED SOLVED WHEN POSSIBLE.