Nagios Support Forum

gormank wrote:Thanks for the BS answer.

If you are not happy with an answer we have given, please express this in a professional manner without the sarcasm. If you wish to speak to me directly about the matter, please email [email protected] and they can forward your message to me. But from this point on, there will be zero tolerance of such replies. I will not be addressing this further in this or in other forum threads.

gormank wrote:The vendor will simply point me back to you since its backing up the NLS DB.

This may be true, but they will be able to provide more information as to how their backups are taken and stored. As has been mentioned, we neither use nor test against NetBackup, so we can neither confirm nor deny any of their functionality interacting with ours. We have our own built-in functionality on which we can comment, but we are in no position to speculate about third-party tools we have not tested. Since you have access to both NetBackup and Nagios Logserver, I would suggest setting up a test Logserver environment, then running NetBackup against that to see whether the backups restore properly.

gormank wrote:I suggest you provide a real answer, or find someone who can.

We have provided real answers in regards to our own software. NetBackup is not our software, and their support offerings are listed here: https://www.veritas.com/support/en_US.html

gormank wrote:This user's support model of ignoring, and deflecting questions is not satisfying to anyone.

We have neither deflected nor ignored. We have answered what we can, and the rest we have directed to the appropriate sources (NetBackup support). As was stated above, if you are dissatisfied with our support, please email [email protected] and ask for me directly.

Netbackup is simply an example. Whether or not a commercial backup solution is sufficient is directly related to the product not the backup software. Any backup product will happily back up files.

The question is whether backed up files can be restored successfully. This is also a question directly related to the product you sell, which has minimal documentation BTW.

Still waiting for a valid response now after 4 requests.

Here's what we support for Nagios Log Server in terms of backups: Elasticsearch snapshots created by our distributed versions of Curator or Knapsack. All a Nagios Log Server cluster requires is a logical, writable path (as mentioned by @avendemore) to store its Curator or Knapsack generated snapshots.

If all Netbackup (or insert backup software here) is doing is keeping tabs on those aforementioned two things (Curator or Knapsack generated snapshots), then it is supported. If Netbackup (or insert backup software here) modifies those Curator or Knapsack snapshots in anyway that makes them unreadable by Curator or Knapsack, then it is not supported. There's no way for myself or any other tech to know how any given backup software is going to interact with those snapshots without testing every single piece of backup software out there, but assuming the backup software is interacting with the snapshots corresponding files in a responsible way I don't see an issue with any particular backup software. In a nutshell, as long as the backup software isn't modifying the Curator or Knapsack snapshots in some fashion, it doesn't really matter what the software is doing as far as Nagios Log Server is concerned.

Now, if you want to use some sort of software (other than our distributed versions of Curator or Knapsack) to do direct manipulation of the Elasticsearch data files, the current state of the Java heap, or archive the Elasticsearch data files by hand, that is absolutely not supported.