asked on

SQL database Backups

My company uses Microsoft SQL for our database. We are a logistics company. We do daily backups. But we have gotten to a point that our backup from yesterday would be too old to restore incase a disaster strikes. Transaction logs seems cumbersome to restore along with yesterdays backup. So for example a credit card company's hard drive crashes. so a purchase today will be lost if we were to restore from a yesterdays backup. What would be the best backup/restore to such a up to the minute type of server?

ASKER CERTIFIED SOLUTION

Dan Muzrall

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Member_2_231077

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Robert3rd

ASKER

We had a scenario that someone changed the quantity of a product to all our warehouse. So our servers didnt crash but it displayed the wrong information but we continued to work on and it wasnt discovered till later. so needless to say, if we restored from yesterdays backup, all the work after would have been gone. so replicating will also replicate the problem to the backup or second server. I guess i was wondering like how does credit card companies do this? Probably hourly backups, but even with that you still have transaction logs to deal with to keep synced. is there even a solution out there?

Member_2_231077

They [credit card companies] probably do a dual phase commit. The client software in the ATMs sends the transaction request to two or more databases and doesn't let you have the cash until it is registered by all of them.