Skip to content

Moving to a New Server

Move a MetaMiner Server installation, with its configuration and MetaMiner Database (MMDB), to a new Windows machine.

Before you begin

  • The new machine meets the System Requirements and can reach the Microsoft endpoints of your cloud over HTTPS, through your proxy if you use one. See Network and Microsoft Endpoints.
  • You have the installer for the same MetaMiner version that runs on the old server.
  • You have a license valid for the new machine.
  • Plan a maintenance window: collection stops while you move. Keep it short: Microsoft returns activity events for about the last 30 days, so a longer gap loses activity.

TODO: state whether a license is bound to the host

Confirm whether moving to a new host name requires a new license key.

What to move

Item Path (under server\) Notes
MMDB data\mmdb\ (embedded) Move with a backup and restore; see below
Configuration config\ Includes config.json (or config.ecf and config.ek), webapps.json, API clients (api-clients.json, token hashes only), trusted certificates
MetaMiner users and roles security\
License files licenses\
Custom properties MetaMinerServer.properties Only if you have custom settings
Dashboard user group silver-jobs\pbi-license-waste\job.json Only if you set a user group on Settings > WebApps; or set it again in MMA
Power BI backup archives alerts\archives\pbi\ by default, or under the Backup Archive Path Only if stored locally

Steps

  1. On the old server, in MMA, click Stop Server. Leave the embedded database (InfolytikPostgres) running.
  2. Back up the MMDB with pg_dump; see Back Up and Restore MMDB.
  3. Copy config\, security\, licenses\, MetaMinerServer.properties and any local backup archive folder to a safe location.
  4. On the new machine, install the same MetaMiner version. See Install the Server. Do not start the server.
  5. Restore the MMDB backup into the new embedded database.
  6. Copy the saved folders over the new installation's server\ folder.
  7. Open MMA on the new machine and check:
    • Configure MMDB: host is localhost for the embedded database, then click Validate and Close.
    • BI Environments: each Power BI environment validates. The new machine makes the Microsoft calls now, so proxy and firewall rules must allow it.
    • Settings > Backup > Backup Archive Path: the path exists on the new machine.
    • Settings > System: memory and temp folder suit the new machine.
    • Settings > WebApps: the dashboards user group is set as before.
  8. Click Start Server.
  9. Point MetaMiner Clients and dashboard users at the new server name; see Connect to a Server.
  10. When the new server works, disable the services on the old server so it does not collect the same tenants.

Do not run two servers on the same tenant

Two MetaMiner Servers collecting the same tenant double the calls to Microsoft and share Microsoft's per-tenant limits, so both are throttled. Stop and disable the old server before or right after the new one starts.

Encrypted configuration

If the configuration is encrypted, copy both config.ecf and config.ek and the use.encrypted.config line in MetaMinerServer.properties.

Verify

  • The MMA health indicator shows no red state and environments show Validated.
  • The MetaMiner Client shows existing content and history.
  • Collection Status shows the environments current after the first cycles.

Troubleshooting

MMS cannot connect to the MMDB after the move

config.json may still point at the old host. For the embedded database, set the host to localhost in Configure MMDB.

Environments fail validation on the new server

Check DNS, proxy and firewall access from the new machine to the Microsoft endpoints. See Validate the Connection.

Next steps