Perform a disaster recovery when the database backup/restore process fails using the "Database Backup/Restore Wizard" for an Embedded Database

Products

• Endpoint Protection

Issue/Introduction

How do I perform a disaster recovery when the database backup/restore process fails using the "Database Backup/Restore Wizard" for an Embedded Database?

Symptoms
Database backup/restore fails through the database backup and restore wizard

Cause

Inability of the "Database Backup/Restore Wizard" to access the database to launch a backup OR a restore operation

Resolution

Follow the steps below to resolve this issue:

• ON THE OLD INSTALLATION
1. Copy the "Server Private Key Backup" folder from:
   \\ProgramFiles\Symantec\ Symantec Endpoint Protection Manager\Server Private Key Backup
   
2. Paste it to another storage area (as it will be deleted during Symantec Endpoint protection Manager uninstall)
3. Stop the services "Symantec Embedded database" and the "Symantec Endpoint Protection Manager"
4. Copy the "db folder" from:
   \\ProgramFiles\Symantec\ Symantec Endpoint Protection Manager\
   
5. Paste it to another storage area.
• ON THE NEW INSTALLATION AFTER THE DISASTER RECOVERY OF OPERATING SYSTEM (OS)

---

Warning: Re-installation of Symantec Endpoint Protection Manager needs to be done on the same IIS Port and Website for it restore client-server communication after the Disaster Recovery Process is complete.

---

1. Ensure that the server has the same IP Address and Host Name the Operating System has been Installed.
2. Install the "Symantec Endpoint Protection Manager" with the "Embedded Database" with the default settings.
3. Log in to the Console
4. Click Admin.
5. Select Tasks> Servers.
6. Under "View Servers", expand Local Site.
7. Click the that identifies the local site.
8. Select Tasks.
9. Click Manage Server Certificate.
10. In the "Welcome panel", click Next.
11. In the "Manage Server Certificate panel", select Update the Server Certificate
12. Click Next.
13. Under "Select the type of certificate to import", select JKS keystore.
14. Click Next.
    Note: If one of the other certificate types has been implemented, select that type.
    
15. In the "JKS Keystore panel", click Browse.
16. Locate and select the backed up "keystore_.jks" keystore file.
17. Click OK
18. Open the "server_.xml" file
19. Select and copy the "keystore password."
20. Activate the "JKS Keystore" dialog box.
21. Paste the "keystore password" into the "Keystore" and "Key boxes."
    Note: The only supported paste mechanism is Ctrl + V.
    
22. Click Next
    Note: If you get an error message that says you have an invalid keystore file, you probably entered invalid passwords. Retry the password copy and paste. (This error message is misleading.)
    
23. In the "Complete panel", click Finish.
24. Stop the services Symantec Embedded database and the Symantec Endpoint Protection Manager
25. Go to:
    \Program Files\Symantec Endpoint Protection Manager\
    on the new "Symantec Endpoint Protection Manager" and rename the "Db" folder to "Db_new"
    
26. Move the "old db" folder under:
    \Program Files\Symantec Endpoint Protection Manager\
    
27. Go to Administrative Tools> Data Sources ODBC
28. Ensure the database connectivity after the changing the database file location to:
    \Program Files\Symantec Endpoint Protection Manager\db1\sem5.db
29. Start the service Symantec Embedded database
30. Run the Management Server Configuration Wizard
31. Click Yes to replace the database after entering the password
32. Login to the "Symantec Endpoint Protection Manager" using the OLD password.
33. Ensure that the Domain ID is same as it was on the old clients.
    • If it not, follow the direction in the below document to restore the Domain ID. This will enable client communication http://service1.symantec.com/support/ent-security.nsf/docid/2007082112135948
      
34. All of the clients should begin reporting back within approximately 30 minutes.