Hot answers tagged

5

A simple filter should do the trick. To build on the prior answer with a proper example -- Explicitly include the parent(s), plus all (**) sub folders and files. Then exclude everything else. Here's filter.txt: + /include_this_dir/ + /include_this_dir/** + /include_that_dir/ + /include_that_dir/** - /** With the command line: rsync -av --dry-run --filter=...


1

As the various backup dirs only contain the changed files by the last current backup, the restore procedure is somewhat complex: you need to restore the current full backup and re-apply the various file-level backup, up to the required (past) date. Can I suggest you a better backup method? Please use the --link-dest option combined with proper rotation. ...


1

What I did once: Implement 2 VPNs or IP Tunnels over each link and use the Linux bonding capabilities to glue them together. I did it with OpenVPN, via UDP and extremely fast encryption. You will not need 2 rsyncs this way, you will get a faster, single one. To speed it up, use very powerful compression and a protocol with less overhead than SSH, maybe ...


1

In short, this is not the correct command... $ rsync -av ./2016-07-01 user@server:./path-to-project/2016-07-01 This is the correct command... $ rsync -av ./2016-07-01 user@server:./path-to-project Note, no forward slash or directory name for destination - when these are left off rsync will create the directory as required. I think the / and 2016-07-01 ...


1

You missed one possibly vital argument to rsync: --hard-links. It depends on the distribution, and I guess it's different now than it is in the past, but system directories and/or files (more so than user files) can easily be hard links to others. For example, in the somewhat recent past on Archlinux, /usr/X11R6/bin was a hard-link to /usr/bin. At present, I ...


1

The error arise from the fact you are trying to sync into a directory which does not exist on the remote side. You have the following possibilities: first create the dir on the target directory issuing mkdir /mnt/myDir/var/www/dms/test (on the remote side), then issue your rsync command elaborating on that, if you need to transfer the entire /var/www ...


1

This won't quite work. The special directories such as /dev and /proc wont get created properly on the second disk. You also won't get the Master Boot Record from the disk and so HDD2 won't be bootable by default. If you start by using dd to clone the disk, and then make updates to it with rsync as more things are installed or updated you might have more ...



Only top voted, non community-wiki answers of a minimum length are eligible