I recently started having issues with my log going over 80% (5.5.3). Doing a "show logpinned" usually points to a long (18-hours) running backup session for one particular node.
This is starting to happen more and more frequently. Once I kill the session, the log utilization drops to almost nothing since there has been a DB backup run earlier in the day. Any suggestions on how to handle this besides killing the session? The node is a standard 2K3 box using the 6.1.2.0 client. It is just a very slow/busy box. The long backups (times vary from 11-19 hours) often dump 120GB of data. Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
