Backing up and restoring the EDR Console to a replacement server

Version 1

    What steps can be taken to backup the EDR (Enterprise Data Replicator) management console so that it can be restored in the event of a complete server failure?

    This information applies to the following Operating System(s):

    - This information is not Operating System specific


    This procedure describes how one can backup the EDR configuration on one server and restore to a replacement server in the event the original management console server's hardware fails completely. Keep in mind backup of the management console must be completed prior to a complete disaster in order to restore the EDR management console successfully. If a backup of the management console was not performed prior to a complete disaster, EDR will have to be reconfigured from scratch. Note the additional requirements below.

    For Guardian OS version 4.4.045 or higher.

    1. Take and save a DR image of the working Snap server running the Snap EDR console.

    2. Configure a replacement system the same way as the original management console. It must have the same 4.4.045 OS version, the same EDR version installed and unconfigured, matching hardware, server name, RAID, volume configuration. Otherwise, the next step will fail.
    3. On the replacement system, navigate to the disaster recovery and choose the radio button for "Recover Server-Specific Settings"
    4. Choose the SnapDRImage file saved in step 1.
    5. Select recover Snap EDR only.
    6. After reboot, check the Disaster Recovery page and confirm the process succeeded in the "Last Recovery Date" column.
    7. Login to the EDR management console and go to the License Keys page. Expect licenses to say "unknown feature (-1)" since the keys are tied to the original server number. These licenses are not needed and can be deleted.
    8. Obtain and apply license keys for the replacement server.

    For Guardian OS versions prior to 4.4.045.
    Backup the EDR Console:

    1 - SSH to the Snap server hosting the EDR console

    2 - Switch user to 'root'
    su -
    3 - Identify the base installation directory for Snap EDR. You can determine this from the /etc/dds.conf file, from the "Install directory is" line. You will want the "SnapEDR" directory (not the "BINARIES/bin"
    eg: Installation directory is
    "/hd/vol_mnt0/SnapEDR/BINARIES/bin" shows that the base install directory is "/hd/vol_mnt0/SnapEDR"
    4 - Stop the SnapEDR services using the 'siginit' control script
    /etc/init.d/siginit stop
    5 - TAR the SnapEDR base install directory
    eg: tar cvf SnapEDRBackup.tar /hd/vol_mnt0/SnapEDR
    6 - Start the SnapEDR services using the 'siginit' control script
    /etc/init.d/siginit start
    7 - Copy the tar file to a safe location

    Restore the EDR Console:

    1 - Return the Snap server to a condition where you can install Snap extensions. In order for the restore of the SnapEDR console to succeed, the Snap server must have the exact hostname and should have the same volume configuration as prior to any failure.

    2 - Install the SnapEDR console using the normal install procedures
    3 - SSH to the Snap server and switch user to 'root'
    4 - Determine the base installation directory as per item 3 in the backup steps. Copy the tar file created above to the Snap server, and place it in the parent directory of the SnapEDR base directory. Change your working directory to this directory.
    eg, /hd/vol_mnt0
    5 - Stop the SnapEDR services
    /etc/init.d/siginit stop
    6 - Restore the tar file to the base installation directory
    tar xvf SnapEDRBackup.tar
    7 - Start the SnapEDR services
    /etc/init.d/signint start
    8 - The SnapEDR console is now restored.