: Re: schedlogretention.
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 02/01/2006
01:44:00 PM:
TSM client 5.3.1.1
OS linux RH 3.0
TSM server 5.3.1.2
On all three of my archive only Linux servers the schedlogretention
and errorlogretention parameters in the dsm.sys are not being used
I ran a scheduled Backup on a single file and the pruning was completed.
I checked the documentation and it states The schedlogretention option
specifies the number of days to keep entries in the schedule log, and
whether to save the pruned entries. The schedule log is pruned after a
scheduled
may want to check you dsmsched.log.
I just found some of mine were over 400mb.
-Original Message-
From: Ochs, Duane
Sent: Thursday, February 02, 2006 11:05 AM
To: 'ADSM: Dist Stor Manager'
Subject: RE: schedlogretention.
I ran a scheduled Backup on a single file and the pruning
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 02/02/2006
06:21:14 AM:
The D after the 7 is no longer acceptable in 5.3. I wouldn't think
your backups/archives are running at all.
This is incorrect. I've got a couple of hundred 5.3.2 clients using D in
the log retention flags.
--
Mark
TSM client 5.3.1.1
OS linux RH 3.0
TSM server 5.3.1.2
On all three of my archive only Linux servers the schedlogretention and
errorlogretention parameters in the dsm.sys are not being used. The
contents in the logs date back to 10-12-05. The dsm.sys has not been
changed since 9-12-2005
: schedlogretention.
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 02/01/2006
01:44:00 PM:
TSM client 5.3.1.1
OS linux RH 3.0
TSM server 5.3.1.2
On all three of my archive only Linux servers the schedlogretention
and
errorlogretention parameters in the dsm.sys are not being used. The
contents
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 02/01/2006
01:44:00 PM:
TSM client 5.3.1.1
OS linux RH 3.0
TSM server 5.3.1.2
On all three of my archive only Linux servers the schedlogretention and
errorlogretention parameters in the dsm.sys are not being used. The
contents
Hello,
Is there any way to tell the client scheduler to roll over the
dsmsched.log, WITHOUT having the user manually set the schedlogretention
value in the dsm.sys or dsm.opt Sorta like a client option set ?
Thank!
Keith
DSMCDEFAULTCOMMAND
Sequence number 0
Option Value schedlogretention 8
Override Yes
DSMCDEFAULTCOMMAND
Sequence number 0
Option Value schedlogretention 8
Override Yes
Keith - SCHEDLOGRETENTION is not defined as a legal CLIENTOpt, so I don't
think you can do it from the server.
What you have done above should be undone: you have changed the default
action of the 'dsmc
10 matches
Mail list logo