BRC - Replication fails with bad mount point

Written By Tami Sutcliffe (Super Administrator)

Updated at June 23rd, 2021

Problem: The user sees the following error after a replication job fails:

Type of alert: Backup FAILED
 Alert message: [For corrective actions www.axcient.com/log-actions]<http://www.axcient.com/log-actions]> Backup 'Backup Job' on 192.168.1.1 Failed --- Error - fuse: bad mount point `/uptiva/mounts/#/#/f$': No such file or directory
 main.c(smbcfs_main):866 ERROR: fuse_parse_cmdline
 Unable to mount //172.16.0.226/f$ on remote host.
 Unable to mount //172.16.0.226/f$ on remote host.
 Errors occurred preparing the client machine for impending backup.
 Errors occurred during task execution.

Cause: This failure occurs when a previous mount point is left behind after a job runs. This happens for various reasons (such as unexpected server shutdown, conflict with other jobs, etc.) and can be cleared by executing the following procedures.

Solution: Do the following to resolve the issue:

1. Reboot the Axcient appliance.

2. If rebooting the Axcient appliance does not resolve the issue, contact Axcient Support to manually unmount the bad point.