• Relax-and-Recover 1.17.2 / Git
• OS_VENDOR=RedHatEnterpriseServer OS_VERSION=6
• Issue: We define a custom NETFS_UMOUNTCMD variable in our site.conf, with a function that basically spits out a backup complete message, along with a timestamp and where the backup was stored so that we can insert that result into a database. The problem is that it seems during the backup/NETFS/default/10_mount_NETFS_path.sh script step, it is trying to run this above custom defined UMOUNT command instead of a stock MOUNT command, even though the NETFS_MOUNTCMD variable is not defined. See the Mounting with line below from my log. Besides failing to mount, since it is running the wrong command, it does not error out, and continues writing the tar.gz file to the /tmp/rear.xxxx directory, filling up the /tmp filesystem.

2016-08-29 16:07:28 Including output/default/98_umount_output_dir.sh
2016-08-29 16:07:28 Unmounting '/tmp/rear.SEVLuCsI5908TRZ/outputfs'
NFSv4 mount point detected
nfs-server.example.com:/rear-backups/Linux umounted
rmdir: removing directory, `/tmp/rear.SEVLuCsI5908TRZ/outputfs'
2016-08-29 16:07:28 Finished running 'output' stage in 1 seconds
2016-08-29 16:07:28 Running 'backup' stage
2016-08-29 16:07:28 Including backup/default/00_valid_backup_methods.sh
2016-08-29 16:07:28 Including backup/NETFS/default/10_mount_NETFS_path.sh
mkdir: created directory `/tmp/rear.SEVLuCsI5908TRZ/outputfs'
2016-08-29 16:07:28 Mounting with 'custom_umount  /tmp/rear.SEVLuCsI5908TRZ/outputfs'
2016-08-29 16:07:28 Backup_Result|nfs://nfs-server.example.com:/rear-backups/Linux/client.example.com/client.example.com-backup.tar.gz|client.example.com|2016-08-29 16:07:28
umount: /tmp/rear.SEVLuCsI5908TRZ/outputfs: not mounted
2016-08-29 16:07:28 Including backup/NETFS/default/15_save_copy_of_prefix_dir.sh
2016-08-29 16:07:28 Including backup/NETFS/default/20_make_prefix_dir.sh
mkdir: created directory `/tmp/rear.SEVLuCsI5908TRZ/outputfs/client.example.com'
2016-08-29 16:07:28 Including backup/NETFS/default/25_create_lock.sh

I even modified the backup/NETFS/default/10_mount_NETFS_path.sh script, for debug purposes, to spit out the contents of all the MOUNTCMD and UMOUNTCMD variables, and none of the UMOUNT variables contain anything, so I don't know where its picking this botched mount command up from.

2016-08-30 15:04:51 Including backup/NETFS/default/10_mount_NETFS_path.sh
mkdir: created directory `/tmp/rear.9ttQqoQPAKL9Dq2/outputfs'
BACKUP_MOUNTCMD =
BACKUP_UMOUNTCMD = custom_umount
NETFS_MOUNTCMD =
NETFS_UMOUNTCMD =
OUTPUT_MOUNTCMD =
OUTPUT_UMOUNTCMD =
2016-08-30 15:04:51 Mounting with 'custom_umount  /tmp/rear.9ttQqoQPAKL9Dq2/outputfs'
...
umount: /tmp/rear.9ttQqoQPAKL9Dq2/outputfs: not mounted

It doesn't seem to matter if I set BACKUP_UMOUNTCMD or NETFS_UMOUNTCMD to my custom umount function, same result either way.

One other thought, we store both the ISO and BACKUP in the same spot on our NFS server, but during the course of the rear mkbackup, the NFS share is mounted and un-mounted 3 times, I believe. Is there any way to let it stay mounted the whole time so only 1 mount and 1 un-mount is required? The first 2 mounts and un-mounts work just fine, its only that 3rd / last mount, during the backup phase, that fails.

A better option (for us) would be a variable we could set that would run at the very end, perhaps during backup/NETFS/default/98_umount_NETFS_dir.sh script, to avoid having to hijack the umount command in the way that we do. Does something like that already exist? I didn't turn up anything obvious in my search.

Thank you in advance for any help you can provide.