Hey #rsync experts!
-
Hey #rsync experts! I have a dilemma. I do a daily backup to an external disk, but some of the files (VM containers) are HUGE (100GB), and because they are zero-padded, their size is always the same. By the time the rsync for these files finishes, they have wildly different mod dates from the originals on my HDD. I can set --modify-wiindow to $BIGNUM, but then all the regular files *don't* back up.
Maybe the answer is to touch all the big files (originals and backup) at the end of the rsync?
-
undefined Evan Prodromou ha condiviso questa discussione
-
Hey #rsync experts! I have a dilemma. I do a daily backup to an external disk, but some of the files (VM containers) are HUGE (100GB), and because they are zero-padded, their size is always the same. By the time the rsync for these files finishes, they have wildly different mod dates from the originals on my HDD. I can set --modify-wiindow to $BIGNUM, but then all the regular files *don't* back up.
Maybe the answer is to touch all the big files (originals and backup) at the end of the rsync?
@pluralistic excluding these big files and setting up a separate run of your backup script with them is (not) an option?
-
Hey #rsync experts! I have a dilemma. I do a daily backup to an external disk, but some of the files (VM containers) are HUGE (100GB), and because they are zero-padded, their size is always the same. By the time the rsync for these files finishes, they have wildly different mod dates from the originals on my HDD. I can set --modify-wiindow to $BIGNUM, but then all the regular files *don't* back up.
Maybe the answer is to touch all the big files (originals and backup) at the end of the rsync?
@pluralistic I am not an expert, and I personally hate it when I ask a question and people answer a different question, BUT I'm going to do that anyway:
Could you mount the VM container image(s) on source and destination and rsync their filesystems separately?
-
undefined Oblomov ha condiviso questa discussione