November 4, 2010 at 7:00 pm
Youre administering a system where each minute of transaction log contains millions dollars of transactions.
If you lose any of those transactions youre company is liable.
How often do you back up your log?
November 4, 2010 at 7:40 pm
sql.monkey (11/4/2010)
Youre administering a system where each minute of transaction log contains millions dollars of transactions.If you lose any of those transactions youre company is liable.
How often do you back up your log?
First, if your database is supporting that level of financial transactions, you probably are running in some kind of high availablity scenerio: database mirroring, clustering, both mirroring and clustering, etc. If not, you really should be!
I would probably also have log shipping running about every 5 minutes, and be moving those to several offsite systems.
November 4, 2010 at 7:58 pm
MSDTC Transactions are used which rules out mirroring.
Backing up the tail of a log is not guaranteed if you have log corruption?
Replication is in place to a number of subscribers but isnt really suitable for restores IMO.
SAN SRDF Mirroring is in place underneath the disks to different disk arrays.
Log shipping isnt in place, and the idea of shipping the logs does appeal.
Clustering is in for place for High Availablity.
Whats the limitation on more frequent log backups, other than disk utilisation on the log backup target disk? one minute? two minutes? why five?
November 4, 2010 at 8:07 pm
If you schedule a t-log backup to run every minute, is that sufficient time to accomplish the backup and not impact processing? Millions of dollars a minute, either there are a lot of transactions or only a few very high dollar transactions.
You and your business are the ones that need to decide how you are going to protect your data assets. The business has to decide how much downtime is permitted and how much data loss is acceptable. There are no 100% solutions.
November 5, 2010 at 2:19 am
sql.monkey (11/4/2010)
Youre administering a system where each minute of transaction log contains millions dollars of transactions.If you lose any of those transactions youre company is liable.
How often do you back up your log?
Been there, done that.
Log backups every 15 min shipped to a secondary DR
Synchronous SAN replication to the primary DR
Clustering
Transactional replication of key tables to a reporting DB
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply