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
  • Brite
  • 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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. What happens before a backup is "created"?

What happens before a backup is "created"?

Scheduled Pinned Locked Moved Unsolved Support
backupretentiontaskssystemtimezone
2 Posts 2 Posters 15 Views 2 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.
  • nottheendN Offline
    nottheendN Offline
    nottheend
    wrote last edited by nottheend
    #1

    I love the improved backup functionalities and more detailed information regarding backups in recent releases, thanks!

    What happens between the scheduled start of a backup and the time a backup is created?
    In my case: What happened between 23:00 and 3:38 AM?

    Let me add the context:

    • Backup schedule is set to 23:00 daily. When is that? If I believe "System" --> "Setting" it would be my GMT timezone, because there it says: "UI timestamps always follow the browser’s time zone."

    • When I check the system logs, I can see exactly at 23:00 a task, is that the beginning of the backup process?

    2026-04-24T23:00:00.009Z locks: write: current locks: {"full_backup_task_8663c238-b4f3-482b-8c4c-a6809dcdeed9":null}
    2026-04-24T23:00:00.009Z locks: acquire: full_backup_task_8663c238-b4f3-482b-8c4c-a6809dcdeed9
    2026-04-24T23:00:00.018Z tasks: startTask - starting task 7538 with options {"timeout":86400000,"nice":15,"memoryLimit":1024,"oomScoreAdjust":-999}. logs at /home/yellowtent/platformdata/logs/tasks/7538.log
    2026-04-24T23:00:00.018Z tasks: updating task 7538 with: {"pending":false}
    2026-04-24T23:00:00.018Z shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 7538 /home/yellowtent/platformdata/logs/tasks/7538.log 15 1024 -999
    
    • However looking at the creation time of the backup in "Backup" --> "Sites" (in Backup "Info") it says: "created at 03:38 AM".
    • On the properties of the same backup, I can see "Backup duration: 2h 38m 4s"

    That my backup takes almost 3 hours is fine with me. But I would like to understand what is happening before the backup is actually "created".

    I checked the system logs but I didn't find much revealing. The Update Schedule is set to 5 AM, and it may interfere with the Backup? Is there a recommendation for doing either the Backup or the update first? I also read that before updates an Backup is taken automatically and I am not sure if that would be skipped if there is a recent backup.

    Any hint would be appreciated! And sorry for squeezing in many questions in that post, but it may reveal some context.

    jamesJ 1 Reply Last reply
    0
    • nottheendN nottheend

      I love the improved backup functionalities and more detailed information regarding backups in recent releases, thanks!

      What happens between the scheduled start of a backup and the time a backup is created?
      In my case: What happened between 23:00 and 3:38 AM?

      Let me add the context:

      • Backup schedule is set to 23:00 daily. When is that? If I believe "System" --> "Setting" it would be my GMT timezone, because there it says: "UI timestamps always follow the browser’s time zone."

      • When I check the system logs, I can see exactly at 23:00 a task, is that the beginning of the backup process?

      2026-04-24T23:00:00.009Z locks: write: current locks: {"full_backup_task_8663c238-b4f3-482b-8c4c-a6809dcdeed9":null}
      2026-04-24T23:00:00.009Z locks: acquire: full_backup_task_8663c238-b4f3-482b-8c4c-a6809dcdeed9
      2026-04-24T23:00:00.018Z tasks: startTask - starting task 7538 with options {"timeout":86400000,"nice":15,"memoryLimit":1024,"oomScoreAdjust":-999}. logs at /home/yellowtent/platformdata/logs/tasks/7538.log
      2026-04-24T23:00:00.018Z tasks: updating task 7538 with: {"pending":false}
      2026-04-24T23:00:00.018Z shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 7538 /home/yellowtent/platformdata/logs/tasks/7538.log 15 1024 -999
      
      • However looking at the creation time of the backup in "Backup" --> "Sites" (in Backup "Info") it says: "created at 03:38 AM".
      • On the properties of the same backup, I can see "Backup duration: 2h 38m 4s"

      That my backup takes almost 3 hours is fine with me. But I would like to understand what is happening before the backup is actually "created".

      I checked the system logs but I didn't find much revealing. The Update Schedule is set to 5 AM, and it may interfere with the Backup? Is there a recommendation for doing either the Backup or the update first? I also read that before updates an Backup is taken automatically and I am not sure if that would be skipped if there is a recent backup.

      Any hint would be appreciated! And sorry for squeezing in many questions in that post, but it may reveal some context.

      jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @nottheend

      @nottheend said:

      When I check the system logs, I can see exactly at 23:00 a task, is that the beginning of the backup process?

      Yes, that is the start of the full backup task.


      @nottheend said:

      That my backup takes almost 3 hours is fine with me. But I would like to understand what is happening before the backup is actually "created".

      Depending on the backup type tgz or rsync it can take some time depending on the apps and size of the apps that need to be included in the backup.
      For the integrity check everything needs to be indexed and sha256 hashed first before the backup to then validate it after the backup.
      For example, Nextcloud stores image previews (thumbnails) in a hashed structured folder system within the appdata directory to optimize performance and prevent too many files in a single directory.
      But this in turn leads to constant changes due to the hashed structured folder system and is so "deep" that sometimes the tgz format just fails because the folder depth, thus the name of the path, is too big to be stored in a tgz due to the primary limitation is the PATH_MAX constant, which is typically 4096 bytes.
      And also takes longer time to index and hash.


      @nottheend said:

      The Update Schedule is set to 5 AM, and it may interfere with the Backup?

      That is no issue.
      When the backup takes longer, the system update task is simply scheduled after that.

      Depending on the backup provider, for example SSHFS, the rsync format can be way faster than tgz.
      The initial backup of rsync can take longer, but every subsequent backup is then very fast since Cloudron can do a remote-copy call instead of copying everything again and again from the Cloudron host to the provider.
      This saves bandwidth and compute time, increasing the backup times significantly.
      For example, my own Cloudron with 24 apps and 600 GB of backup data, only took 36 minutes 28 seconds this night to do a full backup with the rsync format on SSHFS with a Hetzner Storage Box.


      @nottheend said:

      I also read that before updates an Backup is taken automatically and I am not sure if that would be skipped if there is a recent backup.

      A full system backup before every Cloudron update is default and is only skipped when explicitly configured so.
      If you are using the rsync type backup, the backup before the update would be very fast since it just took a backup before.
      Also from my system, since a backup was taken before the Cloudron update, the pre-update backup only took 4 minutes 31 seconds.


      @nottheend said:

      And sorry for squeezing in many questions in that post, but it may reveal some context.

      All good! Always happy to help.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      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