Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
melcraig
Starting Member
39 Posts |
 Posted - 2006-08-21 : 17:45:22
|
| Hello,I have a sql server, that for some unknown reason, they use Tivoli to do the sql backups.They do a full backup nightly and a couple of tran backups daily.The problem is all the the .ldf files are huge and we are running out of disk space. I'm saying the db is maybe 2gig and the .ldf is like 9gig. Has anyone ran into this with Tivoli?Can I just do a full backup and then run a DBCC SHRINKFILE logfilename.ldf?Thanks, Mel |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-08-21 : 17:55:04
|
quote:
Originally posted by melcraig
Hello,I have a sql server, that for some unknown reason, they use Tivoli to do the sql backups.They do a full backup nightly and a couple of tran backups daily.The problem is all the the .ldf files are huge and we are running out of disk space. I'm saying the db is maybe 2gig and the .ldf is like 9gig. Has anyone ran into this with Tivoli?Can I just do a full backup and then run a DBCC SHRINKFILE logfilename.ldf?
this isn't a tivoli problem. This issue can most likely be resolved by performing a one time tlog datafile shrink and then scheduling more frequent tlog backups. A typical schedule would be to backup the tlogs hourly. We have some systems that we backup every 15 mins. Frequent tlog backups will help minimize out of control tlog datafile growth. Adding more space to your filesystem might also be a good thing to look into.-ec |
 |
|
|
melcraig
Starting Member
39 Posts |
Posted - 2006-08-21 : 18:05:54
|
| If I do a full backup of Test DB within SQL itself and do a DBCC SHRINKFILE Test.ldf then do another full backup in SQL this will shrink the test.ldf file?Then in Tivoli schedule more transaction log backups?Thanks, Mel |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-08-21 : 18:14:24
|
quote:
Originally posted by melcraig
If I do a full backup of Test DB within SQL itself and do a DBCC SHRINKFILE Test.ldf then do another full backup in SQL this will shrink the test.ldf file?Then in Tivoli schedule more transaction log backups?Thanks, Mel
if you handle your backups using tivoli, it is probably best that all backups operations are done using this tool. THis will simplify your recovery process in the future. This is because tivoli will be able to retrieve all SQL backups involved in a particular database recovery. If you put one-off backups in a filesystem somewhere you may lose track of them. If these backups are all handled by tivoli, you won't ever lose track of them.Shrink the tlog is sometimes tricky. You may have to shrink the logfile several times for anything substantial to happen. Sometimes you need to wait for additional transactions to occur in the database before the log can be successfully shrunk. There are several articles online that you can find by googling that discuss workarounds and methods for shinking a stubborn tlog.After doing the above, you can schedule more regular tlog backups. Keep in mind that this might have adverse affects on your tivoli environment, since it might be having to mount tapes every hour or so just to service your backups. The last place I worked got around this issue by implementing disk storage pools. The tivoli backups would go to the intermediate disk storage pool and then eventually to tape. This way we didn't have to wait for tape mounting and positioning - which was the most time consuming part of the job in many cases.-ec |
|
|
|
|
|
|
|
|
Tivoli SQL backups