/usr/local/nagiosxi/scripts/backup_xi.sh
Running configuration check...
Stopping nagios:. done.
Starting nagios: done.
Backing up Core Config Manager (NagiosQL)...
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/var/ndo.sock: socket ignored
tar: /usr/local/nagios/var/rw/nagios.qh: socket ignored
tar: /usr/local/nagios/var: file changed as we read it
Backing up Nagios XI...
tar: Removing leading `/' from member names
Backing up MRTG...
tar: Removing leading `/' from member names
Backing up NRDP...
tar: Removing leading `/' from member names
Backing up Nagvis...
tar: Removing leading `/' from member names
Backing up MySQL databases...
Backing up PostgresQL databases...
Backing up logrotate config files...
Backing up Apache config files...
Compressing backup...
===============
BACKUP COMPLETE
===============
Backup stored in /store/backups/nagiosxi/1464887318.tar.gz
It seems like the local backup worked this time. Can you try scheduling a FTP backup a few minutes in the future to see if it is going to complete successfully?
Be sure to check out our Knowledgebase for helpful articles and solutions!
I already knew the local basckups were working (+-) as my disk was filling up fast. Anyway I scheduled it at 23:45. I'll let you know tomorrow hopw it goes. Tested the ftp conection, username password ok, File Upload test ok.
Let us know how it works out for you.
You may want to go back in to the /store/backups/nagiosxi folder and delete the failed backup folders to free up some space on the server.
Be sure to check out our Knowledgebase for helpful articles and solutions!
It seems like repairing the database fixed the issue. The backup script should catch this problems and should give a messgae in the scheduled backups component don't you think?