I've tested this option....it works well, but in cases where the schedule calls a script, didn't worked because the client could not start the session...
On Wed, May 12, 2010 at 12:32 PM, Shawn Drew < shawn.d...@americas.bnpparibas.com> wrote: > Intended for firewall security, the "sessioninitiation" property on the > nodes may work for this. > You will have to disable the setting if anyone actually wanted to do a > manual backup or restore > from the client side, but that's a quick "upd n" > > Only the TSM Server would be allowed to start client sessions. > > Regards, > Shawn > ________________________________________________ > Shawn Drew > > > > > > Internet > leandroma...@gmail.com > > Sent by: ADSM-L@VM.MARIST.EDU > 05/11/2010 04:08 PM > Please respond to > ADSM-L@VM.MARIST.EDU > > > To > ADSM-L > cc > > Subject > [ADSM-L] Securing TSM Client > > > > > > > Hello everyone ! > > I don't know if somebody has this kind of problem, but I have the > following > situation in the company I work for: > > - We have a TSM team to install, configure and maintain the whole backup > process, server and client; > - We have sysadmins that take care of the operational system and the > applications; > - When there's a need for any action to do with backup, they should open a > ticket for the TSM team; > > The problem that we have is that the sysadmins are doing backups/archives > and restores/retrieves without our knowledge, with great impact on our > database (among other things...). We would like to block the access on the > client, but we were not successful. If we use "password generate" on > dsm.sys, the password is prompted only at first access. If we use > "password > prompt", the scheduler doesn't work (ANS2050E)... > Any sugestions from the experts ? Maybe it could be a improvement to IBM > implement on the future... > __________________________________ > Leandro Mazur > > > > 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. Please note that > certain > functions and services for BNP Paribas may be performed by BNP Paribas RCC, > Inc. > -- __________________________________ Leandro Mazur