New answers tagged

0

As the various backup dirs only contain the changed files by the last current backup, the restore procedure is somewhat complex: you need to restore the current full backup and re-apply the various file-level backup, up to the required (past) date. Can I suggest you a better backup method? Please use the --link-dest option combined with proper rotation. ...


1

The error arise from the fact you are trying to sync into a directory which does not exist on the remote side. You have the following possibilities: first create the dir on the target directory issuing mkdir /mnt/myDir/var/www/dms/test (on the remote side), then issue your rsync command elaborating on that, if you need to transfer the entire /var/www ...


-1

iISCSI it is, thanks Michal! I appreciate the follow up


0

Daemon is on your source machine, you have only server configured on this one. Then, all destination machines will sync with him.


0

Your rsync job is not preserving owner/group information. Please add the -a parameter to your rsync command (eg: using rsync -av <src> <dst>)


0

@Cicero can u show the cmd that u r using on client & file permission on server side. Generally this error comes when destination host or file path is not correct. check Ques3 here if it helps I don't have reputation to comment so replying through Answer.


1

As an alternative, consider putting the folder under version control with SVN (if it's a lot of binary files, I recommend against Git). SVN has a lot of advantages over rsync and a few downsides: SVN handles binary files very well, sending only compressed deltas across the wire Everything is versioned, so accidental deletes can be undone Very efficient ...


0

Syntax is correct, you can add "--delete" to remove what's is not wanted anymore. Best choice for making this cool : make 2 scripts (from-remote-to-local and from-local-to-remote), on each machine.If you use periodic updates like in a crontab, you might sync with unwanted data, so, be careful with that ;-) You can also setup an 'rsync' daemon on a third ...


1

As has already been noted rsync can be used to make your backups. If you already have a backup, rsync can be used to apply the incremental changes. It also has features to save changes so you have historical backups using the --backup and related flags. There are a number of backup solutions built on top of the rsync protocol designed to keep historical ...


1

I have found the problem. From server 1 I was using scp /storage/somefile root@server2domain:/storage instead of using the ip. The weird thing is that it worked for over 6 months and it stopped working yesterday out of the blue.


3

Sure. You can use something similar to: rsync -av --delete <src> <dst> to replicate src to dst. The first copy will be slow (all data must be copied), but successive ones will be much faster (only modified/added files will be copied). Using the --delete switch tell rsync to delete files which are not in src anymore; using it, you should be ...


1

When you say "mainly 15Mb tarballs", how many smaller files are there? Do you see the slow rate constantly or does it look faster on the larger files? rsync (and almost any other filesystem operation) is slower at processing many small files rather than fewer large ones due to the filesystem overhead of opening and closing each file (and any directory read/...



Top 50 recent answers are included