[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: Development testing on Production (?) servers --
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Re: Development testing on Production (?) servers -- was 0.3-rc4 released |
Date: |
Thu, 4 Sep 2008 18:25:21 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Thu, Sep 04, 2008 at 08:40:07AM -0700, Jim Busser wrote:
>> It would also be fairly easily doable to reconfigure the
>> source database to not allow any further connections.
>
> Here are the precautionary notes I have added to the wiki. For comment.
>
> One last, *important production note*. Since old versions of the client
> will continue to grant access to the old database, you definitely do not
> want new clinical entries or clinical revisions to be split between two
> databases and the same goes for any importers at risk of continuing to
> import data into the old database. Accordingly, in preparation for
> migrating your *production* database,
>
> * ensure that you have available suitably-configured copies of the
> client for the new production database
> * backup, and then insert a suitable logon banner into, the about-
> to-be-upgraded database
> * stop any and all importers, and point them to the about-to-be new
> database
> * upgrade the old database, resulting in a cloned "new" database
> * modify the logon banner of the new database
> * restart any and all importers
> * depending if it is desired to keep the old database available,
> reconfigure it to not allow any further connections and/or remove or
> control the copies of the client that would point to it
It seems each starts to warrant its own page in the
Administrator Guide:
- Server and Database Installation
- Database upgrade (perhaps under Maintenance ?)
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346