Upgrades, Backups, Restoring & Rollback Procedures

The MCS system has various persistent data stores which should be backed up on a regular basis to minimize the risk of data loss through hardware or software failure.

The following sections outline the places where MCS stores data and the processes that should be followed to:

Create regular backups of the system.
Perform pre-upgrade backups.
Restore to the current or an alternate server using a backup.

The procedures outlined here cover all the data required for the Mitel Communication Service, MiVoice Office Campaign Manager Outbound and MiVoice Office Call Reporter.

For systems using the MiVoice Office Call Recorder features of the solution, only the data associated with calls is backed up using these procedures. Call Archiving must also be implemented to ensure all call recording audio is backed up.

MCS Data Storage Locations

The following elements of the solution need to be backed up, ideally to location which is on different hardware to that which is running the MCS software:

SQL Databases -> Used to store configuration and Call/Chat history.
Registry configuration -> Used to store watchdog and database connection settings.
User files -> User profile images
6900 Handset files -> Firmware files, background images etc.

SQL Databases

The MCS solution uses multiple databases to store configuration, call and chat data. The following table describes each of the databases used by the solution and what is contained within it:

Database	Description
CallRecorder	The working database for the MCS solution. Used to store configuration information (User, PBX), chat history and the call data for the current day.
CallRecorderArchive_1	The first archive DB used by the system, stores historical audit and call data.
CallRecorderArchive_N	Additional archive database where is N is a numeric value which increases over time. New archive databases are created if the time or record limit is reached of the current archive database. For more information please refer to the Database Maintenance section.
CampaignManager	The working database for the MiVoice Office Phone Manager Outbound solution. Used to store configuration information (schedules, imports, exports etc.), campaign data and the call/user data for the current day.
CampaignManager_Archive	Used to store historical call and user data.

All of these databases are automatically backed up on a nightly basis to the following location; C:\DBBackups.

For further resilience it is advised to keep a copy of these backups on hardware different to that which the MCS is running on.

For more information on Database Backups, please refer to the Database Maintenance section.

Registry

The MCS stores a subset of configuration information in the registry. This information includes:

Server ID -> The unique ID given to the server if part of an MCS network (For future use).
Roles -> Configuration of which roles the server is implementing.
Watchdog -> Default configuration for the watchdog.

It is wise to back up the following registry location (including sub keys) after the initial MCS installation:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mitel\CommunicationService\Roles]

User Files & 6900 Handset Files

MCS stores some data outside the database so as not negatively impact database performance. Currently this is limited to:

Profile images users upload from Phone Manager Desktop and Phone Manager Mobile clients.
Firmware files uploaded for 6900 Handsets
Background images uploaded for 6900 Handsets

To retain these files when restoring an MCS solution, ensure the following folder is backed up:

C:\ProgramData\Mitel\Mitel Communication Service\Net Store