Re: [BackupPC-users] Unable to read 4 bytes revisited
-Original Message- From: Adam Goryachev [mailto:mailingli...@websitemanagers.com.au] Sent: den 11 oktober 2014 13:21 To: backuppc-users@lists.sourceforge.net Subject: Re: [BackupPC-users] Unable to read 4 bytes revisited On 11/10/14 21:12, Sorin Srbu wrote: Hi all, I set up BackupPC at home to make more systematic backups of mine and wifeys homefolders on the samba-server and ran into the somewhat dreaded Unable to read 4 bytes-error. Problem is *maybe* that the host to be backed up is running sshd on port 522. Yep, but that is easily solved. What I've done so far is to create the passwordless login with my backuppc-user to the host, tested and this works. As the backuppc-user I can login to the host using ssh over port 522 without entering a password and becoming root. Rsync is used as the transfer method, BTW. In the BPC web-GUI, I've added port 522 to RsyncClientCMD, so that now it reads: $sshPath -q -x -l -p 522 root $host $rsyncPath $argList+ Was this correct to do? No, this is your mistake. You need to know what all those options mean. -l is the username to use when authenticating with the remote host, you have provided the username as -p, and then I don't know what 522 and root are going to be interpreted as, I guess 522 would be the hostname, and root would become the path to rsync... Try this: $sshPath -q -x -l root -p 522 $host $rsyncPath $argList+ I've tried to disable iptables on the host, with no change, still getting the 4 byte-error. What am I missing?? Is there something with rsync not connecting properly maybe? Also, next time please provide the log file as that will usually provide more information if the solution isn't so easy. Thanks for the hints. I'll try this when I get home. Seems I assumed to much with the arguments list... 8-/ -- //Sorin -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho ___ 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/
Re: [BackupPC-users] BackupFilesExcludes using rsync being ignored
Hi again Adam
I stand corrected! The config you suggested did work and on all other
hosts now I can see the excludes being passed. Oddly the one single
machine I was using to test on last night did not work but I suspect
that is a separate issue - I'm no longer seeing XFer errors where the
system is trying to backup /proc/.
So thanks very much for putting me on the straight and narrow.
regards Tom
On 12/10/14 23:34, Adam Goryachev wrote:
On 13/10/14 08:54, Tom Fallon wrote:
Thanks Doug
by my limited understanding, the * wildcard in my example below would
mean the system would exclude any directory called proc or sys etc
regardless of the share, whereas what I think should be used is
ryncshare = / and then specify the directories under there explicitly
which I had done.
Amending to '*' = [ in the config.pl file resulted in same behaviour
I've been seeing all along.
In your config I'd expect it to be excluding file types by extension
rather than directories.
I could try '*/proc' etc I guess but think thats a bandaid approach and
would really like to get this working the way its supposed to based on
the documentation.
regards Tom
On 12/10/14 22:32, Doug Lytle wrote:
Tom Fallon wrote:
$Conf{BackupFilesExclude} = {
'*' = [
'proc',
'sys',
My list shows:
$Conf{BackupFilesExclude} = {
'*' = [
'*/Cache',
'*.mp3',
'*.MP3',
'*.m4a',
'*.M4A',
'*.m4v',
]
};
$Conf{BackupFilesExclude} = {
'/' = [
'/proc/'
'/tmp/'
]
};
The '/' is the share name, so using * just means all shares, since you
only have one share, then there is no difference.
I would suggest using /proc/ (trailing slash) because then you will
backup the directory without the contents. After a full restore, you
will need the directory /proc to exist, or else mounting /proc will
fail, same with /tmp etc.
Also, be careful when excluding /var/log or similar, as some software
will want subdirectories to exist.
Also, you could consider add --one-file-system to the rsync command
which will automatically skip any other mounted drives/partitions.
Finally, if it is still not working, please post the full config file,
along with the log from a full backup run (at least the start where it
shows what command was sent, and a sample where it has backed up some
files that you had requested).
Regards,
Adam
--
Tom Fallon
1033 Aikenhead Road
Glasgow
G44 4QT
Tel: 0141 5697824
Mob: 07909 754 170
Skype: fallontom
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
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/
[BackupPC-users] /var/run/BackupPC Alpha3
Yep, /var/run is on tmpfs... How can i fix this ? Script something? +-- |This was sent by romainp...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho ___ 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/
Re: [BackupPC-users] /var/run/BackupPC Alpha3
13.10.2014 14:52, rpace пишет: Yep, /var/run is on tmpfs... How can i fix this ? Script something? http://askubuntu.com/questions/303120/how-folders-created-in-var-run-on-each-reboot -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho ___ 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/
Re: [BackupPC-users] Compression Experiences?
On Mon, Oct 13, 2014 at 06:24:10AM +0200, Christian Völker wrote: I remember having read about restoring single files from command line needs some BackupPC specific script or tricks to uncompress the files when using ocmpression for BackupPC. I assume you mean using BackupPC_zcat. For a new instance I'm thinking of storing the files without compression to be able to easily restore them directly from command line if needed. Is there anyone out here who has some experience about the average compression ratio in BackupPC? I know it depends on the type of data- most of them are office documents (Word and OpenOffice). If you already have a working backuppc instance, look at the page for any host. The bottom table give you the compression ratios. I have some hosts that routinely have 80% compression (database backups). Others have 0-2% (data directories with most of the data already compressed). -- -- rouilj John Rouillard System Administrator Dyn Corporation 603-244-9084 (cell) -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho ___ 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/
Re: [BackupPC-users] BackupFilesExcludes using rsync being ignored
On 10/12/2014 4:27 PM, Tom Fallon wrote:
Most forum posts I've read show a different syntax in the
/etc/backuppc/config.pl file which I've managed to emulate by adding
the exclusions to the GUI by adding / in the key then using the insert
button to add excluded directories. This ends up with config.pl file
looking more like what others are posting here but the exclusion files
are still not being read.
$Conf{BackupFilesExclude} = {
'/' = [
'proc',
'sys',
'*/Cache',
'RECYCLER',
'System Volume Information',
'dev',
'lost+found',
'tmp',
I am fairly sure I have the syntax of the exclude list correct now,
though advice to the contrary is welcome. I've also tried editing the
config.pl file using the * wildcard and am trying to run backup now
but I suspect this will fail too.
$Conf{BackupFilesExclude} = {
'*' = [
'proc',
'sys',
The exact syntax depends on your xfer method and share names. In
general, it looks like this:
$Conf{BackupFilesExclude} = {
'sharename' = [
'exclusion1',
'exclusion2',
],
};
The sharename must either be the name of one of your configured shares
or the wildcard '*', if you want it to apply to all shares.
The syntax for the exclusions can vary slightly depending on the xfer
method. In general, if it starts with a slash, it is anchored to the
root of the share. If there is no slash, it will match anywhere in the
path. You may or may not need an ending slash or an ending '/*'
depending on the xfer method.
In the GUI, the option names are a link into the docs. So you can click
on the BackupFilesExclude link in the GUI for more information.
--
Bowie
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
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/
Re: [BackupPC-users] /var/run/BackupPC Alpha3
On 13/10/14 23:26, rpace wrote: Thanks for the link but the edit of rc.local didnt work for me. i put this in the init.d script of BackupPC : if [ ! -d /var/run/BackupPC ]; then mkdir /var/run/BackupPC/ chown backuppc /var/run/BackupPC/ fi and it's ok. Probably because rc.local runs AFTER backuppc tries to start You would need to ensure backuppc start script runs after the directory is created, easiest solution, just add it to the backuppc start script like you did. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ 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/
Re: [BackupPC-users] BackupFilesExcludes using rsync being ignored
Hi,
Tom Fallon wrote on 2014-10-13 11:29:43 +0100 [Re: [BackupPC-users]
BackupFilesExcludes using rsync being ignored]:
[...]
The config you suggested did work and on all other
hosts now I can see the excludes being passed.
this was the thing I would have mentioned, had I read your messages earlier.
You should see log lines like Sent exclude ... shortly after where the
command is shown (Running: /usr/bin/ssh -q -x -l ...; after the protocol
version exchange, to be exact). As that is not happening, it would seem that
BackupPC doesn't see the exclude. Some possible causes spring to mind:
1.) You have somehow misspellt the variable name (e.g.
$Conf{BackupFileExcludes} = ...), though I strongly doubt the GUI would
do that ;-), and your quote seems correct, assuming you copied it into
your message with cutpaste rather than by typing it (and inadvertantly
correcting a typo).
2.) There is a second assignment to $Conf{BackupFilesExclude} that overwrites
what you quoted with something different. Again, the GUI shouldn't
generate such code.
3.) The assignment, which you don't quote fully (at least the closing brace
and the following ; are missing), continues in a way that makes it
not happen. I'm not sure what would happen if it was syntactically
incorrect (e.g. because of a missing closing brace), but my guess would
be that BackupPC would complain. To be fully sure, you can test the syntax
of your host.pl file with perl -wc host.pl. However, something like
$Conf {BackupFilesExclude} = { '/' = [ '/proc', '/sys' ] }
if 0;
would be syntactically correct and thus go unnoticed by Perl and BackupPC.
4.) The assignment contains a second value for the same hash key, e.g.:
$Conf {BackupFilesExclude} = {
'/' = [ '/proc', '/sys' ],
'/' = [ '' ],
};
The GUI might even generate that.
5.) You're looking at the wrong host config file :-). BackupPC might be
using default settings (from config.pl) and ignoring the host config
file (because it is misnamed, in the wrong directory, unreadable to
the backuppc user, ...). That would not be totally obvious, unless
your default settings are completely different (which I doubt).
Oddly the one single
machine I was using to test on last night did not work but I suspect
that is a separate issue - I'm no longer seeing XFer errors where the
system is trying to backup /proc/.
Does this mean that you have solved the problem, or that it works on some
machines and not on others?
There is something strange about your log file quote:
Running: /usr/bin/ssh -q -x -l userserver.domain.com /usr/bin/rsync --server
--sender --numeric-ids --perms --owner --group -D --links --hard-links
--times --block-size=2048 --recursive --ignore-times . /
You seem to have removed the user name from the ssh invocation. At least,
/usr/bin/rsync is not a valid host name, and userserver.domain.com is
probably not a valid user name on that invalid host ;-).
Hope that helps.
Regards,
Holger
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
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/
