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.

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 Duration #38

Closed
Slind14 opened this issue Jul 9, 2019 · 2 comments
Closed

Backup Duration #38

Slind14 opened this issue Jul 9, 2019 · 2 comments
Labels

Comments

@Slind14
Copy link

Slind14 commented Jul 9, 2019

I'm curious how does AWS work for you?
It takes half a day for every TB of data.
Am I missing something?

@sjoerdmulder
Copy link

Have the same issue; using compression_format: tar helps for me since clickhouse data is already highly compressed you don't really need to compress it. Makes it 3 times as fast for me;

@AlexAkulov AlexAkulov added the help wanted Extra attention is needed label Sep 23, 2019
@AlexAkulov
Copy link
Collaborator

Hi, @Slind14!

  1. Not everyone have databases of several terabytes. My database size is 220GiB, full backup is uploaded for 2h47m and increments are uploaded for ~6m. v0.4.1 has good performance improvements such as non-blocking pipes and multi-threading gzip support that reduces uploading of full backup of my database to 1h10m and increments to ~2m (after switching from lz4 to gzip).

  2. Upload to s3 is optional feature protecting you from hardware failures. If you want to defend yourself only from destructive operations like DROP DATABASE or ALTER TABLE you may just create periodical backups with clickhouse-backup create keep it local and not put to cloud.

  3. If you have large database and want to be protected from hardware or whole DC failure you may create instance of ClickHouse on another DC and have it fresh by clickhouse-copier combined with periodical backups that will be stored locally for protection from destructive operations.

@AlexAkulov AlexAkulov added FAQ and removed help wanted Extra attention is needed labels Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants