Instead of having to restore each *.LOG file every day, why not just code a POSTSCHEDULECMD that FTP's all the *.LOG files to a central server as <nodename>.dsm*.log
Bill Boyer "Life isn't about how fast you run, or how high you climb but how well you bounce" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Holzwarth Sent: Wednesday, June 27, 2007 1:50 PM To: ADSM-L@VM.MARIST.EDU Subject: AW: Lost in TSM licensing I do that every morning fully automated: Dsmsched.log of every tsm node is restored on a individual name at a central server for reporting of backup problems. It's not that difficult. But you are right - IBM should solve the problem by reporting the cpu count to the tsm server through the client. Regards, Stefan Holzwarth > -----Ursprüngliche Nachricht----- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag > von Gill, Geoffrey L. > Gesendet: Mittwoch, 27. Juni 2007 18:30 > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: Lost in TSM licensing > > So what you are saying is I still have to manually restore hundreds of > files from hundreds of systems to a location, and hopefully the file > name is different on each one or it will overwrite it ever time I > restore it, and then manually go through each file to get the info. > Not to mention the fact it could be some folks may not even have the > web interface up and I actually don't have access to restore the file. > > Sorry, for me, way too much work. > > > Geoff Gill > TSM Administrator > PeopleSoft Sr. Systems Administrator > SAIC M/S-G1b > (858)826-4062 > Email: [EMAIL PROTECTED] > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Warren > Sent: Wednesday, June 27, 2007 9:20 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Lost in TSM licensing > > Hmm, there is always a scheduled TSM command that send's it's output > to a file you have rights to look at later? > > On occaision for small adhoc tasks I have used the TSM scheduler to > initiate a command on a client, when I've needed to do the same thing > across a lot of nodes. > > as TSM administrator, you could send the output to a file, let tsm > back it up, and then restore it elsewhere to get at it, if you really > really had to! > > Matt. > http://tsmwiki.com/tsmwiki > > > > > Internet > [EMAIL PROTECTED] > > To > ADSM-L > Sent by: ADSM-L@VM.MARIST.EDU cc > > 27/06/2007 16:07 > Subject > Re: [ADSM-L] Lost in > TSM licensing > > Please respond to > ADSM-L@VM.MARIST.EDU > > > > > > > > > > M$ offers a tool named MSINFO32 that returns a lot of information > about a >server. > >You can gather information from a remote server - provided you have > enough >rights on the remote machine. > > Ahhh, the ol don't have rights issue. Which is why I keep saying the > best way to get the info is to build it into the client so it can get > and report it on the tsm server. Otherwise with hundreds, if not > thousands of machines, I doubt any one person is going to have a > simple way to get the info. It turns in to a multi day manual task > which is absolutely stupid. > > Geoff Gill > TSM Administrator > PeopleSoft Sr. Systems Administrator > SAIC M/S-G1b > (858)826-4062 > Email: [EMAIL PROTECTED] > > > > This message and any attachments (the "message") is intended solely > for the addressees and is confidential. > If you receive this message in error, please delete it and immediately > notify the sender. Any use not in accord with its purpose, any > dissemination or disclosure, either whole or partial, is prohibited > except formal approval. The internet can not guarantee the integrity > of this message. > BNP PARIBAS (and its subsidiaries) shall (will) not therefore be > liable for the message if modified. > > --------------------------------------------- > > Ce message et toutes les pieces jointes (ci-apres le > "message") sont etablis a l'intention exclusive de ses destinataires > et sont confidentiels. Si vous recevez ce message par erreur, merci de > le detruire et d'en avertir immediatement l'expediteur. Toute > utilisation de ce message non conforme a sa destination, toute > diffusion ou toute publication, totale ou partielle, est interdite, > sauf autorisation expresse. L'internet ne permettant pas d'assurer > l'integrite de ce message, BNP PARIBAS (et ses > filiales) decline(nt) toute responsabilite au titre de ce message, > dans l'hypothese ou il aurait ete modifie. >