Re: [BackupPC-users] question about catalog

2017-12-15 Thread Bzzzz
On Fri, 15 Dec 2017 12:16:50 -0500
David Owens  wrote:

> Hello,

Hi

> I want to backup my backuppc server.  Questions:

Shall we imagine it runs under Linux?

>1. Where is the catalog, and what is the best practice for backing
> it up.

There isn't one, the list is determined by the root of your backup (could
be / ou /DATA or /whatever) and the eventual exclusions you set
into config.pl.

> 2. I was just going to tar the config.  What are the essential
> files / file systems needed to capture.

Assuming it runs under Linux, don't be stingy with space and backup the
whole stuff except the usual suspects (/dev, /proc, /tmp, /var/tmp, …)

Because this way, if you meet a catastrophe, you'll only need to
reinstall a very minimal system including rsync, then restore the last
backup to recover a fully operating system (NB: impossible with w$.)

Otherwise, you'll "save" a few space but bang your head on the wall the
time being when you'll discover you forgot let's say something
like /var/lib.

Of course, for the BPC server, an up to date tar of /etc/backuppc saved
on some other machines can help.

--
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] question about catalog

2017-12-15 Thread David Owens
Hello,



I want to backup my backuppc server.  Questions:



   1. Where is the catalog, and what is the best practice for backing it up.
   2. I was just going to tar the config.  What are the essential files /
   file systems needed to capture.



-Thanks,



David Owens

Systems Administrator | Kitware

david.ow...@kitware.com
--
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] Bug in rsync_bpc --sparse?

2017-12-15 Thread Alexander Kobel

Hi Craig,

thanks for your swift reply.

On 2017-12-15 05:17, Craig Barratt via BackupPC-users wrote:
Unfortunately sparse files are not supported by rsync_bpc, and there are 
no plans to do so.


Okay. Not a big impact for BackupPC's files, anyway - I just thought 
it's safe and no harm, but proven wrong...



I should make it a fatal error if that option is specified.


Yes, that would be great to avoid future mistakes.

I believe a full backup (without --sparse of course) should update the 
files to their correct state.


Okay. For me to understand: the MD5 hashes are generated on the server 
side, correct? So a file that was transferred incorrectly will not be 
stored under the hash of the original file? And the full backup does not 
just skip based on size, times and names, but on the actual hash of the 
file? In that situation I see why running a full backup should resolve 
everything.



May I ask you to crank out a short comment on point d) as well? If it's 
complicated, don't. But I found earlier questions on how to decompress 
an entire pool on the mailing list to employ ZFS' or Btrfs' compression, 
and while it's officially unsupported to convert the pool, I might try 
if (and only if) my assumptions are correct on what would need to be done.

d) On my *actual* server, I used compression. This incident taught
me to verify some of the files manually, and to perhaps migrate to
filesystem compression (which I had planned anyway) to keep things
as simple as possible.
   d.1) BackupPC_zcat for verifying/decompressing has a remarkable
overhead for a well-grown set of small files (even when pointed
directly to the pool files). From what I can tell, Adler's pigz [2]
implementation supports headerless zlib files and is *way* faster.
Also, all my tests show that files compress to output with the
expected hashes encoded in the filename. However, I remembered that
BackupPC's compression flushes in between, apparently much like
pigz. Are BackupPC's compressed files *fully* in default zlib
format, or do I need to expect trouble with large files in corner cases?
   d.2) Conceptually, what is needed to convert an entire v4 pool to
uncompressed storage? Is it just
    - decompression of all files from cpool/??/?? to pool/??/??
(identical names, because hashes are computed on the decompressed data)
    - move poolCnt files from cpool/?? to pool/??
    - replace compression level in pc/$host/backups and
pc/$host/nnn/backupInfo
   or do any refCnt files need to be touched as well?



Thanks a lot,
Alex



smime.p7s
Description: S/MIME Cryptographic Signature
--
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] Trouble with restore

2017-12-15 Thread Jens Potthast
Hi,
Still no progress on this one. Here is a wrap-up of what I have tried so
far:

- Restoring (with smb) to the same or another host: operation breaks, as
soon as a file is restored in an existing directory. 

- Restoring (with smb) to a new directory (same or different host):
directory is created, the first file is restored and then restore fails. 

- When I mount my shares manually as 'backuppcuser', I am able to
copy/change files on Windows hosts. That should rule out any permission
issues.  

- No Warnings or errors in SMB-Log-files on Windows hosts.

- Restoring using ssh, zip or tar works as expected. I had Archive::Zip
missing. Since I never used zip, it went unnoticed.


What I need right now: Someone with a similar configuration/environment
testing a restore (with smb) operation.

My System: Debian 8.10, BackupPC 4.1.5, Hosts: Windows Server 2012 R2,
Windows 7 x64 (via SMB3).


Regards,
Jens



-Original Message-
From: Jens Potthast [mailto:jens.potth...@innovation.uni-bremen.de] 
Sent: Mittwoch, 13. Dezember 2017 14:02
To: backuppc-users@lists.sourceforge.net
Subject: [BackupPC-users] Trouble with restore

Hello,
using BackupPC for several years, I needed to restore a couple of files
recently. The last time, I had to restore some files was years ago. At that
time it was no problem. Right now, restore fails: 

Running: /usr/bin/smbclient server\\sharename -U backuppcuser -E -d 1 -c
tarmode\ full -mSMB3 -Tx -
Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h hostname -n 1886 -s
sharename -t -r /Path\ to\ file -p /Path\ to\ file/filename.txt Xfer PIDs
are now 2600,2601 Domain=[MYDOMAIN] OS=[] Server=[]
tar:316  tarmode is now full, system, hidden, noreset, quiet
tarCreate: Done: 1 files, 237695 bytes, 0 dirs, 0 specials, 0 errors
tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION
readOutput: sysread returns 0 and got EOF (exit ok = , ) XferErr Non-zero
exit status from smbclient restore failed: Non-zero exit status from
smbclient


What is strange: if I redirect the files to another directory, one folder or
file is created before the operation fails. That should rule out all
permission problems with my (Windows 2008 R2) Servers Share. I checked
permissions of backuppc-user on the server, just in case. However,
permissions are ok. If the directory is not there, the directory and one
file is created, is the directory already there, no file is created.

Therefore, my guess is that the return value is not, what BackupPC is
expecting.   

Upping XferLogLevel does not increase log file output. 

I am not sure, if this is connected, but I cannot restore to zip also.
Restore to tar works. Therefore, I am not completely lost right now. 


System: BackupPC 4.1.5, BackupPC-XS 0.57, rsync-bpc-3.0.9.9 [Debian 8.x]

Any clues where to look or how to increase debug level?


Regards,
Jens


smime.p7s
Description: S/MIME cryptographic signature
--
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] BackupPC 4.1.5 released (plus new versions of backuppc-xs and rsync-bpc)

2017-12-15 Thread Daniel Berteaud

Le 14/12/2017 à 19:14, Kris Lou a écrit :

Daniel,

Do you maintain that repo?  How is that different from the COPR?



I do maintain that repo. I don't know how it differs from the COPR. I 
guess the main difference is that my package is named BackupPC4 so it 
won't upgrade automatically a v3 install to a v4. You have to install it 
explicitely.


Cheers,
Daniel

--

Logo FWS

*Daniel Berteaud*

FIREWALL-SERVICES SAS.
Société de Services en Logiciels Libres
Tel : 05 56 64 15 32 
Matrix: @dani:fws.fr
/www.firewall-services.com/

--
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/