You can try to evaluate TSMExplorer from www.s-iberia.com. It has special agent and updater, which can be installed ones together with TSM Client to provide next functionality: 1) remote update of agent to newer version without having access to servers; 2) remote viewing TSM Client logs, TDP for XXX logs, backup logs, etc; 3) remote editing configuration files like dsm.sys, dsm.opt, etc; 4) remote interface to run any commands "dsmutil xxxxxx"; 5) remote interface to run any commands "dsmc xxxxx"; 6) remote interface to run any defined schedules; 7) remote interface to collect detailed host information (CPU, memory, disks, TCP/IP, etc); 8) remote interface to collect detailed information for TSM nodes (domain, node name, node type, TCP/IP address, TSM Client version, operating system, processor type, number of cores, etc) 9) one point of control to use RDC/SSH connection to all servers, if available. I am using TSMExplorer for a few years and I am able to manage all TSM nodes without any access to them via RDC/SSH.
Grigori G. Solonovitch Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw Please consider the environment before printing this E-mail -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Prather, Wanda Sent: Tuesday, November 06, 2012 10:22 PM To: [email protected] Subject: [ADSM-L] Q about TSM notification in a widely-distributed environment One of my customers is becoming effectively a "backup service bureau" for many remote departments (and the number of depts. they service is growing). The central TSM admins have access to the TSM clients in the glass house, but no access to the TSM clients for the remote departments. Currently they use TOR to send email to the remote machine owners when TSM clients fail or miss. Remote admins often ignore the emails; general result is TSM clients miss for long periods, and the central admins don't know whether there is a legitimate problem, the machine has been decommissioned, or the machine owner has been decommissioned. They are looking for a reporting tool that will provide a better way to handle this than sending email out into the vacuum of internet space and hoping for results. (And yes, my customer already has service agreements where the remote owners have agreed that dealing with the failures and misses is their responsibility. But that's not working now, and when the rubber meets the road, it's the TSM admins that get blamed when there are no backups!) One possibility I can think of (short of writing our own apps) is to have TSM send the info (via mail or snmp) to a ticketing system that generates a ticket that has to be addressed or it gets escalated to a manager. But I have no familiarity with such ticketing systems, so can't recommend one. So, what do other people in widely distributed environments do for this? Product recommendations welcomed, we'll look at them. Thanks! W Wanda Prather | Senior Technical Specialist | [email protected] | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o) Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
