Re: Running rsync with sudo ?
This won't be the case if you back up daily, which, I gather, is the point with rsync running as a cron job.
Originally Posted by cogset
You may wish to exclude VMs from your rsync backups altogether and use a different backup strategy for them. The reason for this is that VMs are basically one big file, so even the act of just booting them up, without any changes to the VM OS itself counts as a "changed" file to rsync. I run close to 2 dozen VMs (I like to tinker), so cannot possibly include them in scheduled backups without going crazy. VMs that can be easily reinstalled (Linux, BSD, Unix) are non-issues so I don't back them up. My Windows VMs are backed up manually once every six months. The contents within are backed up much more frequently on a schedule, but using Windows backup software to an external file server. This way, I keep daily rsync backup volume to tiny little nibbles.
...that is excluding some virtual machines that I have installed,because I've found that those take ages.
I find that this depends a lot on HW. On old HW, backing up while other programs are running tends to slow the system to a crawl and I get the same fears that you get. On my newer and far more powerful systems though, the backup process is hardly noticeable even when I am running VMs etc. so I don't worry about multitasking. It's true that you may have some files locked and therefore not backed up, but the nice thing about a daily cron backup is that those files get picked up the next day, so there is really very little exposure. In short, only you can decide what your comfort level is, but in theory, there isn't much that can go wrong if you continue working while rsync is running.
...do you people still use your computer whilst a backup process is running? Is that safe?
Newb: How far must I jump to clear the ledge halfway down?
Guru: It's bad to jump off cliffs. Let's look at better options.
Newb: Stop harping about "best practices" and just let me jump.