I'm building a new reporting server, and need to keep the current, older
version, in production for a while.
I also need to get data into the new monitoring server so I can test my custom
reports and begin collecting historical data for future reporting.
That lets me simply disable report delivery schedules on the old system and
enable on the new, without a significant issue. I don't need the long term
history from the old server, just several days that would be collected on the
new system.
Sounds like my only option is to put multiple local monitoring agents on the
new system. Then, when ready to swing production to the new system, delete the
local agents and upgrade the remote agents on the TSM servers. The only issue
would be identical naming of the Agent I suppose.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lee Miller
Sent: Thursday, October 30, 2014 8:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Monitoring Agent, 2 on a single TSM Server?
You can do that on AIX and Linux, by installing the code into different
directories. You can't however do that on Windows.
But what issue are you dealing with between the versions?
Lee Miller
Tivoli Storage Manager for System Backup and Recovery Development and IBM
Tivoli Monitoring for Tivoli Storage Manager
Phone: 817-874-7484
From: "Vandeventer, Harold [OITS]" <Harold.Vandeventer AT KS DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 10/30/2014 03:58 PM
Subject: [ADSM-L] Monitoring Agent, 2 on a single TSM Server?
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Is it possible to install two Monitoring Agents on a single TSM server?
My hope: leave the current remote agent that pushes data from TSM 6.3.x to the
production Monitoring/Reporting/Admin Center server where production reports
are produced.
But, also install a second Remote Monitoring Agent (related to TSM 7.1.1) on
that same TSM 6.3 server and configure it to push data to a new
Monitoring/Reporting server.
This would let me workout the wrinkles in new reporting and continue to use
Remote Agents, not several local agents.
Alternative, I suppose: create a second local Agent on the new Monitoring
server and in time delete it, when I upgrade the Remote Agent to the new
release.
Thanks.
------------------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631
[Confidentiality notice:]
***********************************************************************
This e-mail message, including attachments, if any, is intended for the person
or entity to which it is addressed and may contain confidential or privileged
information. Any unauthorized review, use, or disclosure is prohibited. If
you are not the intended recipient, please contact the sender and destroy the
original message, including all copies, Thank you.
***********************************************************************
|
