Backing up and Restoring the eG Manager on Windows Environments
To back up and restore the eG manager on Windows, do the following:
- Login to the eG manager host.
- Copy the eGurkha directory to a convenient location.
-
If you want to restore the eG mananger to the same host from which its backup was taken, follow the steps below:
- If you already have a fully operational manager on the target host and you simply want to revert to the backed up version of the eG manager, then, simply replace the eGurkha directory on the target host with the backed up eGurkha directory, and then restart the eG manager.
-
On the other hand, if you want to completely scrap the existing manager installation and replace it with the backed up version, then, follow the steps below:
- Uninstall the existing eG manager.
- Next, install the eG manager with the same specifications as the old manager; for instance, if the old manager was installed using Tomcat and not IIS, make sure the new manager also uses Tomcat. Similarly, install the new manager in the same directory as the old manager. However, during installation, make sure that you do not provide the name of the database used by the old manager. Instead, provide the name of a new ‘dummy’ database for use as the eG backend.
- Replace the eGurkha directory of the new manager with the old eG manager.
- Finally, start the eG manager.
-
If you want to restore the eG manager to a different host (i.e., a host with a different IP address/hostname from that of the backed up manager), then, do the following:
- If you have a fully operational manager on the target host and you simply want to revert to the backed up version of the eG manager, then, to restore the backed up version, simply replace the eGurkha directory on the target host with the backed up eGurkha directory, and then restart the eG manager.
-
On the other hand, if you want to completely scrap the existing manager installation and replace it with the backed up version, then, follow the steps below:
- Uninstall the existing eG manager.
- Next, install the eG manager with the same specifications as the backed up manager; for instance, if the backed up manager was installed using Tomcat and not IIS, make sure the new manager also uses Tomcat. Similarly, install the new manager in the same directory as that of the backed up manager. However, during installation, make sure that you do not provide the name of the database used by the backed up manager. Instead, provide the name of a new ‘dummy’ database for use as the eG backend.
- Replace the eGurkha directory of the new manager with that of the manager in backup.
- Next, run the changeManagerSettings.bat and changeAgentSettings.bat files from the <EG_INSTALL_DIR>\lib directory to change the IP address/host name of the eG manager and agent.
- Replace the old eG manager license with a new license generated for the new IP address/hostname.
- Finally, start the eG manager.