On 01/13/2013 12:30 AM, Gordon Messmer wrote:
> If you want to make a backup that's consistent across a filesystem, you
> need to make a snapshot, mount it, and back up the snapshot content. If
> there are files open for writing, you need to make them consistent while
> the snapshot is made. Whil
On Fri, 18 Jan 2013 at 08:07 -, SilverTip257 wrote:
> If you change a directory name, rsync has no way of knowing that you
> moved it. And since the new directory doesn't exist on the rsync
> source that new directory is removed and those items are rsynced
> again.
>
> Bottom-line: Change th
On 01/19/2013 01:21 PM, John Hinton wrote:
> On 1/19/2013 1:28 PM, Nicolas Thierry-Mieg wrote:
>> See man rsync:
>> Rsync finds files that need to be transferred using a “quick check”
>> algorithm (by default) that looks for files that have changed in size or
>> in last-modified time.
>>
>> and y
On 01/19/2013 11:31 AM, Nicolas Thierry-Mieg wrote:
> agreed, except if both source and dest are local, eg back up to a USB
> HD. If you test that you'll see the speedup is 1 (ie no speedup)
That makes sense because it would take longer to locally checksum both
files and then make a difference b
On Sat, Jan 19, 2013 at 1:53 PM, Gordon Messmer wrote:
> On 01/19/2013 11:31 AM, Nicolas Thierry-Mieg wrote:
>> agreed, except if both source and dest are local, eg back up to a USB
>> HD. If you test that you'll see the speedup is 1 (ie no speedup).
>
> I actually never realized that. Thanks.
I
On 01/19/2013 11:21 AM, John Hinton wrote:
> Yet size only is not reliable. If for instance you have a simple text
> file with the word hellO and someone catches the typo and changes it to
> hello, the filesize doesn't change as near as I can see.
Right. -c is a better option, unless you're tryin
On 01/19/2013 11:31 AM, Nicolas Thierry-Mieg wrote:
> agreed, except if both source and dest are local, eg back up to a USB
> HD. If you test that you'll see the speedup is 1 (ie no speedup).
I actually never realized that. Thanks.
___
CentOS mailing li
Gordon Messmer wrote:
> On 01/19/2013 10:28 AM, Nicolas Thierry-Mieg wrote:
>> Not true: if you change the modification time on a file, by default
>> rsync will copy the whole file again
>
> rsync uses an efficient algorithm to compare file contents and transfer
> only the differences. Reindl was
Reindl Harald wrote:
>
>
> Am 19.01.2013 19:28, schrieb Nicolas Thierry-Mieg:
no I don't think you will, since the file modification times won't have
changed.
>>>
>>> and even if the did - who cares?
>>>
>>> * rsync does not transfer unchanged data ever
>>> * rsync will sync the times to
On 1/19/2013 1:28 PM, Nicolas Thierry-Mieg wrote:
> Reindl Harald wrote:
>>
>> Am 19.01.2013 15:46, schrieb Nicolas Thierry-Mieg:
>>> M. Fioretti wrote:
On Fri, Jan 18, 2013 08:07:40 AM -0500, SilverTip257 wrote:
> if you really want to eliminate that data being transferred, I
> suppos
On 01/19/2013 10:28 AM, Nicolas Thierry-Mieg wrote:
> Not true: if you change the modification time on a file, by default
> rsync will copy the whole file again
rsync uses an efficient algorithm to compare file contents and transfer
only the differences. Reindl was correct. rsync will use very
Reindl Harald wrote:
>
>
> Am 19.01.2013 15:46, schrieb Nicolas Thierry-Mieg:
>> M. Fioretti wrote:
>>> On Fri, Jan 18, 2013 08:07:40 AM -0500, SilverTip257 wrote:
if you really want to eliminate that data being transferred, I
suppose you could do the extra work and rename the directory a
M. Fioretti wrote:
> On Fri, Jan 18, 2013 08:07:40 AM -0500, SilverTip257 wrote:
>> if you really want to eliminate that data being transferred, I
>> suppose you could do the extra work and rename the directory at the
>> same time on the source and destination. Not ideal in the least.
>
> Not idea
On Fri, Jan 18, 2013 08:07:40 AM -0500, SilverTip257 wrote:
> Yes, that's the way it works. If you change a directory name, rsync
> has no way of knowing that you moved it.
I was almost sure that this was the case, but it didn't hurt to ask
for confirmation. Thanks to you, Reindl and all the oth
On Fri, Jan 18, 2013 at 11:53 AM, Gordon Messmer wrote:
> On 01/18/2013 01:59 AM, M. Fioretti wrote:
>> even if all the "rsyncing" needed would be something equivalent to "mv
>> holidays_2013 family_holidays_2013" on the remote server. Is it
>> possible to tell rsync to behave in that way?
>
> No,
On 01/18/2013 01:59 AM, M. Fioretti wrote:
> even if all the "rsyncing" needed would be something equivalent to "mv
> holidays_2013 family_holidays_2013" on the remote server. Is it
> possible to tell rsync to behave in that way?
No, which is why some people use Mercurial or git to keep data in sy
On Fri, Jan 18, 2013 at 5:25 AM, keshab mahapatra wrote:
> rsync -v -d root@192.168.200.10:/var/lib/ .
>
> Use rsync -d option to synchronize only directory tree from source to
> the destination. The below example, synchronize only directory tree in
> recursive manner, not the files in the directo
On Fri, Jan 18, 2013 at 4:59 AM, M. Fioretti wrote:
> On Fri, Jan 11, 2013 12:29:48 PM -0500, ken wrote:
>
> > Considering using rsync on a couple systems for backup, I was
> > wondering if it's possible, and if so how difficult is it...
>
> sorry to step in so late, but I have another question o
rsync -v -d root@192.168.200.10:/var/lib/ .
Use rsync -d option to synchronize only directory tree from source to
the destination. The below example, synchronize only directory tree in
recursive manner, not the files in the directories
--
With Thanks & Regards,
Keshaba Mahapatra
Technical C
On Fri, Jan 11, 2013 12:29:48 PM -0500, ken wrote:
> Considering using rsync on a couple systems for backup, I was
> wondering if it's possible, and if so how difficult is it...
sorry to step in so late, but I have another question on this very topic.
I have noticed that if I just _change_ the n
On 01/13/2013 02:59 AM, Reindl Harald wrote:
>> There is no common
>> >mechanism for making files and databases consistent and making a
>> >snapshot for backups. Admins must do this on their own. If you aren't
>> >actively taking steps to make your backups consistent, they aren't.
> open-vm-tools
On 01/11/2013 02:05 PM, m.r...@5-cent.us wrote:
> A hard link isn't easy: it's an inode that is referenced by more than one
> other inode.
Don't make it complicated. All regular files are hard links to an
inode. The inode contains information about the owner, group,
permissions, and modificati
On 01/11/2013 01:47 PM, ken wrote:
> Cool. Thanks for mentioning time-stamps. I've been assuming that rsync
> would maintain the source files' original permissions and timestamps.
It will if you specify -t/--times and -p/--perms (or -a, which implies
both).
> It's good to hear too that I can c
On 01/11/2013 01:37 PM, ken wrote:
>From what I've read, rsync will work in the background and just fine
> while users (and several system processes) are copying, deleting,
> editing and other things which would confuse tar.
No, it doesn't. rsync does not have any magic powder for making or
On Fri, Jan 11, 2013 at 10:26 PM, Keith Keller <
kkel...@wombat.san-francisco.ca.us> wrote:
> On 2013-01-12, SilverTip257 wrote:
> > You mentioned about it running with other people changing files ... it
> > works ok for me. I have gigabytes of backups that get rsynced in the
> early
> > to late
On 2013-01-12, SilverTip257 wrote:
> You mentioned about it running with other people changing files ... it
> works ok for me. I have gigabytes of backups that get rsynced in the early
> to late morning ... not always are backups completely finished when rsync
> scans the files. So it picks up o
On Fri, Jan 11, 2013 at 1:53 PM, ken wrote:
>
> If I delete files and entire directories on that (source) machine, will
> rsync then subsequently automatically delete them on the destination
>
Not automatically without the --delete flag as others have mentioned.
You delete on the source and with
On Fri, Jan 11, 2013 at 4:34 PM, wrote:
>
> At any rate, the point is that the hard links point to *exactly* the same
> file on the disk, so it *looks* as though they take up equal space, but in
> reality, there's only one copy.
>
> So, if you're copying a directory to a timestamped named directo
Les Mikesell wrote:
> On Fri, Jan 11, 2013 at 4:05 PM, wrote:
>>>
>>> Mark, maybe you could explain what a "parm" is and how using hard links
>>> saves space.
>>
>> A hard link isn't easy: it's an inode that is referenced by more than
>> one other inode. In effect, it's a pointer, rather than a r
On Fri, Jan 11, 2013 at 4:05 PM, wrote:
>>
>> Mark, maybe you could explain what a "parm" is and how using hard links
>> saves space.
>
> A hard link isn't easy: it's an inode that is referenced by more than one
> other inode. In effect, it's a pointer, rather than a reference, so that
> it reall
ken wrote:
> On 01/11/2013 02:33 PM m.r...@5-cent.us wrote:
>> ken wrote:
>>> On 01/11/2013 12:36 PM Les Mikesell wrote:
On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
> Considering using rsync on a couple systems for backup, I was
> wondering if it's possible, and if so how difficult
On 01/11/2013 02:33 PM m.r...@5-cent.us wrote:
> ken wrote:
>> On 01/11/2013 12:36 PM Les Mikesell wrote:
>>> On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
Considering using rsync on a couple systems for backup, I was wondering
if it's possible, and if so how difficult is it, to delete f
On 01/11/2013 12:54 PM zGreenfelder wrote:
> On Fri, Jan 11, 2013 at 12:29 PM, ken wrote:
>> Considering using rsync on a couple systems for backup, I was wondering
>> if it's possible, and if so how difficult is it, to delete files which
>> have been backed up (in order to save space on the backu
On Fri, Jan 11, 2013 at 12:53 PM, ken wrote:
>
> Les, thanks for replying. Yeah, I guess I need to clarify.
>
> I've got a system which is due for an upgrade and, at the same time,
> would like to clean up (delete) files and, in some instances, entire
> directories. Insurance against sudden disk
ken wrote:
> On 01/11/2013 12:36 PM Les Mikesell wrote:
>> On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
>>> Considering using rsync on a couple systems for backup, I was wondering
>>> if it's possible, and if so how difficult is it, to delete files which
>>> have been backed up (in order to save s
Am 11.01.2013 um 19:53 schrieb ken:
> On 01/11/2013 12:36 PM Les Mikesell wrote:
>> On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
>>> Considering using rsync on a couple systems for backup, I was wondering
>>> if it's possible, and if so how difficult is it, to delete files which
>>> have been back
On 01/11/2013 12:36 PM Les Mikesell wrote:
> On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
>> Considering using rsync on a couple systems for backup, I was wondering
>> if it's possible, and if so how difficult is it, to delete files which
>> have been backed up (in order to save space on the backu
Am 11.01.2013 um 19:29 schrieb Les Mikesell:
> On Fri, Jan 11, 2013 at 11:54 AM, zGreenfelder wrote:
>> On Fri, Jan 11, 2013 at 12:29 PM, ken wrote:
>>> Considering using rsync on a couple systems for backup, I was wondering
>>> if it's possible, and if so how difficult is it, to delete files whi
On Fri, Jan 11, 2013 at 11:54 AM, zGreenfelder wrote:
> On Fri, Jan 11, 2013 at 12:29 PM, ken wrote:
>> Considering using rsync on a couple systems for backup, I was wondering
>> if it's possible, and if so how difficult is it, to delete files which
>> have been backed up (in order to save space
On Fri, Jan 11, 2013 at 12:29 PM, ken wrote:
> Considering using rsync on a couple systems for backup, I was wondering
> if it's possible, and if so how difficult is it, to delete files which
> have been backed up (in order to save space on the backup media).
>
> Anyone with experience doing this?
On Jan 11, 2013, at 10:29 AM, ken wrote:
> Considering using rsync on a couple systems for backup, I was wondering
> if it's possible, and if so how difficult is it, to delete files which
> have been backed up (in order to save space on the backup media).
>
> Anyone with experience doing this?
On Fri, Jan 11, 2013 at 11:29 AM, ken wrote:
> Considering using rsync on a couple systems for backup, I was wondering
> if it's possible, and if so how difficult is it, to delete files which
> have been backed up (in order to save space on the backup media).
>
> Anyone with experience doing this?
Considering using rsync on a couple systems for backup, I was wondering
if it's possible, and if so how difficult is it, to delete files which
have been backed up (in order to save space on the backup media).
Anyone with experience doing this?
___
Cen
43 matches
Mail list logo
