{"id":1572,"date":"2022-07-29T15:47:54","date_gmt":"2022-07-29T13:47:54","guid":{"rendered":"https:\/\/hobbykeller.spdns.de\/?p=1572"},"modified":"2022-07-29T16:01:16","modified_gmt":"2022-07-29T14:01:16","slug":"simple-backup-solution-for-mayan-edms","status":"publish","type":"post","link":"https:\/\/hobbykeller.spdns.de\/?p=1572","title":{"rendered":"Simple backup solution for Mayan EDMS"},"content":{"rendered":"\n

When it comes to backing up Mayan, we essentially have to back up two components:<\/p>\n\n\n\n

  1. The \/opt\/mayan-edms\/media<\/code> directory<\/li>
  2. The PostgreSQL database<\/li><\/ol>\n\n\n\n

    Remote storage location<\/h2>\n\n\n\n

    First thing we need is a remote storage location. We go for an NFS share which we mount on the Mayan System. <\/p>\n\n\n\n

    Initial setup<\/h3>\n\n\n\n

    Setup on the storage machine is the same as section 1.1 of the Raspibackup instructions<\/a>.<\/p>\n\n\n\n

    The backup path on the destination machine is: \/home\/nfs\/mayanha<\/code> with ownership privileges for nobody<\/code>:nogroup<\/code>.<\/p>\n\n\n\n

    On the Mayan server, set up a mount point as follows:<\/p>\n\n\n\n

    sudo mkdir -p \/mnt\/nfs\nsudo chown nobody:nogroup \/mnt\/nfs<\/pre><\/div>\n\n\n\n
    Mounting the NFS system<\/h3>\n\n\n\n
    In order to perform a backup, mount the remote NFS system to the mountpoint you created on the Mayan machine:<\/p>\n\n\n\n
    sudo mount 192.168.4.41:\/home\/nfs\/mayanha \/mnt\/nfs<\/pre><\/div>\n\n\n\n
    In case you get a message like the one below, your client machine lacks the nfs-common<\/code> (distros other than Ubuntu may call it nfs-utils<\/code>) package. Just issue sudo apt install nfs-common<\/code>.<\/p>\n\n\n\n
    mount: \/mnt\/nfs: bad option; for several filesystems (e.g. nfs, cifs) you might need a \/sbin\/mount.<type> helper program.\n<\/pre><\/div>\n\n\n\n
    Backup Operation<\/h2>\n\n\n\n
    To backup the PostgreSQL data base, on the Mayan Machine issue the following command:<\/p>\n\n\n\n
    sudo -u postgres pg_dumpall | gzip > \/mnt\/nfs\/20220727_mayan_postgresql.gz<\/pre><\/div>\n\n\n\n
    We prefer to have the complete PostgreSQL Server dumped instead of the single Mayan data base because we don’t have to care about user privileges and passwords that way.<\/p>\n\n\n\n
    Next we will backup the \/opt\/mayan-edms\/media directory as per the backup instructions of the Mayan online documentation. <\/p>\n\n\n\n
    We slightly deviate from the instructions given in the Mayan documentation in two points:<\/p>\n\n\n\n
    1. We stop the supervisor<\/code> daemon to prevent Mayan EDMS from altering the files in the media directory while the backup is running.<\/li>
    2. We leave out the v<\/code>erbose option in the tar<\/code> command as the verbose option results in an endless list of files which (a) slows down the creation of the tar.gz file and (b) prevents us from properly noticing error messages that might be relevant but gets lost in the file list.<\/li><\/ol>\n\n\n\n
      sudo service supervisor stop\nsudo tar -zcf \/mnt\/nfs\/20220728_mayan_media.tar.gz \/opt\/mayan-edms\/media\/<\/pre><\/div>\n\n\n\n
      After the backup don’t forget to reengage the supervisor service:<\/p>\n\n\n\n
      sudo service supervisor start<\/pre><\/div>\n\n\n\n
      Open Questions<\/h3>\n\n\n\n
      Notice that the there are other files and directories under \/opt\/mayan-edms\/media:<\/p>\n\n\n\n
      ilek@mayanha:\/opt\/mayan-edms$ ls -alh\ntotal 32K\ndrwxr-xr-x  7 mayan mayan 4.0K Jun  8 20:24 .\ndrwxr-xr-x  3 root  root  4.0K Jun  8 19:07 ..\ndrwxr-xr-x  3 mayan mayan 4.0K Jul 23 13:15 bin\ndrwxr-xr-x  3 mayan mayan 4.0K Jun  8 19:08 include\ndrwxr-xr-x  3 mayan mayan 4.0K Jun  8 19:07 lib\nlrwxrwxrwx  1 mayan mayan    3 Jun  8 19:07 lib64 -> lib\ndrwxrwxr-x 10 mayan mayan 4.0K Jun 11 10:39 media\n-rw-r--r--  1 mayan mayan   70 Jun  8 19:07 pyvenv.cfg\ndrwxrwxr-x  3 mayan mayan 4.0K Jun  8 19:08 share\n<\/pre><\/div>\n\n\n\n
      This means that upon restore writing just expanding the backup of the media<\/code> subdirectory will not<\/strong> reproduce the complete mayan installation.<\/p>\n\n\n\n
      It should rather be assumed that you have an ’empty’ Mayan EDMS installation<\/strong> installed for which you will have to overwrite the media directory with the content from your backup file.<\/p>\n\n\n\n
      Keep in mind that when creating the empty Mayan installation into which you later  restore, you make sure to use the same passwords as for the installation you just backed up. In particular, you should use identical passwords for…
      – the postgres super user of your database
      – the mayan user of your database
      – the redis user password
      – the rabbitiq user password