New answers tagged rsync
Sven's comment to your question is definitely the right way to do it. You can do it like this: From A SSH to B, creating a tunnel on port 5000 ssh someuser@B -L 5000:127.0.0.1:5000 From that shell on B, SSH to C creating a second tunnel terminating at C's ssh server. ssh someuser@C -NL 5000:127.0.0.1:22 From a second terminal on A, rsync your files ...
I don't see the need to store anything on B, you can just use it to proxy connections between A and C using any proxy software, like ssh port forwarding or socks. Maybe you could even route/nat through B? Or, since you specifically asked, to do it your way you could use NFS/Samba to copy the files and verify completion using various methods. The one that ...
Taking the --rsyncpath option you have rsync --rsync-path="ionice -c 3 nice -n 12 rsync" localDirectory remoteHost:/tmp/ Taking the configuration file option you can change or uncomment in file /etc/default/rsync the RSYNC_NICE='17' value and the RSYNC_IONICE='-c3' value For both the ionice value will be for hard disc priority 1 -> Real time 2 -> Best ...
You can use sshpass like this: sshpass -p 'YourPasswordHere' rsync -av --delete -r -L -k -h firstname.lastname@example.org:/var/www/images /home/swayxp/test-sync/
du file is not a suitable way to measure file size. Even the very first line of the man page says « du - estimate file space usage » (my italics). Instead, use one or more of the following methods (others will also exist): ls -l file # byte size should be the same on both sides cksum file # checksum should be same result on both sides md5sum ...
clamd? It sounds like you're using ClamAV and have on-access scanning enabled where the anti-virus engine attempts to scan opened files for viruses, by loading into memory, the entire contents of every file opened by any other process. Depending on your security posture and the necessity of this transfer, you should evaluate disabling ClamAV on-access ...
A few things ... My rule of thumb for swap space has been to have at least 2x the amount of physical ram. This allows the page/swap daemon the ability to reorg memory efficiently. Server_B has 32GB of ram, so try configuring it for 64GB of swap. IMO, the 2GB of swap space your server has is way too low, especially for a server. If you don't have an ...
So let us read the oom-killer output and see what can be learned from there. When analyzing OOM killer logs, it is important to look at what triggered it. The first line of your log gives us some clues: [kernel] [1772321.850644] clamd invoked oom-killer: gfp_mask=0x84d0, order=0 order=0 is telling us how much memory is being requested. The kernel's ...
If the network connecting both servers is secure (e.g. a local network at your office) then you can use rsync in daemon mode to connect as root. This way you don't use ssh to make the connection. On the secondary system, create a file /etc/rsyncd.conf with the following contents: [all] path = / read only = no uid = 0 gid = 0 hosts allow = ...
I would not try to avoid a delete in that way. Instead, I would rsync the child folders. So to copy a and avoid touching b, I would do something like: rsync -av --delete folder1/a folder2/a Repeat for all the necessary folders.
In the exclude option, just providing b is sufficient. Could you try the following command which is working correctly for me. rsync -av --exclude b --delete folder1/ folder2/ edit: To be safe the -n option is very helpful. It does a dry run of what would be added and deleted.
Ok, I just did not added my omv user in the AllowedUsers in the B server. So, I added the line "AllowUsers root omv" in /etc/ssh/sshd_config, and now it works well. I also generated the certificate in the "Certificates" section of OpenMediaVault.
I think it makes sense to ONLY overwrite the files on the destination NAS if the source (2nd hard drive) file size is bigger. File size would typically be the same; the filesystem tracks file size and corruption won't care about file length boundaries. Should I just stop acting like an idiot and create 2 separate directories for "disk 1" and "disk ...
RAID1 is a mirror so put the drive that failed aside in a safe cool place and only copy data off the disk that didn't fail. Data should be good - unless both disks failed. In the event you find you're missing anything then I'd take both drives in for data recovery which will cost$
Top 50 recent answers are included