multiple dsmcad procs running
Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. By accident I started three instances of adsmcad. I killed two of them and happily went home at the end of the day. The next day I found out that the backup didn't run because the TSM server was unable to contact the client. In the dsmsched.log I found that the last scheduled action was one of the killed dsmcad processes. Am I right in assuming that correct authentication only takes place between the server and the dsmcad process that initiated the first contact with the server? So, in this case the TSM server didn't recognize the dsmcad process? Thanks in advance for your reply. Kind regards, Michiel van Vlijmen Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan.
Re: dsmcad/dsmsched.log showing wrong times
Richard, Thanks for your reply, dsmcad is indeed started by tsm::once:/opt/tivoli/tsm/client/ba/bin/dsmcad /dev/null 21 # TSM Client Acceptor Daemon I will read the technote ans see if it helps. regards, Michiel van Vlijmen -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Richard Sims Verzonden: vrijdag 24 maart 2006 14:18 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] dsmcad/dsmsched.log showing wrong times On Mar 24, 2006, at 3:38 AM, Vlijmen, M. van wrote: Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. The problem I have is that the times shown in the dsmsched.log do not match the (actual ?) time. I stopped and started dsmcad manually which solved the problem. That's nice but I like to know what the reason was since I don't want it to happen again. Anyone any idea? Thanks in advance. Michiel Michiel - You omit the most important information: how your dsmcad is currently being started. Problems like these are typically due to not having established the proper environment settings prior to launching the application, such that it runs under such conditions. That is achieved via a comprehensive start-up script, rather than a terse inittab entry. See IBM site Technote 1159406 for guidance. If you *are* using a start-up script of some kind, it isn't establishing environment settings as your personal login session is, and needs to do the right things, such as proper TZ environment variable setting. Richard Sims Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan.
Re: dsmcad/dsmsched.log showing wrong times
Thanks for your reply Jim. Well, I'm pretty much a newbie on TSM and didn't know of that option. I will look in to it. regards, Michiel van Vlijmen -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens JN Verzonden: vrijdag 24 maart 2006 22:45 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] dsmcad/dsmsched.log showing wrong times Urgentie: Hoog Hi Michiel, I'm pretty sure that you have already thought of this, but have you tried entering the Accept Date command to synchronize the TSM server date/time with the OS Date/Time? Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Vlijmen, M. van Sent: Friday, March 24, 2006 12:39 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] dsmcad/dsmsched.log showing wrong times Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. The problem I have is that the times shown in the dsmsched.log do not match the (actual ?) time. I stopped and started dsmcad manually which solved the problem. That's nice but I like to know what the reason was since I don't want it to happen again. Anyone any idea? Thanks in advance. Michiel Time on RedHat TSM server: [EMAIL PROTECTED] etc]$ date Thu Mar 23 15:46:31 CET 2006 Time on HP/UX 11i TSM client: hp date Thu Mar 23 15:48:33 MET 2006 Note that MET = CET 03/23/06 03:34:59 Querying server for next scheduled event. 03/23/06 03:34:59 Node Name: HPL4 03/23/06 03:34:59 Session established with server SERVER1: Linux/ppc64 03/23/06 03:34:59 Server Version 5, Release 3, Level 2.0 03/23/06 03:34:59 Server date/time: 03/23/06 09:32:44 Last access: 03/23/06 09:30:07 03/23/06 03:34:59 --- SCHEDULEREC QUERY BEGIN 03/23/06 03:34:59 --- SCHEDULEREC QUERY END 03/23/06 03:34:59 Next operation scheduled: 03/23/06 03:34:59 03/23/06 03:34:59 Schedule Name: CS_HPUX_DAILY_0100 03/23/06 03:34:59 Action:Incremental 03/23/06 03:34:59 Objects: / 03/23/06 03:34:59 Options: 03/23/06 03:34:59 Server Window Start: 01:00:00 on 03/24/06 03/23/06 03:34:59 03/23/06 03:34:59 Scheduler has been stopped. (here I did a stop and start) 03/23/06 13:39:29 Scheduler has been started by Dsmcad. 03/23/06 13:39:29 Querying server for next scheduled event. 03/23/06 13:39:29 Node Name: HPL4 03/23/06 13:39:29 Session established with server SERVER1: Linux/ppc64 03/23/06 13:39:29 Server Version 5, Release 3, Level 2.0 03/23/06 13:39:29 Server date/time: 03/23/06 13:37:14 Last access: 03/23/06 13:36:13 Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan. Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan.
dsmcad/dsmsched.log showing wrong times
Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. The problem I have is that the times shown in the dsmsched.log do not match the (actual ?) time. I stopped and started dsmcad manually which solved the problem. That's nice but I like to know what the reason was since I don't want it to happen again. Anyone any idea? Thanks in advance. Michiel Time on RedHat TSM server: [EMAIL PROTECTED] etc]$ date Thu Mar 23 15:46:31 CET 2006 Time on HP/UX 11i TSM client: hp date Thu Mar 23 15:48:33 MET 2006 Note that MET = CET 03/23/06 03:34:59 Querying server for next scheduled event. 03/23/06 03:34:59 Node Name: HPL4 03/23/06 03:34:59 Session established with server SERVER1: Linux/ppc64 03/23/06 03:34:59 Server Version 5, Release 3, Level 2.0 03/23/06 03:34:59 Server date/time: 03/23/06 09:32:44 Last access: 03/23/06 09:30:07 03/23/06 03:34:59 --- SCHEDULEREC QUERY BEGIN 03/23/06 03:34:59 --- SCHEDULEREC QUERY END 03/23/06 03:34:59 Next operation scheduled: 03/23/06 03:34:59 03/23/06 03:34:59 Schedule Name: CS_HPUX_DAILY_0100 03/23/06 03:34:59 Action:Incremental 03/23/06 03:34:59 Objects: / 03/23/06 03:34:59 Options: 03/23/06 03:34:59 Server Window Start: 01:00:00 on 03/24/06 03/23/06 03:34:59 03/23/06 03:34:59 Scheduler has been stopped. (here I did a stop and start) 03/23/06 13:39:29 Scheduler has been started by Dsmcad. 03/23/06 13:39:29 Querying server for next scheduled event. 03/23/06 13:39:29 Node Name: HPL4 03/23/06 13:39:29 Session established with server SERVER1: Linux/ppc64 03/23/06 13:39:29 Server Version 5, Release 3, Level 2.0 03/23/06 13:39:29 Server date/time: 03/23/06 13:37:14 Last access: 03/23/06 13:36:13 Disclaimer : Aan de inhoud van dit bericht kunnen geen rechten worden ontleend. De informatie is uitsluitend bestemd voor de geadresseerde. Gebruik door anderen is verboden. Openbaarmaking, vermenigvuldiging en verstrekking van deze informatie aan derden is niet toegestaan.
