Are these in minutes ?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Gerald Michalak
Sent: Tuesday, November 08, 2005 11:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log pinned, filled, almost crashed
Here's the technote.
Problem
, filled, almost crashed
Here's the technote.
Problem Long-running sessions with poor throughput or hung sessions can
cause the recovery log to become pinned. This can ultimately result in the
TSM Server abending due to an over-committed recovery log. Cause
Solution The THROUGHPUTDATATHRESHOL
On Nov 8, 2005, at 1:56 PM, Joni Moyer wrote:
This is a good idea, but what would reasonable settings be for the
throughputdatathreshold & throughputtimethreshold? They both have a
maximum of , but I can't imagine that you would want to
wait that
long... Any suggestions/experiences wit
Here's the technote.
Problem Long-running sessions with poor throughput or hung sessions can
cause the recovery log to become pinned. This can ultimately result in the
TSM Server abending due to an over-committed recovery log. Cause
Solution The THROUGHPUTDATATHRESHOLD and THROUGHPUTTIMETHRESHOL
To
Dist Stor ADSM-L@VM.MARIST.EDU
Manager" cc
<[EMAIL PROTECTED]
.EDU> Subject
Have you looked into approaches suggested by IBM Technote 1084167?
Richard Sims
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Roger Deschner
>Short of a poison pill daemon that does a HALT at 95% log full, what do
>others do to positively protect the Log from filling up?
Off the top of my head, an incremental TSM backup to disk? Not sure if
that'll han
Last night, a hung client backup session pinned the log, it filled, and
I got called in the middle of the night just in time to avert a messy
log-full crash. This has happened before.
This is the greatest looming fear I have - a Log fillup. The Log is in
Normal Mode, and is 12GB - can't get much l
