Hi everyone,
Recently, I encountered an issue while configuring CIFS backup.
The problem was that when filling in all fields in the web interface, nothing happened. Therefore, I attempted to configure it via CLI using the following command:
orbit partition --local=“/srv/backup_remoto” --remote-host=“192.x.x.x” --remote-path=“/bkp/Segura PAM” --type=“cifs” --user=“” --password=“” --domain=“”
However, this also did not produce any results.
After running the command in debug mode, I noticed that the pipeline was failing during the parsing of ‘‘/etc/fstab’‘. It was difficult to verify directly because once the pipeline execution finished, the entry was removed from the configuration file.
Later, I discovered that spaces in ‘‘/etc/fstab’‘ must not be escaped with a regular backslash (‘‘\’‘). Instead, they must be replaced with ‘‘\040’‘.
As a result, the correct command should be:
orbit partition --local=“/srv/backup_remoto” --remote-host=“192.x.x.x” --remote-path=“/bkp/Segura\040PAM” --type=“cifs” --user=“” --password=“” --domain=“”
Alternatively, you can manually create an entry in ‘‘/etc/fstab’‘:
//192.x.x.x/bkp/Segura\040PAM /srv/backup_remoto cifs credentials=/root/.smbcred,uid=1001,gid=1001,file_mode=0755,dir_mode=0755,vers=3.0,_netdev 0 0
With this format, Linux CIFS utilities will correctly parse the configuration.
Important:
Before manually adding the entry, ensure that your credentials file (‘‘/root/.smbcred’‘) contains valid CIFS user credentials.
After updating ‘‘/etc/fstab’‘, run:
mount -a
This behavior is related to how ‘‘/etc/fstab’‘ parsing works rather than an issue with SMB itself.
Hope this helps.