April 29, 2010 at 6:03 am
Our production database on SQL 2005 has grown to a size of around 800 Terabytes of data and transaction log is around 100 TB. We have set the frequency interval of the log backup job to 10 seconds, but one execution of the log backup is taking 50 seconds to complete. We are not sure when the next backup job is happening after the start of the previous backup job. It's all messed up and systems have become too slow to the extent of hanging frequently. Can someone suggest a better backup and restore solution.
May 14, 2010 at 8:40 am
how many database files is your DB divided in?
Is your DB a OLTP or reporting DB?
Backup and restore strategies will depend on what should be your availability SLA and how fast and how much of data loss is acceptable to business if your db crashes.
Please provide more information and I can suggest some options.
Thanks
May 14, 2010 at 8:48 am
I think this was cross-posted.
Please see the below with a large discussion:
http://www.sqlservercentral.com/Forums/Topic912735-391-1.aspx
I think that the DB and log size's were not as described, especially as transaction logs have a 2TB limit per file
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply