Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FWIW, the one time I had corruption in my backups the problem was a bad DIMM randomly flipping bits. I now insist on ECC RAM. On 03/07/2016 03:51 PM, Henri Shustak wrote: > Just chiming in slightly off topic. > > As a first step if you are going to

Re: Verifying backups

Just chiming in slightly off topic. As a first step if you are going to be backing up files to some media with a computer it would be a really good idea to ensure, that the hardware being used is not faulty. I am not saying that your hardware is faulty. However, it would be worth checking this

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yes, when it comes to local copies cp is significantly faster than rsync. Without --link-dest there isn't much advantage to using rsync for backups. The only thing you get beyond cp -au is --delete. Also, when it comes to static data like media

Re: Verifying backups

In message <560cca51.5cwvptqce1nflu+u%per...@pluto.rain.com>, per...@pluto.rain.com (Perry Hutchison) wrote: >Just because rsync is an awesome hammer, it does not necessarily follow >that every problem involving backups closely resembles a nail :) An excellent and very apropos point. >Since

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (GNU) cp -au is exactly equal to rsync -au. It won't copy files that are already up to date. It just doesn't have an equivalence to - --delete. Therefore, when doing local copies it is often faster to do a cp -au followed by an rsync --delete so

Re: Verifying backups

In message <560ce706@sanitarium.net>, Kevin Korb wrote: >Yes, when it comes to local copies cp is significantly faster than >rsync. Without --link-dest there isn't much advantage to using rsync >for backups. The only thing you get beyond cp -au is --delete. I just

Re: Verifying backups

"Ronald F. Guilmette" wrote: > P.S. I really do hope that I can get this to work with rsync. > I do prefer not reinventing the wheel, but it is starting to seem > simpler to me if I were to just write a Perl script that would > walk two directory hierarchies, in

Re: Verifying backups

In message <560c4a51.4040...@sanitarium.net>, Kevin Korb wrote: >First off, --fileflags --force-change are not in my man rsync so I >don't know what those are. These are probably (Free)BSD specific. Here's what the man page says: --fileflags preserve

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reply inline... On 09/30/2015 05:18 PM, Ronald F. Guilmette wrote: > > In message <560c4a51.4040...@sanitarium.net>, Kevin Korb > wrote: > >> First off, --fileflags --force-change are not in my man rsync so >> I don't know

Verifying backups

For some time now I've been using rsync on FreeBSD to make my system backups. Recently, I accidentally rm'd some files from one directory and I had to go and fetch copies off of my backup drive. After I had done so, I found that about 1/5 of them were corrupted. (They were all .jpg files, by

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First off, --fileflags --force-change are not in my man rsync so I don't know what those are. Second, you should look into using either ZFS subvolume snapshots or rsync --link-dest to maintain multiple backups. Now, for your actual question... Add

Re: Verifying backups

In message <560c7e98.3090...@sanitarium.net>, Kevin Korb wrote: >Remove the -n and look at the results. You would be copying the one >dir into the two dir instead of copying the contents of the one dir >into the two dir. AHHH! OK. Yes. My bad. I keep on

Re: Verifying backups

Kevin Korb , I thank you greatly for your attempts to educate me, however as we get deeper into discussing more and more different rsync options, I feel that I am actually just getting more confused and frustrated. I've been sitting here, trying all sorts of different

Re: Verifying backups

In message <560c660f.5000...@sanitarium.net>, Kevin Korb wrote: >Just add --itemize-changes and --checksum to what you were doing >before and know that it will take a long time. I'm still not getting to where I need to be. Maybe you can explain what has gone wrong in

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Remove the -n and look at the results. You would be copying the one dir into the two dir instead of copying the contents of the one dir into the two dir. On 09/30/2015 08:28 PM, Ronald F. Guilmette wrote: > > In message

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because you are making two/one. Change to: rsync -n -v --itemize-changes -checksum -a one/ two/ On 09/30/2015 07:22 PM, Ronald F. Guilmette wrote: > rsync -n -v --itemize-changes -checksum -a one two - --

Re: Verifying backups

In message <560c79ff.5010...@sanitarium.net>, Kevin Korb wrote: >Because you are making two/one. Change to: >rsync -n -v --itemize-changes -checksum -a one/ two/ OK, I tried it with your suggested command line, and yes, that produces rather more substantially useful

Re: Verifying backups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just add --itemize-changes and --checksum to what you were doing before and know that it will take a long time. On 09/30/2015 06:42 PM, Ronald F. Guilmette wrote: > > Kevin Korb , > > I thank you greatly for your attempts to