We need to use test server and test databases as a prod.

Mike

Moderator
Hi ,

Tom/team,

Progress version:- 9.1d 32 bit and 64 bit
Os version:- HPUX
application version:- Eb2 sp4 qad mfg/pro

We have one test server for two databases. I mean its a different test server where we have two test databases same as production and they are refreshing every week from prod progress backup. So the requirement to make test server test database as a prod. So what are the requirement for that for database level.

1:- What are the requirements from database admin side?
2:- And what about application side?
3:- Do we need to change the ip address?
4:- How the all-prod users and access database of test? Do we need something to change server side?

Thanks Mike
 
Are you asking what you need to do in a "fail over" situation to be able to replace an existing database on a PROD server with one of the TEST databases? Presumably in a situation where the PROD server has failed?
 
Tom,

Actually , We are closing production server and database and make the test database as production. Its a requirement.
 
In that case your requirements for db admin and application admin are basically the same as "old PROD". I can't see why anything would change there. You might have to update your various scripts and config files to reflect new host names, IP addresses and ports and paths but that's not really a change in requirements.

You _could_ change the IP address (or the hostname) to be whatever "old PROD" has but that isn't strictly _required_. It would, maybe, make it easier for users that have the old IP address (or hostname) embedded in connection strings. On the other hand... NOT changing it is a good way to find out about unknown users. When their connections break they will have to reach out to you for new information. Plus your TEST users (presumably you are keeping the 2nd TEST database for testing purposes?) would need to change their target - unless you configure 2 IP addresses or hostnames for the same host.
 
Back
Top