User Data on VSC is not backuped.

Backup is solely the responsibility of each user.

RAID-5 or RAID-6 is used on NFS and FhGFS servers to protect against single disk failure. Up to one (RAID-5) or two (RAID-6) disks failing concurrently can be sustained.

Other failure modes like disk controller failure or filesystem software faults are very seldom but might lead to loss of data.

A continuous backup from VSC has to circumvent the entering of the OTP numbers. If it its possible to keep a ssh session alive for a longer time, it can be used to create a tunnel for connecting to a rsync daemon.

Do the following steps:

1. on the remote machine:

   wget https://wiki.vsc.ac.at/lib/exe/fetch.php?media=doku:rsync:rsyncd_setup_remote.sh -O rsyncd_setup_remote.sh
   bash rsyncd_setup_remote.sh

2. On the local machine:

   wget https://wiki.vsc.ac.at/lib/exe/fetch.php?media=doku:rsync:rsyncd_setup_local.sh -O rsyncd_setup_local.sh
   bash rsyncd_setup_local.sh

3. start the rsync daemon with the 'start_rsync' command specified in the 'alias' on the remote machine (!!! remember on which login node you started the daemon, you have to connect to it later). The command looks like:

   rsync --daemon --config=/home/ ..../ rsyncd.conf

4. open the ssh tunnel 'tunnel_vsc_rsync' on the local machine this will tunnel map a local port to the remote port of the listening rsync daemon. This example maps the local port 5100 to port 8077 on the login node l32:

    ssh -L 5100:l32.cm.cluster:8077 <user>@l32.vsc.ac.at 

   (the login node “l32” conntected to must be the same as in step 3)

5. do the 'backup_vsc' on the local machine. This command connects via the local port of the ssh-tunnel from step 4 to the remote rsync daemon:

   rsync --password-file=/home/.../rsyncd.secrets -av --port 5100 rsync://<user>@localhost/myfiles /tmp/