• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 17 subscribers
  • Views 6558 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Netvault 11.4 - Unable to acknowledge individual warnings

david_turner
over 6 years ago

After upgrading to version 11.4, I am unable to acknowledge individual warnings in a list of warnings.  Once I select the warning and hit acknowledge, ALL of the warnings disappear.  I have also noted that the tool bar that held the action tools listing is missing, apparently replaced with an individual actions column.  Is this by design? 

  • +2 over 6 years ago

    Hi david_turner

    The "Acknowledge" option by design clears all warnings and errors.

    If you select a specific job and choose to Acknowledge, it asks "Are you sure you wish to clear errors and warnings on: All regular jobs in the 'warning/failed' state?"

    As for the Actions button which is an option-able setting to the left of the Jobs Table under 'Actions' at the bottom of the Jobs Table screen, you can set it back by clicking the "Settings" icon at the top of the WebUI:

     

    I hope this helps!

     

  • 0 over 6 years ago
    Thanks for helping me iron this out. I need to remember that my actions may have some unintentional consequenses.
  • 0 over 6 years ago

    True, but perhaps the "Acknowledge" option when highlighting a specific job should in fact just acknowledge that particular job. However, they initially have been introduced to be acknowledged as a whole. The way to clear an individual job from the "warning/failed" state is to actually find why the job is in that state, fix, and then have its Exit Status as Successful.

    That being said, jobs in Warning are actually just Successful jobs with a warning flag and no need to run those again to clear it.

    Additionally, Warnings themselves are usually and most often nothing to be concerned about. They typically are logged in that state when a backup skips files that are locked, or too busy at the time to be backed up, or not backed up because of OS exclusions lists and the like. If these are Windows Servers and File System Plugin BUs and you are using the "Standard" backup method in the "File System Plugin Options" - then consider changing the option to VSS instead of Standard. It may eliminate some of the warnings on these jobs because files will be backed up after a VSS Snapshot has been taken, thus not affected by a lock or activity.

    I hope this helps even further!

  • 0 over 5 years ago

    In 12.0.1 I can acknowledge individual warnings. Seems to me like they made some improvements here