Note that this does not affect the copying of symlinks or other special files. Also, a difference of file format between the sender and receiver is always considered to be important enough for an update, no matter what date is on the objects. In other words, if the source has a directory where the destination has a file, the transfer would occur regardless of the timestamps. It just limits the files that the receiver requests to be transferred.
Without this option, hard-linked files in the source are treated as though they were separate files. This option does NOT necessarily ensure that the pattern of hard links on the destination exactly matches that on the source.
Cases in which the destination may end up with extra hard links include the following: o If the destination contains extraneous hard-links more linking than what is present in the source file list , the copying algorithm will not break them explicitly.
However, if one or more of the paths have content differences, the normal file-update process will break those extra links unless you are using the --inplace option. Page content loaded. Mar 19, AM. Mar 22, AM. Communities Get Support. Sign in Sign in Sign in corporate. Browse Search. Ask a question.
Can anyone offer any arguments as to why this option should be used when making 'clones' of the system partition?
More Less. Reply I have this question too I have this question too Me too Me too. All replies Drop Down menu. Loading page content. User profile for user: MacLemon MacLemon. The advantage is that identical files in say 7 backups only occupy the space once on the drive.
That way you can keep several backups of your data and only need the space to keep them once plus the changed files. It also speeds up the backup process for subsequent incremental backups as not all the files have to be transferred. Especially if you have a few big files that don't change often this is a huge time and space saver. I haven't experimented with cloning a system via rsync and have some doubt that this will actually work out fine. I use Cabon Copy Cloner for that as most of us do.
However, make logins more restrictive, either through ssh configuration, or using an alternate shell. If the private key is obtained by an attacker, they will have free run of all the systems involved. If you are unclear on how to do this, see ssh 1 , sshd 1 , and ssh-keygen 1. Backup scripts are run as the same user that rsnapshot is running as.
Typically this is root. Make sure that all of your backup scripts are only writable by root, and that they don't call any other programs that aren't owned by root. If you fail to do this, anyone who can write to the backup script or any program it calls can fully take over the machine. Of course, this is not a situation unique to rsnapshot.
By default, rsync transfers are done using the --numeric-ids option. The assumption is that the backups will be restored in the same environment they came from. Without this option, restoring backups for multiple heterogeneous servers would be unmanageable.
If you are archiving snapshots with GNU tar, you may want to use the --numeric-owner parameter. If you remove backup points in the config file, the previously archived files under those points will permanently stay in the snapshots directory unless you remove the files yourself. Nathan Rosenquist [email protected]. David Cantrell [email protected].
Carl Wilhelm Soderstrom [email protected]. Ted Zlatanov [email protected]. Ralf van Dooren [email protected]. Carl Boe [email protected]. Shane Leibling [email protected]. Christoph Wegscheider [email protected]. Bharat Mediratta [email protected]. Peter Palfrader [email protected]. Nicolas Kaiser [email protected]. Robert Jackson [email protected]. Justin Grote [email protected]. Anthony Ettinger [email protected].
William Bear [email protected]. Eric Anderson [email protected]. Alan Batie [email protected]. Dieter Bloms [email protected].
Henning Moll [email protected]. Ben Low [email protected]. This man page is distributed under the same license as rsnapshot: the GPL see below. It can take incremental snapshots of local and remote filesystems for any number of machines. The command line options are as follows: -v verbose, show shell commands being executed -t test, show shell commands that would be executed -c path to alternate config file -x one filesystem, don't cross partitions within each backup point -q quiet, suppress non-fatal warnings -V same as -v, but with more detail -D a firehose of diagnostic information.
All parameters in this file must be separated by tabs. Default is 1. This is recursive, but you may need to be careful about paths when specifying which file to include.
We check to see if the file you have specified is readable, and will yell an error if it isn't. We recommend using a full path. Note that shell meta-characters may be interpreted. This script will run immediately before each backup operation but not any rotations. If the execution fails, rsnapshot will stop immediately. This script will run immediately after each backup operation but not any rotations. You may include options to the commands also.
The lvcreate, lvremove, mount and umount commands are required for managing snapshots of LVM volumes and are otherwise optional. A deprecated alias for 'retain' is 'interval'.
Example: retain alpha 6 retain beta 7 retain gamma 4 beta.
0コメント