Cron is starting a second full backup while manual started full backup is running
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I installed the backup app and started a full backup manually using occ backup:point:create on a shell.
When I had a look on what is happening at the system I found 2 directories in the apps data directory:
ls /var/www/nextcloud/data/appdata_ocu2885nl06t/backup/
20220417062826-full-fnbY9wEPqbllW9E
20220418102015-full-MbazSzn4ROTsL6j
This backup takes quite a long time (> 24h) and is still running, so I figured out that the following processes are accessing these directories:
235510 be/4 www-data 482.48 K/s 399.66 K/s 0.00 % 99.99 % php occ backup:point:create
269902 be/4 www-data 396.06 K/s 327.65 K/s 0.00 % 99.99 % php -f /var/www/nextcloud/cron.php
My interpretation is that there are 2 processes running each creating a full backup. Is this correct?
This should be avoided.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the interaction between the occ backup:point:create command and cron.php while a full backup is running. Trace how each entry point decides whether to start a full backup; done means a scheduled run does not create a second full backup while a manual run is active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100