nextcloud / nextcloud/backup

Feature Suggestions: Delete single backups

Open
#110 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
272
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Hello,

first of all thanks for the nextcloud app. Finally something enjoyable to backup our nextcloud and good bye backup scripts :)

I tried different scenarios already and i am really satisfied with the outcome. I would like to add some feature requests or more feature suggestions for the future.

  • Delete single backups (i had the issue, that one of my backups did not work as expected (connection issues) and i wanted to delete the backup entry. The only two options i found were to remove the backup via cli or configure a new appdata path.
  • Status of current backup job (a status in the webfrontend (maybe including the process ids) would be helpful to figure out if the job is still running or if it was cancelled somehow.

In addition i noticed that when you delete the backup (by changing the appdata path) that the old backup will be moved into the admins recycle bin - maybe it would be easier to "simply" remove it instead of having it in the recycle bin.

As stated before i am really satisfied and just wanted to share some thoughts. Also if you guys need support with the Faq section i would be happy to assist :)

Thanks for this great app,
Oliver

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue proposes deleting individual backups, showing current backup status in the web frontend, and changing how removed backups reach the administrator's recycle bin. Start by tracing the existing CLI deletion flow and appdata-path removal behavior, then inspect the web frontend entry point for backup jobs. Done requires narrowing these suggestions into a scoped feature with defined behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, cli, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.