lines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Zoltan Forray/AC/VCU
Sent: donderdag 12 augustus 2010 16:50
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Recovery log filling up
AHA..Finally someone else with a similar experience!
I have
onfidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
From:
"Loon, EJ van - SPLXO"
To:
ADSM-L@VM.MARIST.EDU
Date:
08/12/2010 04:14 AM
Subject:
[ADSM-L] Recovery log filling up
Sent by:
"ADSM: Dist Stor Manager"
Hi TSM-ers!
T
start backing up.
The strange thing is that on all three servers I see the recovery log
filling up to more than 80 percent at least one time during the night.
The backup trigger is set to 75%, but I see ANR2997W multiple times.
Sometimes I even notice the following message:
ANR4556W Attention: the
Unfortunately this keeps happening with different clients and the sessions
can't be cancelled without taking down the entire server. Is there any way
to force a session to end? They won't cancel and they never time out so the
recovery log just keeps filling up as one of the sessions has the log
pin
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of John C Dury
>As several people suggested, what is happening is that I have
>at least one
>client session that is seemingly hung and causing the recovery
>log to be
>pinned. I've tried cancelling the session but it doesn't work
Subject
Recovery log filling up quickly,
too quickly. Ideas?
I have v5311 AIX server installed. The DB is not in roll forward mode.
There isn't anything that has changed recently that would be causing this.
>>You can empty your log with a db backup (incremental or full).
Unless, as others have noted, you have pinned data.
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of John C Dury
>I have v5311 AIX server installed. The DB is not in roll forward mode.
>There isn't anything that has changed recently that would be
>causing this.
>It seems it might be a bug in v5311 that doesn't let the recovery
John -
You need to check recent ANE summary stats or dsmaccnt records for
the clients and compare against past records, to see if there is
actually an increase in client activity. Examining numbers for the
server store inventory is rather pointless, as churn is what affects
the Recovery Log. That i
You could try running the "show logpinned" command, you should be able to
identify what is pinning the log.
From: ADSM: Dist Stor Manager on behalf of John C Dury
Sent: Thu 5/5/2005 10:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Recovery log
I have v5311 AIX server installed. The DB is not in roll forward mode.
There isn't anything that has changed recently that would be causing this.
It seems it might be a bug in v5311 that doesn't let the recovery log
empty as it happens sporadically. Expiration which runs daily is suddenly
taking a
Subject: Re: recovery log filling up rapidly: Please help:
EMERGENCY !
Hi Joni
Its strange to see recovery log filling up to 5GB level in NORMAL mode (
you mentioned that in ur previous mail).
In NORMALMODE recovery log doesn't keep transactions, it deletes
transaction as soon as it
I've seen the log fill in Normal if you have a client running that's not
sending commits often enough. Clients with NICs set to Autonegotiate, then
ending up at 100/Half Duplex (or 10/Half duplex, a couple of times) will
"pin" the log due to not getting to a commit point. Add in expiration on
an
Hi Joni
Its strange to see recovery log filling up to 5GB level in NORMAL mode (
you mentioned that in ur previous mail).
In NORMALMODE recovery log doesn't keep transactions, it deletes
transaction as soon as it committed to database.Thats why only
Point-in-Retsore ( till the last consi
Run an incremental to dump the log.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 7:02 AM
To: [EMAIL PROTECTED]
Subject: recovery log filling up rapidly: Please help
>...I usually run a full DB backup every day at 4:30. What can I do? ...
First, determine what's eating your Recovery Log by doing periodic queries
through the day of the Recovery Log, Processes, and Sessions. Judicious
scheduling of the whoppers will help.
Do Incremental backups of your TSM DB
:recovery log filling up rapidly: Please help:
EMERGENCY!
My recovery log is filling up at a rapid rate. I am running TSM at 4.1.3
on the mainframe. It is 4.6 GB and my DB is 48 GB with 46 GB in use. I am
not running expiration of the inventory yet due to a previous deletion of a
:
Subject: recovery log filling up rapidly: Please help:
EMERGENCY!
My recovery log is filling up at a rapid rate. I am running TSM at 4.1.3
on the mainframe. It is 4.6 GB and my DB is 48 GB with 46 GB in use. I am
not running expiration of the inventory yet due to a
My recovery log is filling up at a rapid rate. I am running TSM at 4.1.3
on the mainframe. It is 4.6 GB and my DB is 48 GB with 46 GB in use. I am
not running expiration of the inventory yet due to a previous deletion of a
nodes data, could that be the cause? I noticed that the log is reaching
19 matches
Mail list logo
