On 09/11/2015 11:06 AM, Bowie Bailey wrote:
On 9/11/2015 10:34 AM, Robert Moskowitz wrote:
On 09/11/2015 10:21 AM, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
--- Quoted text --
SSh is not parsing the port the way http does, it seems:
$ rsync -a
On 9/11/2015 10:34 AM, Robert Moskowitz wrote:
On 09/11/2015 10:21 AM, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
--- Quoted text --
SSh is not parsing the port the way http does, it seems:
$ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/
/ho
On 09/11/2015 10:21 AM, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
--- Quoted text --
SSh is not parsing the port the way http does, it seems:
$ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/
/home/rgm/data/htt/httnet/homebase/new/dhcp
ssh: co
On 09/10/15, Robert Moskowitz wrote:
--- Quoted text --
SSh is not parsing the port the way http does, it seems:
$ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/
/home/rgm/data/htt/httnet/homebase/new/dhcp
ssh: connect to host 192.168.129.2 port 22: No route to
Am 11.09.2015 um 05:49 schrieb Robert Moskowitz :
>
>
> On 09/10/2015 11:19 PM, Carl E. Hartung wrote:
>> On Thu, 10 Sep 2015 22:50:47 -0400
>> Robert Moskowitz wrote:
>>
>>>
>>> $ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/
>>> /home/rgm/data/htt/httnet/homebase/new/dhcp
>
On 09/10/2015 11:19 PM, Carl E. Hartung wrote:
On Thu, 10 Sep 2015 22:50:47 -0400
Robert Moskowitz wrote:
That will use the default port on the remote host, you can override
that without specifying the -e if required using -p .
$ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dh
On Thu, 10 Sep 2015 22:50:47 -0400
Robert Moskowitz wrote:
> > That will use the default port on the remote host, you can override
> > that without specifying the -e if required using -p .
>
>
> $ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/
> /home/rgm/data/htt/httnet/hom
On 09/10/2015 02:31 PM, C Linus Hicks wrote:
On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
Quoted text
Try this:
rsync -ah --stats 192.168.192.2:/root/samba.PDC/
/home/rgm/data/htt/httnet/homebase/new/root/
---
Ah, I should have checked your second email!
On 09/10/2015 02:31 PM, C Linus Hicks wrote:
On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
Quoted text
Try this:
rsync -ah --stats 192.168.192.2:/root/samba.PDC/
/home/rgm/data/h
On 09/10/2015 02:23 PM, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
Quoted text
I just tried the following:
rsync -ah --stats "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/
/home/rgm/data/htt/httnet/homebase/new/root/
And it failed
On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote:
Quoted text
Try this:
rsync -ah --stats 192.168.192.2:/root/samba.PDC/
/home/rgm/data/htt/httnet/homebase/new/root/
- End Quote -
On 09/10/15, Robert Moskowitz wrote:
Quoted text
I just tried the following:
rsync -ah --stats "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/
/home/rgm/data/htt/httnet/homebase/new/root/
And it failed with:
Unexpected remote arg: 192.168.192.2:/roo
On 09/09/2015 08:17 PM, Carl E. Hartung wrote:
On Wed, 9 Sep 2015 05:51:38 -0700 (PDT)
Mark Milhollan wrote:
On Tue, 8 Sep 2015, Carl E. Hartung wrote:
On Tue, 8 Sep 2015 10:25:33 -0700 (PDT) Mark Milhollan wrote:
-e specifies the *local* transport command to use
What?! Straight from the d
On 09/09/2015 08:17 PM, Carl E. Hartung wrote:
On Wed, 9 Sep 2015 05:51:38 -0700 (PDT)
Mark Milhollan wrote:
On Tue, 8 Sep 2015, Carl E. Hartung wrote:
On Tue, 8 Sep 2015 10:25:33 -0700 (PDT) Mark Milhollan wrote:
-e specifies the *local* transport command to use
What?! Straight from the d
On Wed, 9 Sep 2015 05:51:38 -0700 (PDT)
Mark Milhollan wrote:
> On Tue, 8 Sep 2015, Carl E. Hartung wrote:
> >On Tue, 8 Sep 2015 10:25:33 -0700 (PDT) Mark Milhollan wrote:
>
> >> -e specifies the *local* transport command to use
> >
> >What?! Straight from the documentation:
> >
> >" -e, --
I ran it again but with:
rsync -ah --stats --delete -e "ssh -p613 -l root"
192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/newetc
And the newetc directory was created with all the files. I again ran:
rsync -ah --stats --delete -e "ssh -p613 -l root"
192.168.192.2:/etc/name*
On Tue, 8 Sep 2015 10:25:33 -0700 (PDT)
Mark Milhollan wrote:
> On Mon, 7 Sep 2015, Carl E. Hartung wrote:
> >On Mon, 7 Sep 2015 13:05:59 -0400
> >Robert Moskowitz wrote:
>
> >> rsync -ah --stats --delete -e "ssh -p613 -l root"
> >> 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new
I tried your rsync command and it worked on my LAN over ssh.
The following was placed in the destination directory:
drwxr-x--- 2 root smmsp 4.0K Jul 28 21:05 named/
-rw-r- 1 root smmsp 1.6K Oct 30 2013 named.conf
-rw-r--r-- 1 root smmsp 2.4K Jul 28 21:05 named.iscdlv.key
-rw-r- 1 root
On Mon, 7 Sep 2015 14:58:00 -0400
Robert Moskowitz wrote:
>
>
> On 09/07/2015 02:17 PM, Carl E. Hartung wrote:
> > On Mon, 7 Sep 2015 13:05:59 -0400
> > Robert Moskowitz wrote:
8< - - - - - trimmed - - - - - >8
> > Do you really mean '-h' human-readable vs. '-H' preserve hard links?
>
> Yes.
O
On 09/07/2015 02:17 PM, Carl E. Hartung wrote:
On Mon, 7 Sep 2015 13:05:59 -0400
Robert Moskowitz wrote:
I am trying to rsync the named files under /etc for backup purposes.
I tried:
rsync -ah --stats --delete -e "ssh -p613 -l root"
192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase
On Mon, 7 Sep 2015 13:05:59 -0400
Robert Moskowitz wrote:
> I am trying to rsync the named files under /etc for backup purposes.
> I tried:
>
> rsync -ah --stats --delete -e "ssh -p613 -l root"
> 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc
>
> The stats shows it sees all
I am trying to rsync the named files under /etc for backup purposes. I
tried:
rsync -ah --stats --delete -e "ssh -p613 -l root"
192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc
The stats shows it sees all the files, but only moves the dir /etc/named
and the files within i
On Mon, October 20, 2014 10:49, Denniston, Todd A CIV NAVSURFWARCENDIV Crane
wrote:
>
> [OP: `they don't allow ssh between the datacenters` ...but... they nfs between
> them...??? ME: much head scratching.]
We have a Value Added Network (VAN) provider who insists on a similar thing.
We were giv
On Mon, Oct 20, 2014 at 3:05 PM, Tim Dunphy wrote:
> >
> > > Don't forget that the time taken to build the file list is a function
> of
> > > the number of files present, and not their size. If you have many
> > millions
> > > of small files, it will indeed take a very long time. Over sshfs with
On 2014-10-20, Les Mikesell wrote:
> On Mon, Oct 20, 2014 at 1:12 PM, Keith Keller
>>
>> The OP said he was mounting the NFS over sshfs.
>
> OK, I don't see how that is possible because something would either be
> mounted as nfs or sshfs, not one over the other.
I'm just repeating what he wrote;
On Mon, Oct 20, 2014 at 1:12 PM, Keith Keller
wrote:
> On 2014-10-20, Les Mikesell wrote:
>>
>> So, you probably want the 'source' side of the transfer to be local
>> for faster startup. But... in what universe is NFS mounting across
>> data centers considered more secure than ssh? Or even a rea
On 2014-10-20, Les Mikesell wrote:
>
> So, you probably want the 'source' side of the transfer to be local
> for faster startup. But... in what universe is NFS mounting across
> data centers considered more secure than ssh? Or even a reasonable
> thing to do? How about a VPN between the two host
On Sun, Oct 19, 2014 at 9:05 PM, Tim Dunphy wrote:
>>
>> > Don't forget that the time taken to build the file list is a function of
>> > the number of files present, and not their size. If you have many
>> millions
>> > of small files, it will indeed take a very long time. Over sshfs with
>> > a s
> -Original Message-
> From: John Doe [mailto:jd...@yahoo.com]
> Sent: Monday, October 20, 2014 5:30 AM
> To: CentOS mailing list; Tim Dunphy
> Subject: Re: [CentOS] rsync question: building list taking forever
>
> Are you "allowed" to temporarily run an
Are you "allowed" to temporarily run an ssh tunnel (or stunnel) on your jumpbox?
So connecting from host1 to jumpbox on port XXX would be tunneled to ssh port
on host2...
Or with netcat (if you can mkfifo)?
mkfifo backpipe
nc -l 12345 0backpipeBut you will have to trick ssh
into accepting yo
>
> > Don't forget that the time taken to build the file list is a function of
> > the number of files present, and not their size. If you have many
> millions
> > of small files, it will indeed take a very long time. Over sshfs with
> > a slowish link, it could be days.
> >
> > and it may end
On Mon, Oct 20, 2014 at 7:57 AM, Steve Thompson wrote:
> On Sun, 19 Oct 2014, Keith Keller wrote:
>
> I suspect that sshfs's relatively poor performance is having an impact
>> on your transfer. I have a 30TB filesystem which I rsync over an
>> OpenVPN link, and building the file list doesn't ta
On 2014-10-19, Steve Thompson wrote:
>
> Don't forget that the time taken to build the file list is a function of
> the number of files present, and not their size. If you have many millions
> of small files, it will indeed take a very long time. Over sshfs with
> a slowish link, it could be days.
On 2014/10/19 08:01, Keith Keller wrote:
On 2014-10-19, Tim Dunphy wrote:
... and remember to use tcp for nfs transfer ;)
Hmm you mean specify tcp for rsync? I thought that's default.
No, he means use TCP for NFS (which is also the default).
I suspect that sshfs's relatively poor performance
On Sun, 19 Oct 2014, Keith Keller wrote:
I suspect that sshfs's relatively poor performance is having an impact
on your transfer. I have a 30TB filesystem which I rsync over an
OpenVPN link, and building the file list doesn't take that long (maybe
an hour?). (The links themselves are reasonabl
On 2014-10-19, Tim Dunphy wrote:
>> ... and remember to use tcp for nfs transfer ;)
>
> Hmm you mean specify tcp for rsync? I thought that's default.
No, he means use TCP for NFS (which is also the default).
I suspect that sshfs's relatively poor performance is having an impact
on your transfer.
On 10/19/2014 8:55 AM, Tim Dunphy wrote:
I've setup an rsync between two directories that I've mounted locally on a
jump box. Long story short, the two directories are both NFS shares from
two different hosts. Our security dept won't allow us to SSH between the
two data centers, directly. But t
2014-10-19 20:49 GMT+03:00 Tim Dunphy :
> > ... and remember to use tcp for nfs transfer ;)
>
>
> Hmm you mean specify tcp for rsync? I thought that's default. But holy
> crap, you were right about it taking a long time to build a file list! The
> rsync just started a few minutes ago... !
>
No, t
> ... and remember to use tcp for nfs transfer ;)
Hmm you mean specify tcp for rsync? I thought that's default. But holy
crap, you were right about it taking a long time to build a file list! The
rsync just started a few minutes ago... !
dumps/dotmedia.031237.svndmp
dumps/dotmedia.031238.svndmp
2014-10-19 20:03 GMT+03:00 Eero Volotinen :
>
>
> 2014-10-19 18:55 GMT+03:00 Tim Dunphy :
>
>> Guys,
>>
>> I've setup an rsync between two directories that I've mounted locally on
>> a
>> jump box. Long story short, the two directories are both NFS shares from
>> two different hosts. Our security
2014-10-19 18:55 GMT+03:00 Tim Dunphy :
> Guys,
>
> I've setup an rsync between two directories that I've mounted locally on a
> jump box. Long story short, the two directories are both NFS shares from
> two different hosts. Our security dept won't allow us to SSH between the
> two data centers,
Guys,
I've setup an rsync between two directories that I've mounted locally on a
jump box. Long story short, the two directories are both NFS shares from
two different hosts. Our security dept won't allow us to SSH between the
two data centers, directly. But the jump host can contact both. So wha
centos.org [mailto:centos-boun...@centos.org] On Behalf Of
John R Pierce
Sent: Tuesday, 31 July 2012 5:16 p.m.
To: centos@centos.org
Subject: Re: [CentOS] rsync question
On 07/30/12 10:05 PM, Smithies, Russell wrote:
> I'm trying to rsync a 8TB data folder containing squillions of small
On 07/31/2012 07:05 AM, Smithies, Russell wrote:
> Is it possible to do something simple like scp the whole dir in one go so
> they're duplicates in the first instance, then get rsync to just keep them in
> sync without an initial transfer?
>
> Or is there a better way?
I use tar and ttcp for an
On 07/30/12 10:05 PM, Smithies, Russell wrote:
> I'm trying to rsync a 8TB data folder containing squillions of small files
> and it's taking forever (i.e. weeks) to get anywhere.
> I'm assuming the slow bit is check-summing everything with a single CPU (even
> though it's on a 12-core server ;-(
I'm trying to rsync a 8TB data folder containing squillions of small files and
it's taking forever (i.e. weeks) to get anywhere.
I'm assuming the slow bit is check-summing everything with a single CPU (even
though it's on a 12-core server ;-( )
Is it possible to do something simple like scp the
On Monday 04 August 2008 11:35:18 pm Mag Gam wrote:
> Hi All,
>
> I am trying to understand the purpose of rsyncd. Why does it exist?
> Why not just use rsync ad-hoc or via script?
This is explained in the rsync documentation, read the man page for more info.
You either need to use rsync with a r
Mag Gam wrote:
Hi All,
I am trying to understand the purpose of rsyncd. Why does it exist?
Why not just use rsync ad-hoc or via script?
well, if you use rsync -> rsyncd, there's no encryption, so less CPU
overhead, so faster transfers, but there's also less security, so this
should only b
On Tue, Aug 5, 2008 at 1:35 PM, Mag Gam <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I am trying to understand the purpose of rsyncd. Why does it exist?
> Why not just use rsync ad-hoc or via script?
The rsyncd is optional. I did not use it by myself, so can't comment on that.
>
> Also, to a more se
Hi All,
I am trying to understand the purpose of rsyncd. Why does it exist?
Why not just use rsync ad-hoc or via script?
Also, to a more serious note. I need to keep a filesystem on 1 server
and another server synced by.
What is the best way to do this? I want to have /source and /target to
be ex
On Tuesday 08 April 2008 17:58, Nicolas KOWALSKI wrote:
> Anne Wilson <[EMAIL PROTECTED]> writes:
> > The command is
> >
> > rsync -auvz --delete-after
> > --exclude-from=/home/anne/rsync_skiplist_mail.txt /home/anne/Maildir/
> > /Data3/anne/Maildir/
>
> The roots are the Maildirs themselves, so it
On Tuesday 08 April 2008 15:16, Jeff Larsen wrote:
> On Tue, Apr 8, 2008 at 5:18 AM, Anne Wilson <[EMAIL PROTECTED]>
wrote:
> > I run several backup scripts by cron, one of which backs up my mail. I
> > do not want it to back up the Trash folder, but it appears to be doing
> > so. I conclude tha
Anne Wilson <[EMAIL PROTECTED]> writes:
> The command is
>
> rsync -auvz --delete-after --exclude-from=/home/anne/rsync_skiplist_mail.txt
> /home/anne/Maildir/ /Data3/anne/Maildir/
The roots are the Maildirs themselves, so it should not be necessary
to re-specify them in the exclude list.
> whe
On Tuesday 08 April 2008 15:16:22 Jeff Larsen wrote:
> On Tue, Apr 8, 2008 at 5:18 AM, Anne Wilson <[EMAIL PROTECTED]>
wrote:
> > I run several backup scripts by cron, one of which backs up my mail. I
> > do not want it to back up the Trash folder, but it appears to be doing
> > so. I conclude t
On Tue, Apr 8, 2008 at 5:18 AM, Anne Wilson <[EMAIL PROTECTED]> wrote:
> I run several backup scripts by cron, one of which backs up my mail. I do not
> want it to back up the Trash folder, but it appears to be doing so. I
> conclude that my script is faulty somewhere, and would be grateful for
I run several backup scripts by cron, one of which backs up my mail. I do not
want it to back up the Trash folder, but it appears to be doing so. I
conclude that my script is faulty somewhere, and would be grateful for
advice.
The command is
rsync -auvz --delete-after --exclude-from=/home/an
Jeff Larsen wrote:
On Mon, Apr 7, 2008 at 12:07 PM, Ray Leventhal <[EMAIL PROTECTED]> wrote:
rsync does not create archives. Are you sure that the archive does not
exist in the source directory? Is it just being rsynced along with
everything else? Perhaps it is left over from previous backup
Alfred von Campe wrote:
On Apr 7, 2008, at 13:07, Ray Leventhal wrote:
I want to backup the /home tree to that box nightly via rsync
(cronjob), so I tried this:
rsync -avrogz /home/ /mnt/backup/
First, drop "rog" from the options, as they are implied with -a.
Also, since you are not going
On Mon, Apr 7, 2008 at 12:07 PM, Ray Leventhal <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I've been trying to wrap my head around this for a bit, done my googling
> and archive searching but I still can't seem to 'get' it.
>
> Here goes:
>
> I've a spare drive in my CentOS5.1 box, which (for tes
On Apr 7, 2008, at 13:07, Ray Leventhal wrote:
I want to backup the /home tree to that box nightly via rsync
(cronjob), so I tried this:
rsync -avrogz /home/ /mnt/backup/
First, drop "rog" from the options, as they are implied with -a.
Also, since you are not going over a (potentially sl
Hi folks,
I've been trying to wrap my head around this for a bit, done my googling
and archive searching but I still can't seem to 'get' it.
Here goes:
I've a spare drive in my CentOS5.1 box, which (for testing now) I mount
manually under /mnt/backup
I want to backup the /home tree to that
I have an external USB that I backup to. Rsync uses a bunch of memory
in the process. So I thought I would build the file list and output that to
a file then let rsync read the file names from a file list (hopefully
not taking TONS of memory)...
I do the command:
rsync --only-write-batch=rsync
62 matches
Mail list logo
