Hey #rsync experts! I have a large (100GB) Veracrypt partition that I often mount but rarely make changes to. However, it seems like the mere act of mounting this partition changes its mod date, such that rsync wants to recopy it, which takes a long time. How do I avoid this? I don't want to just ignore that file (because I do *sometimes* mod it). Nor do I want to back up its contents in the clear on the backup drive (I want to back up the encrypted partition blob). Ideas?

Hey #rsync experts! I have a large (100GB) Veracrypt partition that I often mount but rarely make changes to. However, it seems like the mere act of mounting this partition changes its mod date, such that rsync wants to recopy it, which takes a long time. How do I avoid this? I don't want to just ignore that file (because I do *sometimes* mod it). Nor do I want to back up its contents in the clear on the backup drive (I want to back up the encrypted partition blob). Ideas?

@willhbr I'm a sucker for GNU #parallel, so I use it for that kind of use cases:

parallel -j 3 --eta rsync -a {} destination/ Downloads/*

#rclone is fine, but I don't like to have duplicate tools and I'm very fond to #rsync

After a couple of days of sysadmin work, I've got rid of Kamal and #Docker. I can now deploy @brinjel with zero downtime thanks to #Ansible, #Caddy, #systemd and #rsync.

Simplifying your stack and making your infra more robust at the time, that's the way!

#myElixirStatus #elixirlang #buildInPublic #indiehackers

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?

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?

Added 𝗨𝗣𝗗𝗔𝗧𝗘 𝟮 - 𝗜𝗻𝘁𝗲𝗿𝗶𝗺 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 [UPDATE 2 - Interim Solution] to 𝗙𝗮𝗶𝗹𝗲𝗱 𝗕𝗮𝗰𝗸𝘂𝗽 𝗦𝗲𝗿𝘃𝗲𝗿 𝗕𝘂𝗶𝗹𝗱 [Failed Backup Server Build] article.

https://vermaden.wordpress.com/2025/05/28/failed-backup-server-build/#interim

#verblog #freebsd #hardware #backup #NAS #rsync #linux #zfs #openzfs