How to search and kill this phantom alert.

Why do you think it is phantom?  It was there at the time it was trigerred... you may continue to ignore it or make sure enough devices/volumes are available at the time of alert to address this (of course, one could fix it with session parallelism too).

Please confirm if there is any group in waiting state. Also check is there is any manual backup started from any client.

Run inventory on the library, it might help you to clear this error message.

If its not cleared, then you might need to restart NetWorker services on the server to clear this error message.

Regards,

Prajith

Hi,

Phantom?  >>>>because of it was running from many days and no group are running on this backup server.

Hi Moin,

I wouldn't call it "phantom". The alert was there for a reason, so in order to avoid those alerts, as Hrvoje said, you better ensure that you have enough volumes/devices available for the backups, otherwise the alert will be again triggered.

Why the alert is still there? Good question, but you can get rid of it in the main NMC window-> Events->Right click on it->Dismiss

This should remove the alert.

Thank you.

Carlos.

Yes checked sufficient volume are there

Group is not running....let me check other solution provided by you..Will update you .

Thanks for quick reply

CarlosRojas wrote: Why the alert is still there? Good question, but you can get rid of it in the main NMC window-> Events->Right click on it->Dismiss This should remove the alert.

I believe in the past that would be removed automatically once the request has been addressed? Only failed groups would remain.  I do not use that feature of NMC for years now so I can't say if this is the case or not with current releases.

As for the statement that groups do not run there, do you have client initiated backups that might use those pools?

Hi Moin,

You have to double check that there is no running jobs requesting devices on those pools either scheduled jobs or client initiated jobs as these alerts should be cleared out once the device is available for the job or when the job aborted.

If you ensured that there is no running jobs requesting devices for those pools so please provide us with s the NetWorker version and build you have as well as the Java version installed for the NMC , I it "may be" an issue with the NMC and Java that is not updating events properly "this is the least possibility cause"

Thanks,

Ahmed Bahaa