Rsync two OMV machines

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Rsync two OMV machines

      Rsync two OMV machines

      Requirements
      - 2 OMV Servers running at least OMV 1.X

      Description
      This Guide will tell you how to Rsync two OMV machines. For example, 1 productive server, 1 backup server. After this guide you have identical content on both disks.

      Thanks @JanN for this Guide!


      Configuration
      Let´s call them: Machine A and Machine B.

      1. Machine A:
      • Create a share (for example: "DATA")
      • Include the whole disk in this share (path: "/")
      • User (admin account) and Administrators-Group should have privileges to read and write
      • root permission to read, write and execute


      2. Machine B:
      • Create a share (for example: "BACKUPDATA")
      • Include also the whole disk in this share (path: "/")
      • User (admin account) and Administrators-Group should have privileges to read and write
      • root permission to read, write and execute


      3. Machine A:
      • Add Rsync-module with name (for example "DATA")
      • Select the share you created on this machine
      • User: root, Group: root
      • Activate chroot
      • Activate authentification, real only
      • Add IP-Adress of Machine B in allowed hosts
      • Switch to User-Tab and add an entry for the admin account


      4. Machine B:
      • Add a rsync-job
      • Type remote, Mode pull
      • Source-Entry is "rsync://adminaccount@IPofMachineA/DATA" (Of course, you have to adopt IP... and DATA if you have created another folder for syncing!)
      • Target-Share is the folder you created on Machine B
      • Password field is the admin password
      • Check Recurse into directories, Preserver modification times, Delete files on the receiving side that don´t exist on sender (IF you want this), Set the destination permissions to be the same as source permissions, Update the destination ACLs to be the same as the source ACLs, Update the destination extended attributes to be the same as the local ones and Send command output via email.
      • Also Check "Perform a trial run with no changes made" (<< REMOVE this if everything runs well after the first sync)

      Optional:
      Add a cron-schedule-data to automatically start the sync as you like (If you do not do this, you have to start your sync manually!)



      Usage
      As far as you do not have configured the con-schedule-data, you can start your sync manually by:
      • Open Rsync on Machine B
      • Click on your created Job
      • Click on RUN
      If it runs ok, uncheck the point "Perform a trial run with no changes made"



      Questions / Problems / Diskussions
      Click here to get to the diskussions thread


      Version 1.0 // 08.01.2015
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive

      The post was edited 1 time, last by WastlJ ().