May 6, 2009 at 6:00 am
HI Everyone,
I have been recently doing Datamodel design and I do understand disaster recovery is very important to take in to consideration. When one should actually implement Disaster recovery? Is it after development or before development? Any suggestion will be very helpful.
ta
May 6, 2009 at 6:07 am
On the first day. You need disaster recovery in place for your developement area.
May 6, 2009 at 6:50 am
homebrew you have my vote.
DR must be part of the project's blueprint from day one otherwise how are you planning to get it funded?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 6, 2009 at 7:35 am
Does this mean I need to create replication before starting the development?
Ta
May 6, 2009 at 7:40 am
vidhyasudha (5/6/2009)
Does this mean I need to create replication before starting the development?Ta
No, it does not mean you have to create replication. It means you need to have a plan for recovering what you could lose. Replication is only one of the options.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
May 6, 2009 at 7:42 am
vidhyasudha (5/6/2009)
Does this mean I need to create replication before starting the development?Ta
Not necessarily. You just need to put whatever measures in place that make you feel comfortable if your server died while you were in the development process. This could just be backing up your database (full and tlog) on a defined schedule and make sure they are on a different server. The reason I think tlog backups are so important when developing is that if you make a mistake and want to get back to your previous state, you can.
May 6, 2009 at 7:48 am
I clearly understood that I first plan what needs to recovered in case of disaster then try to figure out DR method that suits my business process and implement at early stage so that I dont miss anything even during development. Im grateful to all of you replied to this post. Thanks again.
Ta
May 6, 2009 at 7:56 am
Just as a short note, backup and restore should be your first DR thought. You might supplement that with mirroring, replication, etc., but be sure you can restore a db if a server dies tomorrow.
May 6, 2009 at 7:59 am
vidhyasudha (5/6/2009)
I clearly understood that I first plan what needs to recovered in case of disaster then try to figure out DR method that suits my business process and implement at early stage so that I dont miss anything even during development. Im grateful to all of you replied to this post. Thanks again.Ta
Keep in mind that a DR plan for development can be completely different from a production DR plan. A development DR plan could be as simple as, for example, scripting out the database(s) after every code change and daily backups of the data. This probably would not be enough for most production databases.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
May 6, 2009 at 8:06 am
Alvin Ramard (5/6/2009)Keep in mind that a DR plan for development can be completely different from a production DR plan. A development DR plan could be as simple as, for example, scripting out the database(s) after every code change and daily backups of the data.
... and send those scripts/dump files to an external location.
For small projects the poors man solution is to zip the daily DR files, attach them to an email and send it to a "secure" hotmail account 😀 No kidding, I've seen that happening. 😉
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 6, 2009 at 8:14 am
PaulB (5/6/2009)
Alvin Ramard (5/6/2009)Keep in mind that a DR plan for development can be completely different from a production DR plan. A development DR plan could be as simple as, for example, scripting out the database(s) after every code change and daily backups of the data.
... and send those scripts/dump files to an external location.
For small projects the poors man solution is to zip the daily DR files, attach them to an email and send it to a "secure" hotmail account 😀 No kidding, I've seen that happening. 😉
I always email myself a copy of my genealogy database backups.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
May 6, 2009 at 8:35 am
Nothing wrong with emailing to Hotmail if it isn't sensitive information.
We used to zip up each day, copy to a remote disk, separate folder for each day. Gave us easy 7 day recovery for development stuff.
May 6, 2009 at 8:44 am
sorry, Im not able to see any information on the link you provided. Can you give specify the correct link
Ta
May 6, 2009 at 12:39 pm
DR is the basic building block of a any online business.Personally it makes me more confident having a solid DR plan.
I always tend to give this example to everyone that of the famous Journalspace, check out Brent's blog:
http://www.brentozar.com/archive/2009/01/why-back-up-ask-journalspace/
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply