Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Restore not possible

Restore not possible

Scheduled Pinned Locked Moved Solved Support
20 Posts 6 Posters 387 Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P p44

    We discussed this issue here:
    https://forum.cloudron.io/topic/12632/tarextract-pipeline-error-invalid-tar-header/24

    I've encountered this problem twice...

    @sponch I have a question: Were the backups you're trying to restore still in their original location (where they were first created), or had they been moved/copied to a different Hetzner Box before restoring?

    I’m asking because the files I tried to recover (unsuccessfully) had been transferred between Hetzner Boxes, and I’m wondering if that could be the root of the issue.

    Edit: Were the files you tried to restore from the Hetzner Box originally created by the same specific Cloudron instance? Or were they from a different instance (e.g., after a reinstall)? I’m asking to help trace the root cause of the issue.

    @james I believe that in some cases encryption is necessary, so increased security inherently comes with the trade-off of being locked out of the recovery process. However, in this specific case, we should investigate the root cause of the issue, since it seems that has affected multiple users...

    @sponch @james Another hypothesis that comes to mind is the use of special characters in the password, which might not be interpreted correctly during the backup recovery process – Eg. a Gui problem –. I’ve since updated my passwords to only include uppercase letters, lowercase letters, and numbers (40 characters long), and the issue appears to be resolved... but this is only an hypothesis.

    sponchS Offline
    sponchS Offline
    sponch
    wrote last edited by sponch
    #11

    @sponch I have a question: Were the backups you're trying to restore still in their original location (where they were first created), or had they been moved/copied to a different Hetzner Box before restoring?

    Same location (only the prefixed changed months ago - should not concern the recent backups)

    I’m asking because the files I tried to recover (unsuccessfully) had been transferred between Hetzner Boxes, and I’m wondering if that could be the root of the issue.

    Edit: Were the files you tried to restore from the Hetzner Box originally created by the same specific Cloudron instance? Or were they from a different instance (e.g., after a reinstall)? I’m asking to help trace the root cause of the issue.

    Same instance. Nextcloud is backed up daily. Last fews days restoring always ends up with same error.

    @sponch @james Another hypothesis that comes to mind is the use of special characters in the password, which might not be interpreted correctly during the backup recovery process – Eg. a Gui problem

    Just restored another (unimportant) app from same backup day. Worked perfectly.

    1 Reply Last reply
    1
    • P Offline
      P Offline
      p44
      translator
      wrote last edited by
      #12

      @sponch ok thanks for informations. I hope those informations could help to reproduce issue and eventually find the source cause...

      1 Reply Last reply
      0
      • sponchS Offline
        sponchS Offline
        sponch
        wrote last edited by sponch
        #13

        hi and thanks four you information. Unfortunately I could not find the cause.... and set up a new Nextcloud instance (only had 5 users and offline data from the clients).
        As other apps could be restored w/o any problems it must have been s.th. related to Nextcloud specific restoration I guess.
        Just made a clone of the new Nextcloud App (encryption disabled....)worked perfectly.

        P 1 Reply Last reply
        1
        • sponchS sponch

          hi and thanks four you information. Unfortunately I could not find the cause.... and set up a new Nextcloud instance (only had 5 users and offline data from the clients).
          As other apps could be restored w/o any problems it must have been s.th. related to Nextcloud specific restoration I guess.
          Just made a clone of the new Nextcloud App (encryption disabled....)worked perfectly.

          P Offline
          P Offline
          p44
          translator
          wrote last edited by
          #14

          @sponch you disabled Cloudron Backup Encryption or Nextcloud App Encription?

          sponchS 1 Reply Last reply
          0
          • sponchS sponch

            what would you recommend: rsync or tgz for future backups?

            K Offline
            K Offline
            Kelsey67
            wrote last edited by
            #15

            @sponch I learned the hard way and lost a ton of data using tgz. Rsync is definitely better, i dont even know why anyone would both with tgz. Unless you combine them, use rsync for daily incremental backups to a remote server and tgz for weekly/monthly full archives. i have a large Nextcloud data directory on an AWS server, managed HostJane EC2 - https://www.hostjane.com: supporting 500MB of changes daily (e.g., new uploads, modified files) needing frequent backups for tens of GBs for mainly photos). I like to set up rsync via Cygwin, automate it with Task Scheduler, and pair it with database dumps.

            e.g. Rsync transfers the full 50GB data directory to the NAS.
            Time: ~2 hours at 5MB/s (50GB ÷ 5MB/s = 10,000 seconds ≈ 167 minutes).
            Bandwidth: 50GB.

            Compare that to tgz. Backup takes ~6 hours 20 minutes, regardless of changes, due to full compression and transfer. tgz completely screws up Nextcloud availability if maintenance mode extends into active hours. tgz requires a full archive each time, additional steps to manage multiple archives. tgz is redundant for every use case of every Nextcloud backup I have ever done.

            sponchS 1 Reply Last reply
            1
            • P p44

              @sponch you disabled Cloudron Backup Encryption or Nextcloud App Encription?

              sponchS Offline
              sponchS Offline
              sponch
              wrote last edited by sponch
              #16

              @p44 I haven't uses NC Encryption. I disabled backup encryption now (which doesn't feel right....). But as I said - other apps could be restored w/o any problems.
              As restoring backups should be one of the most important thing for everyone here I wonder why there came no further support from "official" side here.

              P 1 Reply Last reply
              1
              • K Kelsey67

                @sponch I learned the hard way and lost a ton of data using tgz. Rsync is definitely better, i dont even know why anyone would both with tgz. Unless you combine them, use rsync for daily incremental backups to a remote server and tgz for weekly/monthly full archives. i have a large Nextcloud data directory on an AWS server, managed HostJane EC2 - https://www.hostjane.com: supporting 500MB of changes daily (e.g., new uploads, modified files) needing frequent backups for tens of GBs for mainly photos). I like to set up rsync via Cygwin, automate it with Task Scheduler, and pair it with database dumps.

                e.g. Rsync transfers the full 50GB data directory to the NAS.
                Time: ~2 hours at 5MB/s (50GB ÷ 5MB/s = 10,000 seconds ≈ 167 minutes).
                Bandwidth: 50GB.

                Compare that to tgz. Backup takes ~6 hours 20 minutes, regardless of changes, due to full compression and transfer. tgz completely screws up Nextcloud availability if maintenance mode extends into active hours. tgz requires a full archive each time, additional steps to manage multiple archives. tgz is redundant for every use case of every Nextcloud backup I have ever done.

                sponchS Offline
                sponchS Offline
                sponch
                wrote last edited by
                #17

                @Kelsey67 thanks. that’s what I have used anyway.

                1 Reply Last reply
                0
                • J joseph has marked this topic as solved
                • sponchS sponch

                  @p44 I haven't uses NC Encryption. I disabled backup encryption now (which doesn't feel right....). But as I said - other apps could be restored w/o any problems.
                  As restoring backups should be one of the most important thing for everyone here I wonder why there came no further support from "official" side here.

                  P Offline
                  P Offline
                  p44
                  translator
                  wrote last edited by
                  #18

                  @sponch Thanks, keep us posted.

                  1 Reply Last reply
                  0
                  • necrevistonnezrN Offline
                    necrevistonnezrN Offline
                    necrevistonnezr
                    wrote last edited by
                    #19

                    restic is made for this. Fast, e2e encrypted, any provider you can imagine via rclone.

                    P 1 Reply Last reply
                    1
                    • necrevistonnezrN necrevistonnezr

                      restic is made for this. Fast, e2e encrypted, any provider you can imagine via rclone.

                      P Offline
                      P Offline
                      p44
                      translator
                      wrote last edited by
                      #20

                      @necrevistonnezr Thanks a lot, it seems to be a very good strategy, but implementation is out of my personal knowledge.

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search