Re: [BackupPC-users] Tricks for Win 10 SMB Backup?

2018-07-29 Thread Craig Barratt via BackupPC-users
What is the value of $Conf{SmbClientFullCmd} and what is the smb command
that is being run (see the XferLOG file)?

Craig

On Sun, Jul 29, 2018 at 12:22 PM Tim Evans  wrote:

> Unable to connect to a new Windows 10 client via SMB for backup.
> Command-line testing with 'smbclient' works ok:
>
> $ smbclient -L new-pelican -Ubackup%xxx
>
> Sharename Type Comment
> -  ---
> ADMIN$ Disk Remote Admin
> C Disk
> C$ Disk Default share
> E Disk
> E$ Disk Default share
> IPC$ IPC Remote IPC
> Users Disk
> SMB1 disabled -- no workgroup available
>
> Note the last line of the output above ("SMB1 disabled...").
>
> I can login with 'smbclient' and interactively display files in the
> shares.  BackupPC, however, won't connect.
>
> 2018-07-27 15:07:03 Backup failed on new-pelican (No files dumped for
> share C$)
>
> Googling the SMB1 reference leads to suggestions to add the following to
> smb.conf:
>
> client min protocol = SMB2
> client max protocol = SMB3
>
> I added this and restarted Samba. This doesn't resolve the issue.  Other
> suggestions?
>
> Thanks.
> --
> Tim Evans   |5 Chestnut Court
> 443-394-3864|Owings Mills, MD 21117
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] cpool directory twice as big as reported and missing pool files reported by BackupPC_refCountUpdate

2018-07-29 Thread Craig Barratt via BackupPC-users
Cody,

There were some bugs in earlier versions of 4.x that could cause missing
pool files.  But they have been fixed for some time.

How did you determine the cpool directory size (eg, du -sh)?

At any point did you run backups with compression off?

Here's how to find which backup is referencing a particular digest:

   - pick an md5 digrest (32 hex characters) that got an error
   - take the first 2 hex digits and and it with 0xfe (ie, round down to
   the next even number, eg: 0x77 -> 0x76; 0xaf -> 0xae).  Call those two
   digits XY
   - run BackupPC_poolCntPrint TOPDIR/pc/*/*/refCnt/poolCnt.1.XY | less
   - use less to search for the hex digest (ie, type "/" then paste the 32
   digit digest, then hit return)
   - then search upwards to find the file name (ie, type "?Pool Ref", then
   hit return
   - based on the file name, you can find out the host name and backup
   number

To find which directory / file in the specific backup references that
digest, you would need to use BackupPC_ls -R -h HOST -n BackupNUM -s Share
/ | egrep HexDigest

Craig

On Thu, Jul 5, 2018 at 7:32 PM Cody Jackson  wrote:

> Hi all,
>
> BackupPC reports that my pool is about 800GB, but my cpool directory is
> 1.6TB.
>
> When I try running BackupPC_refCountUpdate, I get about 350 errors
> similar to:
>
> BackupPC_refCountUpdate: missing pool file [md5 hash] count 1
>
> Questions:
>
> * Are these issues related?
> * How can I find out which computers have references to these hashes
> that are missing?
> * Why is my pool so big?
>
> For the pool size, I did recently change the compress level (going from
> 3 to 7), but the older backups should have fallen off the radar by now
> and been removed.
>
> Cheers,
>
> -C
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] Xfer errors

2018-07-29 Thread Craig Barratt via BackupPC-users
Pete,

Can you send me more lines from the XferLOG file for a full backup?
Ideally the entire log file, or otherwise several hundred lines before and
after the errors.

Craig

On Fri, Jun 29, 2018 at 4:53 AM Pete Geenhuizen  wrote:

> I'm running BackupPC 4.2.1 on CentOS 7.5 using rsync and it's running
> just fine with one seemingly minor problem.
>
> I recently upgraded a host from CentOS 6.9 to CentOS 7.5 and forced a
> level 0 backup, and since then I see the following errors.
>
> cannot delete non-empty directory: bin
> could not make way for new symlink: bin
> cannot delete non-empty directory: lib
> could not make way for new symlink: lib
> cannot delete non-empty directory: lib64
> could not make way for new symlink: lib64
> cannot delete non-empty directory: sbin
> could not make way for new symlink: sbin
> cannot delete non-empty directory: var/lock
> could not make way for new symlink: var/lock
> cannot delete non-empty directory: var/run
> could not make way for new symlink: var/run
>
> Although these errors don't seem to affect the backups and seem to be
> benign I'd like to deal with them.
>
> Any ideas on how to best eliminate these error?
>
> Thanks
>
> Pete
>
> --
> Unencumbered by the thought process.
>   -- Click and Clack the Tappet brothers
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Re: [BackupPC-users] Old data in Windows backups

2018-07-29 Thread Craig Barratt via BackupPC-users
Let's start with your 4.1.5 BackupPC.

Does your $Conf{RsyncArgs} include the --delete option?  If not, add it.
If so, I'd be curious to see a portion of the XferLOG file for a full
backup of a directory where old files remain.

Craig

On Fri, Jul 20, 2018 at 2:04 AM B Consultants 
wrote:

> Hello,
>
> We use Bpc (V4.1.5 and V3) to backup Linuxes and Windows boxes. All
> backups are made through rsync, even on our few Windows boxes.
> Everything is okay as far as data backups are concerned.
>
> When browsing the Windows backups through Bpc web interface, we found
> that they still show and contains *very old* data that have been deleted
> from the relevant computers several months ago. This holds true for full
> and incremental backups, as far as our (limited) checks have shown, for
> all our Windows machines and for BPC 4 and 3.
>
> This seems weird (especially wrt EU's GDPR). Did we make some mistake
> while configuring the backups ?
>
> Tia,
> --
> B Consultants - Sécurité informatique - www.ba-consultants.fr
> Tel. : +33 (0) 563 277 241 - Fax : +33 (0) 567 737 829
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


[BackupPC-users] Tricks for Win 10 SMB Backup?

2018-07-29 Thread Tim Evans
Unable to connect to a new Windows 10 client via SMB for backup. 
Command-line testing with 'smbclient' works ok:


$ smbclient -L new-pelican -Ubackup%xxx

Sharename Type Comment
-  ---
ADMIN$ Disk Remote Admin
C Disk
C$ Disk Default share
E Disk
E$ Disk Default share
IPC$ IPC Remote IPC
Users Disk
SMB1 disabled -- no workgroup available

Note the last line of the output above ("SMB1 disabled...").

I can login with 'smbclient' and interactively display files in the 
shares.  BackupPC, however, won't connect.


2018-07-27 15:07:03 Backup failed on new-pelican (No files dumped for 
share C$)


Googling the SMB1 reference leads to suggestions to add the following to 
smb.conf:


client min protocol = SMB2
client max protocol = SMB3

I added this and restarted Samba. This doesn't resolve the issue.  Other 
suggestions?


Thanks.
--
Tim Evans   |5 Chestnut Court
443-394-3864|Owings Mills, MD 21117

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/