Login Enterprise backup and recovery

Overview

External database

Internal database

Overview

You can migrate the database from a malfunctioning Login Enterprise instance to a functional one, preserving your data and configuration. Please note that encrypted data, such as user passwords and application secrets, will not be transferred, but your overall configuration will remain intact.

This article outlines the process for creating a backup of the internal database to facilitate restoration on a rebuilt appliance. Additionally, it provides instructions on how to configure a new appliance to connect to an existing external database and recover configurations.

External database

For the external database, you can set up a new appliance and configure it to connect to the existing database. Avoid directing two appliances to the same database simultaneously. If you need to replace an appliance, it's straightforward to create a new one and configure it to use the existing database.

Alternatively, you might have the option to clone the database from a running appliance to a new instance and then connect a new appliance to this cloned database. Despite both appliances using the same configuration, they won't conflict.

Internal database

ATTENTION: YOU CAN TRANSPLANT THE DATABASE IF YOU HAVE THE ENCRYPTION KEY THAT WAS SET DURING THE INITIAL CONFIGURATION OF THE OLD SERVER, AND YOU HAVE PROVIDED IT DURING THE INITIAL CONFIGURATION OF THE NEW SERVER.

For the internal database, it's crucial to obtain a copy of the database before your appliance VM becomes inaccessible. You must ensure that all the Login Enterprise services are stopped before proceeding with the following steps:

1. Log in to the appliance with the admin account, go to Troubleshooting, and open the Bash shell.

2. loginvsid stop

3. cd /loginvsi ; tar -zcvf data.tgz data

4. Download /loginvsi/data.tgz to some other machine. Use tar to ensure proper preservation of file permissions and ownership.

To install the database on a new appliance (multiple appliances can use copies of the same database without conflict), follow these steps:

5. Upload data.tgz to /loginvsi

6. loginvsid stop

7. cd /loginvsi ; tar -zxvf data.tgz

8. loginvsid start

After logging back into the Login Enterprise, your data and configurations will be automatically restored.