Skip to content
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

backup restore content revision #1330

Closed
wants to merge 2 commits into from
Closed

backup restore content revision #1330

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d2c3715
backup restore content revision
rsajwani Jan 3, 2023
aa32adc
code review
rsajwani Jan 26, 2023
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
27 changes: 10 additions & 17 deletions content/en/docs/16.0/user-guides/operating-vitess/backup-and-restore/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,28 +76,21 @@ All three programs can be made aware of Backup Engine and Backup Storage using t
</ul>
</td>
</tr>
<tr>
<td><code>backup_storage_hook</code></td>
<td>If set, the content of every file to backup is sent to a hook. The
hook receives the data for each file on stdin. It should echo the
transformed data to stdout. Anything the hook prints to stderr will
be printed in the vttablet logs.<br>
Hooks should be located in the <code>vthook</code> subdirectory of the
<code>VTROOT</code> directory.<br>
The hook receives a <code>-operation write</code> or a
<code>-operation read</code> parameter depending on the direction
of the data processing. For instance, <code>write</code> would be for
encryption, and <code>read</code> would be for decryption.</br>
</td>
</tr>
<tr>
<td><code>backup_storage_compress</code></td>
<td>This flag controls if the backups are compressed by the Vitess code.
By default it is set to true. Use
<code>--backup_storage_compress=false</code> to disable.</br>
This is meant to be used with a <code>--backup_storage_hook</code>
hook that already compresses the data, to avoid compressing the data
twice.
</td>
</tr>
<tr>
<td><code>backup_storage_block_size</code></td>
<td>If <code>--backup_storage_compress</code> is true, <code>backup_storage_block_size</code> sets the byte size for each block while compressing (default is 250000).
</td>
</tr>
<tr>
<td><code>backup_storage_number_blocks</code></td>
<td>If <code>--backup_storage_compress</code> is true, <code>backup_storage_number_blocks</code> sets the number of blocks that can be processed, at once, before the writer blocks, during compression. It should be equal to the number of CPUs available for compression. (default 2)
</td>
</tr>
<td><code>compression-level</code></td>
Expand Down