Migrating GoldMine to a new server.[Uploaded File]

Version 1


    How to move any version of GoldMine and SQL to a new server.


    If you have any questions about the below steps you may contact your GoldMine solutions partner for further assistance.  Please note these steps do not take into account all variations in a migration path to a new server.

    1.    Log into MSSQL on the production server. 
    2.    Make a backup (.bak) of each database that needs to be moved to the new server
    3.    Move the .bak files to the new server by the method of your choice
    4.    Install SQL Server on the new server.  Be sure to install SQL as “Mixed Mode” authentication (see also Install guide if steps to install Microsoft SQL Server are needed)
    5.    Restore the .bak file to each database shell that was created respectfully >> make sure to verify the Microsoft SQL Server Compatibility Level for the database(s) in the Options of the SQL Database
    7.    Install GoldMine (the same version) on the new server and select “Create new database”.  This is just a dummy database to connect to GoldMine
    8.    Login using the default username and password combo: master/access
    9.    Once connected to the new database in GoldMine the database alias(es) need to be created in order to make them available for GoldMine. It is absolutely recommended to use the same alias as on the old server although also different names are technically possible by clicking on Tools >> Databases >> Alias Manager (each restored database requires again a database alias)

    10. While logged in as a Master/access >> Set the login database under  Tools > Options >> Login. Set the database under GoldMine Database (GOLDDIR) and if applicable/possible the correct Default Contact Database. File >     Exit from GoldMine and log back in to open the Restored database.

    11.  When the original database alias names were used the alias(es) should be now already attached as additional contact sets but this needs to be verified and if applicable adjusted for each database via Tools >> Databases  >> Open Database and attach each alias using the Properties or Attach button

    12.    To open the database click on Tools > Databases >> Open Database
    13.    Highlight the database and click OPEN

    14.    On the production (old) server copy the GoldMine root directory and move it to a different directory the new server.  (desktop is fine)
    15.    Move the desired data files into the new GoldMine directory. (default is C:\Program Data)
    a.    FOLDERS: Please note that some of these folders might not exist if you do not use the specific feature associated with the folder.
    i.    \Docs
    ii.    \Reports
    iii.    \Templates
    iv.    \Mailbox 
    v.    \TMPLinks
    vi.    \Macros
    vii.    \Sync
    viii.    \Setup
    ix.    \Speller
    b.    FILES:  Please note that some of these files might not exist if you do not use the specific feature associated with the file.  All located at the root of GoldMine Folder. Be sure to include the Master files as well.
    i.    username.ini - Example, your user name is Steve, the file will be Steve.ini.
    ii.    username.tbi - Example, your user name is Steve, the file will be Steve.tbi.
    iii.    username.bin – Example, your user name is Steve, the file will be Steve.bin.
    iv.    Lookup.ini
    16.    Update the GM.ini on each client machine to point to the new server directory
    a.    If you were launching GoldMine from a network share you may have to re-map the new server and change the target of the GoldMine icon.
    b.    Local installs will have their own gm.ini file in the GoldMine root directory.  This gm.ini will need to be updated to reflect the location of the new realini location.
    ** please note that depending on the file path of the linked documents/attachments, you may need to update the database references on the back end to reflect where the new files are located by using the Linked Document Mover under Tools > Data Management > Move Linked Docs & Attachments