20

I have Nextcloud installed as a snap. I would like to back it up to a folder on a separate drive within the server. Nextcloud appears to have an official backup app, which I have installed on the Nextcloud instance.

Is it possible to connect a folder on a separate drive to Nextcloud running as a snap? What permissions should such a folder have?

top 2 comments
sorted by: hot top controversial new old
[-] prcrst@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

I use nextcloud.export which comes with the snap (https://github.com/nextcloud-snap/nextcloud-snap/wiki/How-to-backup-your-instance), but the backup app looks nicer.

[-] notsofunnycomment@mander.xyz 1 points 1 year ago* (last edited 1 year ago)

I have a weekly crontab that does...

  • ...nextcloud.export -abc (everything except the data)
  • ...a backintime snapshot of the raw data folder.


I'm not fully happy with this yet though.

  • The nextcloud.export -abc command makes a full export of the config, database and apps. So in contrast to backintime, which rebuilds each snapshot only in terms of the files that changed since the previous snapshot, I have a full-blown new backup of config, database and apps every week.
  • I put the nextcloud instance in maintenance mode while running both commands, so the config, database and apps should fit the snapshot of the raw data. But it still feels tricky. I would prefer to have just have one full "file-change-based" weekly (or daily?) snapshot of e.g. a VM. That's why I'm looking at this: https://docs.hanssonit.se/s/W6fMouPiqQz3_Mog/virtual-machines-vm/d/W6fMquPiqQz3_Moi/nextcloud-vm
load more comments
view more: next ›
this post was submitted on 27 Jul 2023
20 points (83.3% liked)

Selfhosted

39258 readers
185 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS