Backup Symlinked Data



  • When moving data to an external location like described in the docs under Moving a single app's data directory to another location the symlinked location is not part of the backup. How can I change the backup configuration to also include this data?

    total 242952
    drwxr-xr-x 4 yellowtent yellowtent      4096 Oct 19 20:53 ./
    drwxr-xr-x 6 root       root            4096 Oct 21 12:53 ../
    -rw-r--r-- 1 yellowtent yellowtent      2814 Oct 23 10:01 config.json
    lrwxrwxrwx 1 root       root              19 Oct 19 20:53 data -> /srv/nextcloud-data/
    drwxrwx--- 9 www-data   www-data        4096 Oct 16 20:05 data_orig/
    -rw-r--r-- 1 root       root             529 Oct 23 10:01 fsmetadata.json
    -rw-r--r-- 1 yellowtent yellowtent 248753695 Oct 23 10:01 postgresqldump
    drwxr-xr-x 2 lxd        lxd             4096 Oct 23 13:47 redis/
    root@my:/home/yellowtent/appsdata/dc3a15ad-9993-4e5c-9039-46e73d048341# 
    

    The folder data is missing in the backup, whereas data_orig is there.



  • @tobru You should make the /home/yellowtent/appsdata/dc3a15ad-9993-4e5c-9039-46e73d048341 a symlink instead.

    So something like:

    1. stop the containers
    2. move the data directory. in the example below, I am assuming /srv/nextcloud does not exist. If it already exists, remove it (otherwise the mv will move it as a subdirectory).
    mv /home/yellowtent/appsdata/dc3a15ad-9993-4e5c-9039-46e73d048341 /srv/nextcloud
    ln -s /srv/nextcloud /home/yellowtent/appsdata/dc3a15ad-9993-4e5c-9039-46e73d048341
    
    1. start the containers


  • Thanks @girish, that did the trick and lead straight into Backup Improvements: Restic as Backend.