June 22, 2005 at 2:01 pm
Time to think about it at least...
June 22, 2005 at 2:12 pm
LOL!!
* Noel
June 22, 2005 at 2:26 pm
Thanks...
June 22, 2005 at 2:29 pm
Sorry,
I never meant to be rude just that the post above was funny. I have been in your position before and is not pleasant.
Please, accept my apologies
* Noel
June 22, 2005 at 2:39 pm
Oh That's OK...I didn't even think it that way..
But ya..This problem is solved now by bringing data from some other resources ...and the company thinks to bring in new stratagies for back ups.Specially regarding the transaction logs.
Thanks for all help and keep posted about any new methods for disaster recovery.
June 23, 2005 at 6:39 am
So how much data was lost in the end?
June 23, 2005 at 7:38 am
Everything is back to normal now.That data is stored in some staging tables too.Package ran for 8 tables.Only 2 tables were not in staging ..So we had to work again on the same transactions for those 1 and half days.
Thanks.
June 23, 2005 at 7:42 am
k, it's not the worst case scenario then... the good news is that you'll be able to restore the db next time a problem occurs. you tested the new backups you're taking right???
June 23, 2005 at 7:54 am
Ya...
This is the plan the company wants to execute-
1. A full database backup on Sunday night.
2. A set of transaction log backups'll be made every four hours during the day,
3. Each night a differential backup will be taken
working good so far.and tested well.
Let me know about any other ideas.
June 23, 2005 at 8:09 am
How about differential every 4 hours and log back ups every 15 minutes?? Can't lose more than 15 minutes of data that way.
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply