Migrating to a new server

When upgrading your server, we recommend that your hardware technicians follow the steps in this guide to ensure your transition is as smooth as possible.

For information on Minfos Server configuration, please refer to Minfos System Requirements

Server Migration options/limitations

Windows currently has some limitations (based on the Windows database engine that is packaged with the Windows Operating System) on the environment the Minfos database can migrate to.  This is because the Microsoft esent engine version which the Minfos Database runs on, is not backwards compatible when migrating to older Operating Systems. 

Note: Minfos recommends having a Windows 10 Operating system (temporary server option) available on the network in the event of Server failure.  This provides the option to migrate to a Server 2022 after the Server hardware issue is addressed. *Windows 11 does not migrate to Server 2022

Listed below are the Database migration options (from operating system A to operating system B) available:

Migrate FromMigrate To
Server 2012 / R2Server 2012(R2) / 2016 / 2019 / 2022 - Windows 10
Server 2016Server 2016 / 2019 / 2022 - Windows 10/11
Server 2019Server 2019 / 2022 - Windows 10/11
Server 2022Server 2022 - Windows 10/11
Windows 10Server 2022 - Windows 10/11
Windows 11Unable to migrate from Windows 11 at this stage
Warning:  Migrating the database to an earlier Operating System version may not be supported.  Please ensure you are migrating to the same Operating System version or later. For example: Migrating from Windows 10 to Windows Server 2019 (or older) is not supported. Windows Server 2022 will be required to support the migration.


Migration options:

  1. VM Migration
  2. Physical Server migration


VM Migration Notes/Considerations:

Copying the vhdx will help speed up some log file copying.  We recommend following consideration:

  • Before copying the h: vhdx, rename the logs folder. This will help split the gap between old log files and recently created log files, reducing any 'delta' changes in log file copies after the go live
    • FROM: H:\MINFOS01\LOGSPicture2
    • TO: H:\MINFOS01\LOGS-PreMigration
  • After setting up the new environment with the attached vhdx, before proceeding with a clean install of the minfos database, rename the folders below (this will help ensure a clean new install of minfos in a new H:\MINFOS01 folder): 
    • FROM: H:\MINFOS01
    • TO: H:\MINFOS02
  • Proceed with the guideline below, noting that any file copies from the old environment will be located in your H:\minfos02 folder and will need to be copied/moved to the new install location
    • Recommend moving the LOGS-PreMigration folder based on the qty of files within this folder, it is faster this way
      • FROM: H:\MINFOS02\LOGS-PreMigration
      • TO: H:\MINFOS01\LOGS-PreMigration
    • Then the live migration takes place, the H:\MINFOS02\LOGS folder will have less log files to copy over


Server Migration Steps

In this section we have referred to the servers in the following way:

  • Old Minfos Server/Database: This is the system that is currently running and will be superseded
  • New Minfos Server/Database: This is the new system that will supersede the old Minfos Server


Migration Preparation steps

Please be aware of the following steps which will require action after the server migration is complete:

  • If the store is located in Tasmania, please log a ticket with Minfos to setup RTR
  • My Health Record Setup, re-activate PRODA and re-install certificates:
    1. Proda
    2. NASH Certificate
  • If the store is using the Minfos Gateway for Multistore, please raise a ticket with Minfos to setup the Gateway Registration
  • If the store has the Minfos Remote Access Proxy installed on the server, please raise a ticket with Minfos to get this re-installed on the new server

Third Party applications to be contacted and updated to point to the new server, consider applications like, but not limited to:

  • Plus One
  • Packing
  • DDBooks/Modeus
  • Robotic Dispense


Step 1: Run a manual backup of the old Minfos Database

On the old Minfos Server:

  1. Close all Minfos applications on all workstations except for the backoffice machine.
  2. On the backoffice machine, leave the Minfos Launch Pad open, then close all other connections to Minfos, including PBS Online.
  3. On the Minfos Launch Pad, click the Special menu, and then click Back Up Database. 

The Backup database window is displayed.

If the Connections text box shows:

  • More than 0 connections, this means that Minfos (or a Minfos utility) is running on one of the pharmacy’s computers 
    1. Locate and close the Minfos program or service that is still running.
    2. Close the Back Up Database window then re-open it to refresh the connections, until there are “0” connections.
  • If 0 connections, check the Continue check box, then click Okay, to backup the old Minfos Database


Step 2: Set up the new Minfos Server

Note: We recommend that the new Minfos Server is set up before taking the old server offline.

Your hardware technician is responsible for setting up the new Minfos Server environment appropriately so that it runs efficiently for your store. See Minfos Server station in Minfos System Requirements for hardware requirements and recommendations.

Retrieve information from the old Minfos Server

On the old Minfos Server:

  1. Log in as an administrator.
  2. Get the latest Minfos build:
    1. Download the latest Minfos software release—Minfos Launch Pad > File > Minfos Software Update > Yes.
    2. The SOFTUPD.exe package is located in the folder H:\MINFOS01\MNET\SOFTUPD.exe.
      1. You can copy the SOFTUPD.exe to the new server in the same location.
  3. Rename the log folder to allow the start of copying over the log files up to this point:
    Note: By law, a store is required to keep the last 2 years of the ePrescribe folders log files.  This folder can contain an excessive number of small files, and copying the files to a new environment can take hours. This file copy is not required for the migration go-live, however, will be required before or after the store completes the database migration.
    1. FROM: H:\MINFOS01\LOGS
    2. TO: H:\MINFOS01\LOGS-PreMigration
  4. Copy the following files and folders onto an external storage device:
    • F:\MINFOS01\DB\BACK\* (All files and folders). This is the latest Minfos backup and contains the following folders: 
      • CLAIMS 
      • FMT 
      • LABELS 
      • new
      • PATIENTS
    • H:\MINFOS01\MNET\SOFTUPD.exe. This is the latest Minfos software release that you downloaded in the previous step
    • H:\MINFOS01\dseback.dat
    • H:\MINFOS01\Multistore\. Only required if your store is part of a Multi-store group
    • H:\MINFOS01\vcredist_x86_2022.exe
    • H:\MINFOS01\LOGS-PreMigration (can be done before or after the migration - not required for go-live)


Step 3: Set up the new Minfos Database

On the new Minfos Server:

  1. Create the following database folders:
    • H:\Minfos01\DB
    • F:\Minfos01\DB\BACK
  2. In the H:\MINFOS01 folder, paste the following files that you copied from the old Minfos Server:
    • H:\MINFOS01\MNET\SOFTUPD.exe
    • H:\MINFOS01\MinConfig.exe
    • H:\MINFOS01\dseback.dat
  3. In the F:\MINFOS01\DB\BACK folder, paste the folders that you copied from the old Minfos Server:
    • CLAIMS 
    • FMT 
    • LABELS 
    • new
    • PATIENTS
  4. Copy all of the files in F:\Minfos01\DB\BACK\FMT and paste into H:\Minfos01\DATA.
  5. Copy the folder F:\Minfos01\DB\BACK\LABELS and paste into H:\Minfos01.
  6. Copy the folders log files H:\MINFOS01\LOGS-PreMigration (Can be done before or after migration).
  7. Run Minconfig.exe and ensure the following information is correct:
    • Name / Address
    • ESE Database Locations and options
      1. Database: H:\MINFOS01\DB
      2. Backup: F:\MINFOS01\DB\BACK
    • Note: If you have issues running Minconfig.exe, run vcredist_x86_2022.exe, then try running Minconfig.exe again
  8. Run H:\MINFOS01\MNET\SOFTUPD.exe and extract to H:\MINFOS01.
  9. .Run H:\MINFOS01\Minw2d.exe
    • All Minfos files and folders are created and the minfos database service starts automatically
    • Note: To view the Minfos database service status, open wcsdb5.ui.exe and view the database status
    • When prompted, restore the database, then confirm that the date and the time of the last dispensed script are correct
  10. Create a shortcut for wcsdb5.ui.exe on the Desktop and rename it Minfos Server UI.


Step 4: Log into the new Minfos Database

On the new Minfos Server:

  1. Run minw2.exe.
  2. Log in using the pharmacy’s credentials.
  3. To set up a new client, or modify an existing one, follow the steps in Preparing a new Minfos Client specified in Minfos System Requirements.


Migrate to the new Minfos Server (Night of Go-Live)

The migration process involves copying the most-recent data from the old Minfos Database to the new Minfos Database.

Note: Migrating the pharmacy’s data must be performed outside of trading hours.


Backup the old Minfos Database

This backup is only required if the pharmacy has traded since the last backup you performed in “Step 1: Run a manual backup of the old Minfos Database”. 

If the pharmacy has not traded since the backup, you do not have to back up the database again. Continue to the next procedure.

Note: To backup the old Minfos Database see, “Step 1: Run a manual backup of the old Minfos Database”.


Copy data from the old Minfos Database to the new Minfos Database

1. On the new Minfos Database, delete the contents of the following folders:

  • H:\Minfos01\CMI\PATIENTS
  • H:\Minfos01\DATA
  • H:\Minfos01\DB
  • H:\Minfos01\LABELS
  • H:\Minfos01\LOG 
    • Note: this will be a smaller size copy for the go-live migration with the H:\MINFOS01\LOGS-PreMigration separated out
  • H:\Minfos01\XML
  • F:\MINFOS01\DB\BACK

2. Copy the .config and .log files from the old Minfos Database to the new Minfos Database:

  • H:\MINFOS01\*.config These files contain various configurations for eRx, Robotic Dispense, and other integrations
  • H:\MINFOS01\*.log  These files are important to keep as history of the database’s activity

3. Copy the contents of the following folders from the old Minfos Database to the new Minfos Database:

  • H:\Minfos01\LOG
    • Note: this will contain a lower number of logs compared with the H:\MINFOS01\LOGS-PreMigration so this file copy will be 'quick' in comparison to the Logs-PreMigration folder
    • This helps to ensure that log files are kept with the database, for diagnostic purposes
  • H:\MINFOS01\XML 
    • This folder contains previously downloaded claims reports and other third-party files
  • F:\Minfos01\DB\BACK
    • This folder contains the backup of your old Minfos Server Database


Configure the new Minfos Database

On the new Minfos Database:

  1. Copy all of the files in F:\Minfos01\DB\BACK\PATIENTS and paste into H:\Minfos01\CMI\PATIENTS.
  2. Copy all of the files in F:\Minfos01\DB\BACK\FMT and paste into H:\Minfos01\DATA.
  3.  Copy the folder F:\Minfos01\DB\BACK\LABELS and paste into H:\Minfos01.
  4. Run Minconfig.exe and ensure the following information is correct:
    • Name / Address
    • ESE Database Locations and options
  5. Run Minfos and check that all of the data is correct:
    1. On the Desktop, run the Minfos Server (wcsdb5.ui.exe).
    2. When prompted, restore the database, then confirm that the date and the time of the last dispensed script are correct.
    3. On the Desktop, run Minfos Launch Pad (minw2.exe), then confirm that all users can log in and the data is correct. For example, check that the script history, sales history, and stock order history are correct.
  6. Check that the software and the database schema are synchronised:
    1. Close the Minfos Launch Pad.
    2. Run H:\MINFOS01\MNET\SOFTUPD.exe and extract to the default location.
    3. On the Minfos Database window, click Update.
  7. The Minfos software is updated. Ensure all client machines are connecting to the new server. Minfos requires the F: and H: to be mapped to the new server’s F: and H: drives.


Update configuration files on Minfos clients

If the new server has a new machine name or a slight configuration change in MinConfig.exe, the configuration files on each Minfos clients must be updated. 

To update the configuration files on Minfos clients:

1. On each client machine, run command-prompt and run the following commands:

CD c:\Minfos01
Copy h:\Minfos01\dseback.dat
Copy h:\Minfos01\*.cfg

2. Run the Minfos Launch Pad (minw2.exe).

The Minfos software may update automatically on launch before you can log in.


Check that the new Minfos Server is set up correctly

Before the new Minfos Server can go live, check that you can:

  • Scan and dispense an e-script
  • Scan a product and sell a script at the till
  • Perform a stocktake
  • If the pharmacy uses Loyalty, ensure you can perform a loyalty sale at the till


Take the old Minfos Server offline

Your hardware vendor can advise you of the best way to decommission your old Minfos Server.


Post migration

After the migration is complete, there are some additional steps required to help configure the various integrations.