Re: TDP for Domino

Del,

Thank you for the response. I had misunderstood how the /Threshold parameter works. I now realize that it checks for the highvalue which is a percentage of the transaction log capacity. I do have a dedicated volume set aside for transaction logs and there is no other data in that drive space.

Thanks,

Radha

Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

06/01/01 02:45 AM
Please respond to "ADSM: Dist Stor Manager"

To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: TDP for Domino

Radha,

It must be that your log disk device is not 80% full.
If it were, then logs would be archived until it is at 20%.
You are using the /THRESHOLD=80,20 option.
From the User's Guide:

=================================================================
/THRESHold=highvalue, lowvalue

Use this option to specify when the archivelog command should
start and stop archiving eligible transaction log files. The highvalue,
specified as a percentage of the transaction log capacity,
identifies the point at which log archiving should begin.
If the current occupancy of the transaction log equals or
exceeds the value for this parameter, eligible log files are
archived until the occupancy falls to or below the lowvalue
which is also specified as a percentage of the log capacity.
highvalue is an integer in the range from 1 to 99.

lowvalue is an integer in the range from 0 to 98 but it must be
less than the high value. The default is 0 which means that all
log files eligible for archive will be archived.

If the /threshold option is not specified, then all eligible
transaction log files are archived.

For example, specifying

/threshold=90,50

will cause transaction log files to be archived only after
the log is at or more than 90% full and the archive process
will stop once sufficient space has been reclaimed to make
the log less than or equal to 50% full.
=================================================================

By the way, your log device should not have any other
data residing on it besides logs. This could cause
the threshold calculations to be askew as well as
cause performance problems due to disk contention.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

"It's a beautiful day. Don't let it get away." -- Bono

Radha
Parameswaran To: ADSM-L AT VM.MARIST DOT EDU
<csctivol@BART cc:
.GOV> Subject: TDP for Domino
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MAR
IST.EDU>

05/31/2001
04:51 PM
Please respond
to "ADSM: Dist
Stor Manager"

I have recently setup TDP for Domino on our mail system which has over
1700+ mail files. I am running archivelog periodically to archive the log
files. When I look at the domarc.log file it shows that there are 12 log
files to be archived, but 0 archived. I am really concerned about this. I
have the threshold set for 80,20. Am I missing something?

This is the command I use to run the archivelog:

start /B domdsmc archivelog /threshold=80,20 /adsmoptfile=dsm.opt
/logfile=domasch.log >> domarc.log

Here is the info from domarc.log file:

Current date is:
Thu 05/31/2001
Current time is:
12:01p

Tivoli Storage Manager
Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 1.0
(C) Copyright IBM Corporation 1999, 2000. All rights reserved.

License file exists and contains valid license data.

ACD5221I The d:\PROGRA~1\IBM\ADSM\domino\domasch.log log file has been
pruned successfully.

Starting Domino transaction log archive...
Initializing Domino connection...
Logging on to the Tivoli Storage Manager server, please wait...

Total Domino transaction log files ready for archive: 12
Total Domino transaction log files archived: 0

Throughput rate: 0.00 Kb/Sec
Total bytes transferred: 0
Elapsed processing time: 0.00 Secs