Section 1

Section 2
Configuring for First Use

Section 3
Changing Admin Password

Section 4
Creating Accounts

Section 5
Global Component Settings

Section 6

6.3 Backup Location

6.4 Backup History

6.5 Saving to External Medium

6.6 Backup ID

6.7 Restoring a Backup

Section 7
Log Files

Section 8
User Interface Settings

Section 9
Database Connections

Section 10
Non-Standard Ports

Section 11

Section 12

Section 13
Tracking and Recipient Profiles

Section 14
Editing INI Files

Section 15
Distributed Components

Section 16
User Interface Branding

Section 17
Evaluation Mode

Section 18
International Character Sets

Appendix A
Standard Default Ports

6.7 Restoring a Backup

In the unfortunate event of having to restore a backup, follow this procedure:

  • Identify the backup that is to be restored.

This usually is the most recent backup, but it also must be a successful backup. If there were errors during the most recent backup, revert to the next most recent backup, which may have to be retrieved from an external medium.

To find out if a backup was successful, check the backup log in the folder:

\Program Files\L-Soft\Application Server\hub\logs

For each backup triggered by the Administration Hub, a report named "backupReport_ID.txt", where "ID" is replaced with the ID of the backup in question, is saved into this folder. The IDs are assigned in alphanumeric order; the most recent backups have higher order IDs (in an alphanumeric sense). Use the file date of the report file to locate the most recent backup.

If the backup was successful, an entry like this will appear at the end of the file:

"The backup was completed successfully
Final completion date: <date here>

If the backup was unsuccessful for any reason, then the report will contain entries detailing the errors that occurred.

If the logs folder cannot be accessed (because a disk crash destroyed the disk of the Administration Hub installation, for example), it is still possible to locate the most recent successful backup by opening the readme.txt file in the backup folder of each component. The readme.txt file lists the backup ID and the success state of that particular backup. If no errors are reported in that file, then the backup of this component was successful. If successful backups with the same ID of all the other components are located, then a complete and successful backup set exists and can be restored.

  • Find the backup folders from all components that belong to the same backup set.

Once the backup to be restored has been identified and the backup ID is determined, the next step is to find all the backup folders of the individual components that contain data for this backup. Check the readme.txt in the backup folder of each component. If it contains the same ID, the right backup folder for this component has been located.

  • Make a fresh installation of all components.

This includes uninstalling old versions (if necessary) and installing the components on the servers where needed. Do not start the components after installation. Some program files and INI files need to be edited. To edit INI files see Section 14 Editing LISTSERV Maestro INI Files. Instead, proceed as follows:

  • To restore the Administration Hub

Remove the existing versions of the file "hub.ini" and the folders "accountreg" and "hubreg", including their contents, from the Administration Hub home folder:

\Program Files\L-Soft\Application Server\hub

Replace them with the versions from the backup folder of the Administration Hub component.

  • To restore the Maestro User Interface

Remove the existing versions of the files "lui.ini" and "my.ini" and the folders "luidata" and "registry", including their contents, from the Maestro User Interface home folder:

\Program Files\L-Soft\Application Server\lui

Replace them with the versions from the backup folder of the Maestro User Interface component. Next, add a new entry to the "lui.ini" file like the example below:


The "path_to_backup_folder" is replaced with the path name that leads to the backup folder from which the files and folders, as described above, were copied.

This path name may either be a full path name including driver letter, or it may be an absolute path without driver letter starting with "\" or "/", which is then interpreted as being absolute on the drive/root where the application server is installed (for example, in the default case, the same drive where "\Program Files\L-Soft\Application Server" is located). Or a relative path without a driver letter may be used, and not starting with either "\" or "/", which is then interpreted as being relative to the home folder of the Maestro User Interface component (for example, in the default case, that would be the folder "\Program Files\L-Soft\Application Server\lui").

Forward slashes "/ or backslashes \ may be used as the filename separator. However, if backslashes are used, then use double backslashes. Example, either write:




This entry to the "lui.ini" file will be automatically removed during the first startup of the component. It is only present to signal to the component that it should restore all required data from the given folder, which happens automatically during the next startup, whenever this INI file entry is present. For more information on editing INI files, see Section 14 Editing LISTSERV Maestro INI Files.

  • To restore Maestro Tracker

Remove all "*.dat" files from the folder called "data" inside Maestro Tracker home folder:

\Program Files\L-Soft\Application Server\trk\data

Replace then with the "*.dat" files from the backup folder of the Maestro Tracker component. Also remove the file "tracker.ini" from the Maestro Tracker home folder, (but not into the "data" folder) and replace it with the same file from the backup folder.

If components are being restored on different servers or a different combination of servers than the original backup was taken from, it may be necessary to edit the respective *.ini files of the components. This would include restoring a backup to a server with a different name, using a different port number, or changing how the components are grouped on a server or servers. For example, if components that were all originally on the same server are moving to different servers, or taking components that were originally on different servers and moving them to the same server.

It might also be necessary to make changes in some of the settings configured in the Administration Hub itself. However, before this can be done, the hub and the components in question must first start. They may not start up correctly at first, but after the configuration changes in the hub, and probably a restart of the components, they should then start up correctly.

  • Start all components normally.