Re: sync prob with big files

So you are using rsync on boxA that replicates a file mounted via CIFS on boxB to a file mounted via CIFS on boxC? How do you know this isn't a CIFS problem instead of a rsync one? Try rsyncing the file from boxB to /tmp on boxA and if that's successful, rsync it to boxC. Maybe there's a problem

Re: sync prob with big files

Hi. > It is saying that it can't chown the files because the filesystem > doesn't support ownerships. This is a drawback of using -a when not > all of the features of -a will work. I suggest swapping -a > (--archive) with -rt (--recursive and --times). That is what I did. Running my test sync w

Re: sync prob with big files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is saying that it can't chown the files because the filesystem doesn't support ownerships. This is a drawback of using -a when not all of the features of -a will work. I suggest swapping -a (--archive) with -rt (--recursive and --times). Also, di

Re: sync prob with big files

Hi list. > I gave it another try and started it after ssh to the box using this > command: > nohup ./ic_scripts/executedByCron/sync_NAS_devices.sh >> > /var/log/rsync.log 2>&1 & > > This is what I got now: > -rwxrwxrwx 1 bacula pulse157810688 Dec 9 2011 .bkp-nas-0002.Ysteoo > > This must b

Re: sync prob with big files

Original - Text > What is renaming the file? Your rsync command line implies that you > are syncing directories. That means the file names should be the > same. That is not the format of rsync's temporary file names. I gave it another try and started it after ssh to the box u

Re: sync prob with big files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --checksum is almost never the right thing. In almost all cases it is faster to simply re-copy stuff than it is to checksum it. In this case with both source and target being a network mount a re-copy would mean a read and a write. A --checksum wo

Re: sync prob with big files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/09/11 10:18, fuzzy_4711 wrote: > Thanks again for your time. > >> What is renaming the file? Your rsync command line implies that >> you are syncing directories. That means the file names should be >> the same. That is not the format of rsync

Re: sync prob with big files

fuzzy_4711 schrieb: Hi list. rsync --omit-dir-times --size-only -avzAX \ --bwlimit=$KILOBYTES_PER_SECOND --devices --specials --numeric-ids \ --delete $BACULA_BACKUP_DIR $MOUNT_DIR/$SYNC_DIR I miss -c (or --checksum) there. You never know whether the filesize changed, or whether the time is co

Re: sync prob with big files

Thanks again for your time. > What is renaming the file? Your rsync command line implies that you > are syncing directories. That means the file names should be the > same. That is not the format of rsync's temporary file names. What is the conclusion, if this is not rysnc's temp file name? Do

Re: sync prob with big files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/09/11 05:23, fuzzy_4711 wrote: > Thank you very much for your help. > > I still get an error, even I changed the script according to your > suggestions. Thanks for that. This is what I got. > > At the device to read from I have this file which

RE: sync prob with big files

fuzzy_4711 wrote: > At the device to read from I have this file which should be synced to > the target: > -rwxrwxrwx 1 bacula pulse 128497545778 Nov 3 13:19 bkp-nas-0002 > > At the device where the file should have been written, I got this: > -rwxrwxrwx 1 bacula pulse 128497545778 Dec 9 01:28 c

Re: sync prob with big files

Thank you very much for your help. I still get an error, even I changed the script according to your suggestions. Thanks for that. This is what I got. At the device to read from I have this file which should be synced to the target: -rwxrwxrwx 1 bacula pulse 128497545778 Nov 3 13:19 bkp-nas-0002

Re: sync prob with big files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, several things here 1. according to the man page error code 1 is a syntax error meaning it is simply failing to run. Try expanding those variables to make sure they are coming out the way you think they are. Also, capture any error that rsyn

sync prob with big files

Hi list. We have 2 NAS-Devices, each mounted on the same (virtual) box. For our backup we use bacula. Bacula ist writing its files to the first NAS (192.168.1.9). These are big files, up to 160 GB. For implementing a good backup strategy we decided to mirror (sync) another NAS-Device (192.168.1.8