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

Feature request: Disable tarring before uploading to Storage #662

Closed
dhampik opened this issue May 6, 2015 · 8 comments
Closed

Feature request: Disable tarring before uploading to Storage #662

dhampik opened this issue May 6, 2015 · 8 comments

Comments

@dhampik
Copy link

dhampik commented May 6, 2015

I'd like to refer issue #255 and request that feature again with little more explanation why it is good.

I suppose that when we have separate files for db backups and different folder is way much better rather than having a single tar file or even tar splitted in chunks. That is because in case if nework connection will fail or external storage will get out of space or something else, it is more likely to be able to have at least part of data backed up with possibility ot be easily restored.
In case of tar splitted in chunks it'll probably be harder to restore it in case when one of the chunks got lost or not all chunks were properly uploaded to external storage (is it possible at all to restore it in that case???).

Taking into account the fact that backups could usually be pretty big in size, it makes it even more significant not to upload all the data in a single file, but have it splitted into a separate self-containing archives (not chunks) which could be restored separetly.

@tombruijn
Copy link
Member

Already suggested on the Feature issue tracker here backup/backup-features#25

It's accepted and implemented in the next major version.

@tombruijn
Copy link
Member

Tiny addition: We're not disabling tarring/compressing for most things. Unless no compressor is configured for the entire backup. So it's either compress everything or nothing.

Sources (databases, files, etc) will be in separate archives when being backed up, so no more big archives.

@dhampik
Copy link
Author

dhampik commented May 6, 2015

Awesome! Thanks for info. You are doing a great thing!

@amerkay
Copy link

amerkay commented May 8, 2015

+1 for skipping tar + gzip.

We have large DB tables that we wish they'd stay per file for easier recovery. Any work around at the moment?

@tombruijn
Copy link
Member

@amerk86 you can create a model per configuration and run them separately

@amerkay
Copy link

amerkay commented May 9, 2015

@tombruijn Any example code or discussion thread to get me started?

@tombruijn
Copy link
Member

@amerk86 not really. Just create a new model for every database/table, share parts of the config in the config.rb perhaps?

@amerkay
Copy link

amerkay commented May 15, 2015

Brain-fart! That's what I did. I misunderstood your previous comment. Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants