Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for a quick installation and setup HowTo #6

Open
themelle opened this issue Jan 3, 2023 · 1 comment
Open

Request for a quick installation and setup HowTo #6

themelle opened this issue Jan 3, 2023 · 1 comment
Assignees
Labels
enhancement support Support request

Comments

@themelle
Copy link

themelle commented Jan 3, 2023

Dear Marcel,

I'm glad I found your lnx_backup check plugin, ad I am grateful for the work you've already done.

We are using check-mk raw edition, and I was able to install lnx_backup-2.0.mkp through the command line.

Also, I was able to figure out the basic usage, e.g.
/opt/omd/sites/MYSITE/local/share/check_mk/agents/lnx_backup BACKUP_NAME duply duply default status
gathers backup status and statistics and writes this data to
/var/lib/check_mk_agent/lnx_backup/BACKUP_NAME
, while
/opt/omd/sites/MYSITE/local/share/check_mk/agents/plugins/lnx_backup
is the actual agent plug-in which inserts the data from
/var/lib/check_mk_agent/lnx_backup/BACKUP_NAME
into the check-mk-agent output.

So, I assume I have to first download
/opt/omd/sites/MYSITE/local/share/check_mk/agents/plugins/lnx_backup
to the monitored host and place it into
/usr/lib/check_mk_agent/plugins/.

But what should I do with
/opt/omd/sites/MYSITE/local/share/check_mk/agents/lnx_backup
?

Should I use it as a wrapper for the actual duply cronjob on the monitored machine?
Or should it run in parallel?
Or is it invoked by check_mk_agent by any means?

That''s the part that is not really clear to me.

Thanks for your help,
and all the best for 2023!
Andreas

@mape2k mape2k self-assigned this Jan 27, 2023
@mape2k
Copy link
Owner

mape2k commented Jan 27, 2023

Thanks for your request.
You're right. You have to use agents/lnx_backup as a wrapper for rsync, tar and so on...

e.g. if your using rsync for your backup
lnx_backup My_Backup_Name rsync rsync --stats --other-args ...

where...
My_Backup_Name is the Name of the backup - every backup results in a single check item on check_mk
(first) rsync is the type of backup mechanism, so the wrapper could parse output correctly
(second) rsync and following arguments are your original command line for the backup

Hope this helps. I'll leave the issue to add some quick installation guide in future.

@mape2k mape2k added the support Support request label Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement support Support request
Projects
None yet
Development

No branches or pull requests

2 participants