We want to host an oracle 11g server for a customer. Let say the company and customer are in New York.

our company has a data center in New York and Texas with high speed connection between sites,

Does it make sense to setup a DEV/TEST box in Texas and PROD box local In NEw york. The point of this is to use the DEV/TEST box as a production box in case the PROD box gets a disaster (flood, fire, etc.).

Does this make sense? Is there any pros/cons of doing this versus having two boxes local in New York.

All dba administration will be done in New York.
Who is Participating?
George K.Connect With a Mentor Commented:
A test environment is not to be used as a disaster recovery system.
Their purpose of use, and function is completely different

So if it is not a matter of budget/costs these two,  should be separate systems.

Anyway many companies tend to do this.
In case the testing system will have to be used as a disaster recovery option, one should consider that there might be additional effort/costs
to bring this systems at the same level of functionality the production system was:
-remove all features serving testing purposes
-re-instal/reconfigure so that it matches the specifications/features of a productive system.
-restore data etc

All this of course, concerns both hardware and software.
Everything depends on how critical/how long and what kind of effort will be needed to restore your production environment.

I wouldn 't recommend having a test system to be also used as disaster recovery option.
The correct answer is to keep them separately ;-)
Mixing them up might have serious unpredictable side effects at critical moments.

George K.Commented:
1) regarding disaster recovery planning:disaster recovery sites should always at a different geographical location-something like 150Km away from the    
    productive site. Otherwise it doesn't make sense.
2) If there is no networking / bandwidth issues the testing system could be also placed at Texas.
     In this case, regarding large software updates/upgrades, CD 's , backup set placement on devices, or for example system restarts/reloads minimum
     physical presence/help will be required.
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

sam15Author Commented:
so basically you recommend having a production box, dev/test box and dr box?
it would be kind of expensive.

I think the idea is as follows.

If production box in NY goes down, you can take an oracle backup, and create and restore it to the DEV/TEST box in TX, then you switch all users to use the IP of that  box (in Texas) until you fix the issues in NY box. Cant this be done?

If the O/S is similar on both systems then it might work but if you do an image copy of production box to deve/test box you wipe out all you dev/test databases. am i correct?
slightwv (䄆 Netminder)Connect With a Mentor Commented:
It 'can' be done the question is 'should it'.

The number one question you have to answer is:  How long can the PROD system be down?

You also have issues about code 'in progress' on the DEV/TEST system before you would want to wipe it for the PROD retore.

I also agree that your dev/test boxes are typically not a mirror of production and are typically configured very differently.

>>it would be kind of expensive.

In the grand scheme of things, hardware is cheap.  You need to look at the larger picture:  How much does 1 hour of downtime cost?

I would strongly suggest you go with a third DR system using data guard or streams replication.
Mark GeerlingsDatabase AdministratorCommented:
I agree with the others, that the main issue is not: "Can you put a Dev/Test environment in Texas and a Production site in New YorK?"  Because, you certainly can do that if you want to.  The main question is "Should you...?"

Yes, it will certainly cost more initially to set up a third site that will be strictly a disaster-recovery site.  But waiting to re-configure a Dev/Test environment to support production if you ever have to do that will also cost something.  The questions are: how long will that likely take you and how much will this down time cost your customer?
sam15Author Commented:
the prod system can be down for 3 days. we have to get it back up in that time.

This is a lightweight database system (30 GB).

I am not following you when you say you have to rebuild the dev/test box. Do you mean the O?S. I am thinking all you need is to create a 3rd PROD instance and export the production database. Am i missing something?

I am also thinking whether it is better to hav DEV/TEST/PROD on one box in NY and have a 2nd box with an image backup in TX for DR. OUr deve/test is very lightweight and we have been doing that for 10 years. I know many say it is not good practice. But would not this work better.
Mark GeerlingsConnect With a Mentor Database AdministratorCommented:
No, I don't mean rebuilding the O/S.  That step would normally not be required.  I'm assuming you have the Dev/Test server running the same O/S as the Prod system, and that you have a copy of the Prod database software already installed.  What you would need to rebuild is the Prod database.  If the Prod system really is down (or inaccessible) you would need to restore a copy of the Prod data on the Dev/Test server.  This may (or may not) involve shutting down the Dev and Test systems to allow sufficient server resources for the Prod system to be restored, then started.

You mentioned "export the production database".  Would you actually plan to use the Oracle export (or expdp) utility for this?  That is possible, but that is not the usual way of replicating a production Oracle database server.  Doing a database restore from an export (or a DataPump export) usually takes *MUCH* more time than doing a database restore from a backup.
sam15Author Commented:
i mean restore production system from a backup.

cant you do it on the DEV/TEST server with another production instance if needed?

we can have the instance ready but unused. WHen production server goes down, just go to the DEV/TEST server and restore the last copy of production.
slightwv (䄆 Netminder) Commented:
As long as your backup is good there should be no reason you cannot restore it on whatever box you have available.

Where you might run into problems is the DEV/Test box might have a different version or Oracle installed.

You will need the same version/patchset installed that is running in production.
Mark GeerlingsDatabase AdministratorCommented:
Yes, you should be able to restore a Prod instance on a Dev/Test server, assuming o course that you have enough free disk space on the Dev/Test server.  Watch out for TNS port conflicts.  To avoid this, you should make sure that your Dev and Test systems normally use a different port than the one you use for production.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.