4 Replies Latest reply on Jan 18, 2008 11:38 AM by bwagrocki

    epo3.6 Backup & Recovery

      Hello,

      are there any official documents form mcafee describing how to backup and restore an epo server? What do I have to do if I want to back up epo and what do i have to do if I have to restore epo?

      --
      Best Regards
      -bwagrocki-
        • 1. RE: epo3.6 Backup & Recovery
          looking for the same information, what to backup on the server without doing a full disk backup?
          • 2. RE: epo3.6 Backup & Recovery
            Still waiting for help!

            Is it sufficient to back up the SQL DB/instance.
            What does the sql instance contain?
            All policies, configurations and master repository ???

            For recovery will it be enough when reinstalling epo just to connect to the backedup/restored sql instance to achieve the originally status?

            best regards
            -bwagrocki-
            • 3. RE: epo3.6 Backup & Recovery
              twenden
              Below is the "Recommended recovery procedure for EPO 3.6.x". It is from the McAfee knowledge base and has Document ID: 2150095. In my environment, I back up the MSDE database and DB folder on a weekly basis. These are saved off the server on an external HDD and on my personal workstation. Hope this answers your question.

              Recommended recovery procedure for ePolicy Orchestrator 3.6.x

              Environment

              McAfee ePolicy Orchestrator 3.6.x
              Microsoft SQL Server 2000
              Microsoft SQL Server 2005 (ePO 3.6.1 only)
              Microsoft SQL Server Desktop Engine 2000

              Summary

              For an online demonstration of the steps performed in this article see: Recommended recovery procedure for ePO3.6.

              For a list of all ePO articles, see KB40780.

              If you do not have Flash Player installed, download it from: http://www.adobe.com/products/flashplayer/.


              IMPORTANT: This information is intended for use by network and ePO administrators only. McAfee does not assume responsibility for any damages incurred by these instructions as these are meant to be used as guidelines for a Disaster Recovery process. All liability for use of the information below remains with the user.

              The details included in this article can also be used for customers who wish to move or migrate the ePolicy Orchestrator Server to another computer. This is currently only possible if the new computer is going to have the same computer name and IP Address and that the original Server is then decommissioned post transfer of all relevant files.

              SQL Server Hardware Failure:

              Contact OEM for replacement of affected hardware.

              SQL Server Database Failure:

              Contact Microsoft for procedures on restoring SQL databases.
              For the ePolicy Orchestrator (ePO) database specifically, refer to procedures for backing up and restoring an ePO database in:

              NAI37402 - Backing up the ePO 3.x.x / ProtectionPilot 1.x.x MSDE database using an OSQL command, the DBBAK utility or SQL Enterprise Manager

              NAI21630 Restoring an ePolicy Orchestrator 3.x.x / Protection Pilot 1.x.x database via SQL Enterprise Manager or using DBBak.Exe


              ePO Server Hardware Failure:

              Contact OEM for replacement of affected hardware.

              ePO Server Software Failure

              Step 1 - The following data will be required to be backed up to restore ePO to its original state in case of a failure:

              * ePO database
              * \DB directory

              1. Back up the ePO database using the procedures outlined in:

              NAI37402 - Backing up the ePO 3.x.x / ProtectionPilot 1.x.x MSDE database using an OSQL command, the DBBAK utility or SQL Enterprise Manager.

              2. The following folder must also be backed up:

              C:\Program Files\McAfee\ePO\3.6.x\DB\ (default path for new installation of ePO 3.6.x)
              OR
              C:\Program Files\Network Associates\ePO\3.6.x\DB\ (default path for upgrade from ePO 3.5.x to 3.6.x)

              NOTE: The DB folder contains information for distributed repositories, server certificates and contents of the entire Master Repository.

              Step 2 - Make a note of the existing Ports stored in the ePO Server.ini file

              1. Use Windows Explorer to navigate to the ..\DB folder in either:

              C:\Program Files\McAfee\ePO\3.6.x\DB\ (default path for new installation of ePO 3.6.x)
              OR
              C:\Program Files\Network Associates\ePO\3.6.x\DB\ (default path for upgrade from ePO 3.5.x to 3.6.x)

              2. Double-click on the SERVER.INI to edit.
              3. Make a note of the Port numbers for the following entries (default values stated):

              HTTPPort= 80 (Agent-to-Server communication port)
              ConsoleHTTPPort= 81 (Console-to-Server communication port)
              AgentHttpPort= 8081 (Agent Wake-Up communication port)
              SecureHttpPort= 8443 (Console-to-Application Server communication port)
              BroadcastPort= 8082 (Agent Broadcast communication port)
              AVERTAlertsPort= 8801 (Security Threats HTTP port)


              Step 3 - To restore the ePO server to a new computer after a server crash:

              1. Set up a new ePO 3.6.x server on another computer with the same IP address and same Hostname.
              2. Use the same port numbers that were used during the original installation and obtained in the previous step.

              3. During the installation of ePO 3.6.x, use the original SQL server when prompted.

              NOTE: This will create a database called ePO_<epo_servername>. Because the name of the computer was retained, the original database will need to be backed up and detached. Otherwise, the installer will fail with the error that the database already exists.
              4. After the installation of ePO, apply all Service Packs and/or HotFixes originally applied to the downed ePO sever.
              5. Install and enable software deployment for all previously managed products.


              Step 4 - Restore the original back up copy of the ePO Database

              Restore the backed up copy of the ePO database.

              Refer to NAI21630 - Restoring an ePolicy Orchestrator 3.x.x / Protection Pilot 1.x.x database via SQL Enterprise Manager or using DBBak.Exe

              IMPORTANT: For SQL 2005, ensure that SQL Server 2000 (80) is selected in the Compatibility level section for the ePO database once it has been restored. To do this, right-click on the ePO database, select Properties and click Options.

              Step 5 - Restore the original contents of the ...\DB files and folders:

              1. Restore the backed up copy of the following files:

              IMPORTANT: Restore the entire DB folder.

              C:\Program Files\McAfee\ePO\3.6.x\DB\ (default path for new installation of ePO 3.6.x)
              OR
              C:\Program Files\Network Associates\ePO\3.6.x\DB\ (default path for upgrade from ePO 3.5.x to 3.6.x)

              Step 6 - Use CfgNaiMs.Exe utility to verify the correct ePO Server/Database is specified

              Stop ePolicy Orchestrator Services:

              1. Click Start, Run, type: services.msc, then click OK.
              2. Right-click on the following services and select Stop:

              * McAfee ePolicy Orchestrator 3.6.x Server
              * McAfee ePolicy Orchestrator 3.6.x Event Parser
              * McAfee ePolicy Orchestrator 3.6.x Application Server


              3. Minimize the services window.

              Launch CfgNaiMs.Exe:

              1. Click Start, Run and type: explorer, then click OK.
              2. Navigate to appropriate folder listed below and double-click CfgNaiMs.Exe:

              C:\Program Files\McAfee\ePO\3.6.x\ (default path for new installation of ePO 3.6.x)
              OR
              C:\Program Files\Network Associates\ePO\3.6.x\ (default path for upgrade from ePO 3.5.x to 3.6.x)

              3. On the SQL Server tab, type in the original ePO database name in the Database name: field. (Example: ePO_OLDSERVERNAME)
              4. Ensure the SQL Server name is correct and click OK.

              Start ePolicy Orchestrator Services:

              1. Click Start, Run, type: services.msc, then click OK.
              2. Right-click on each of the following services and select Start:

              * McAfee ePolicy Orchestrator 3.6.x Server
              * McAfee ePolicy Orchestrator 3.6.x Event Parser
              * McAfee ePolicy Orchestrator 3.6.x Application Server

              3. Close the services window

              Step 7 - Log on to the ePO console:

              1. Log on to the ePO console with the original username and password from the old ePO server. Refer to KB42032 for information on logging on to the ePO console.
              2. Verify that all of the restored information is correct.
              • 4. RE: epo3.6 Backup & Recovery
                Thanks a lot!
                That was exactly what I was looking for.

                best regards
                -bwagrocki-