Database Import

You can use an existing Macula database to import resources into any other Macula installation. This feature allows you to migrate the server configuration 1-to-1 or reuse the configuration of devices and channels, user profiles, maps, recording calendars, etc., to speed up the site configuration.

Prerequisites

The database may come from any server and/or software edition, but it must contain no more than one server in its configuration. If you wish to import from a Macula Enterprise database, create a copy of it for backup, then remove all recording servers from its configuration first (move the devices to the Macula Enterprise server first if you need to preserve them), and use the single-server version for resource import.

Possible scenarios for this feature may be as follows:

  • combine many Macula Professional servers into a single Macula Enterprise installation

  • transfer configuration from one Macula Professional server to another

The database you need to take for future import is named VMSConfig-xxxxxxxxxxxx.db and it is located in the ProgramData directory.

By default, all Macula databases are located in the following directories:

  • C:\ProgramData\GSF Corporation Pte Ltd\Macula Professional - for the Macula Professional product edition

  • C:\ProgramData\GSF Corporation Pte Ltd\Macula Enterprise - for the Macula Enterprise product edition

  • C:\ProgramData\GSF Corporation Pte Ltd\Macula Enterprise Recording Server - for the Macula Enterprise Recording Server component of a Macula Enterprise installation

To start data import, press the application menu button in the upper-right-hand corner of the Macula Console window and choose the Configuration import from a database option.

From the standard Windows Explorer Open File dialog box, locate the target VMSConfig-xxxxxxxxxxxx.db file and open it.

The resource selection dialog box will appear. Choose the items to be imported using checkmarks in the left column; use the search field in the upper right corner to filter the items by type or by any other text field. In case the imported entities already exist on the host server (e.g., built-in recording profiles), their import action will be Merge; otherwise, the action will be marked as Add. When resources are merged, their permissions are merged as well. All types of resources can be imported.

When you have finished with resource selection, click OK to proceed.

Before applying all the changes, review your import summary and click OK to confirm and finish the import.

All selected items will be added to the server configuration immediately and you will be able to work with them normally.

Last updated