This is how you connect a virtual machine in your Private Cloud to your Managed Backup Storage — via NFS, SMB, SFTP, SSH, rsync or Borg. The connection only works from the private network to which you have connected the storage.

Requirements

  • A connection (Anbindung) to the private network your machine is in — see First steps.
  • The service you want is switched on in the Dienste (services) section (aktiv, active).
  • For SMB, an SMB password; for SFTP, SSH, rsync and Borg, an SSH key.

Where to find the credentials

The Zugangsdaten (credentials) section of your Managed Backup Storage shows:

Benutzer (user)
Your user name, in the form u<service ID>.
Freigabe (share)
/backup for NFS, backup for SMB.
Host
The IP address of the storage in your private network, one per connection.

Below that, you find ready-made commands with your values for every service that is switched on. In the examples below, <IP> stands for the address under Host and u<service ID> for your user name.

NFS (Linux) — port 2049

mount -t nfs4 <IP>:/backup /mnt/backup

When you switch NFS on, the field IP-Allow-Liste (IP allow list) appears next to it. Use it to restrict access to certain addresses in your network; empty means: the whole network. Apply your entry with Allow-Liste speichern (save allow list).

SMB (Windows, Linux, macOS) — port 445

First set an SMB password with at least 12 characters in the Dienste section and click setzen (set). Then, on Linux:

mount -t cifs //<IP>/backup /mnt/backup -o username=u<service ID>,vers=3.1.1,seal

The seal option makes sure the connection is encrypted. On Windows, open \\<IP>\backup in File Explorer and sign in with the user u<service ID>.

SFTP — port 22

sftp -i ~/.ssh/mbs-sftp u<service ID>@<IP>

With restic over SFTP:

restic -o sftp.args="-i ~/.ssh/mbs-sftp" -r sftp:u<service ID>@<IP>:/home/restic init

SSH — port 22

ssh -i ~/.ssh/mbs-ssh u<service ID>@<IP>

You get a restricted command line in your storage — with file tools and archivers such as tar, zip and 7z.

rsync — port 2222

rsync -av -e "ssh -p 2222 -i ~/.ssh/mbs-rsync" ./data/ u<service ID>@<IP>:backup/

Borg — port 2222

BORG_RSH="ssh -p 2222 -i ~/.ssh/mbs-borg" borg init -e repokey ssh://u<service ID>@<IP>:2222/./home/borg

A separate key for each access. SFTP, SSH, rsync and Borg recognize from the key what you are allowed to do. So always pass the matching key with -i ~/.ssh/mbs-<purpose>. Details: Setting up SSH keys.

If it does not work

  • No connection: check that your machine is in the same private network as the connection, and that the service is set to aktiv.
  • NFS mount is refused: is your machine in the IP-Allow-Liste?
  • Borg reports an rsync error (or the other way round): you are connecting with the wrong key. Pass the key for exactly this purpose with -i.

Where to go next

Was this answer helpful? 0 Users Found This Useful (0 Votes)

Most Popular Articles

Managed Backup Storage: overview and first steps

Managed Backup Storage is backup storage for your Private Cloud. Your virtual machines write...
Managed Backup Storage: setting up SSH keys (one key for one purpose)

For SFTP, SSH, rsync and Borg you sign in to your Managed Backup Storage with an SSH key, not...
Managed Backup Storage: ransomware protection, snapshots and restore

With ransomware protection, an immutable snapshot — a frozen state — of your Managed Backup...
Managed Backup Storage: storage, usage and upgrades

Your Managed Backup Storage has a fixed size that you booked — between 1 and 50 TB. This article...
Ordering Managed Backup Storage (only with Platform Vienna)

You order Managed Backup Storage in the Store under Managed Backup Storage → Cloud Backup. In the...