Skip to content

Potential fixes for 3 code quality findings #4734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
mykaul wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Potential fixes for 3 code quality findings #4734

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7978701
Apply suggested fix to docs/source/backup/native-backup.rst from Copi…
mykaul Jan 14, 2026
a06f9f7
Apply suggested fix to docs/source/backup/native-backup.rst from Copi…
mykaul Jan 14, 2026
b10bc9c
Apply suggested fix to docs/source/backup/native-backup.rst from Copi…
mykaul Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/source/backup/native-backup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Native Backup
=============

ScyllaDB Manager uses ScyllaDB Manager Agents deployed on each ScyllaDB node to coordinate backups.
Those agents serve as a proxy to `ScyllaDB REST API <https://docs.scylladb.com/manual/stable/operating-scylla/rest.html>`_, but they also act as `rclone <https://github.com/scylladb/rclone>`_ servers responsible for communication between the node and backup location.
These agents serve as a proxy to `ScyllaDB REST API <https://docs.scylladb.com/manual/stable/operating-scylla/rest.html>`_ and also act as `rclone <https://github.com/scylladb/rclone>`_ servers responsible for communication between the node and backup location.

Since rclone server is separate from ScyllaDB internal schedulers, yet they both live on the same machine,
it is allocated with limited resources not to interfere with ScyllaDB performance.
Expand All @@ -15,7 +15,7 @@ This solution results in:
* Increased disk storage utilization (snapshots are stored on disk for a longer time)

Native backup aims to solve these problems by moving backup responsibilities from rclone server into ScyllaDB itself.
It's important to note that both native and rclone backups performed by ScyllaDB Manager have the same :doc:`specification <specification>` consisting of backup directory layout, manifest, schema and SSTable files. This means that all backups can be used for all types of restores (e.g. regular restore, 1-1-restore, native restore, ...).
It is important to note that both native and rclone backups performed by ScyllaDB Manager have the same :doc:`specification <specification>` consisting of backup directory layout, manifest, schema and SSTable files. This means that all backups can be used for all types of restores (e.g. regular restore, 1-1-restore, native restore, ...).
In the `Status`_ section you can find the parts of backup procedure already moved to ScyllaDB.

Status
Expand Down Expand Up @@ -86,7 +86,7 @@ Usage
=====

The native backup usage is controlled with the :ref:`sctool backup --method <sctool-backup>` flag.
It supports three values: ``rclone (default)``, ``native``, and ``auto``:
It supports three values: ``rclone`` (default), ``native``, and ``auto``:

* ``native``: Uses all native backup functionalities listed in `Status`_ section.
Use this value for native backup configuration validation and testing.
Expand Down
Loading