Nagios Support Forum

I responded to your other post with some information. As for moving... the scheduled SSH or FTP backups remove the file they make when they do the backup after it's been uploaded.

As for your permissions... I'm not sure how your volume is mounted but it will need to be able to be accessed by apache and nagios (nagios:nagcmd)

I mount the volume with /etc/fstab like this:

svm_dg3:/backups/NAGIOS01 /var/Digipolis/Backup nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0

The volume, is writeable for all unix users, which are translated to a ad user with write permissions (through NetApp)

Grtz

So if you set it to do a scheduled backup to that local directory a couple minutes into the future can it actually create and write that file? I wouldn't trust the permissions check 100% because it's being ran through a php script and it's not going to be 100% accurate. If it works even though the permission check failed, then there may be a need to make the permissions check more advanced.

Jake,

I set the local backup to run in 5 minutes to the mounted volume and will let you know if it works. Is it supposed to also place the backups first in /store/backups/nagioxi and then move it to the location configured in local backup component?

Grtz

Unlike the SSH and FTP tabs... the local backup tab will be using backup_xi.sh's user-set directory functionality so it should not be placing it in the /store/backups/nagiosxi and moving it. Instead it will be placed the directory you specified directly by passing the directory to the backup_xi.sh ... you can also read the backup_xi.sh to see what it is actually doing but for your question it will be doing this directly:

backup_xi.sh -d /your/specific/directory -n filename

Hey,

Should I try to do execute this for testing? backup_xi.sh -d /your/specific/directory -n filename
Tried again with the gui, but the backup was not placed in my mounted volume.

Grtz.

You can test the actual script from the CLI but you'll need to su into nagios to test it out properly, if you test it in the CLI though it will be able to tell us if it's a problem with the component or not.