Re: Securing TSM Client

2010-05-17 Thread Allen S. Rout
On Tue, 11 May 2010 17:08:27 -0300, Leandro Mazur leandroma...@gmail.com said: 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...). Charge them for it, and charge

Re: Securing TSM Client

2010-05-12 Thread Richard Sims
Leandro - The problem you're dealing with is a personnel management one, which can't be solved by technology alone. The management there is the only avenue of solution. Technology can help, though. You can harvest records from the dsmaccnt.log to compile a report to management demonstrating

Re: Securing TSM Client

2010-05-12 Thread Leandro Mazur
Humm...that's interesting...I'll take a look ! Thanks Richard ! On Wed, May 12, 2010 at 8:18 AM, Richard Sims r...@bu.edu wrote: Leandro - The problem you're dealing with is a personnel management one, which can't be solved by technology alone. The management there is the only avenue of

Re: Securing TSM Client

2010-05-12 Thread Shawn Drew
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

Re: Securing TSM Client

2010-05-12 Thread Leandro Mazur
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

Securing TSM Client

2010-05-11 Thread Leandro Mazur
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

Re: Securing TSM Client

2010-05-11 Thread Lindsay Morris
Maybe you could lock all the nodes during the day (LOCK NODE...), and unlock them at night for your scheduled backups ... ? Lindsay Morris CEO, TSMworks Tel. 1-859-539-9900 lind...@tsmworks.com On Tue, May 11, 2010 at 4:08 PM, Leandro Mazur leandroma...@gmail.comwrote:

Re: Securing TSM Client

2010-05-11 Thread Fred Johanson
Better to lock the admin. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lindsay Morris Sent: Tuesday, May 11, 2010 3:59 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Securing TSM Client Maybe you could lock all the nodes during the day

Re: Securing TSM Client

2010-05-11 Thread Huebner,Andy,FORT WORTH,IT
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

Re: Securing TSM Client

2010-05-11 Thread Remco Post
On 11 mei 2010, at 22:08, Leandro Mazur wrote: 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

Re: Securing TSM Client

2010-05-11 Thread Leandro Mazur
Thanks for the answers ! About the sugestions: - I can't lock the nodes during the day, because several backups run every 2, 4 and 6 hours; - Lock the admin is a good sugetsion, although not possible... - The admins have the administrator/root password, so they can do anything... - Is not the