Thanks for the break down and that made perfect sense. I am now testing everything between 2 servers on the LAN.
I am trying to replicate home directories from 10.1.1.24 > 10.1.1.25.
When I ran the command, It yelled at me because I would assume during the first tar command, after the "f", it wants the name or tar file you're created in the "c" tag and then a space and the path of the file you're generating the tar from.
Here was my error:
I then ran the following command with a basic generic name for the tar:
[root@lt2fs1 /]# tar -cjf home/ | ssh email@example.com tar -xpjvf - - C /
tar: Cowardly refusing to create an empty archive
Try `tar --help' for more information.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Invalid argument
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Child returned status 2
tar: -: Not found in archive
tar: C: Not found in archive
tar: /: Not found in archive
tar: Error exit delayed from previous errors
From that command it sits there forever and does not time out or do anything...
[root@lt2fs1 /]# tar -cjf home.tar.bz2 home/ | ssh firstname.lastname@example.org tar -xpjvf - - C /
Any thoughts on what I am doing wrong? I notice that in server 10.1.1.24 where I issued the command from, I have a home.tar.bz2 file under /. I don't know why SSH did not send it to 10.1.1.25 and extract it there unless I just killed the process prematurely.