Backup Stor can be reached over SFTP, FTP/FTPS and SMB/CIFS. The host in every case is backup.sayob.com, and the user name is the one issued with your storage, in the form kdXXXXXXX.
Which protocol to choose
SFTP is the best choice where your software supports it: encrypted by default, a single port, and it works with key authentication, which is what makes unattended backups possible. See Setting up SSH key access to Backup Stor.
FTPS is a good alternative when a tool speaks FTP and nothing else. It is FTP with TLS encryption added — not to be confused with SFTP, which is a different protocol despite the similar name. Performance is comparable, it automates easily, and it supports resuming an interrupted transfer.
SMB/CIFS is the option to use when software needs to see the storage as an ordinary directory or drive letter. Note that SMB traffic is filtered by many internet providers as a protective measure, so a connection that works from your server may fail from an office or home network.
Do not use plain FTP. Over unencrypted FTP the user name, the password and the data itself are transmitted in clear text and can be intercepted.
Connecting over SFTP
sftp [email protected]
For transferring a large amount of data, rsync over SSH is better still — it resumes after an interruption and copies only what has changed:
rsync -avz --progress /local/path/ [email protected]:/backups/
Connecting over FTPS
WinSCP and FileZilla both work well.
WinSCP
On first launch WinSCP offers SFTP; if you want FTPS, set the parameters yourself:
- File protocol — FTP;
- Encryption — explicit TLS/SSL;
- Host name — backup.sayob.com, port 21;
- User name and password — from your service access details.
Click Login.
For automated backups, WinSCP can generate the session code for you: in the connection settings, choose to generate session code and copy the command into your script.
FileZilla
The same settings: protocol FTP, explicit TLS encryption, host backup.sayob.com, port 21, with your user name and password.
Connecting over SMB/CIFS
Windows
Map it as a network drive using the path \\backup.sayob.com\kdXXXXXXX — see Connecting Backup Stor as a network drive in Windows for the full procedure and the common pitfalls.
Linux
Install the required package:
apt install cifs-utils # Debian, Ubuntu dnf install cifs-utils # AlmaLinux, Rocky Linux
Create a mount point:
mkdir /mnt/backup
Mount the storage:
mount -t cifs //backup.sayob.com/kdXXXXXXX /mnt/backup/ \ -o username=kdXXXXXXX,password=YYYYYYYY,nounix
If you mount into a user's home directory, add uid and gid so that the files belong to that user:
mount -t cifs //backup.sayob.com/kdXXXXXXX /home/user/backup/ \ -o username=kdXXXXXXX,password=YYYYYYYY,uid=1000,gid=1000,nounix
Mounting automatically at boot
A line in /etc/fstab mounts the storage on every start. Do not put the password in it directly: /etc/fstab is readable by every user on the system.
Create a credentials file readable only by root:
cat > /root/.backupstor <
Then reference it in /etc/fstab:
//backup.sayob.com/kdXXXXXXX /mnt/backup cifs rw,credentials=/root/.backupstor,nounix 0 0
Test it before relying on it:
mount -a df -h /mnt/backup
An error in /etc/fstab can prevent the server from booting normally, so always test with mount -a rather than discovering the problem at the next restart.
Useful links
If a connection fails, check the user name and password first, then whether the port is blocked on the network you are connecting from. If it still does not work, open a ticket from your client area.
