July 24, 2006 at 8:20 pm
Hi,
I have a 2-node clustered server running SQL Server 2000 SP3 (8.00.760) and Windows 2003 Enterprise Etd SP1. 8GB Physical Memory (PAE, AWE enabled. SQL use 6GB and OS 2GB). SAN box wtih plenty of disk space.
The biggest database in that instance is now 60GB. The rest are small 100MB-200MB in size. It used to take 20 minutes (size then is about 54GB) to do a full backup for that biggest database alone. Now it take average 60-80 minutes. The backup is done during the off-peak hours and no change of scheduled time has be made.
I heard the native SQL backup is relatively slow compare to other 3th party backup tool. But for that size of backup, is native SQL backup not good enough?
I suspect that might be disk problem. what should I look in Perf Monitor and Profiler?
July 25, 2006 at 3:41 am
if it has mystically doubled in time but the .bak file is the same size then the obvious one to check is in the maintenance plan - check if the backup is being verified - if it is then was it before ???
failing that then it could be disk speed - but since you're on a san then that would be up to whoever looks after your san.
SQL native backups are pretty lame for large databases compared to SQL litespeed and Redgates SQLBackup offerings which use compression technology to reduce the amount that is written to disk (at the cost of consuming CPU)
MVDBA
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply