TSM V7.1 Operations Center Flashcards
what is a hub server?
the server that connects to the OC
what is a spoke server?
a server that is added and monitored via the OC?
where is the OC spoke server data stored?
in the TSM database of the Hub server and on the Spoke server.
Per 1000 TSM clients , how much additional TSM database space should be reserved for the OC data?
2 GB TSM database space + 10 GB archive log space.
at the hub this needs to be added for the spoke servers) as well
OC terminology: inventory =
TSM database + active + archive log
OC terminology: peer server
target server in node replication
5 OC authority levels, which ones?
system, policy, storage, operator, node
describe OC authority policy
can work with nodes (clients) registration and settings and alerts (note: cannot work with servers and has no client access!)
describe OC authority: storage
can backup the TSM db, alerts and work with stgpools
note: cannot work with servers!
describe OC authority: operator
can work with alerts and cancel client sessions
describe OC authority: node
can open the client web interface (only!)
which authority is needed for changing the Global Settings?
system authority
what are Global Settings
settings that are common for all servers
how do I switch between authorities?
logout, login
alerts can show activity log messages surrounding them. How many?
500 before and 500 after.
what is the OC url?
https://localhost:11090/oc/
main menu: structure? (6 drop down menu’s)
overview, clients, services, servers, storage pools, storage devices
overview menu ‘s submenu’s?
overview & alerts
client menu: submenu’s
per client: overview, properties, file spaces, client access
services menu:?
overview of policies (read only)
servers menu?
per server: overview, properties, alerts, active tasks, completed tasks
stgpools menu:
quick look & backup stgpools
The OC is supported/delivered from which version TSM onwards?
TSM V6.3.4 +
3 states for alerts in the OC, which 3?
active, inactive, closed
how do I make sure that alerts are monitored in the OC?
use the set command: set alertmonitoring on (default, at server initialization, it is off)
How do I define how long an alert in the OC will remain in it’s current state?
use the set command:
set alertinactiveduration num_min (default 480)
set alertactiveduration num_min (default 480)
set alertclosedduration num_min (default 60, 0=deleted right away)
3 types of clients in the OC, which 3?
Applications, Virtual Machines and Systems
What are “ tasks” ?
processes + sessions
“At Risk” settings for clients are used for???
times since last backup: default (7 days), bypass(ignore) or custom (defin enr of days)
“at risk” settings require the server to be level …
7.1
