Mitel Standard Linux (MSL) server commands

MSL backup

This software makes use of the MSL PostgreSQL database. When you perform an MSL backup, the Platform Manager database is included.
Configure a daily scheduled MSL backup. A schedule backup is programmed via the MSL Server Manager: Administration > Backup > Configure network backup.

An MSL backup is a complete representation of an MSL server at the time of backup. It includes MSL and application databases. It does not include application software. If you need to restore to a new system you must be prepared to install MSL, the backup file, and the application Blade. You may restore an MSL backup to an existing system without reinstalling MSL or Platform Manager.

Note

Restoring a database that originated on a higher version of Platform Manager than the restore target is not supported.

Restore from MSL backup

There are two ways to restore from MSL Backup:

  • At MSL install time:When installing MSL onto a new system you will be prompted with an opportunity to restore MSL from a backup.

  • From the MSL console: Log into the Linux console as root, type 'console' , select menu item 'Restore from Backup' and follow the prompts. When the server reboots you will be asked to select the restore method. Choose 'Restore from network share'.

Warning

You will need access to a Linux console, either by sitting directly in front of the computer or using a lights-out management terminal. the server will reboot and you will need to respond to prompts during boot up to complete the restore.

Factory reset

You may restore the Platform Manager database to its original default state.

Warnings

This command will delete all data in the system.

If the database contains ARIDs, the associated hardware IDs will not be cleared at the AMC.

To delete all data in the database, enter the following in the Linux root shell: 

\[root@d4 ~\]# /opt/dist_oria-bim-setup/scripts/maint/bim_db_delete.sh

Migrate from another Platform Manger server

Use this procedure if you want to replace an existing server (S1) with a new one (S2). After following this procedure server S1 will be halted and the configuration on server S2 will be a clone of the that on server S1.

Before starting this procedure, perform an MSL backup of server S1.

Caution

The IP address of the new server will be replaced with that from server S1.

  1. On the new server S2, follow the MSL database restore procedure, and select Restore from another running server.

  2. When prompted, enter the address and credentials of server S1, which is the server that has the database you want. When the restore is completed, if the new server does not have the Platform Manager application Blade installed, install it now.

  3. If there is an ARID, clear the hardware ID at the AMC.

Start and stop Platform Manager

The following commands are available from the Linux command line.

To start the Platform Manager application: 

  •  \[root@d4 ~\]# bimstart -–now

If the Platform Manager is already running, it will be restarted.

To stop the Platform Manager application: 

  • \[root@d4 ~\]# bimstop --now

If the computer reboots, Platform Manager automatically restarts.

Platform Manager logs

A complete set of logs may be retrieved by running the MSL Collect log files function, as follows:
In the MSL server manager: Administration > View Log Files > Collect

This is also sometimes called the "SOS report".

The sosreport.tar.gz file will be generated, containing logs and diagnostic information about your system. A tar.gz file is a compressed archive that may be opened on Windows computers with utilities such as WinRAR and 7-Zip.

Alternate backup and restore method

On the Linux command line, you can create a Platform Manager backup zip file and perform a restore later.

Caution

The backup file produced by this method is not compatible with the file produced by the MSL Backup procedure.

This method cannot restore an MSL backup file nor can an MSL Restore procedure restore a file created via this method.

  • To make a backup, use the command, bimdbzip.

  • To restore, use the command bimdbrestore.

Example

To make a backup: 

\[root@datest4 ~\]# bimdbzip 
<clipped> pg_dump: reading rewrite rules pg_dump: reading large objects pg_dump: reading dependency data
pg_dump: saving encoding = SQL_ASCII
zip file is /tmp/bimdb_20160404165835.zip

The example command above is verbose. On the last line you will see the backup file name. In the case above, it is /tmp/bimdb_20160404165835.zip. Store this file in a safe place.

To restore the file:

Note

Platform manager will reboot. 

bimdbrestore --file /tmp/bimdb_20160404165835.zip --dbname zip --reboot

This full command must be entered on one line.

For more information on the usage of these commands, type: 

  • \[root@datest4 ~\]# bimdbzip -–help
  • \[root@datest4 ~\]# bimdbrestore --help