Re: schedlogretention.
The D after the 7 is no longer acceptable in 5.3. I wouldn't think your backups/archives are running at all. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 01, 2006 3:49 PM To: ADSM-L@VM.MARIST.EDU Subject: 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. The contents in the logs date back to 10-12-05. The dsm.sys has not been changed since 9-12-2005. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Curiousity: have you tried adding it to the relevant client option set on the server? I for one would be interested as to whether that did the job better. Another curiousity: does log retention work on archives only? I always see the trimming going on at the end of a scheduled backup. You might try a single scheduled backup on one box to see if that trims the logs. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Re: schedlogretention.
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 event completes. Which would indicate to me that it is suppose to run after any scheduled event. Is something broke or is the documentation wrong ? If anybody can clarify I would appreciate. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 01, 2006 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: 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. The contents in the logs date back to 10-12-05. The dsm.sys has not been changed since 9-12-2005. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Curiousity: have you tried adding it to the relevant client option set on the server? I for one would be interested as to whether that did the job better. Another curiousity: does log retention work on archives only? I always see the trimming going on at the end of a scheduled backup. You might try a single scheduled backup on one box to see if that trims the logs. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Re: schedlogretention.
Just got E-mail back from IBM. Found Apar IC45287 a change was made to TSM 5.3 code to not prune log until the scheduler processes is recycled. They changed back to having pruning run after every schedule is run. This was add in TSM 5.3.2 client code level. If you are running 5.3 - 5.3.1.? You 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 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 event completes. Which would indicate to me that it is suppose to run after any scheduled event. Is something broke or is the documentation wrong ? If anybody can clarify I would appreciate. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 01, 2006 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: 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. The contents in the logs date back to 10-12-05. The dsm.sys has not been changed since 9-12-2005. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Curiousity: have you tried adding it to the relevant client option set on the server? I for one would be interested as to whether that did the job better. Another curiousity: does log retention work on archives only? I always see the trimming going on at the end of a scheduled backup. You might try a single scheduled backup on one box to see if that trims the logs. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Re: schedlogretention.
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 Stapleton ([EMAIL PROTECTED]) US Bank MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
schedlogretention.
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. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Duane Ochs Information Systems - Enterprise Computing Quad/Graphics Inc. Sussex, Wisconsin 414-566-2375 phone 414-566-4010 pin# 2375 beeper [EMAIL PROTECTED] www.QG.com outbind://8/www.QG.com
Re: schedlogretention.
Have your restarted the scheduler? The scheduler only reads the dsm.sys file on startup. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 01, 2006 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: 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. The contents in the logs date back to 10-12-05. The dsm.sys has not been changed since 9-12-2005. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Curiousity: have you tried adding it to the relevant client option set on the server? I for one would be interested as to whether that did the job better. Another curiousity: does log retention work on archives only? I always see the trimming going on at the end of a scheduled backup. You might try a single scheduled backup on one box to see if that trims the logs. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
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. The contents in the logs date back to 10-12-05. The dsm.sys has not been changed since 9-12-2005. An archive process is scheduled to run every 12 hours. errorlogretention 7 d schedlogretention 7 d errorlogname /another_directory/dsmerror.log schedlogname /another_directory/dsmsched.log Has anybody seen this before ? Curiousity: have you tried adding it to the relevant client option set on the server? I for one would be interested as to whether that did the job better. Another curiousity: does log retention work on archives only? I always see the trimming going on at the end of a scheduled backup. You might try a single scheduled backup on one box to see if that trims the logs. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Any way to set schedlogretention on the server??
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
Client optionset schedlogretention doesn't work !?
Hello, I have the below client optionset on my 4.1 server, but my clients never get their logs pruned. The logs just grow and grow. I have a mix of 3.7 , 4.1.2.12 clients and I think they all experience the same thing. Anyone have any ideas? Keith Optionset WIN32_INCLEXCL Option DSMCDEFAULTCOMMAND Sequence number 0 Option Value schedlogretention 8 Override Yes
Re: Client optionset schedlogretention doesn't work !?
I have the below client optionset on my 4.1 server, but my clients never get their logs pruned. The logs just grow and grow. I have a mix of 3.7 , 4.1.2.12 clients and I think they all experience the same thing. Anyone have any ideas? Optionset WIN32_INCLEXCL Option 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' command from Loop to a nonsensical value. (The undocumented DSMCDEFAULTCOMMAND option, which would go in dsm.opt if used, defines what happens when you invoke 'dsmc' with no operands. Conceivably, you might change it to something like HELP rather than LOOP; but probably nothing else.) Richard Sims, BU
