Full Backups and T Log backups
-
Real world situation:
System set-up with FULL backup daily at 9PM and T log backups every hour at 5 past.
Production server gets corrupted employee information which propogates changes/updates etc.. throughout entire system.
Easy fix to restore from last good backup and apply t log backups to get back to last "good" state and then go from there by putting good updated back after that and moving forward.. WRONG!
Our system was set that IF the FULL backup was good then OVERWRITE the T log backup and start over....
Luckily, our system is more or less batch-mode and we can re-load the 2 days of data (instead of 1) and get back on track.
I guess the moral of this story is to always backup the T logs and NOT overwrite for a period of time just in case. This change was put in place today and it will not get us again...
Hope this helps someone else out there if they are set-up the same
Good Hunting!AJ Ahrens
webmaster@kritter.net -
Use this Managed Online backup service, and you will have very peaceful nights and days...www.evault.com, i wish it was introduced a long time back...It just keeps on working without any problems..What relief!!! There is something out there that actually works like a miracle....
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply