Tar over ssh
Imagine the situation where you have to recursive transfer files and directories from station A to station B. While using recursive scp (scp -r), you notice all symbolic links are transferred as normal directories, multiplying the amount of data. When I was in this situation, and googled for a solution, I found this blog post: recursive scp and symlinks.
Unfortunately, using rsync was not an option for me, because:
- rsync wasn't available on the system
- the broken file system was mounted read only (RO), thus making it impossible to
yum install rsync:-(
Luckily I noticed the comment made by "John Mitchell":
Didn't have rsync installed so I used tar over ssh
Hé, that sounds like my situation :-) He suggests using tar with ssh instead of recursive scp to transfer symlinks:
# On the source server:
tar cf - * | ssh user@destination '(cd /path/to/content; tar xf - )'
The files are compressed and piped into the ssh stream, and uncompressed to /path/to/content on the destination server.
Use the tar -p parameter if you want to preserve file permissions:
tar cfp - * | ssh user@destination '(cd /path/to/content; tar xfp - )'
The blog posts Using tar and ssh to efficiently copy files preserving permissions on meinit.nl and Howto: Use tar Command Through Network Over SSH Session on nixCraft provide more nifty tar over ssh options.
Excluding hidden files / folders in tar
You can exclude hidden files and folders in tar by using --exclude=".*" as first parameter. For example:
tar --exclude=".*" -czvf downloads.tgz Downloads/
Downloads/
Downloads/ISO
tar -czvf downloads.tgz Downloads/
Downloads/
Downloads/.secret
Downloads/ISO
Downloads/.hidden1
Want to manually install OpenSSH in Windows Server?
TL;DR: when using recursive scp, symbolic links aren't preserved and are copied as if they are normal directories. So you have to look for another solution to recursively transfer. Use tar over ssh!