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 CMS, Audit and CMS databases, and web tier of every environment. See Network Ports and Firewall.
  • 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: pulls stop while you move.

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), 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
Backups and versions alerts\archives\ and backup\ by default, or the paths on Settings > Backup 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 and version folders 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.
    • Settings > Backup: paths exist on the new machine.
    • Settings > System: memory and temp folder suit the new machine.
  8. Click Start Server.
  9. Point MetaMiner Clients 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 pull the same environments.

Do not run two servers on the same environments

Two MetaMiner Servers pulling the same CMS double the load on BusinessObjects. 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 validate.
  • The MetaMiner Client shows existing content and history.
  • Data Integrity Status counts match after the next pulls.

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 and firewall access from the new machine to each CMS and web tier, and trust any certificates again with Test REST.

Next steps