To create a backup copy of the PolyAnalyst server settings, user configuration parameters, user profiles, etc., use the following command line argument:

where <destination> is a path to a folder where you plan to store backup data.

The --backup option is used as an argument to "rserver.exe" or "loginserver.exe" depending on whether you want to perform a backup of an Analytical Server or a Login Server. The commands you need to use are given in the example below:

or

where server_backup and login_server_backup are the folders which were created beforehand.

One should bear in mind that the backup process is invisible to the user. Whether you want to monitor the process, run MiniDumper.exe --monitor command as it is shown in the screenshot below.

If there are no servers performing a backup, the MiniDumper.exe program exits after 10 seconds.

A project backup is treated incrementally. A project won’t be backed up again if there is already a backed up one. Other items are always overwritten when being backed up.

Backup is a transactional operation, i.e. all stages of the operation are important – if a non-internal occurs, the process is aborted and the backup folder is restored to the previous state.

When you back up the Login Server, it must be stopped as well. The Login Server backup includes users’ database, central Appearance storage, users Home folders and user settings. Thus, when performing a backup of both the Analytical and Login Servers, the following data will be backed up:

The backup operation keeps the regid.id file, i.e. a registration ID.

If there is a Standalone configuration, the Login server will be off when you shut down the Analytical Server. In case of a Сluster configuration, one should manually shut the Login Server.

If you perform a backup again, the previous backup script will be contained in the restore.cmd.old file (or ls_restore.cmd.old for the Login Server).

Starting from PA6.5 2612 you can back up both Analytical and Login Servers with the use of backup.cmd file. This will create a restore.cmd (to restore an Analytical Server) and ls_restore.cmd (to restore a Login Server) files. To restore the data, they must be run consequently, i.e. first run restore.cmd and then ls_restore.cmd.

You can create a server backup using the --config argument and specifying a third-party server configuration file. In this case, this argument specifying a third-party configuration file should also be used when starting the restored server.

In case of a successful backup you will see either a restore.cmd or ls_restore.cmd file in the backup directory.

If there were any errors or the backup was not performed completely, you will not find the files in hand. See the server log file to find the reason of an unsuccessful backup and contact Megaputer Support.

When the backup process is finished, you can use the following argument to restore the data:

where <source> is a path to a folder where the PolyAnalyst server has been installed. Bear in mind that a Login Server can be installed in a different folder, e.g. in case of a Cluster configuration.

It is important to restore the server to the same folder where it has been installed, i.e. all of the server files must be present (including Dictionaries folder, etc.).