Thank you for helping me.
You are correct I killed it very quickly. Because in the previous version,
the dump command would show the actual shares I wanted on the command line
{ and not / } and I would not get any messages like
*Remote[2]: file has vanished: "/proc/2/exe"
*
which indicates it is *really* looking at / and not *only* at the mounts I
want.
You said:
*During this time, the target "lamp" is looking at every file on the disk,
once finished, it will send the list across.*
Really it looks at the whole disk when I don't want to backup the whole
disk?
Is it going to send the whole list across?
Has this changed in this version then? Because I can run dump on my old
version and it does not do that.
*
*
FWIW boxes on same lan, no firewall, lamp just has one disk with everything
in /
Thanks again.
On Wed, Jan 30, 2013 at 7:40 PM, Adam Goryachev <
mailingli...@websitemanagers.com.au> wrote:
> On 31/01/13 04:26, Ctdi Unix wrote:
> [SNIP]
>
>
> dump as a debug shows:
>
> *full backup started for directory /*
> *started full dump, share=/*
> *Running: /usr/bin/ssh -q -x -l root lamp /usr/bin/rsync --server
> --sender --numeric-ids --perms --owner --group -D --links --hard-links
> --times --block-size=2048 --recursive --ignore-times . /*
> *Xfer PIDs are now 5652*
> *xferPids 5652*
> *Got remote protocol 29*
> *Negotiated protocol version 28*
> *Remote[2]: file has vanished: "/proc/2/exe"*
> *
> *
>
> *You should add:
> * -x, --one-file-system don't cross filesystem boundaries
> to the $Conf{RsyncArgs} either in the machine config, or global config
> file.
>
> <control c>
>
> You have cancelled the backup before any error, please be more patient,
> this step can take a very long time. If the target "lamp" is a machine
> which is not on your local LAN, or is behind a firewall, the firewall or
> NAT router can sometimes drop the connection because of this long period of
> network silence. During this time, the target "lamp" is looking at every
> file on the disk, once finished, it will send the list across. I is also
> possible that the remote machine has come across a file which is blocking
> it, usually the one-file-system option will help with this to avoid files
> in /proc or /sys etc... (which are not important/real files anyway).
>
> Also, send the output of "df" on lamp, you may need to change the share to
> /home if you have a different mountpoint for /home.
>
> Regards,
> Adam
>
> --
> Adam Goryachev
> Website Managerswww.websitemanagers.com.au
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
