Tech Tip - ehealth - Supported reasons to move an eHealth database.

Document created by Rich_V Employee on Aug 26, 2014Last modified by SamCreek on Dec 17, 2016
Version 2Show Document
  • View in full screen mode

Supported reasons to move an eHealth database.


There are only 2 main reasons why you would copy an eHealth database from one host to another:


1.     If you have machine failure and you are moving the eHealth install to a new machine.

2.     If you are doing a migration from one OS to another (i.e. win2003 à win2008, windows à UNIX) or to newer hardware.


When you copy the DB, you are copying everything.

Machine names, machine id’s group info.


This is especially problematic if you try to use the DB from one cluster member to create another cluster member.

This should never be done.


If you need to split a database, then you can engage CA services to perform a split/merge.

Otherwise, you should always create a new DB when you do the new install.