Settings and activity
27 results found
-
2 votes
Dominik
supported this idea
·
-
64 votes
An error occurred while saving the comment An error occurred while saving the comment Dominik
commented
Incremental backups would be great to save disk space. Currently i create a ploop snapshot, mount it and use rdiff-backup to backup all openvz VEs.
For KVM i am using lvmsync for incremental backups.
Maybe this tools gives you an inspiration.
Dominik
supported this idea
·
-
21 votesDominik
supported this idea
·
-
1 voteDominik
shared this idea
·
-
1 voteDominik
shared this idea
·
-
3 votesDominik
shared this idea
·
-
4 votesDominik
supported this idea
·
-
7 votesDominik
supported this idea
·
-
11 votesDominik
supported this idea
·
-
9 votesDominik
supported this idea
·
-
5 votesDominik
shared this idea
·
-
36 votesDominik
supported this idea
·
-
5 votesDominik
supported this idea
·
-
2 votesDominik
supported this idea
·
-
4 votesDominik
supported this idea
·
-
4 votesDominik
supported this idea
·
-
26 votes
An error occurred while saving the comment Dominik
commented
I think this should be left to the client. Too much things can go wrong when resizing the filesystem.
-
12 votesDominik
supported this idea
·
-
18 votesDominik
supported this idea
·
-
12 votesDominik
supported this idea
·
I had already written a comment on this. Meanwhile i switched to borg for OpenVZ and KVM, which just works great. Its deduplicating + compressing, so backups need almost no additional space (depending on the changes since the last backup).
What I really want to say:
If you are planning a new backup concept, please use incremental backups and, for security reasons, the backups should be pulled, not pushed.
Otherwise, the new backup system would not be better than it is now.
Another option would be to build the new backup system modularly so that developers can add their own backup systems.