Menu
▾
▴
backuppc-devel — BackupPC developer list
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(7) |
Feb
(6) |
Mar
(3) |
Apr
(9) |
May
(5) |
Jun
(11) |
Jul
(40) |
Aug
(15) |
Sep
(3) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2004 |
Jan
(2) |
Feb
(8) |
Mar
(8) |
Apr
(25) |
May
(10) |
Jun
(11) |
Jul
(5) |
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
(7) |
Dec
(6) |
| 2005 |
Jan
(6) |
Feb
(17) |
Mar
(9) |
Apr
(3) |
May
(4) |
Jun
(11) |
Jul
(42) |
Aug
(33) |
Sep
(13) |
Oct
(14) |
Nov
(19) |
Dec
(7) |
| 2006 |
Jan
(23) |
Feb
(19) |
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(50) |
Aug
(16) |
Sep
(4) |
Oct
(18) |
Nov
(15) |
Dec
(10) |
| 2007 |
Jan
(10) |
Feb
(13) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(5) |
Aug
(7) |
Sep
(25) |
Oct
(58) |
Nov
(15) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(13) |
Mar
(3) |
Apr
(10) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(23) |
Sep
(21) |
Oct
(7) |
Nov
(3) |
Dec
(12) |
| 2009 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(7) |
May
(6) |
Jun
(25) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(3) |
Nov
(2) |
Dec
(2) |
| 2010 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
(2) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
|
Nov
|
Dec
(3) |
| 2011 |
Jan
(10) |
Feb
(2) |
Mar
(71) |
Apr
(4) |
May
(8) |
Jun
|
Jul
|
Aug
(4) |
Sep
(3) |
Oct
(1) |
Nov
(5) |
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(15) |
Jun
(1) |
Jul
|
Aug
(20) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2013 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(4) |
May
(2) |
Jun
(11) |
Jul
(12) |
Aug
|
Sep
(19) |
Oct
(25) |
Nov
(7) |
Dec
(9) |
| 2014 |
Jan
(6) |
Feb
(2) |
Mar
(7) |
Apr
(5) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(4) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
(16) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(12) |
Jun
(3) |
Jul
|
Aug
(5) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(6) |
Mar
(68) |
Apr
(18) |
May
(8) |
Jun
(1) |
Jul
|
Aug
(10) |
Sep
(2) |
Oct
(1) |
Nov
(13) |
Dec
(25) |
| 2018 |
Jan
(18) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
|
|
From: Michael S. <mic...@me...> - 2018-01-18 18:10:45
|
On Jan 18, 2018, at 12:53 AM, Marc Gilliatt <m.g...@li...> wrote: > > Hi Craig, > > Are there any updates on my issue, please? A quick recap of where we landed: (Craig): version 3.3.1 doesn’t work with 4.3 of smbclient. (Marc): I am running those exact versions What update are you expecting? Unless you downgrade smbclient or upgrade BackupPC, we can only reiterate, yes, you are continuing to encounter a known issue. |
|
From: Marc G. <m.g...@li...> - 2018-01-18 08:53:24
|
Hi Craig,
Are there any updates on my issue, please?
It failed again on the 15th January. I've posted the contents of the errors log.
Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.0.z, modified 2018-01-15 11:36:09 (Extracting only Errors)
Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - \\Archive \\IT-Downloads \\NI\ Sample\ Libraries \\Impulse\ Responses \\Backup \\User\ Guides\ Installs \\SoundsDatabase
full backup started for share audio
Xfer PIDs are now 47236,47235
[ skipped 1 lines ]
tar:316 tarmode is now full, system, hidden, noreset, quiet
[ skipped 4564241 lines ]
tar:712 Total bytes received: 8890396401246
[ skipped 50 lines ]
tarExtract: Done: 0 errors, 4378148 filesExist, 8830097565642 sizeExist, 7110487703451 sizeExistComp, 4391696 filesTotal, 8890406089197 sizeTotal
Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd
Got fatal error during xfer (No files dumped for share audio)
Backup aborted (No files dumped for share audio)
Saving this as a partial backup
________________________________
From: Marc Gilliatt <m.g...@li...>
Sent: 16 January 2018 09:35
To: Craig Barratt via BackupPC-devel
Cc: Craig Barratt
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
I'm using...
smbclient
Version 4.3.11-Ubuntu
BackupPC
3.3.1-2ubuntu3.3
________________________________
From: Craig Barratt via BackupPC-devel <bac...@li...>
Sent: 13 January 2018 05:46
To: Developers discussion
Cc: Craig Barratt
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
Marc,
What versions of BackupPC and smbclient are you using? There have been multiple changes to the output format from smbclient, and BackupPC has only recently caught up.
I recall from an earlier thread that you are running 3.3.1. Compatibility with Samba 4.3 was added in BackuPC 3.3.2.
Craig
On Fri, Jan 12, 2018 at 7:42 AM, Marc Gilliatt <m.g...@li...<mailto:m.g...@li...>> wrote:
I believe that resolved the issue, I'm no longer getting the NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
However, it still failed. I have posted the XferLOG Errors only for you.
Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.bad.z, modified 2018-01-12 14:10:40 (Extracting only Errors)
Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - \\SoundsDatabase
full backup started for share audio
Xfer PIDs are now 15172,15170
[ skipped 1 lines ]
tar:316 tarmode is now full, system, hidden, noreset, quiet
[ skipped 734106 lines ]
tar:712 Total bytes received: 2389181924809
[ skipped 22 lines ]
tarExtract: Done: 0 errors, 721209 filesExist, 2347961021801 sizeExist, 1891391027032 sizeExistComp, 724415 filesTotal, 2389184522827 sizeTotal
Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd
Got fatal error during xfer (No files dumped for share audio)
Backup aborted (No files dumped for share audio)
Not saving this as a partial backup since it has fewer files than the prior one (got 724415 and 0 files versus 4387717)
________________________________
From: Michael Stowe <mic...@me...<mailto:mic...@me...>>
Sent: 10 January 2018 15:33
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On 2018-01-10 03:08, Marc Gilliatt wrote:
Is the following in the correct format?
$Conf{SmbShareName} = [
'audio'
]; $Conf{SmbSharePasswd} = ‘Password1’; $Conf{SmbShareUserName} = ‘backuppc’; $Conf{XferMethod} = ‘smb’; $Conf{BackupFilesOnly} = {
‘audio’ => [ '\\Archive'],
‘audio’ => [ '\\IT-Downloads'],
‘audio’ => [ '\\NI Sample Libraries'],
‘audio’ => [ '\\Impulse Responses'],
‘audio’ => [ '\\Backup'],
‘audio’ => [ '\\User Guides Installs'],
‘audio’ => [ '\\SoundsDatabase'];
}
No, Sorry, I should have provided a more complete example:
$Conf{BackupFilesOnly} = {
'audio' => [ '\\Archive',
'\\IT-Downloads',
'\\NI Sample Libraries',
'\\Impulse Responses',
'\\Backup',
'\\User Guides Installs',
'\\SoundsDatabase' ];
}
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
Bac...@li...<mailto:Bac...@li...>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
|
From: Marc G. <m.g...@li...> - 2018-01-16 09:35:49
|
I'm using...
smbclient
Version 4.3.11-Ubuntu
BackupPC
3.3.1-2ubuntu3.3
________________________________
From: Craig Barratt via BackupPC-devel <bac...@li...>
Sent: 13 January 2018 05:46
To: Developers discussion
Cc: Craig Barratt
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
Marc,
What versions of BackupPC and smbclient are you using? There have been multiple changes to the output format from smbclient, and BackupPC has only recently caught up.
I recall from an earlier thread that you are running 3.3.1. Compatibility with Samba 4.3 was added in BackuPC 3.3.2.
Craig
On Fri, Jan 12, 2018 at 7:42 AM, Marc Gilliatt <m.g...@li...<mailto:m.g...@li...>> wrote:
I believe that resolved the issue, I'm no longer getting the NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
However, it still failed. I have posted the XferLOG Errors only for you.
Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.bad.z, modified 2018-01-12 14:10:40 (Extracting only Errors)
Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - \\SoundsDatabase
full backup started for share audio
Xfer PIDs are now 15172,15170
[ skipped 1 lines ]
tar:316 tarmode is now full, system, hidden, noreset, quiet
[ skipped 734106 lines ]
tar:712 Total bytes received: 2389181924809
[ skipped 22 lines ]
tarExtract: Done: 0 errors, 721209 filesExist, 2347961021801 sizeExist, 1891391027032 sizeExistComp, 724415 filesTotal, 2389184522827 sizeTotal
Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd
Got fatal error during xfer (No files dumped for share audio)
Backup aborted (No files dumped for share audio)
Not saving this as a partial backup since it has fewer files than the prior one (got 724415 and 0 files versus 4387717)
________________________________
From: Michael Stowe <mic...@me...<mailto:mic...@me...>>
Sent: 10 January 2018 15:33
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On 2018-01-10 03:08, Marc Gilliatt wrote:
Is the following in the correct format?
$Conf{SmbShareName} = [
'audio'
]; $Conf{SmbSharePasswd} = ‘Password1’; $Conf{SmbShareUserName} = ‘backuppc’; $Conf{XferMethod} = ‘smb’; $Conf{BackupFilesOnly} = {
‘audio’ => [ '\\Archive'],
‘audio’ => [ '\\IT-Downloads'],
‘audio’ => [ '\\NI Sample Libraries'],
‘audio’ => [ '\\Impulse Responses'],
‘audio’ => [ '\\Backup'],
‘audio’ => [ '\\User Guides Installs'],
‘audio’ => [ '\\SoundsDatabase'];
}
No, Sorry, I should have provided a more complete example:
$Conf{BackupFilesOnly} = {
'audio' => [ '\\Archive',
'\\IT-Downloads',
'\\NI Sample Libraries',
'\\Impulse Responses',
'\\Backup',
'\\User Guides Installs',
'\\SoundsDatabase' ];
}
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
Bac...@li...<mailto:Bac...@li...>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
|
From: Craig B. <cba...@us...> - 2018-01-13 05:46:49
|
Marc,
What versions of BackupPC and smbclient are you using? There have been
multiple changes to the output format from smbclient, and BackupPC has only
recently caught up.
I recall from an earlier thread that you are running 3.3.1. Compatibility
with Samba 4.3 was added in BackuPC 3.3.2.
Craig
On Fri, Jan 12, 2018 at 7:42 AM, Marc Gilliatt <m.g...@li...>
wrote:
> I believe that resolved the issue, I'm no longer getting the NT_STATUS_ACCESS_DENIED
> listing \System Volume Information\SRM\*
>
> However, it still failed. I have posted the XferLOG Errors only for you.
>
> Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.bad.z, modified
> 2018-01-12 14:10:40 (Extracting only Errors)
>
> Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - \\SoundsDatabase
> full backup started for share audio
> Xfer PIDs are now 15172,15170
> [ skipped 1 lines ]
> tar:316 tarmode is now full, system, hidden, noreset, quiet
> [ skipped 734106 lines ]
> tar:712 Total bytes received: 2389181924809
> [ skipped 22 lines ]
> tarExtract: Done: 0 errors, 721209 filesExist, 2347961021801 sizeExist, 1891391027032 sizeExistComp, 724415 filesTotal, 2389184522827 sizeTotal
> Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd
> Got fatal error during xfer (No files dumped for share audio)
> Backup aborted (No files dumped for share audio)
> Not saving this as a partial backup since it has fewer files than the prior one (got 724415 and 0 files versus 4387717)
>
>
> ------------------------------
> *From:* Michael Stowe <mic...@me...>
> *Sent:* 10 January 2018 15:33
> *To:* Marc Gilliatt
> *Cc:* Developers discussion
> *Subject:* Re: [BackupPC-devel] SMB Windows share not backing up -
> NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
>
>
> On 2018-01-10 03:08, Marc Gilliatt wrote:
>
> Is the following in the correct format?
>
> $Conf{SmbShareName} = [
>
> 'audio'
>
> ]; $Conf{SmbSharePasswd} = ‘Password1’; $Conf{SmbShareUserName} =
> ‘backuppc’; $Conf{XferMethod} = ‘smb’; $Conf{BackupFilesOnly} = {
>
> ‘audio’ => [ '\\Archive'],
>
> ‘audio’ => [ '\\IT-Downloads'],
>
> ‘audio’ => [ '\\NI Sample Libraries'],
>
> ‘audio’ => [ '\\Impulse Responses'],
>
> ‘audio’ => [ '\\Backup'],
>
> ‘audio’ => [ '\\User Guides Installs'],
>
> ‘audio’ => [ '\\SoundsDatabase'];
>
> }
>
> No, Sorry, I should have provided a more complete example:
>
> $Conf{BackupFilesOnly} = {
>
> 'audio' => [ '\\Archive',
> '\\IT-Downloads',
> '\\NI Sample Libraries',
> '\\Impulse Responses',
> '\\Backup',
> '\\User Guides Installs',
> '\\SoundsDatabase' ];
> }
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-devel mailing list
> Bac...@li...
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
|
|
From: Marc G. <m.g...@li...> - 2018-01-12 15:57:40
|
I believe that resolved the issue, I'm no longer getting the NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
However, it still failed. I have posted the XferLOG Errors only for you.
Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.bad.z, modified 2018-01-12 14:10:40 (Extracting only Errors)
Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - \\SoundsDatabase
full backup started for share audio
Xfer PIDs are now 15172,15170
[ skipped 1 lines ]
tar:316 tarmode is now full, system, hidden, noreset, quiet
[ skipped 734106 lines ]
tar:712 Total bytes received: 2389181924809
[ skipped 22 lines ]
tarExtract: Done: 0 errors, 721209 filesExist, 2347961021801 sizeExist, 1891391027032 sizeExistComp, 724415 filesTotal, 2389184522827 sizeTotal
Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd
Got fatal error during xfer (No files dumped for share audio)
Backup aborted (No files dumped for share audio)
Not saving this as a partial backup since it has fewer files than the prior one (got 724415 and 0 files versus 4387717)
________________________________
From: Michael Stowe <mic...@me...>
Sent: 10 January 2018 15:33
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On 2018-01-10 03:08, Marc Gilliatt wrote:
Is the following in the correct format?
$Conf{SmbShareName} = [
'audio'
]; $Conf{SmbSharePasswd} = ‘Password1’; $Conf{SmbShareUserName} = ‘backuppc’; $Conf{XferMethod} = ‘smb’; $Conf{BackupFilesOnly} = {
‘audio’ => [ '\\Archive'],
‘audio’ => [ '\\IT-Downloads'],
‘audio’ => [ '\\NI Sample Libraries'],
‘audio’ => [ '\\Impulse Responses'],
‘audio’ => [ '\\Backup'],
‘audio’ => [ '\\User Guides Installs'],
‘audio’ => [ '\\SoundsDatabase'];
}
No, Sorry, I should have provided a more complete example:
$Conf{BackupFilesOnly} = {
'audio' => [ '\\Archive',
'\\IT-Downloads',
'\\NI Sample Libraries',
'\\Impulse Responses',
'\\Backup',
'\\User Guides Installs',
'\\SoundsDatabase' ];
}
|
|
From: Michael S. <mic...@me...> - 2018-01-10 15:33:28
|
On 2018-01-10 03:08, Marc Gilliatt wrote:
> Is the following in the correct format?
>
> $Conf{SmbShareName} = [
> 'audio'
> ];
> $Conf{SmbSharePasswd} = 'Password1';
> $Conf{SmbShareUserName} = 'backuppc';
> $Conf{XferMethod} = 'smb';
> $Conf{BackupFilesOnly} = {
>
> 'audio' => [ '\\Archive'],
>
> 'audio' => [ '\\IT-Downloads'],
>
> 'audio' => [ '\\NI Sample Libraries'],
>
> 'audio' => [ '\\Impulse Responses'],
>
> 'audio' => [ '\\Backup'],
>
> 'audio' => [ '\\User Guides Installs'],
>
> 'audio' => [ '\\SoundsDatabase'];
>
> }
>
No, Sorry, I should have provided a more complete example:
$Conf{BackupFilesOnly} = {
'audio' => [ '\\Archive',
'\\IT-Downloads',
'\\NI Sample Libraries',
'\\Impulse Responses',
'\\Backup',
'\\User Guides Installs',
'\\SoundsDatabase' ];
}
|
|
From: Marc G. <m.g...@li...> - 2018-01-10 11:24:02
|
Is the following in the correct format?
$Conf{SmbShareName} = [
'audio'
];
$Conf{SmbSharePasswd} = 'Password1';
$Conf{SmbShareUserName} = 'backuppc';
$Conf{XferMethod} = 'smb';
$Conf{BackupFilesOnly} = {
'audio' => [ '\\Archive'],
'audio' => [ '\\IT-Downloads'],
'audio' => [ '\\NI Sample Libraries'],
'audio' => [ '\\Impulse Responses'],
'audio' => [ '\\Backup'],
'audio' => [ '\\User Guides Installs'],
'audio' => [ '\\SoundsDatabase'];
}
________________________________
From: Michael Stowe <mic...@me...>
Sent: 09 January 2018 17:34
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On Jan 9, 2018, at 8:01 AM, Marc Gilliatt <m.g...@li...<mailto:m.g...@li...>> wrote:
Sorry, my mistake. That was the overall config file I posted, and I apologise again, I should've just posted the section regarding smb, I've put the includes in the host's config file.
$Conf{SmbShareName} = [
'audio'
];
$Conf{SmbSharePasswd} = 'Password1';
$Conf{SmbShareUserName} = 'backuppc';
$Conf{XferMethod} = 'smb';
$Conf{BackupFilesOnly} = {
'\\Archive' => [
''
],
'\\IT-Downloads' => [
''
],
'\\NI Sample Libraries' => [
''
],
'\\Impulse Responses' => [
''
],
'\\Backup' => [
''
],
'\\User Guides Installs' => [
''
],
'\\SoundsDatabase' => [
''
]
};
________________________________
Ah ha!
The way the BackupFilesOnly section is written, it says, “for the share called \Archive, backup only these files: ‘’, and so on for shares named “\IT Downloads” etc.
As there are no entries matching the share ‘audio’ it will fall back to other rules.
Try
$Conf{BackupFilesOnly} = {
‘audio’ => [ ‘\\Archive’ ] };
|
|
From: Michael S. <mic...@me...> - 2018-01-09 17:34:37
|
> On Jan 9, 2018, at 8:01 AM, Marc Gilliatt <m.g...@li...> wrote:
>
> Sorry, my mistake. That was the overall config file I posted, and I apologise again, I should've just posted the section regarding smb, I've put the includes in the host's config file.
>
> $Conf{SmbShareName} = [
> 'audio'
> ];
> $Conf{SmbSharePasswd} = 'Password1';
> $Conf{SmbShareUserName} = 'backuppc';
> $Conf{XferMethod} = 'smb';
> $Conf{BackupFilesOnly} = {
> '\\Archive' => [
> ''
> ],
> '\\IT-Downloads' => [
> ''
> ],
> '\\NI Sample Libraries' => [
> ''
> ],
> '\\Impulse Responses' => [
> ''
> ],
> '\\Backup' => [
> ''
> ],
> '\\User Guides Installs' => [
> ''
> ],
> '\\SoundsDatabase' => [
> ''
> ]
> };
>
Ah ha!
The way the BackupFilesOnly section is written, it says, “for the share called \Archive, backup only these files: ‘’, and so on for shares named “\IT Downloads” etc.
As there are no entries matching the share ‘audio’ it will fall back to other rules.
Try
$Conf{BackupFilesOnly} = {
‘audio’ => [ ‘\\Archive’ ] }; |
|
From: Marc G. <m.g...@li...> - 2018-01-09 16:01:36
|
Sorry, my mistake. That was the overall config file I posted, and I apologise again, I should've just posted the section regarding smb, I've put the includes in the host's config file.
$Conf{SmbShareName} = [
'audio'
];
$Conf{SmbSharePasswd} = 'Password1';
$Conf{SmbShareUserName} = 'backuppc';
$Conf{XferMethod} = 'smb';
$Conf{BackupFilesOnly} = {
'\\Archive' => [
''
],
'\\IT-Downloads' => [
''
],
'\\NI Sample Libraries' => [
''
],
'\\Impulse Responses' => [
''
],
'\\Backup' => [
''
],
'\\User Guides Installs' => [
''
],
'\\SoundsDatabase' => [
''
]
};
________________________________
From: Michael Stowe <mic...@me...>
Sent: 09 January 2018 15:55
To: Developers discussion
Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
On 2018-01-09 07:31, Marc Gilliatt wrote:
Ive posted to the correct mailing list.
Here are the contents to my config.pl
Right list, wrong file.
You didn't put any excludes in that one.
Also, you might want to just include the relevant parts of the file (which would be, in this case, the ones related to the SMB transport, includes and excludes.)
Given that there were no excludes in this file, it's a logical inference that they're in the machine-specific configuration file. Or they're not in any file, and your problem has been identified.
|
|
From: Michael S. <mic...@me...> - 2018-01-09 15:55:56
|
On 2018-01-09 07:31, Marc Gilliatt wrote: > Ive posted to the correct mailing list. > > Here are the contents to my config.pl Right list, wrong file. You didn't put any excludes in that one. Also, you might want to just include the relevant parts of the file (which would be, in this case, the ones related to the SMB transport, includes and excludes.) Given that there were no excludes in this file, it's a logical inference that they're in the machine-specific configuration file. Or they're not in any file, and your problem has been identified. |
|
From: Marc G. <m.g...@li...> - 2018-01-09 15:31:47
|
Ive posted to the correct mailing list. Here are the contents to my config.pl #============================================================= -*-perl-*- # # Configuration file for BackupPC. # # DESCRIPTION # # This is the main configuration file for BackupPC. # # This file must be valid perl source, so make sure the punctuation, # quotes, and other syntax are valid. # # This file is read by BackupPC at startup, when a HUP (-1) signal # is sent to BackupPC and also at each wakeup time whenever the # modification time of this file changes. # # The configuration parameters are divided into four general groups. # The first group (general server configuration) provides general # configuration for BackupPC. The next two groups describe what # to backup, when to do it, and how long to keep it. The fourth # group are settings for the CGI http interface. # # Configuration settings can also be specified on a per-PC basis. # Simply put the relevant settings in a config.pl file in the # PC's backup directory (ie: in __TOPDIR__/pc/hostName). # All configuration settings in the second, third and fourth # groups can be overridden by the per-PC config.pl file. # # AUTHOR # Craig Barratt <cba...@us...> # # COPYRIGHT # Copyright (C) 2001-2015 Craig Barratt # # See http://backuppc.sourceforge.net. # #======================================================================== ########################################################################### # General server configuration ########################################################################### # # Host name on which the BackupPC server is running. # $ENV{'PATH'} = '/bin:/usr/bin'; delete @ENV{'IFS', 'CDPATH', 'ENV', 'BASH_ENV'}; $Conf{ServerHost} = 'backuppc01'; chomp($Conf{ServerHost}); # # TCP port number on which the BackupPC server listens for and accepts # connections. Normally this should be disabled (set to -1). The TCP # port is only needed if apache runs on a different machine from BackupPC. # In that case, set this to any spare port number over 1024 (eg: 2359). # If you enable the TCP port, make sure you set $Conf{ServerMesgSecret} # too! # $Conf{ServerPort} = -1; # # Shared secret to make the TCP port secure. Set this to a hard to guess # string if you enable the TCP port (ie: $Conf{ServerPort} > 0). # # To avoid possible attacks via the TCP socket interface, every client # message is protected by an MD5 digest. The MD5 digest includes four # items: # - a seed that is sent to the client when the connection opens # - a sequence number that increments for each message # - a shared secret that is stored in $Conf{ServerMesgSecret} # - the message itself. # # The message is sent in plain text preceded by the MD5 digest. A # snooper can see the plain-text seed sent by BackupPC and plain-text # message from the client, but cannot construct a valid MD5 digest since # the secret $Conf{ServerMesgSecret} is unknown. A replay attack is # not possible since the seed changes on a per-connection and # per-message basis. # $Conf{ServerMesgSecret} = ''; # # PATH setting for BackupPC. An explicit value is necessary # for taint mode. Value shouldn't matter too much since # all execs use explicit paths. However, taint mode in perl # will complain if this directory is world writable. # $Conf{MyPath} = '/bin'; # # Permission mask for directories and files created by BackupPC. # Default value prevents any access from group other, and prevents # group write. # $Conf{UmaskMode} = 23; # # Times at which we wake up, check all the PCs, and schedule necessary # backups. Times are measured in hours since midnight. Can be # fractional if necessary (eg: 4.25 means 4:15am). # # If the hosts you are backing up are always connected to the network # you might have only one or two wakeups each night. This will keep # the backup activity after hours. On the other hand, if you are backing # up laptops that are only intermittently connected to the network you # will want to have frequent wakeups (eg: hourly) to maximize the chance # that each laptop is backed up. # # Examples: # $Conf{WakeupSchedule} = [22.5]; # once per day at 10:30 pm. # $Conf{WakeupSchedule} = [2,4,6,8,10,12,14,16,18,20,22]; # every 2 hours # # The default value is every hour except midnight. # # The first entry of $Conf{WakeupSchedule} is when BackupPC_nightly is run. # You might want to re-arrange the entries in $Conf{WakeupSchedule} # (they don't have to be ascending) so that the first entry is when # you want BackupPC_nightly to run (eg: when you don't expect a lot # of regular backups to run). # $Conf{WakeupSchedule} = [ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23 ]; # # Maximum number of simultaneous backups to run. If there # are no user backup requests then this is the maximum number # of simultaneous backups. # $Conf{MaxBackups} = 5; # # Additional number of simultaneous backups that users can run. # As many as $Conf{MaxBackups} + $Conf{MaxUserBackups} requests can # run at the same time. # $Conf{MaxUserBackups} = 5; # # Maximum number of pending link commands. New backups will only be # started if there are no more than $Conf{MaxPendingCmds} plus # $Conf{MaxBackups} number of pending link commands, plus running jobs. # This limit is to make sure BackupPC doesn't fall too far behind in # running BackupPC_link commands. # $Conf{MaxPendingCmds} = 15; # # Nice level at which CmdQueue commands (eg: BackupPC_link and # BackupPC_nightly) are run at. # $Conf{CmdQueueNice} = 10; # # How many BackupPC_nightly processes to run in parallel. # # Each night, at the first wakeup listed in $Conf{WakeupSchedule}, # BackupPC_nightly is run. Its job is to remove unneeded files # in the pool, ie: files that only have one link. To avoid race # conditions, BackupPC_nightly and BackupPC_link cannot run at # the same time. Starting in v3.0.0, BackupPC_nightly can run # concurrently with backups (BackupPC_dump). # # So to reduce the elapsed time, you might want to increase this # setting to run several BackupPC_nightly processes in parallel # (eg: 4, or even 8). # $Conf{MaxBackupPCNightlyJobs} = 5; # # How many days (runs) it takes BackupPC_nightly to traverse the # entire pool. Normally this is 1, which means every night it runs, # it does traverse the entire pool removing unused pool files. # # Other valid values are 2, 4, 8, 16. This causes BackupPC_nightly to # traverse 1/2, 1/4, 1/8 or 1/16th of the pool each night, meaning it # takes 2, 4, 8 or 16 days to completely traverse the pool. The # advantage is that each night the running time of BackupPC_nightly # is reduced roughly in proportion, since the total job is split # over multiple days. The disadvantage is that unused pool files # take longer to get deleted, which will slightly increase disk # usage. # # Note that even when $Conf{BackupPCNightlyPeriod} > 1, BackupPC_nightly # still runs every night. It just does less work each time it runs. # # Examples: # # $Conf{BackupPCNightlyPeriod} = 1; # entire pool is checked every night # # $Conf{BackupPCNightlyPeriod} = 2; # two days to complete pool check # # (different half each night) # # $Conf{BackupPCNightlyPeriod} = 4; # four days to complete pool check # # (different quarter each night) # $Conf{BackupPCNightlyPeriod} = 1; # # Maximum number of log files we keep around in log directory. # These files are aged nightly. A setting of 14 means the log # directory will contain about 2 weeks of old log files, in # particular at most the files LOG, LOG.0, LOG.1, ... LOG.13 # (except today's LOG, these files will have a .z extension if # compression is on). # # If you decrease this number after BackupPC has been running for a # while you will have to manually remove the older log files. # $Conf{MaxOldLogFiles} = 14; # # Full path to the df command. Security caution: normal users # should not allowed to write to this file or directory. # $Conf{DfPath} = '/bin/df'; # # Command to run df. The following variables are substituted at run-time: # # $dfPath path to df ($Conf{DfPath}) # $topDir top-level BackupPC data directory # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{DfCmd} = '$dfPath $topDir'; # # Full path to various commands for archiving # $Conf{SplitPath} = '/usr/bin/split'; $Conf{ParPath} = undef; $Conf{CatPath} = '/bin/cat'; $Conf{GzipPath} = '/bin/gzip'; $Conf{Bzip2Path} = '/bin/bzip2'; # # Maximum threshold for disk utilization on the __TOPDIR__ filesystem. # If the output from $Conf{DfPath} reports a percentage larger than # this number then no new regularly scheduled backups will be run. # However, user requested backups (which are usually incremental and # tend to be small) are still performed, independent of disk usage. # Also, currently running backups will not be terminated when the disk # usage exceeds this number. # $Conf{DfMaxUsagePct} = 95; # # How long BackupPC_trashClean sleeps in seconds between each check # of the trash directory. Once every 5 minutes should be reasonable. # $Conf{TrashCleanSleepSec} = 300; # # List of DHCP address ranges we search looking for PCs to backup. # This is an array of hashes for each class C address range. # This is only needed if hosts in the conf/hosts file have the # dhcp flag set. # # Examples: # # to specify 192.10.10.20 to 192.10.10.250 as the DHCP address pool # $Conf{DHCPAddressRanges} = [ # { # ipAddrBase => '192.10.10', # first => 20, # last => 250, # }, # ]; # # to specify two pools (192.10.10.20-250 and 192.10.11.10-50) # $Conf{DHCPAddressRanges} = [ # { # ipAddrBase => '192.10.10', # first => 20, # last => 250, # }, # { # ipAddrBase => '192.10.11', # first => 10, # last => 50, # }, # ]; # $Conf{DHCPAddressRanges} = []; # # The BackupPC user. # $Conf{BackupPCUser} = 'backuppc'; # # Important installation directories: # # TopDir - where all the backup data is stored # ConfDir - where the main config and hosts files resides # LogDir - where log files and other transient information # InstallDir - where the bin, lib and doc installation dirs reside. # Note: you cannot change this value since all the # perl scripts include this path. You must reinstall # with configure.pl to change InstallDir. # CgiDir - Apache CGI directory for BackupPC_Admin # # Note: it is STRONGLY recommended that you don't change the # values here. These are set at installation time and are here # for reference and are used during upgrades. # # Instead of changing TopDir here it is recommended that you use # a symbolic link to the new location, or mount the new BackupPC # store at the existing $Conf{TopDir} setting. # $Conf{TopDir} = '/var/lib/backuppc'; $Conf{ConfDir} = '/etc/backuppc'; $Conf{LogDir} = '/var/lib/backuppc/log'; $Conf{InstallDir} = '/usr/share/backuppc'; $Conf{CgiDir} = '/usr/share/backuppc/cgi-bin'; # # Whether BackupPC and the CGI script BackupPC_Admin verify that they # are really running as user $Conf{BackupPCUser}. If this flag is set # and the effective user id (euid) differs from $Conf{BackupPCUser} # then both scripts exit with an error. This catches cases where # BackupPC might be accidently started as root or the wrong user, # or if the CGI script is not installed correctly. # $Conf{BackupPCUserVerify} = '1'; # # Maximum number of hardlinks supported by the $TopDir file system # that BackupPC uses. Most linux or unix file systems should support # at least 32000 hardlinks per file, or 64000 in other cases. If a pool # file already has this number of hardlinks, a new pool file is created # so that new hardlinks can be accommodated. This limit will only # be hit if an identical file appears at least this number of times # across all the backups. # $Conf{HardLinkMax} = 31999; # # Advanced option for asking BackupPC to load additional perl modules. # Can be a list (array ref) of module names to load at startup. # $Conf{PerlModuleLoad} = undef; # # Path to init.d script and command to use that script to start the # server from the CGI interface. The following variables are substituted # at run-time: # # $sshPath path to ssh ($Conf{SshPath}) # $serverHost same as $Conf{ServerHost} # $serverInitdPath path to init.d script ($Conf{ServerInitdPath}) # # Example: # # $Conf{ServerInitdPath} = '/etc/init.d/backuppc'; # $Conf{ServerInitdStartCmd} = '$sshPath -q -x -l root $serverHost' # . ' $serverInitdPath start' # . ' < /dev/null >& /dev/null'; # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{ServerInitdPath} = undef; $Conf{ServerInitdStartCmd} = ''; ########################################################################### # What to backup and when to do it # (can be overridden in the per-PC config.pl) ########################################################################### # # Minimum period in days between full backups. A full dump will only be # done if at least this much time has elapsed since the last full dump, # and at least $Conf{IncrPeriod} days has elapsed since the last # successful dump. # # Typically this is set slightly less than an integer number of days. The # time taken for the backup, plus the granularity of $Conf{WakeupSchedule} # will make the actual backup interval a bit longer. # $Conf{FullPeriod} = '6.9'; # # Minimum period in days between incremental backups (a user requested # incremental backup will be done anytime on demand). # # Typically this is set slightly less than an integer number of days. The # time taken for the backup, plus the granularity of $Conf{WakeupSchedule} # will make the actual backup interval a bit longer. # $Conf{IncrPeriod} = '0.9'; # # Number of full backups to keep. Must be >= 1. # # In the steady state, each time a full backup completes successfully # the oldest one is removed. If this number is decreased, the # extra old backups will be removed. # # If filling of incremental dumps is off the oldest backup always # has to be a full (ie: filled) dump. This might mean one or two # extra full dumps are kept until the oldest incremental backups expire. # # Exponential backup expiry is also supported. This allows you to specify: # # - num fulls to keep at intervals of 1 * $Conf{FullPeriod}, followed by # - num fulls to keep at intervals of 2 * $Conf{FullPeriod}, # - num fulls to keep at intervals of 4 * $Conf{FullPeriod}, # - num fulls to keep at intervals of 8 * $Conf{FullPeriod}, # - num fulls to keep at intervals of 16 * $Conf{FullPeriod}, # # and so on. This works by deleting every other full as each expiry # boundary is crossed. # # Exponential expiry is specified using an array for $Conf{FullKeepCnt}: # # $Conf{FullKeepCnt} = [4, 2, 3]; # # Entry #n specifies how many fulls to keep at an interval of # 2^n * $Conf{FullPeriod} (ie: 1, 2, 4, 8, 16, 32, ...). # # The example above specifies keeping 4 of the most recent full backups # (1 week interval) two full backups at 2 week intervals, and 3 full # backups at 4 week intervals, eg: # # full 0 19 weeks old \ # full 1 15 weeks old >--- 3 backups at 4 * $Conf{FullPeriod} # full 2 11 weeks old / # full 3 7 weeks old \____ 2 backups at 2 * $Conf{FullPeriod} # full 4 5 weeks old / # full 5 3 weeks old \ # full 6 2 weeks old \___ 4 backups at 1 * $Conf{FullPeriod} # full 7 1 week old / # full 8 current / # # On a given week the spacing might be less than shown as each backup # ages through each expiry period. For example, one week later, a # new full is completed and the oldest is deleted, giving: # # full 0 16 weeks old \ # full 1 12 weeks old >--- 3 backups at 4 * $Conf{FullPeriod} # full 2 8 weeks old / # full 3 6 weeks old \____ 2 backups at 2 * $Conf{FullPeriod} # full 4 4 weeks old / # full 5 3 weeks old \ # full 6 2 weeks old \___ 4 backups at 1 * $Conf{FullPeriod} # full 7 1 week old / # full 8 current / # # You can specify 0 as a count (except in the first entry), and the # array can be as long as you wish. For example: # # $Conf{FullKeepCnt} = [4, 0, 4, 0, 0, 2]; # # This will keep 10 full dumps, 4 most recent at 1 * $Conf{FullPeriod}, # followed by 4 at an interval of 4 * $Conf{FullPeriod} (approx 1 month # apart), and then 2 at an interval of 32 * $Conf{FullPeriod} (approx # 7-8 months apart). # # Example: these two settings are equivalent and both keep just # the four most recent full dumps: # # $Conf{FullKeepCnt} = 4; # $Conf{FullKeepCnt} = [4]; # $Conf{FullKeepCnt} = [ 1 ]; # # Very old full backups are removed after $Conf{FullAgeMax} days. However, # we keep at least $Conf{FullKeepCntMin} full backups no matter how old # they are. # # Note that $Conf{FullAgeMax} will be increased to $Conf{FullKeepCnt} # times $Conf{FullPeriod} if $Conf{FullKeepCnt} specifies enough # full backups to exceed $Conf{FullAgeMax}. # $Conf{FullKeepCntMin} = 1; $Conf{FullAgeMax} = 90; # # Number of incremental backups to keep. Must be >= 1. # # In the steady state, each time an incr backup completes successfully # the oldest one is removed. If this number is decreased, the # extra old backups will be removed. # $Conf{IncrKeepCnt} = 6; # # Very old incremental backups are removed after $Conf{IncrAgeMax} days. # However, we keep at least $Conf{IncrKeepCntMin} incremental backups no # matter how old they are. # $Conf{IncrKeepCntMin} = 1; $Conf{IncrAgeMax} = 30; # # Level of each incremental. "Level" follows the terminology # of dump(1). A full backup has level 0. A new incremental # of level N will backup all files that have changed since # the most recent backup of a lower level. # # The entries of $Conf{IncrLevels} apply in order to each # incremental after each full backup. It wraps around until # the next full backup. For example, these two settings # have the same effect: # # $Conf{IncrLevels} = [1, 2, 3]; # $Conf{IncrLevels} = [1, 2, 3, 1, 2, 3]; # # This means the 1st and 4th incrementals (level 1) go all # the way back to the full. The 2nd and 3rd (and 5th and # 6th) backups just go back to the immediate preceeding # incremental. # # Specifying a sequence of multi-level incrementals will # usually mean more than $Conf{IncrKeepCnt} incrementals will # need to be kept, since lower level incrementals are needed # to merge a complete view of a backup. For example, with # # $Conf{FullPeriod} = 7; # $Conf{IncrPeriod} = 1; # $Conf{IncrKeepCnt} = 6; # $Conf{IncrLevels} = [1, 2, 3, 4, 5, 6]; # # there will be up to 11 incrementals in this case: # # backup #0 (full, level 0, oldest) # backup #1 (incr, level 1) # backup #2 (incr, level 2) # backup #3 (incr, level 3) # backup #4 (incr, level 4) # backup #5 (incr, level 5) # backup #6 (incr, level 6) # backup #7 (full, level 0) # backup #8 (incr, level 1) # backup #9 (incr, level 2) # backup #10 (incr, level 3) # backup #11 (incr, level 4) # backup #12 (incr, level 5, newest) # # Backup #1 (the oldest level 1 incremental) can't be deleted # since backups 2..6 depend on it. Those 6 incrementals can't # all be deleted since that would only leave 5 (#8..12). # When the next incremental happens (level 6), the complete # set of 6 older incrementals (#1..6) will be deleted, since # that maintains the required number ($Conf{IncrKeepCnt}) # of incrementals. This situation is reduced if you set # shorter chains of multi-level incrementals, eg: # # $Conf{IncrLevels} = [1, 2, 3]; # # would only have up to 2 extra incremenals before all 3 # are deleted. # # BackupPC as usual merges the full and the sequence # of incrementals together so each incremental can be # browsed and restored as though it is a complete backup. # If you specify a long chain of incrementals then more # backups need to be merged when browsing, restoring, # or getting the starting point for rsync backups. # In the example above (levels 1..6), browing backup # #6 requires 7 different backups (#0..6) to be merged. # # Because of this merging and the additional incrementals # that need to be kept, it is recommended that some # level 1 incrementals be included in $Conf{IncrLevels}. # # Prior to version 3.0 incrementals were always level 1, # meaning each incremental backed up all the files that # changed since the last full. # $Conf{IncrLevels} = [ 1 ]; # # Disable all full and incremental backups. These settings are # useful for a client that is no longer being backed up # (eg: a retired machine), but you wish to keep the last # backups available for browsing or restoring to other machines. # # There are three values for $Conf{BackupsDisable}: # # 0 Backups are enabled. # # 1 Don't do any regular backups on this client. Manually # requested backups (via the CGI interface) will still occur. # # 2 Don't do any backups on this client. Manually requested # backups (via the CGI interface) will be ignored. # # In versions prior to 3.0 Backups were disabled by setting # $Conf{FullPeriod} to -1 or -2. # $Conf{BackupsDisable} = 0; # # A failed full backup is saved as a partial backup. The rsync # XferMethod can take advantage of the partial full when the next # backup is run. This parameter sets the age of the partial full # in days: if the partial backup is older than this number of # days, then rsync will ignore (not use) the partial full when # the next backup is run. If you set this to a negative value # then no partials will be saved. If you set this to 0, partials # will be saved, but will not be used by the next backup. # # The default setting of 3 days means that a partial older than # 3 days is ignored when the next full backup is done. # $Conf{PartialAgeMax} = 3; # # Whether incremental backups are filled. "Filling" means that the # most recent full (or filled) dump is merged into the new incremental # dump using hardlinks. This makes an incremental dump look like a # full dump. Prior to v1.03 all incremental backups were filled. # In v1.4.0 and later the default is off. # # BackupPC, and the cgi interface in particular, do the right thing on # un-filled incremental backups. It will correctly display the merged # incremental backup with the most recent filled backup, giving the # un-filled incremental backups a filled appearance. That means it # invisible to the user whether incremental dumps are filled or not. # # Filling backups takes a little extra disk space, and it does cost # some extra disk activity for filling, and later removal. Filling # is no longer useful, since file mangling and compression doesn't # make a filled backup very useful. It's likely the filling option # will be removed from future versions: filling will be delegated to # the display and extraction of backup data. # # If filling is off, BackupPC makes sure that the oldest backup is # a full, otherwise the following incremental backups will be # incomplete. This might mean an extra full backup has to be # kept until the following incremental backups expire. # # The default is off. You can turn this on or off at any # time without affecting existing backups. # $Conf{IncrFill} = '0'; # # Number of restore logs to keep. BackupPC remembers information about # each restore request. This number per client will be kept around before # the oldest ones are pruned. # # Note: files/dirs delivered via Zip or Tar downloads don't count as # restores. Only the first restore option (where the files and dirs # are written to the host) count as restores that are logged. # $Conf{RestoreInfoKeepCnt} = 10; # # Number of archive logs to keep. BackupPC remembers information # about each archive request. This number per archive client will # be kept around before the oldest ones are pruned. # $Conf{ArchiveInfoKeepCnt} = 10; # # List of directories or files to backup. If this is defined, only these # directories or files will be backed up. # # When editing from the web interface, you should add a valid ShareName # (based on $Conf{XferMethod}), and then enter the directories specific # to that ShareName. A special ShareName "*" matches any ShareName that # doesn't have an explicit entry. # # For Smb, only one of $Conf{BackupFilesExclude} and $Conf{BackupFilesOnly} # can be specified per share. If both are set for a particular share, then # $Conf{BackupFilesOnly} takes precedence and $Conf{BackupFilesExclude} # is ignored. # # This can be set to a string, an array of strings, or, in the case # of multiple shares, a hash of strings or arrays. A hash is used # to give a list of directories or files to backup for each share # (the share name is the key). If this is set to just a string or # array, and $Conf{SmbShareName} contains multiple share names, then # the setting is assumed to apply all shares. # # If a hash is used, a special key "*" means it applies to all # shares that don't have a specific entry. # # Examples: # $Conf{BackupFilesOnly} = '/myFiles'; # $Conf{BackupFilesOnly} = ['/myFiles']; # same as first example # $Conf{BackupFilesOnly} = ['/myFiles', '/important']; # $Conf{BackupFilesOnly} = { # 'c' => ['/myFiles', '/important'], # these are for 'c' share # 'd' => ['/moreFiles', '/archive'], # these are for 'd' share # }; # $Conf{BackupFilesOnly} = { # 'c' => ['/myFiles', '/important'], # these are for 'c' share # '*' => ['/myFiles', '/important'], # these are other shares # }; # $Conf{BackupFilesOnly} = {}; # # List of directories or files to exclude from the backup. For Smb, # only one of $Conf{BackupFilesExclude} and $Conf{BackupFilesOnly} # can be specified per share. If both are set for a particular share, # then $Conf{BackupFilesOnly} takes precedence and # $Conf{BackupFilesExclude} is ignored. # # When editing from the web interface, you should add a valid ShareName # (based on $Conf{XferMethod}), and then enter the directories or files # specific to that ShareName. A special ShareName "*" matches any # ShareName that doesn't have an explicit entry. # # This can be set to a string, an array of strings, or, in the case # of multiple shares, a hash of strings or arrays. A hash is used # to give a list of directories or files to exclude for each share # (the share name is the key). If this is set to just a string or # array, and $Conf{SmbShareName} contains multiple share names, then # the setting is assumed to apply to all shares. # # The exact behavior is determined by the underlying transport program, # smbclient or tar. For smbclient the exlclude file list is passed into # the X option. Simple shell wild-cards using "*" or "?" are allowed. # # For tar, if the exclude file contains a "/" it is assumed to be anchored # at the start of the string. Since all the tar paths start with "./", # BackupPC prepends a "." if the exclude file starts with a "/". Note # that GNU tar version >= 1.13.7 is required for the exclude option to # work correctly. For linux or unix machines you should add # "/proc" to $Conf{BackupFilesExclude} unless you have specified # --one-file-system in $Conf{TarClientCmd} or --one-file-system in # $Conf{RsyncArgs}. Also, for tar, do not use a trailing "/" in # the directory name: a trailing "/" causes the name to not match # and the directory will not be excluded. # # Users report that for smbclient you should specify a directory # followed by "/*", eg: "/proc/*", instead of just "/proc". # # FTP servers are traversed recursively so excluding directories will # also exclude its contents. You can use the wildcard characters "*" # and "?" to define files for inclusion and exclusion. Both # attributes $Conf{BackupFilesOnly} and $Conf{BackupFilesExclude} can # be defined for the same share. # # If a hash is used, a special key "*" means it applies to all # shares that don't have a specific entry. # # Examples: # $Conf{BackupFilesExclude} = '/temp'; # $Conf{BackupFilesExclude} = ['/temp']; # same as first example # $Conf{BackupFilesExclude} = ['/temp', '/winnt/tmp']; # $Conf{BackupFilesExclude} = { # 'c' => ['/temp', '/winnt/tmp'], # these are for 'c' share # 'd' => ['/junk', '/dont_back_this_up'], # these are for 'd' share # }; # $Conf{BackupFilesExclude} = { # 'c' => ['/temp', '/winnt/tmp'], # these are for 'c' share # '*' => ['/junk', '/dont_back_this_up'], # these are for other shares # }; # $Conf{BackupFilesExclude} = {}; # # PCs that are always or often on the network can be backed up after # hours, to reduce PC, network and server load during working hours. For # each PC a count of consecutive good pings is maintained. Once a PC has # at least $Conf{BlackoutGoodCnt} consecutive good pings it is subject # to "blackout" and not backed up during hours and days specified by # $Conf{BlackoutPeriods}. # # To allow for periodic rebooting of a PC or other brief periods when a # PC is not on the network, a number of consecutive bad pings is allowed # before the good ping count is reset. This parameter is # $Conf{BlackoutBadPingLimit}. # # Note that bad and good pings don't occur with the same interval. If a # machine is always on the network, it will only be pinged roughly once # every $Conf{IncrPeriod} (eg: once per day). So a setting for # $Conf{BlackoutGoodCnt} of 7 means it will take around 7 days for a # machine to be subject to blackout. On the other hand, if a ping is # failed, it will be retried roughly every time BackupPC wakes up, eg, # every one or two hours. So a setting for $Conf{BlackoutBadPingLimit} of # 3 means that the PC will lose its blackout status after 3-6 hours of # unavailability. # # To disable the blackout feature set $Conf{BlackoutGoodCnt} to a negative # value. A value of 0 will make all machines subject to blackout. But # if you don't want to do any backups during the day it would be easier # to just set $Conf{WakeupSchedule} to a restricted schedule. # $Conf{BlackoutBadPingLimit} = 3; $Conf{BlackoutGoodCnt} = 1; # # One or more blackout periods can be specified. If a client is # subject to blackout then no regular (non-manual) backups will # be started during any of these periods. hourBegin and hourEnd # specify hours fro midnight and weekDays is a list of days of # the week where 0 is Sunday, 1 is Monday etc. # # For example: # # $Conf{BlackoutPeriods} = [ # { # hourBegin => 7.0, # hourEnd => 19.5, # weekDays => [1, 2, 3, 4, 5], # }, # ]; # # specifies one blackout period from 7:00am to 7:30pm local time # on Mon-Fri. # # The blackout period can also span midnight by setting # hourBegin > hourEnd, eg: # # $Conf{BlackoutPeriods} = [ # { # hourBegin => 7.0, # hourEnd => 19.5, # weekDays => [1, 2, 3, 4, 5], # }, # { # hourBegin => 23, # hourEnd => 5, # weekDays => [5, 6], # }, # ]; # # This specifies one blackout period from 7:00am to 7:30pm local time # on Mon-Fri, and a second period from 11pm to 5am on Friday and # Saturday night. # $Conf{BlackoutPeriods} = [ { 'hourEnd' => 20, 'weekDays' => [ 0, 1, 2, 3, 4, 5, 6 ], 'hourBegin' => 7 } ]; # # A backup of a share that has zero files is considered fatal. This is # used to catch miscellaneous Xfer errors that result in no files being # backed up. If you have shares that might be empty (and therefore an # empty backup is valid) you should set this flag to 0. # $Conf{BackupZeroFilesIsFatal} = '1'; ########################################################################### # How to backup a client # (can be overridden in the per-PC config.pl) ########################################################################### # # What transport method to use to backup each host. If you have # a mixed set of WinXX and linux/unix hosts you will need to override # this in the per-PC config.pl. # # The valid values are: # # - 'smb': backup and restore via smbclient and the SMB protocol. # Easiest choice for WinXX. # # - 'rsync': backup and restore via rsync (via rsh or ssh). # Best choice for linux/unix. Good choice also for WinXX. # # - 'rsyncd': backup and restore via rsync daemon on the client. # Best choice for linux/unix if you have rsyncd running on # the client. Good choice also for WinXX. # # - 'tar': backup and restore via tar, tar over ssh, rsh or nfs. # Good choice for linux/unix. # # - 'archive': host is a special archive host. Backups are not done. # An archive host is used to archive other host's backups # to permanent media, such as tape, CDR or DVD. # # $Conf{XferMethod} = 'rsync'; # # Level of verbosity in Xfer log files. 0 means be quiet, 1 will give # will give one line per file, 2 will also show skipped files on # incrementals, higher values give more output. # $Conf{XferLogLevel} = 1; # # Filename charset encoding on the client. BackupPC uses utf8 # on the server for filename encoding. If this is empty, then # utf8 is assumed and client filenames will not be modified. # If set to a different encoding then filenames will converted # to/from utf8 automatically during backup and restore. # # If the file names displayed in the browser (eg: accents or special # characters) don't look right then it is likely you haven't set # $Conf{ClientCharset} correctly. # # If you are using smbclient on a WinXX machine, smbclient will convert # to the "unix charset" setting in smb.conf. The default is utf8, # in which case leave $Conf{ClientCharset} empty since smbclient does # the right conversion. # # If you are using rsync on a WinXX machine then it does no conversion. # A typical WinXX encoding for latin1/western europe is 'cp1252', # so in this case set $Conf{ClientCharset} to 'cp1252'. # # On a linux or unix client, run "locale charmap" to see the client's # charset. Set $Conf{ClientCharset} to this value. A typical value # for english/US is 'ISO-8859-1'. # # Do "perldoc Encode::Supported" to see the list of possible charset # values. The FAQ at http://www.cl.cam.ac.uk/~mgk25/unicode.html # is excellent, and http://czyborra.com/charsets/iso8859.html # provides more information on the iso-8859 charsets. # $Conf{ClientCharset} = ''; # # Prior to 3.x no charset conversion was done by BackupPC. Backups were # stored in what ever charset the XferMethod provided - typically utf8 # for smbclient and the client's locale settings for rsync and tar (eg: # cp1252 for rsync on WinXX and perhaps iso-8859-1 with rsync on linux). # This setting tells BackupPC the charset that was used to store file # names in old backups taken with BackupPC 2.x, so that non-ascii file # names in old backups can be viewed and restored. # $Conf{ClientCharsetLegacy} = 'iso-8859-1'; ########################################################################### # Samba Configuration # (can be overwritten in the per-PC log file) ########################################################################### # # Name of the host share that is backed up when using SMB. This can be a # string or an array of strings if there are multiple shares per host. # Examples: # # $Conf{SmbShareName} = 'c'; # backup 'c' share # $Conf{SmbShareName} = ['c', 'd']; # backup 'c' and 'd' shares # # This setting only matters if $Conf{XferMethod} = 'smb'. # $Conf{SmbShareName} = [ 'C$' ]; # # Smbclient share user name. This is passed to smbclient's -U argument. # # This setting only matters if $Conf{XferMethod} = 'smb'. # $Conf{SmbShareUserName} = ''; # # Smbclient share password. This is passed to smbclient via its PASSWD # environment variable. There are several ways you can tell BackupPC # the smb share password. In each case you should be very careful about # security. If you put the password here, make sure that this file is # not readable by regular users! See the "Setting up config.pl" section # in the documentation for more information. # # This setting only matters if $Conf{XferMethod} = 'smb'. # $Conf{SmbSharePasswd} = ''; # # Full path for smbclient. Security caution: normal users should not # allowed to write to this file or directory. # # smbclient is from the Samba distribution. smbclient is used to # actually extract the incremental or full dump of the share filesystem # from the PC. # # This setting only matters if $Conf{XferMethod} = 'smb'. # $Conf{SmbClientPath} = '/usr/bin/smbclient'; # # Command to run smbclient for a full dump. # This setting only matters if $Conf{XferMethod} = 'smb'. # # The following variables are substituted at run-time: # # $smbClientPath same as $Conf{SmbClientPath} # $host host to backup/restore # $hostIP host IP address # $shareName share name # $userName user name # $fileList list of files to backup (based on exclude/include) # $I_option optional -I option to smbclient # $X_option exclude option (if $fileList is an exclude list) # $timeStampFile start time for incremental dump # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{SmbClientFullCmd} = '$smbClientPath \\\\$host\\$shareName $I_option -U $userName -E -d 1 -c tarmode\\ full -Tc$X_option - $fileList'; # # Command to run smbclient for an incremental dump. # This setting only matters if $Conf{XferMethod} = 'smb'. # # Same variable substitutions are applied as $Conf{SmbClientFullCmd}. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{SmbClientIncrCmd} = '$smbClientPath \\\\$host\\$shareName $I_option -U $userName -E -d 1 -c tarmode\\ full -TcN$X_option $timeStampFile - $fileList'; # # Command to run smbclient for a restore. # This setting only matters if $Conf{XferMethod} = 'smb'. # # Same variable substitutions are applied as $Conf{SmbClientFullCmd}. # # If your smb share is read-only then direct restores will fail. # You should set $Conf{SmbClientRestoreCmd} to undef and the # corresponding CGI restore option will be removed. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{SmbClientRestoreCmd} = '$smbClientPath \\\\$host\\$shareName $I_option -U $userName -E -d 1 -c tarmode\\ full -Tx -'; ########################################################################### # Tar Configuration # (can be overwritten in the per-PC log file) ########################################################################### # # Which host directories to backup when using tar transport. This can be a # string or an array of strings if there are multiple directories to # backup per host. Examples: # # $Conf{TarShareName} = '/'; # backup everything # $Conf{TarShareName} = '/home'; # only backup /home # $Conf{TarShareName} = ['/home', '/src']; # backup /home and /src # # The fact this parameter is called 'TarShareName' is for historical # consistency with the Smb transport options. You can use any valid # directory on the client: there is no need for it to correspond to # any Smb share or device mount point. # # Note also that you can also use $Conf{BackupFilesOnly} to specify # a specific list of directories to backup. It's more efficient to # use this option instead of $Conf{TarShareName} since a new tar is # run for each entry in $Conf{TarShareName}. # # On the other hand, if you add --one-file-system to $Conf{TarClientCmd} # you can backup each file system separately, which makes restoring one # bad file system easier. In this case you would list all of the mount # points here, since you can't get the same result with # $Conf{BackupFilesOnly}: # # $Conf{TarShareName} = ['/', '/var', '/data', '/boot']; # # This setting only matters if $Conf{XferMethod} = 'tar'. # $Conf{TarShareName} = [ '/' ]; # # Command to run tar on the client. GNU tar is required. You will # need to fill in the correct paths for ssh2 on the local host (server) # and GNU tar on the client. Security caution: normal users should not # allowed to write to these executable files or directories. # # $Conf{TarClientCmd} is appended with with either $Conf{TarFullArgs} or # $Conf{TarIncrArgs} to create the final command that is run. # # See the documentation for more information about setting up ssh2 keys. # # If you plan to use NFS then tar just runs locally and ssh2 is not needed. # For example, assuming the client filesystem is mounted below /mnt/hostName, # you could use something like: # # $Conf{TarClientCmd} = '$tarPath -c -v -f - -C /mnt/$host/$shareName' # . ' --totals'; # # In the case of NFS or rsh you need to make sure BackupPC's privileges # are sufficient to read all the files you want to backup. Also, you # will probably want to add "/proc" to $Conf{BackupFilesExclude}. # # The following variables are substituted at run-time: # # $host host name # $hostIP host's IP address # $incrDate newer-than date for incremental backups # $shareName share name to backup (ie: top-level directory path) # $fileList specific files to backup or exclude # $tarPath same as $Conf{TarClientPath} # $sshPath same as $Conf{SshPath} # # If a variable is followed by a "+" it is shell escaped. This is # necessary for the command part of ssh or rsh, since it ends up # getting passed through the shell. # # This setting only matters if $Conf{XferMethod} = 'tar'. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{TarClientCmd} = '$sshPath -q -x -n -l root $host env LC_ALL=C $tarPath -c -v -f - -C $shareName+ --totals'; # # Extra tar arguments for full backups. Several variables are substituted at # run-time. See $Conf{TarClientCmd} for the list of variable substitutions. # # If you are running tar locally (ie: without rsh or ssh) then remove the # "+" so that the argument is no longer shell escaped. # # This setting only matters if $Conf{XferMethod} = 'tar'. # $Conf{TarFullArgs} = '$fileList+'; # # Extra tar arguments for incr backups. Several variables are substituted at # run-time. See $Conf{TarClientCmd} for the list of variable substitutions. # # Note that GNU tar has several methods for specifying incremental backups, # including: # # --newer-mtime $incrDate+ # This causes a file to be included if the modification time is # later than $incrDate (meaning its contents might have changed). # But changes in the ownership or modes will not qualify the # file to be included in an incremental. # # --newer=$incrDate+ # This causes the file to be included if any attribute of the # file is later than $incrDate, meaning either attributes or # the modification time. This is the default method. Do # not use --atime-preserve in $Conf{TarClientCmd} above, # otherwise resetting the atime (access time) counts as an # attribute change, meaning the file will always be included # in each new incremental dump. # # If you are running tar locally (ie: without rsh or ssh) then remove the # "+" so that the argument is no longer shell escaped. # # This setting only matters if $Conf{XferMethod} = 'tar'. # $Conf{TarIncrArgs} = '--newer=$incrDate+ $fileList+'; # # Full command to run tar for restore on the client. GNU tar is required. # This can be the same as $Conf{TarClientCmd}, with tar's -c replaced by -x # and ssh's -n removed. # # See $Conf{TarClientCmd} for full details. # # This setting only matters if $Conf{XferMethod} = "tar". # # If you want to disable direct restores using tar, you should set # $Conf{TarClientRestoreCmd} to undef and the corresponding CGI # restore option will be removed. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{TarClientRestoreCmd} = '$sshPath -q -x -l root $host env LC_ALL=C $tarPath -x -p --numeric-owner --same-owner -v -f - -C $shareName+'; # # Full path for tar on the client. Security caution: normal users should not # allowed to write to this file or directory. # # This setting only matters if $Conf{XferMethod} = 'tar'. # $Conf{TarClientPath} = '/bin/tar'; ########################################################################### # Rsync/Rsyncd Configuration # (can be overwritten in the per-PC log file) ########################################################################### # # Path to rsync executable on the client # $Conf{RsyncClientPath} = '/usr/bin/rsync'; # # Full command to run rsync on the client machine. The following variables # are substituted at run-time: # # $host host name being backed up # $hostIP host's IP address # $shareName share name to backup (ie: top-level directory path) # $rsyncPath same as $Conf{RsyncClientPath} # $sshPath same as $Conf{SshPath} # $argList argument list, built from $Conf{RsyncArgs}, # $shareName, $Conf{BackupFilesExclude} and # $Conf{BackupFilesOnly} # # This setting only matters if $Conf{XferMethod} = 'rsync'. # $Conf{RsyncClientCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+'; # # Full command to run rsync for restore on the client. The following # variables are substituted at run-time: # # $host host name being backed up # $hostIP host's IP address # $shareName share name to backup (ie: top-level directory path) # $rsyncPath same as $Conf{RsyncClientPath} # $sshPath same as $Conf{SshPath} # $argList argument list, built from $Conf{RsyncArgs}, # $shareName, $Conf{BackupFilesExclude} and # $Conf{BackupFilesOnly} # # This setting only matters if $Conf{XferMethod} = 'rsync'. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{RsyncClientRestoreCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+'; # # Share name to backup. For $Conf{XferMethod} = "rsync" this should # be a file system path, eg '/' or '/home'. # # For $Conf{XferMethod} = "rsyncd" this should be the name of the module # to backup (ie: the name from /etc/rsynd.conf). # # This can also be a list of multiple file system paths or modules. # For example, by adding --one-file-system to $Conf{RsyncArgs} you # can backup each file system separately, which makes restoring one # bad file system easier. In this case you would list all of the mount # points: # # $Conf{RsyncShareName} = ['/', '/var', '/data', '/boot']; # $Conf{RsyncShareName} = [ '/' ]; # # Rsync daemon port on the client, for $Conf{XferMethod} = "rsyncd". # $Conf{RsyncdClientPort} = 873; # # Rsync daemon user name on client, for $Conf{XferMethod} = "rsyncd". # The user name and password are stored on the client in whatever file # the "secrets file" parameter in rsyncd.conf points to # (eg: /etc/rsyncd.secrets). # $Conf{RsyncdUserName} = ''; # # Rsync daemon user name on client, for $Conf{XferMethod} = "rsyncd". # The user name and password are stored on the client in whatever file # the "secrets file" parameter in rsyncd.conf points to # (eg: /etc/rsyncd.secrets). # $Conf{RsyncdPasswd} = ''; # # Whether authentication is mandatory when connecting to the client's # rsyncd. By default this is on, ensuring that BackupPC will refuse to # connect to an rsyncd on the client that is not password protected. # Turn off at your own risk. # $Conf{RsyncdAuthRequired} = '1'; # # When rsync checksum caching is enabled (by adding the # --checksum-seed=32761 option to $Conf{RsyncArgs}), the cached # checksums can be occasionally verified to make sure the file # contents matches the cached checksums. This is to avoid the # risk that disk problems might cause the pool file contents to # get corrupted, but the cached checksums would make BackupPC # think that the file still matches the client. # # This setting is the probability (0 means never and 1 means always) # that a file will be rechecked. Setting it to 0 means the checksums # will not be rechecked (unless there is a phase 0 failure). Setting # it to 1 (ie: 100%) means all files will be checked, but that is # not a desirable setting since you are better off simply turning # caching off (ie: remove the --checksum-seed option). # # The default of 0.01 means 1% (on average) of the files during a full # backup will have their cached checksum re-checked. # # This setting has no effect unless checksum caching is turned on. # $Conf{RsyncCsumCacheVerifyProb} = '0.01'; # # Arguments to rsync for backup. Do not edit the first set unless you # have a thorough understanding of how File::RsyncP works. # $Conf{RsyncArgs} = [ '--numeric-ids', '--perms', '--owner', '--group', '-D', '--links', '--hard-links', '--times', '--block-size=2048', '--recursive' ]; # # Additional arguments added to RsyncArgs. This can be used in # conbination with $Conf{RsyncArgs} to allow customization of # the rsync arguments on a part-client basis. The standard # arguments go in $Conf{RsyncArgs} and $Conf{RsyncArgsExtra} # can be set on a per-client basis. # # Examples of additional arguments that should work are --exclude/--include, # eg: # # $Conf{RsyncArgsExtra} = [ # '--exclude', '/proc', # '--exclude', '*.tmp', # ]; # # Both $Conf{RsyncArgs} and $Conf{RsyncArgsExtra} are subject # to the following variable substitutions: # # $client client name being backed up # $host host name (could be different from client name if # $Conf{ClientNameAlias} is set) # $hostIP IP address of host # $confDir configuration directory path # # This allows settings of the form: # # $Conf{RsyncArgsExtra} = [ # '--exclude-from=$confDir/pc/$host.exclude', # ]; # $Conf{RsyncArgsExtra} = [ '--one-file-system', '' ]; # # Arguments to rsync for restore. Do not edit the first set unless you # have a thorough understanding of how File::RsyncP works. # # If you want to disable direct restores using rsync (eg: is the module # is read-only), you should set $Conf{RsyncRestoreArgs} to undef and # the corresponding CGI restore option will be removed. # # $Conf{RsyncRestoreArgs} is subject to the following variable # substitutions: # # $client client name being backed up # $host host name (could be different from client name if # $Conf{ClientNameAlias} is set) # $hostIP IP address of host # $confDir configuration directory path # # Note: $Conf{RsyncArgsExtra} doesn't apply to $Conf{RsyncRestoreArgs}. # $Conf{RsyncRestoreArgs} = [ '--numeric-ids', '--perms', '--owner', '--group', '-D', '--links', '--hard-links', '--times', '--block-size=2048', '--relative', '--ignore-times', '--recursive' ]; ########################################################################### # FTP Configuration # (can be overwritten in the per-PC log file) ########################################################################## # # Which host directories to backup when using FTP. This can be a # string or an array of strings if there are multiple shares per host. # # This value must be specified in one of two ways: either as a # subdirectory of the 'share root' on the server, or as the absolute # path of the directory. # # In the following example, if the directory /home/username is the # root share of the ftp server with the given username, the following # two values will back up the same directory: # # $Conf{FtpShareName} = 'www'; # www directory # $Conf{FtpShareName} = '/home/username/www'; # same directory # # Path resolution is not supported; i.e.; you may not have an ftp # share path defined as '../otheruser' or '~/games'. # # Multiple shares may also be specified, as with other protocols: # # $Conf{FtpShareName} = [ 'www', # 'bin', # 'config' ]; # # Note also that you can also use $Conf{BackupFilesOnly} to specify # a specific list of directories to backup. It's more efficient to # use this option instead of $Conf{FtpShareName} since a new tar is # run for each entry in $Conf{FtpShareName}. # # This setting only matters if $Conf{XferMethod} = 'ftp'. # $Conf{FtpShareName} = [ '' ]; # # FTP user name. This is used to log into the server. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # $Conf{FtpUserName} = ''; # # FTP user password. This is used to log into the server. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # $Conf{FtpPasswd} = ''; # # Whether passive mode is used. The correct setting depends upon # whether local or remote ports are accessible from the other machine, # which is affected by any firewall or routers between the FTP server # on the client and the BackupPC server. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # $Conf{FtpPassive} = '1'; # # Transfer block size. This sets the size of the amounts of data in # each frame. While undefined, this value takes the default value. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # $Conf{FtpBlockSize} = 10240; # # The port of the ftp server. If undefined, 21 is used. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # $Conf{FtpPort} = 21; # # Connection timeout for FTP. When undefined, the default is 120 seconds. # # This setting is used only if $Conf{XferMethod} = 'ftp'. # #$Conf{FtpTimeout} = 120; $Conf{FtpTimeout} = 240; # # Behaviour when BackupPC encounters symlinks on the FTP share. # # Symlinks cannot be restored via FTP, so the desired behaviour will # be different depending on the setup of the share. The default for # this behavor is 1. Directory shares with more complicated directory # structures should consider other protocols. # $Conf{FtpFollowSymlinks} = '0'; ########################################################################### # Archive Configuration # (can be overwritten in the per-PC log file) ########################################################################### # # Archive Destination # # The Destination of the archive # e.g. /tmp for file archive or /dev/nst0 for device archive # $Conf{ArchiveDest} = '/tmp'; # # Archive Compression type # # The valid values are: # # - 'none': No Compression # # - 'gzip': Medium Compression. Recommended. # # - 'bzip2': High Compression but takes longer. # $Conf{ArchiveComp} = 'gzip'; # # Archive Parity Files # # The amount of Parity data to generate, as a percentage # of the archive size. # Uses the commandline par2 (par2cmdline) available from # http://parchive.sourceforge.net # # Only useful for file dumps. # # Set to 0 to disable this feature. # $Conf{ArchivePar} = '0'; # # Archive Size Split # # Only for file archives. Splits the output into # the specified size * 1,000,000. # e.g. to split into 650,000,000 bytes, specify 650 below. # # If the value is 0, or if $Conf{ArchiveDest} is an existing file or # device (e.g. a streaming tape drive), this feature is disabled. # $Conf{ArchiveSplit} = 0; # # Archive Command # # This is the command that is called to actually run the archive process # for each host. The following variables are substituted at run-time: # # $Installdir The installation directory of BackupPC # $tarCreatePath The path to BackupPC_tarCreate # $splitpath The path to the split program # $parpath The path to the par2 program # $host The host to archive # $backupnumber The backup number of the host to archive # $compression The path to the compression program # $compext The extension assigned to the compression type # $splitsize The number of bytes to split archives into # $archiveloc The location to put the archive # $parfile The amount of parity data to create (percentage) # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{ArchiveClientCmd} = '$Installdir/bin/BackupPC_archiveHost $tarCreatePath $splitpath $parpath $host $backupnumber $compression $compext $splitsize $archiveloc $parfile *'; # # Full path for ssh. Security caution: normal users should not # allowed to write to this file or directory. # $Conf{SshPath} = '/usr/bin/ssh'; # # Full path for nmblookup. Security caution: normal users should not # allowed to write to this file or directory. # # nmblookup is from the Samba distribution. nmblookup is used to get the # netbios name, necessary for DHCP hosts. # $Conf{NmbLookupPath} = '/usr/bin/nmblookup'; # # NmbLookup command. Given an IP address, does an nmblookup on that # IP address. The following variables are substituted at run-time: # # $nmbLookupPath path to nmblookup ($Conf{NmbLookupPath}) # $host IP address # # This command is only used for DHCP hosts: given an IP address, this # command should try to find its NetBios name. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{NmbLookupCmd} = '$nmbLookupPath -A $host'; # # NmbLookup command. Given a netbios name, finds that host by doing # a NetBios lookup. Several variables are substituted at run-time: # # $nmbLookupPath path to nmblookup ($Conf{NmbLookupPath}) # $host NetBios name # # In some cases you might need to change the broadcast address, for # example if nmblookup uses 192.168.255.255 by default and you find # that doesn't work, try 192.168.1.255 (or your equivalent class C # address) using the -B option: # # $Conf{NmbLookupFindHostCmd} = '$nmbLookupPath -B 192.168.1.255 $host'; # # If you use a WINS server and your machines don't respond to # multicast NetBios requests you can use this (replace 1.2.3.4 # with the IP address of your WINS server): # # $Conf{NmbLookupFindHostCmd} = '$nmbLookupPath -R -U 1.2.3.4 $host'; # # This is preferred over multicast since it minimizes network traffic. # # Experiment manually for your site to see what form of nmblookup command # works. # # Note: all Cmds are executed directly without a shell, so the prog name # needs to be a full path and you can't include shell syntax like # redirection and pipes; put that in a script if you need it. # $Conf{NmbLookupFindHostCmd} = '$nmbLookupPath $host'; # # For fixed IP address hosts, BackupPC_dump can also verify the netbios # name to ensure it matches the host name. An error is generated if # they do not match. Typically this flag is of... [truncated message content] |
|
From: Holger P. <wb...@pa...> - 2018-01-09 13:01:38
|
Hi, Marc Gilliatt wrote on 2018-01-09 12:00:55 +0000 [[BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*]: > [...] > Any suggestions/ideas would be truly appreciative. try reading the responses you already got. It's all in there. Repeating it likely won't help. If you don't understand something in the responses, ask specifically. I can't talk for others, but I don't feel like explaining something in yet a different way if I don't know if it's the specific thing you didn't understand or not, and when I don't know what the problem in understanding it was. I'll try just the same: * This is the wrong mailing list. bac...@li... is the correct one. * You *cannot* use includes and excludes with smb at the same time. Your excludes will simply be ignored. * We need your configuration settings if you want us to tell you what is wrong with them, not some vague descriptions of about what they might be like. Saying what you're *intending* to do won't reveal the syntax error. Hope that helps. Regards, Holger |
|
From: Marc G. <m.g...@li...> - 2018-01-09 12:01:05
|
I've emailed before in the past regarding my Windows share not performing its first full backup. And I've lost the email thread so I apologise for emailing again regarding the same issue. I'm using smb for the Xfer Method, I have given the user full permissions and it's still not completing its first full backup, This has been going on now for a few months and I can't seem to get a resolution for my problem. Here are the contents from the Xfer log..... Contents of file /var/lib/backuppc/pc/ukaudio/XferLOG.bad.z, modified 2018-01-02 09:31:40 (Extracting only Errors) Running: /usr/bin/smbclient \\\\ukaudio\\audio -U backuppc -E -d 1 -c tarmode\ full -Tc - full backup started for share audio Xfer PIDs are now 32860,32859 [ skipped 1 lines ] tar:316 tarmode is now full, system, hidden, noreset, quiet [ skipped 4559736 lines ] NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* [ skipped 501 lines ] tar:712 Total bytes received: 8876931906486 [ skipped 42 lines ] tarExtract: Done: 0 errors, 4378315 filesExist, 8830447301234 sizeExist, 7110741768601 sizeExistComp, 4387717 filesTotal, 8876941560049 sizeTotal Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukaudio full ukaudio ukaudio audio smb /usr/bin/ssh DumpPostUserCmd tail: cannot open '/var/lib/backuppc/pc/ukaudio/LOG.012018' for reading: No such file or directory Got fatal error during xfer (No files dumped for share audio) Backup aborted (No files dumped for share audio) Not saving this as a partial backup since it has fewer files than the prior one (got 4387717 and 0 files versus 4387717) I have excluded the \System Volume Information\SRM\* directory and it still keeps failing and I still get this error. It runs for about 3 - 4 days and then fails. I've included only the directories that I want backing up, and it still fails and I get the same error as above! Im running smbd 4.3.11-Ubuntu and backuppc 3.3.1-2ubuntu3.3 Any suggestions/ideas would be truly appreciative. |
|
From: Craig B. <cba...@us...> - 2017-12-24 12:22:02
|
What versions of BackupPC and smbclient are you using?
Seeing aside the NT_STATUS_ACCESS_DENIED error, it looks like you have a
sufficiently new version of smbclient, and a sufficiently old version of
BackupPC that causes successful file counting to fail:
tarExtract: Done: 0 errors, 4376935 filesExist, 8783933204861 sizeExist,
7077067832073 sizeExistComp, 4386347 filesTotal, 8830430446024 sizeTotal
Got fatal error during xfer (No files dumped for share audio)
Obviously a lot of files did get transferred (the first line above), but
the output of smbclient (which unfortunately frequently changes) isn't
recognized by BackupPC (the 2nd line above).
The last few versions of BackupPC have fixes to lib/BackupPC/Xfer/Smb.pm to
better detect the number of files smbclient says it transferred.
Craig
On Wed, Dec 20, 2017 at 9:40 AM, Les Mikesell <les...@gm...> wrote:
> On Mon, Dec 18, 2017 at 4:11 AM, Marc Gilliatt <m.g...@li...>
> wrote:
> >
> > This has failed yet again. And its because it's trying to backup
> \System Volume Information\
> >
> > I do not know how to stop backuppc from not backing up this directory?
> I've tried excluding the directory, and then only included the directories
> that I want backing up.
> >
>
> Are you using both exclude and include on the same share? Per the docs:
>
> "For Smb, only one of $Conf{BackupFilesExclude} and
> $Conf{BackupFilesOnly} can be specified per share. If both are set for
> a particular share, then $Conf{BackupFilesOnly} takes precedence and
> $Conf{BackupFilesExclude} is ignored."
>
> --
> Les Mikesell
> les...@gm...
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-devel mailing list
> Bac...@li...
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
|
|
From: Craig B. <cba...@us...> - 2017-12-24 11:52:02
|
It doesn't look like the backup of your windows machine worked at all - the error says access denied for C$. So it's likely the restore failed for a similar reason. Please look in the RestoreLOG file. Craig On Mon, Dec 18, 2017 at 3:32 AM, Marc Gilliatt <m.g...@li...> wrote: > I've been tasked to restore a Linux server(ukgitlab2), because one of its > raid drives has failed, to a Windows server(ukntmbuildarc) so the whole > office has access to it. > > I went into ukgitlab2 browse backups page in BackupPC, and selected all > the files to restore and then selected ukntmbuildarc to where I want it to > be restored too. There's a share on ukntmbuildarc called /ukgitlab2 so the > whole office has access to it. > > Every time I select restore now, I get the following error in the general > logs: > > 2017-12-18 11:11:16 Started restore on ukntmbuildarc <http://backuppc01.dsdb.int/backuppc/index.cgi?host=ukntmbuildarc> (pid=41732) > 2017-12-18 11:11:21 Restore failed on ukntmbuildarc <http://backuppc01.dsdb.int/backuppc/index.cgi?host=ukntmbuildarc> (BackupPC_tarCreate failed) > > > Contents of file /var/lib/backuppc/pc/ukntmbuildarc/XferLOG.bad.z, > modified 2017-12-18 11:01:00 > > Running: /usr/bin/smbclient \\\\ukntmbuildarc\\C\$ -U backuppc -E -d 1 -c tarmode\ full -Tc - > full backup started for share C$ > Xfer PIDs are now 41469,41468 > Domain=[DSDAMBUSTER] OS=[Windows Server 2016 Standard 14393] Server=[Windows Server 2016 Standard 6.3] > tree connect failed: NT_STATUS_ACCESS_DENIED > Domain=[DSDAMBUSTER] OS=[Windows Server 2016 Standard 14393] Server=[Windows Server 2016 Standard 6.3] > tree connect failed: NT_STATUS_ACCESS_DENIED > tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > exiting after signal INT > Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) > > > Contents of file /var/lib/backuppc/pc/ukntmbuildarc/XferLOG.bad.z, > modified 2017-12-18 11:01:00 (Extracting only Errors) > > Running: /usr/bin/smbclient \\\\ukntmbuildarc\\C\$ -U backuppc -E -d 1 -c tarmode\ full -Tc - > full backup started for share C$ > Xfer PIDs are now 41469,41468 > [ skipped 1 lines ] > tree connect failed: NT_STATUS_ACCESS_DENIED > [ skipped 1 lines ] > tree connect failed: NT_STATUS_ACCESS_DENIED > tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd > exiting after signal INT > Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) > > > I tried to do a full backup on ukntmbuildarc to see if BackupPC has access > to it, and it did perform a full backup of it. So it has access to it. > > I tried restoring ukgitlab2 to a Linux server instead of a Windows server, > and the restore worked perfeclty! So is this because I backed up ukgitlab2 > using rsync, and the only way you can restore to a Windows server is via > SMB maybe? > > I'm not sure on what configuration changes I need to make in order to > restore a Linux server/contents to a Windows server/share? > > Any help would be truly appreciated, thank you. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > > |
|
From: Craig B. <cba...@us...> - 2017-12-24 05:42:47
|
Alex,
Thanks for the offer to prepare a pull request, but it doesn't seem worth
making the change.
Have you considered simply reducing your $Conf{WakeupSchedule} so your disk
drive wakes up less often?
I made the DDMMYYYY change in the docs. Thanks.
Craig
On Tue, Dec 5, 2017 at 1:33 AM, Alexander Kobel <a-...@a-...> wrote:
> Hi,
>
> for a tiny BackupPC instance with on an SSD+HDD-server, I want the HDD to
> be in standby mode (spinned down) most of the time. Hence, I only store
> __TOPDIR__ on it, and have everything else on the SSD. This almost works,
> except for the fact that unsuccessful pings write a log entry in
> __TOPDIR__/pc/$host/LOG.DDMMYYYY, and LOCK is touched. Which happens on
> every wakeup when some client is not reachable; in other words, too often.
>
> AFAICS, from what's inside pc/, actually vital for the integrity of the
> backups are the nnn and refCnt dirs (and, to some extent, the backups and
> config.pl files). Those are only accessed during backup or restore jobs,
> when the "vault" disk is active anyway.
> So, in short, I want to bring __TOPDIR__/pc/$host/LOG* and LOCK from the
> HDD to somewhere else. Note that both LOG* and nnn are moving targets, so
> symlinks only work to a certain extent.
> (By the way: LOG.DDMMYYYY is actually LOG.MMYYYY, without DD, on my 4.1.3
> installation.)
>
>
> My usual approach is anything-sync-daemon (which uses an overlayfs to move
> some directory to tmpfs, and sync backs periodically and/or on user
> request). However, this only works at directory level, and would require
> moving the entire __TOPDIR__/pc directory to tmpfs. nnn can easily become
> large, and overlayfs is ill-suited for that.
> Another approach would be to move __TOPDIR__/pc to the SSD and rsync back
> each __TOPDIR__/pc/$host/ to the HDD in a DumpPostUserCmd and, perhaps,
> after each nightly. That's better, but again, the nnn can grow large (at
> least in number of files) and might become ill-suited even for the SSD
> and/or rootfs.
>
>
> => Question 1.) Short of patching BackupPC, does anyone have a suggestion
> or alternate solution I didn't think of?
>
>
> It would be way easier to properly separate the two kinds of data if the
> location of the per-host LOG* and LOCK files would be configurable, e.g. to
> somewhere below __LOGDIR__. This would match the logic for the global LOCK
> (which resides at __LOGDIR__), even though I'd typically expect lock files
> to live below /run/lock or /var/run/lock.
> Full backward compatibility could be kept, e.g., through a
> __PERHOSTLOGDIR__ variable defaulting to __TOPDIR__/pc/.
>
> I'd be willing to look into preparing a patch and pull request, if there
> is any interest. But I understand that the scenario and motivation are
> negligible in an enterprise setup, and that changing the storage layout can
> a royal pain in the * for existing systems. Hence,
>
>
> => Question 2.) Would such a change have any chance to be integrated in
> BackupPC? If so, under what constraints for the interface? Any
> recommendations for locations? What about {Xfer,Restore,Archive}{ERR,LOG
> ,Info}*?
>
>
>
> Best,
> Alex
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-devel mailing list
> Bac...@li...
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
|
|
From: Craig B. <cba...@us...> - 2017-12-24 05:36:45
|
The excludes should be relative to the share name. If you share name is /home, then the exclude should be 'felfert/.m2/repository', not '/home/ felfert/.m2/repository'. Your manual example works because you used "/home" instead of "/home/". The more equivalent command for BackupPC is: rsync -av --exclude=felfert/.m2/repository target:/home/ . Craig On Thu, Nov 30, 2017 at 7:14 AM, Fritz Elfert <fr...@fr...> wrote: > I just have upgraded my local server to Fedora 26 which included an > uprade of BackupPC v3 to BackupPC 4.1.3. > > Unfortunately, I experience a subtle difference of the file exclusion > mechanism which hits me hard performancewise. > > With old BackupPC (cannot prove anymore) as well as with a > manual test like > > rsync -av --exclude=/home/felfert/.m2/repository target:/home . > > On the target (in rsync terms: server), the specified directory is > simply skipped which takes just millisecs. > > With BackupPC 4.3.1, the directory is missing in the resultin backup (as > expected). > However: The whole hierarchy below /home/felfert/.m2/repository is still > recursively read on the target which takes ages (in my case ~2hours) and > also puts quite some load on the target. > > This is a huge performance degradation compared to v3. > > Can somebody confirm this or do I have overlooked some necessary change > (ragading v3 -> v4 migration) in the config? > > -Fritz > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > > |
|
From: Craig B. <cba...@us...> - 2017-12-24 05:24:22
|
Alexander, Sure, I'd be happy to apply a pull request. One other potential change is reordering the left navigation bar to keep the host search on top (so the order is host search, host, global). Craig On Wed, Nov 29, 2017 at 3:16 AM, Alexander Kobel <a-...@a-...> wrote: > Dear all, > > I'm certainly not the first one to shoot myself in the foot by confusing > the "Edit Config" link for a specific host with the "Edit Config" for the > server's global configuration, and not paying attention to the headers. > > Wouldn't it be a good idea to rename them to distinct labels, like "Edit > Config for host" and "Edit global Config" (intentionally not following the > same pattern)? It could provide at least some visual cue with minimal > effort, and is less invasive than e.g. changing the color scheme to reddish > for global configuration and leaving it blueish for host config (which > would be awesome!)... > > Except for the different language files, I can produce a patch / pull > request if there's any interest. > > > Cheers, > Alex > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > > |
|
From: Les M. <les...@gm...> - 2017-12-20 17:41:06
|
On Mon, Dec 18, 2017 at 4:11 AM, Marc Gilliatt <m.g...@li...> wrote:
>
> This has failed yet again. And its because it's trying to backup \System Volume Information\
>
> I do not know how to stop backuppc from not backing up this directory? I've tried excluding the directory, and then only included the directories that I want backing up.
>
Are you using both exclude and include on the same share? Per the docs:
"For Smb, only one of $Conf{BackupFilesExclude} and
$Conf{BackupFilesOnly} can be specified per share. If both are set for
a particular share, then $Conf{BackupFilesOnly} takes precedence and
$Conf{BackupFilesExclude} is ignored."
--
Les Mikesell
les...@gm...
|
|
From: Michael S. <mic...@me...> - 2017-12-20 17:18:24
|
On 2017-12-18 02:11, Marc Gilliatt wrote: > This has failed yet again. And its because it's trying to backup > \System Volume Information\ > > I do not know how to stop backuppc from not backing up this > directory? I've tried excluding the directory, and then only included > the directories that I want backing up. > > I'm not sure on what do next? > > I really need this SMB share backing up through backuppc. > > Any ideas, please? Could we move this to backuppc-users? The next step is probably to post the relevant portions of your config.pl (most likely, the machine-specific config with the includes and excludes) so that you can obtain help in debugging it. There's a very high chance that there's a simple logical error that's causing BackupPC to interpret the exclusions (or inclusions) differently than you're expecting. Also quite helpful: the resulting command line (it will be smbclient for SMB/CIFS transports) since this tells us how BackupPC, ultimately, has interpreted your config files. |
|
From: Marc G. <m.g...@li...> - 2017-12-18 11:32:29
|
I've been tasked to restore a Linux server(ukgitlab2), because one of its raid drives has failed, to a Windows server(ukntmbuildarc) so the whole office has access to it. I went into ukgitlab2 browse backups page in BackupPC, and selected all the files to restore and then selected ukntmbuildarc to where I want it to be restored too. There's a share on ukntmbuildarc called /ukgitlab2 so the whole office has access to it. Every time I select restore now, I get the following error in the general logs: 2017-12-18 11:11:16 Started restore on ukntmbuildarc<http://backuppc01.dsdb.int/backuppc/index.cgi?host=ukntmbuildarc> (pid=41732) 2017-12-18 11:11:21 Restore failed on ukntmbuildarc<http://backuppc01.dsdb.int/backuppc/index.cgi?host=ukntmbuildarc> (BackupPC_tarCreate failed) Contents of file /var/lib/backuppc/pc/ukntmbuildarc/XferLOG.bad.z, modified 2017-12-18 11:01:00 Running: /usr/bin/smbclient \\\\ukntmbuildarc\\C\$ -U backuppc -E -d 1 -c tarmode\ full -Tc - full backup started for share C$ Xfer PIDs are now 41469,41468 Domain=[DSDAMBUSTER] OS=[Windows Server 2016 Standard 14393] Server=[Windows Server 2016 Standard 6.3] tree connect failed: NT_STATUS_ACCESS_DENIED Domain=[DSDAMBUSTER] OS=[Windows Server 2016 Standard 14393] Server=[Windows Server 2016 Standard 6.3] tree connect failed: NT_STATUS_ACCESS_DENIED tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd exiting after signal INT Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) Contents of file /var/lib/backuppc/pc/ukntmbuildarc/XferLOG.bad.z, modified 2017-12-18 11:01:00 (Extracting only Errors) Running: /usr/bin/smbclient \\\\ukntmbuildarc\\C\$ -U backuppc -E -d 1 -c tarmode\ full -Tc - full backup started for share C$ Xfer PIDs are now 41469,41468 [ skipped 1 lines ] tree connect failed: NT_STATUS_ACCESS_DENIED [ skipped 1 lines ] tree connect failed: NT_STATUS_ACCESS_DENIED tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd Executing DumpPostUserCmd: /var/lib/backuppc/backuppc_notification.sh 0 ukntmbuildarc full ukntmbuildarc ukntmbuildarc C$ smb /usr/bin/ssh DumpPostUserCmd exiting after signal INT Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) I tried to do a full backup on ukntmbuildarc to see if BackupPC has access to it, and it did perform a full backup of it. So it has access to it. I tried restoring ukgitlab2 to a Linux server instead of a Windows server, and the restore worked perfeclty! So is this because I backed up ukgitlab2 using rsync, and the only way you can restore to a Windows server is via SMB maybe? I'm not sure on what configuration changes I need to make in order to restore a Linux server/contents to a Windows server/share? Any help would be truly appreciated, thank you. |
|
From: Marc G. <m.g...@li...> - 2017-12-18 10:11:34
|
This has failed yet again. And its because it's trying to backup \System Volume Information\ I do not know how to stop backuppc from not backing up this directory? I've tried excluding the directory, and then only included the directories that I want backing up. I'm not sure on what do next? I really need this SMB share backing up through backuppc. Any ideas, please? ________________________________ From: Michael Stowe <mic...@me...> Sent: 13 December 2017 15:03 To: Marc Gilliatt Cc: Holger Parplies; Developers discussion Subject: Re: [BackupPC-devel] Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On 2017-12-13 01:56, Marc Gilliatt wrote: I've included the screenshot of the config file. You say I haven't? But here is the proof! Why would I lie? You're not lying, per se, but the screenshot does show the contrary — that because you are using the include list, your excludes are irrelevant. What it does not show, incidentally, is how those are configured or if they are being used — the relevant portions of the config.pl would be better for diagnosis. And I'm not an expert in “Windoze” it's why I asked the community. And is this the best mailing list to email support questions too? If not, could I please have the correct mailing list so I can ask my support questions. BackupPC-users is the right one I would just like some help and advice into why this Windows share is failing on backup? The short verson: because you're [still] trying to read \System Volume Information\ via SMB. The next step is to work on that. |
|
From: Craig B. <cba...@us...> - 2017-12-13 19:39:53
|
There were a couple of bugs in rsync-bpc-3.0.9.9 that are fixed in a newly released rsync-bpc-3.0.9.11 <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.11>. If you have installed rsync-bpc-3.0.9.9 or rsync-bpc-3.0.9.10, please upgrade to rsync-bpc-3.0.9.11. Craig On Sun, Dec 3, 2017 at 8:28 PM, Craig Barratt < cba...@us...> wrote: > BackupPC 4.1.5 <https://github.com/backuppc/backuppc/releases/tag/4.1.5> has > been released on Github. > > New versions of BackupPC-XS 0.57 > <https://github.com/backuppc/backuppc-xs/releases/tag/0.57> and > rsync-bpc 3.0.9.9 > <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.9> have also > been released. BackupPC 4.1.5 requires BackupPC-XS 0.57. > > The cumulative changes including 4.1.4 > <https://github.com/backuppc/backuppc/releases/tag/4.1.4> (released last > week but not announced) are listed below. Upgrading is strongly > recommended. > > Thanks to the multiple contributions and debugging help. > > Enjoy! > > Craig > > #------------------------------------------------------------------------ > # Version 4.1.5, 3 Dec 2017 > #------------------------------------------------------------------------ > > * Changed required BackupPC::XS version from 0.56 to 0.57. > > * bin/BackupPC_dump now updates inodeLast for share being backed up. > > * bin/BackupPC_refCountUpdate: inodeLast is checked and updated during > fsck; > needs BackupPC::XS 0.57. > > #------------------------------------------------------------------------ > # Version 4.1.4, 25 Nov 2017 > #------------------------------------------------------------------------ > > Merged pull requests #99, #121, #125, #131, #133, #134, #137, #148, #149, > #150 > #151, #152, #153, #155, #157, #167 > > * lib/BackupPC/Xfer/Smb.pm: made pipeSMB non-blocking to avoid a > reported deadlock when BackupPC's select() returns ok for reading, > but there are no bytes to read from the client tar's log/stdout > output. Parallel change to lib/BackupPC/Xfer/Tar.pm in 4.1.3. > > * bin/BackupPC_tarCreate and bin/BackupPC_zipCreate: untaint the host name > so they work with setuid under CGI; fixes empty tar or zip files > downloaded via CGI interface (fixes issue #156) > > * bin/BackupPC: fixed BackupPC::XS min version checking and error message, > from @moisseev (#152) > > * bin/BackupPC: added more detailed startup information (perl and BackupPC > version) to log, from @moisseev (#157) > > * bin/BackupPC_rrdUpdate: fixed empty pools hiding from @moisseev (#167) > > * lib/BackupPC/Xfer/Smb.pm: now ignores additional debug messages from > smbclient, and flags lines in the XferLOG it doesn't recognize. > > * lib/BackupPC/CGI/Browse.pm: default display now has the last, rather > than first, share opened. > > * Replaced submit with button so that Enter doesn't activate the Delete > button. Fixes issue #161, reported by Philippe-M. > > * removed commented-out settings for some ftp args (eg, port#) in > lib/BackupPC/Xfer/Ftp.pm; reported by Adam W. > > * bin/BackupPC_backupDelete: only print delta counts if LogLevel is >= 5 > > * bin/BackupPC_tarExtract: fix existing file size count and size > > * lib/BackupPC/CGI/EditConfig.pm: fixed masking of subheadings in > config editor. > > * config/config.pl: added -mSMB3 to $Conf{SmbClientIncrCmd} and > $Conf{SmbClientRestoreCmd}, from @SvenBunge (#99) > > * lib/BackupPC/Xfer/Rsync.pm: improved cleanup of orphan rsyncTmp files > > * In bin/BackupPC_dump, added "share" to __bpc_progress_state__ message so > it is 'backup share "$shareName"'. Patch #150 by @guestisp (issue #143) > > * added share name to log message in lib/BackupPC/CGI/Restore.pm for tar > and zip restore. > > * makeDist: fixed exit code from @moisseev (#153) > > * Added Travis CI configuration from @moisseev (#155) and enabled travis > > * Replaced "Homepage" with "Github" in config.pl and configure.pl from > @moisseev (#121) > > * Spelling fixes, mainly in comments from @ka7 (#125). > > * Fixed comment in config.pl (zh_CH -> zh_CN) from @patch (#131) > > * Fixed German translations from @mainboarder (#133, #134) > > * Fixed minor comment typo in config.pl from @pbe-axelor (#137) > > * Fixed comments in systemd/README from @schuetzm (#138) > > * Fixed Italian translations from @guestisp (#148, #149; issue #142) > > * Fixed incorrect hash key in German translations from @moisseev (#151) > > |
|
From: Michael S. <mic...@me...> - 2017-12-13 15:04:36
|
On 2017-12-13 01:56, Marc Gilliatt wrote: > I've included the screenshot of the config file. You say I haven't? > But here is the proof! > > Why would I lie? You're not lying, per se, but the screenshot does show the contrary -- that because you are using the include list, your excludes are irrelevant. What it does not show, incidentally, is how those are configured or if they are being used -- the relevant portions of the config.pl would be better for diagnosis. > And I'm not an expert in "Windoze" it's why I asked the community. > > And is this the best mailing list to email support questions too? If > not, could I please have the correct mailing list so I can ask my > support questions. BackupPC-users is the right one > I would just like some help and advice into why this Windows share is > failing on backup? The short verson: because you're [still] trying to read \System Volume Information\ via SMB. The next step is to work on that. |
|
From: Marc G. <m.g...@li...> - 2017-12-13 10:12:24
|
I've included the screenshot of the config file. You say I haven't? But here is the proof!
Why would I lie?
And I'm not an expert in "Windoze" it's why I asked the community.
And is this the best mailing list to email support questions too? If not, could I please have the correct mailing list so I can ask my support questions.
I would just like some help and advice into why this Windows share is failing on backup?
________________________________
From: Holger Parplies <wb...@pa...>
Sent: 13 December 2017 01:05
To: Marc Gilliatt
Cc: Michael Stowe; Developers discussion
Subject: Re: [BackupPC-devel] Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*
Hi,
I've been wanting to say this for a long time:
Which patch to BackupPC are you proposing?
Hint: you are posting to the -devel-list, so you are obviously discussing
something pertaining to the development of BackupPC.
Marc Gilliatt wrote on 2017-12-12 09:37:57 +0000 [Re: [BackupPC-devel] Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\*]:
> I exclude \System Volume Information\ so it doesn't get backed up. But it
> still tries to back it up.
Apparently, you aren't, else it wouldn't.
> I have full permissions on the directories, I should be able to backup
> the directories I want to back up. I'm not sure on how to test if I can
> access the directories through SMB?
I'm not an expert on Windoze, but in this case, I don't need to be. You don't
need to test. You can't.
> How do I get SMB access to those directories?
You don't. Read this again:
> From: Michael Stowe <mic...@me...>
> Sent: 12 December 2017 06:34
> [...]
>
> 2) You cannot access \System Volume Information\
Quite unambiguous.
But let's back up a step. You wrote:
> I have excluded that directory (\System Volume Information\SRM\), and I have
> included to only backup the certain directories that I want backing up.
No. You didn't. Again, the art of reading helps. From config.pl:
# For Smb, only one of $Conf{BackupFilesExclude} and $Conf{BackupFilesOnly}
# can be specified per share. If both are set for a particular share, then
# $Conf{BackupFilesOnly} takes precedence and $Conf{BackupFilesExclude}
# is ignored.
So, you ***didn't*** exclude anything. Why your BackupFilesOnly includes
\System Volume Information\ remains a mystery (at least to me).
Regards,
Holger
|
17 messages has been excluded from this view by a project administrator.
