I have to rsync files between a pair of NAS over a WAN, and since each NAS has
an administrative server, we do the rsync 'server-to-server' using SSH.
-Original Message-
From: rsync-boun...@lists.samba.org [mailto:rsync-boun...@lists.samba.org] On
Behalf Of Chris Arnold
Sent: Wednesday,
On 4/11/2012 10:05 PM, Chris Arnold wrote:
I hopethis hope this makes sense. How do you make rsync run even when not
physically connected to the server? In other words, I run rsync from the
terminal via vnc and when I log out of the connection, rsync stops running. Is
there a script or somethi
On Wed, 11 Apr 2012, Chris Arnold wrote:
> I hopethis hope this makes sense. How do you make rsync run even when
> not physically connected to the server? In other words, I run rsync from
> the terminal via vnc and when I log out of the connection, rsync stops
> running. Is there a script or somet
On 04/11/2012 09:23:57 PM, Kevin Korb wrote:
> Cron will allow for an rsync to be running in the background.
> However, there are additional steps (such as a lock file) you should
> take to make sure two don't end up running at the same time.
You could also use "at" if you want something to run on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cron will allow for an rsync to be running in the background.
However, there are additional steps (such as a lock file) you should
take to make sure two don't end up running at the same time.
On 04/11/12 22:22, Chris Arnold wrote:
> I just thought abo
I just thought about cron! Will a cron job accomplish this?
Sent from my iPhone
On Apr 11, 2012, at 10:07 PM, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Use screen or tmux. You can start rsync (or anything else) running
> then detach. Later you can log back in an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Use screen or tmux. You can start rsync (or anything else) running
then detach. Later you can log back in and re-attach.
On 04/11/12 22:05, Chris Arnold wrote:
> I hopethis hope this makes sense. How do you make rsync run even
> when not physically
I hopethis hope this makes sense. How do you make rsync run even when not
physically connected to the server? In other words, I run rsync from the
terminal via vnc and when I log out of the connection, rsync stops running. Is
there a script or something I can use?
Sent from my iPhone
--
Please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/2012 02:08 PM, Kevin Korb wrote:
> "Skipping directory ." because you didn't tell it to run
> recursively. I was suggesting options to add to a normal rsync not
> the only options to use. You would still need either --recursive
> or --archiv
https://bugzilla.samba.org/show_bug.cgi?id=8856
--- Comment #3 from ron 2012-04-12 00:27:12 UTC ---
It sure makes sense to handle all those entities in the same way, even though
it gets confusing when the same command acts on them in different ways. As in
the case of hard-linking symlinks, where
On Wed, 11 Apr 2012, Kevin Korb wrote:
> Using either rsync over ssh or rsyncd which is what I said in my
> original reply. But unfortunately few NAS appliances support those.
>
Check for a custom kerhel for your NAS box - most have a ssh daemon and
rsync. We did that a lot a few years ago, but h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rsync doesn't run over ftp anymore than it runs over smb.
Those two URLs are discussions about alternatives to rsync.
Of course if you fuse mount an ftp server then rsync could run on it
but then you could do that with cifs too.
The big difference is
Another option (that I'm looking into,but haven't tried) is to do rsync
over ftp. Many NASs support ftp, so that may work for you.
See:
http://serverfault.com/questions/24622/how-to-use-rsync-over-ftp
http://fixunix.com/debian/129298-website-backups-using-rsync-via-ftp.html
Joe
> -BEGIN PGP
On 11.04.2012 11:14, James Moe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
> I restored a filesystem by using rsync to copy directories and files
> from a backup volume to the newly recreated volume. All of the
> re-created files were given the current date and time rathe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using either rsync over ssh or rsyncd which is what I said in my
original reply. But unfortunately few NAS appliances support those.
On 04/11/12 18:04, Chris Arnold wrote:
> So what would plan A be?
>
> - Original Message - From: "Kevin Korb
So what would plan A be?
- Original Message -
From: "Kevin Korb"
To: rsync@lists.samba.org
Sent: Wednesday, April 11, 2012 5:39:31 PM
Subject: Re: Rsync to a Remote NAS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You mean mount -t cifs ;)
This is a good plan B if the remote system ca
That's how I do it too - from a linux box:
# mount -t cifs -o username=tylerdurden //cifsbox/share /linuxmountpoint
(Then you are prompted for tylerdurden's Windows/CIFS password)
After that:
# rsync (your options here) / /linuxmountpoint
Bill Dorrian
Network Administrator
Desk: 904-273-7625
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You mean mount -t cifs ;)
This is a good plan B if the remote system can't support rsyncd or
rsync over ssh. But unfortunately it would mean running with --whole-file
On 04/11/12 17:36, Greg Deback (rsync) wrote:
> Hi,
>
> I don't think rsync nativ
Hi,
I don't think rsync natively supports samba shared volumes. You should
probably start by mounting your shared volume, using mount -t smbfs, then
sync. See http://users.softlab.ece.ntua.gr/~ttsiod/backup.html
Greg
On Wed, Apr 11, 2012 at 11:31 PM, Chris Arnold
wrote:
> Forgive me if this has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rsync does not communicate via smb. It either communicates to its own
service (rsyncd) or to another rsync command over ssh (like scp does).
On 04/11/12 17:31, Chris Arnold wrote:
> Forgive me if this has been addressed here before. We have a remote
Forgive me if this has been addressed here before. We have a remote office that
we need to backup to our NAS. We have a site to site certificate VPN. The
remote site has over 51gb that needs to be backed up to our NAS over that VPN.
I have tried this command:
rsync --verbose --progress --stats -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Skipping directory ." because you didn't tell it to run recursively.
I was suggesting options to add to a normal rsync not the only options
to use. You would still need either --recursive or --archive if you
are trying to rsync a directory.
On 04/1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/2012 01:53 PM, Kevin Korb wrote:
> It shouldn't care which way the time stamps are off. --times
> (which is part of --archive) will tell rsync to correct the time
> stamps and --size-only tells rsync to assume that files of the same
> size ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --times --size-only --itemize-changes
check it out first with --dry-run
On 04/11/12 14:14, James Moe wrote:
> Hello, I restored a filesystem by using rsync to copy directories
> and files from a backup volume to the newly recreated volume. All
> of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I restored a filesystem by using rsync to copy directories and files
from a backup volume to the newly recreated volume. All of the
re-created files were given the current date and time rather than the
original file's timestamp. I am sure ther
25 matches
Mail list logo
