4 Germanium

Re: control timings of tape alert generation

Ah - your new statement " ... but here only a single tape drive is enabled at all, ..." clarifies the situation.

In your yesterday's note you mentioned " ... but currently, only one is not enabled,"

The tape drive parallelism only controls the number of data streams.

Unfortunately, there is no specific log file for the 2 library control daemons.

However, you can increase the debug level for a running process (nsrjb or nsrd) while it is running.

The appropriate command would be dbgcommand:

  - find the appropriate proccess id (PID)

  - select another debug level using       dbgcommand -p <pid> Debug=#

You will find the information in the daemon.raw file.

Do not forget to switch to debug level 0 later - the log file might become very big very fast.

2 Iron

Re: control timings of tape alert generation

Thanks for the details outlining the mechanisms.

Our issue is the following: the Media alerts go out to a IT team inbox, where the admin on duty needs to take action ... when there is need for action.

Thus, tape alerts that get resolved over night are nuisance alerts: the admin on duty will start NMC and have a look, only to see that everything is OK.

If I understand the explanations correctly, rising the value of target sessions could alleviate the issue, but this will probably have other implications, as more sessions are multiplexed to tape, potentially raising recovery duration.

I consider switching off the mail alert, and polling the NMC for open alerts with a monitoring tool like Nagios.

Would this be possible?

Regards, Thomas

0 Kudos
4 Germanium

Re: control timings of tape alert generation

There is no such switch available in the NW Admin GUI.

Of course this is potentially possible via nsradmin. However, if you try, you will be noticed that this is a read-only attribute.

Maybe you should contact EMC support to check whether there is another method which could help.

0 Kudos
6 Indium

Re: control timings of tape alert generation

I don't know your setup, but you can also try to add device to pool.  NW requests volumes per pool and when it knows it has one device for that pool, then alert management is kicked off differently.  You standby folks can use nsrwatch instead and check pending message and device status in more quicker fashion.

0 Kudos