What is MigDBUtil?

 

The Migration Database Utility (MigDBUtil for short) is used in scenarios by which you have replicated mail files from a remote slow connection server, to a more centrally located server in order to improve migration throughout, or simply for preference. When you use Notes Migrator for Exchange is has the Directory Export process that reads the NAB and takes the mail file path address from this and imports that into our database. So the NAB will not reflect the replicated mail file changes, which is where the MigDBUtil tool comes in, which allows us to modify these changes. A screenshot of the tool is below. The tool consists of the following components:

 

    · Add Servers

This component is only used when you have replicated the mail files to a new server which would in no way be within our database and until recently, not have been within the NAB. If you have replicated the mail files to a server that already existed, then this is not required to be run, you can simply run the modify Mail File Paths. By default sample input file is provided within the default installation difrectory named ‘sample_server.csv’

· Modify Mail File Paths

Here we use this by specifying a collection, namely a grouping of users, with an associated input file that contains details of the source path and the now new path. By default a sample input file is provided within the default installation directory named ‘sample_mailfilepath.csv’

· Import/Export Collections

This will not be discussed in detail but is used to back and restore any or all collections you use for the migration

 

 Looking at the Locate Notes Data Stores screen, you may have the following mail file path, which is named as the Domino Server Address column within the NME GUI under the Locate Notes Data Stores menu.

 

 

 

In our scenario we wish to change this path because you have replicated the mail file from the following path of:

Domino65/Wingra!!mail\Folder\gwbush.nsf

To the following new replicated path of:

NewServer/Wingra!!mail\NewFolder\gwbush.nsf

 

Run the Add Servers

Because we have specified a new server we will need to run the Add Servers section of the MigDBUtil and also generate/modify the sample_servers.csv file with the new server name. Below is a screenshot of the template file supplied that has been modified with the new server I will be using.

 

 

Now we save this file and use the Add Servers component to add this server record into our database as seen below.

 

 

Now this record has been successfully added into our database, we can now continue on to modify the mail file path of the user(s) by utilising the ‘Modify Mail File Paths’ component so that when we finally migrate, we are migrating from the newly replicated NSF.

 

Run the Modify Mail File Paths

 

Open the template ‘sample_mailfilepaths.csv’, located in the root install directory. You will need to modify this with Excel (or notepad) and a bit of copy/paste. The original file is below for your reference.

 

 

 

When modified, the resultant file will look like the following:

 

 

The ‘Source Address’ column within our database must match the one within this input file. We gain the ‘Source Address’ column value from a collection we can export from the tool. This is done via the Manage User Collections in the Quest GUI, selecting the collection and then exporting that collection. A snippet of this export is shown below. So we use the ‘SourceAddress’ column as shown, and paste this into the ‘Source Address’ column of the ‘sample_mailfilepaths.csv’.

 

 

Now run the modify Mail File Paths specifying the input file ‘sample_mailfilepaths.csv’ and the result is shown below.

 

 

To confirm this has now worked, the following Locate Notes Data Stores screen will reflect the changes in the GUI.