Thank you for checking Del. I'll share the info with our Notes admins.
Del Hoobler <[EMAIL PROTECTED]>
04/05/2001 10:48 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc: (bcc: Lisa Cabanas/SC/MODOT)
Subject: Re: a question about archivelog
Lisa,
This means that there is currently no TDP command that
will figure this out for you. TDP figures this out
by measuring current remaining disk space vs. how many
transaction logs are ready to be archived.
There are some Domino server console commands
that can show a lot of stats that could help...
...then again...maybe not... but here it goes...
I received the following from the Lotus Domino
Server team... I don't pretend to be an
expert on these stats... but I am providing
them to you in case they are helpful.
On the Domino server console.... using the "SHOW STAT" command:
=======================================================================
-----> SHOW STAT DATABASE.RM.*
COMMAND SENT: SH STAT DATABASE.RM.*
Database.RM.Current.K.Restart.Redo.Hold = 54783
Database.RM.Current.K.UnCommited.Undo.Hold = 0
Database.RM.Current.MaxChkptScan.msec = 16
Database.RM.LastChkpt.Avg.K.Logged.PerTran = 2
Database.RM.LastChkpt.Interval.Sec = 99001
Database.RM.LastChkpt.K.Logged = 17067
Database.RM.LastChkpt.Time = 07/07/1999 09:31:10 PDT
Database.RM.LastChkpt.Total.DBs = 41
Database.RM.LastChkpt.Trans = 7261
Database.RM.Peak.Avg.K.Logged.PerTran = 1
Database.RM.Peak.Interval.Sec = 168
Database.RM.Peak.K.Logged = 17092
Database.RM.Peak.Time = 06/01/1999 08:14:47 PDT
Database.RM.Peak.Total.DBs = 14
Database.RM.Peak.Trans = 10237
Database.RM.Peak.Trans.PerMin = 3656
Database.RM.Restart.Duration.Sec = 34
Database.RM.Restart.K.Applied = 22735
Database.RM.Restart.Time = 06/01/1999 08:11:59 PDT
Database.RM.SinceChkpt.K.Logged = 6904
Database.RM.SinceChkpt.Trans = 2593
Database.RM.SinceStartup.Aborts = 2
Database.RM.SinceStartup.Critical.Log.Times = 0
Database.RM.SinceStartup.Log.Recs.Analyzed = 60771
Database.RM.SinceStartup.Log.Recs.Applied = 24734
Database.RM.SinceStartup.Log.Recs.Read = 93658
Database.RM.SinceStartup.Log.Recs.Written = 1105304
Database.RM.SinceStartup.M.Logged = 473
Database.RM.SinceStartup.Trans = 212551
Database.RM.Sys.Logged = Enabled
Database.RM.Sys.Log.Type = Circular
Database.RM.Sys.M.Chkpt.Interval = 16
Database.RM.Sys.M.Log.Size = 1489
Database.RM.Sys.M.Redo.Limit = 49
Database.RM.Sys.Phase = Normal
=======================================================================
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Lisa Cabanas <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/05/2001
10:13:13 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: a question about archivelog
A question about the command--
on pg 70 of the Redbook, 3.1.3.1 When to use archive log. It says to set
up an hourly schedule to run archivelog hi=80 lo=20-- and it will check
utilization of the transaction log space & perform a backup of the
transaction files if the threshold is triggered.
However, in the next paragraph, it says "Unfortunately, there is not way
to query the current utilization of the Domino database transaction log."
What gives? How can you do thresholds if you can't query how much space
the extents occupy?
(and please forgive me if I am being braindead, I come by it pretty
naturally)
lisa
Del Hoobler <[EMAIL PROTECTED]>
04/02/2001 08:26 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc: (bcc: Lisa Cabanas/SC/MODOT)
Subject: Re: TDP for domino: filling archive logs disk.
Hello,
In a normal situation, once you archive the
Domino R5 logs successfully, the log files will
be "resused" when necessary. There normally should
be no need to manually delete the already archived
log files.
Now, having said that, I will mention two things:
1. The Domino R5 server will actually leave the
archived log file around, with the old name
until it needs a new log extent. At that point,
it will look at its list of "already archived"
log files, pick one, rename the file to the
next logical sequence number, and start using it.
It does it this way to save "formatting" time.
Now, that is how it *normally* works...
2. There is a known Domino R5 bug that in some
situations, those log extents will not be reused.
Lotus has a fix for that problem.
The fix is in Domino R5 server, version 5.07.
You can get the fix from here:
http://notes.net/
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
R Marcos <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/31/2001 07:07:01 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: TDP for domino: filling archive logs disk.
I've a doubt:
If you've implemented archive log mode for your
transaction logs for domino 5, using tdp to archive
it, you know, you'll aware to archive the txn files
frequently. If not, the txn old files are not signed
like archived files and not removed.
I mean, if you've problems in your network, with tsm
system or something else... and txn files are not
archived for a few days, you have the risk of become
your disk full. Nevertheless you archive the files
again, they'll remain in your disk unless you remove
them manually.
I think this is not a very fine way to do that. I'm
looking for a transparent way to do that.
Has anybody been anytime in a chance like that?
Thanks everybody.
_______________________________________________________________
Do You Yahoo!?
Envma mensajes instantaneos y recibe alertas de correo con
Yahoo! Messenger - http://messenger.yahoo.es
