sam15
asked on
OrclProdBox_Arcitecture..
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Additionally,
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.
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.
ASKER
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?
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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?
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?
ASKER
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
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.
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.
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.
http://www.drj.com/drworld/content/w1_025.htm
http://searchdisasterrecovery.techtarget.com/feature/Disaster-recovery-testing-FAQ
http://bazman.tripod.com/testplancontents.html
http://www.fortuitous.com/docs/primers/SystemsTesting.pdf