comando rsync [RESOLVIDO]

Novaesma
(usa Outra)

Enviado em 15/04/2020 - 11:22h

RogerDez
(usa Outra)

Enviado em 15/04/2020 - 19:32h

             Note  that  the expansion of wildcards on the commandline (*.c)

         into a list of files is handled by the shell before it runs  rsync  and

         not  by  rsync  itself  (exactly the same as all other posix-style pro-

         grams).

...

                rsync -avz foo:src/bar /data/tmp



         This would recursively transfer all files from the directory src/bar on

         the  machine foo into the /data/tmp/bar directory on the local machine.

...

                rsync -avz foo:src/bar/ /data/tmp



         A  trailing slash on the source changes this behavior to avoid creating

         an additional directory level at the destination.  You can think  of  a

         trailing / on a source as meaning "copy the contents of this directory"

         as opposed to "copy the directory by name", but in both cases  the at-

         tributes  of the containing directory are transferred to the containing

         directory on the destination.  In other words, each  of  the  following

         commands  copies  the files in the same way, including their setting of

         the attributes of /dest/foo:



                rsync -av /src/foo /dest

                rsync -av /src/foo/ /dest/foo



         Note also that host and module  references  don’t  require  a  trailing

         slash to copy the contents of the default directory.  For example, both

         of these copy the remote directory’s contents into "/dest":



                rsync -av host: /dest

                rsync -av host::module /dest

... 

rsync -ahv   .  saai@150.163.38.130:/home/saai/backups 

rsync -ahv   /caminho/completo/ate/pasta/   saai@150.163.38.130:/home/saai/backups 

         Older  versions  of rsync required using quoted spaces in the SRC, like

         these examples:



                rsync -av host:'dir1/file1 dir2/file2' /dest

                rsync host::'modname/dir1/file1 modname/dir2/file2' /dest



         This word-splitting still works (by default) in the latest  rsync,  but

         is not as easy to use as the first method.



         If  you  need  to transfer a filename that contains whitespace, you can

         either specify the --protect-args (-s) option, or you’ll need to escape

         the whitespace in a way that the remote shell will understand.  For in-

         stance:



                rsync -av host:'file\ name\ with\ spaces' /dest 

Novaesma
(usa Outra)

Enviado em 17/04/2020 - 09:01h

danniel-lara
(usa Fedora)

Enviado em 17/04/2020 - 09:08h

Novaesma
(usa Outra)

Enviado em 20/04/2020 - 09:54h

[useRME@bacurau CHPG]$ rsync -ahv . saai@150.163.38.130:/home/saai/backups

ssh: connect to host 150.163.38.130 port 22: Connection timed out

rsync: connection unexpectedly closed (0 bytes received so far) [sender]

rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2] 

danniel-lara
(usa Fedora)

Enviado em 20/04/2020 - 10:53h

[useRME@bacurau CHPG]$ rsync -ahv . saai@150.163.38.130:/home/saai/backups

ssh: connect to host 150.163.38.130 port 22: Connection timed out

rsync: connection unexpectedly closed (0 bytes received so far) [sender]

rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2] 

Novaesma
(usa Outra)

Enviado em 20/04/2020 - 11:01h

RogerDez
(usa Outra)

Enviado em 20/04/2020 - 12:25h

Novaesma
(usa Outra)

Enviado em 22/04/2020 - 09:17h

[useRME@bacurau CHPG]$ rsync -ahv . saai@150.163.38.130:/home/saai/backups

ssh: connect to host 150.163.38.130 port 22: Connection timed out

rsync: connection unexpectedly closed (0 bytes received so far) [sender]

rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2] 

danniel-lara
(usa Fedora)

Enviado em 22/04/2020 - 12:32h

 ssh saai@150.163.38.130 

danniel-lara
(usa Fedora)

Enviado em 22/04/2020 - 12:33h

[useRME@bacurau CHPG]$ ssh saai@150.163.38.130