I’m working on some replications to backup datasets to a dedicated backup pool. The data in question is nextcloud but this isn’t specific to the next cloud app.
My current structure is:
ssdpool
apps
nextcloud
db
html
datapool
apps
nextcloud
data
backupspool
apps
nextcloud
data
db
html
I have 2 replication tasks:
1 - Replicates both /mnt/ssdpool/apps/nextcloud/db and /mnt/ssdpool/apps/nextcloud/html to /mnt/backuppool/apps/nextcloud/
2 - Replicates /mnt/datapool/apps/nextcloud/data to /mnt/backuppool/apps/nextcloud/
The problem I have is they behave differently. Replication number 1 will copy the datasets selected to identical ones underneath the “nextcloud” dataset on the backup pool. This is what I expect to happen.
Replication number 2 however, will copy the contents of the data dataset directly into the nextcloud dataset, it doesn’t create the new dataset as a child. This completely breaks the directory structure.
My questions are - why is the behaviour different, and how do I override it so that it works consistently?