Re: [BackupPC-users] Trouble with restore

[Craig Barratt via BackupPC-users]

It looks like this issue was opened on github
<https://github.com/backuppc/backuppc/issues/175> a couple of days ago.  I
responded there with some suggestions.

Craig

On Wed, Dec 13, 2017 at 10:50 AM, Holger Parplies <wb...@parplies.de> wrote:

> Hi,
>
> let's start over.
>
> Jens Potthast wrote on 2017-12-13 14:01:46 +0100 [[BackupPC-users] Trouble
> with restore]:
> > [...]
> > 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
>
> you've got an error in your arguments, or you've misquoted from your log
> file
> (or your version of BackupPC is broken). That may or may not be related,
> but
> it's something to check. You are apparently using the web interface for a
> direct restore to the client system.
>
> a) Personally, I wouldn't do that, but you may have good reasons.
> b) You are possibly filling in some incorrect values into the web form. The
>arguments to BackupPC_tarCreate are directing it to
>- remove "/Path to file" from the paths in the backup and
>- add"/Path to file/filename.txt" in front of all paths.
>Is that what you want? The "filename.txt" seems misplaced, and it will
>likely be difficult to create a directory of that name on the target
>system if there happens to be a file of that name present, which might
>explain your error (or not).
>Also, there are no file name arguments, which should cause
>BackupPC_tarCreate to terminate with an error message. Strange.
>Note: the '-r' and '-p' arguments wouldn't be created if the two paths
>were equal (at least the code says so).
>
> > [...]
> > tarCreate: Done: 1 files, 237695 bytes, 0 dirs, 0 specials, 0 errors
>
> That sounds as if it had worked ...
>
> > tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION
>
> ... and that doesn't mention "filename.txt".
>
> What's in the RestoreInfo.xxx file for the restore attempt?
>
> Regards,
> Holger
>
> 
> --
> 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] Trouble with restore

[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] Trouble with restore

[Holger Parplies]

Hi,

let's start over.

Jens Potthast wrote on 2017-12-13 14:01:46 +0100 [[BackupPC-users] Trouble with 
restore]:
> [...]
> 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

you've got an error in your arguments, or you've misquoted from your log file
(or your version of BackupPC is broken). That may or may not be related, but
it's something to check. You are apparently using the web interface for a
direct restore to the client system.

a) Personally, I wouldn't do that, but you may have good reasons.
b) You are possibly filling in some incorrect values into the web form. The
   arguments to BackupPC_tarCreate are directing it to
   - remove "/Path to file" from the paths in the backup and
   - add"/Path to file/filename.txt" in front of all paths.
   Is that what you want? The "filename.txt" seems misplaced, and it will
   likely be difficult to create a directory of that name on the target
   system if there happens to be a file of that name present, which might
   explain your error (or not).
   Also, there are no file name arguments, which should cause
   BackupPC_tarCreate to terminate with an error message. Strange.
   Note: the '-r' and '-p' arguments wouldn't be created if the two paths
   were equal (at least the code says so).

> [...]
> tarCreate: Done: 1 files, 237695 bytes, 0 dirs, 0 specials, 0 errors

That sounds as if it had worked ...

> tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION

... and that doesn't mention "filename.txt".

What's in the RestoreInfo.xxx file for the restore attempt?

Regards,
Holger

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

[Jens Potthast]

Thanks for the explanation. I'll see, if I can check permissions and logs on
my Server and report back tomorrow.

-Original Message-
From: B [mailto:lazyvi...@gmx.com] 
Sent: Mittwoch, 13. Dezember 2017 15:43
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] Trouble with restore

On Wed, 13 Dec 2017 15:21:09 +0100
"Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:

> Ok, I don't understand, what you are talking about. Sorry. 

>From some Samba ML posts, this error code means the server command is not
able to either create the destination directory OR can't write in it.
But it is Samba, not m$.

> BackupPC does create a directory, if it does not already exists. If it 
> does, it stops with an error. It restores the first file and then it 
> stops.

Hmm, have a look at w$ logs, if they are correctly set (? duno if it is even
possible to change the log level into nsa self-service), they may reflect
what the real problem is on your client as m$ is also known to sometimes
group several errors under only one error code.

> So, if neither directory nor files do exists, why would restore fail?

I had some permissions problems in the past on a friend's Linux/w$
installation (but didn't took notes, as I do not use w$ anymore and he
switched to a w$ freeware solution :/) - IIRC, there was a user substitution
to the "system" user (or from, I don't remember) that clobbered the whole
restoration process or something close to that.


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


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

[Bzzzz]

On Wed, 13 Dec 2017 15:21:09 +0100
"Jens Potthast"  wrote:

> Ok, I don't understand, what you are talking about. Sorry. 

>From some Samba ML posts, this error code means the server command is
not able to either create the destination directory OR can't write in it.
But it is Samba, not m$.

> BackupPC does create a directory, if it does not already exists. If it
> does, it stops with an error. It restores the first file and then it
> stops.

Hmm, have a look at w$ logs, if they are correctly set (? duno if it is
even possible to change the log level into nsa self-service), they may
reflect what the real problem is on your client as m$ is also known to
sometimes group several errors under only one error code.

> So, if neither directory nor files do exists, why would restore
> fail?

I had some permissions problems in the past on a friend's Linux/w$
installation (but didn't took notes, as I do not use w$ anymore and he
switched to a w$ freeware solution :/) - IIRC, there was a user
substitution to the "system" user (or from, I don't remember) that
clobbered the whole restoration process or something close to that.

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

[Jens Potthast]

Ok, I don't understand, what you are talking about. Sorry. 

BackupPC does create a directory, if it does not already exists. If it does,
it stops with an error. It restores the first file and then it stops. So, if
neither directory nor files do exists, why would restore fail?

Anyway, thanks for helping!

-Original Message-
From: B [mailto:lazyvi...@gmx.com] 
Sent: Mittwoch, 13. Dezember 2017 14:57
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] Trouble with restore

On Wed, 13 Dec 2017 14:44:25 +0100
"Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:

Correction, the samba ML links this code to an inability to _create_ the
destination DIR (should be a m$ signification; they love Doublespeak :/)

> No, that's not the problem. Files should be overwritten. *But* even 
> restoring to a new and empty directory fails with the same error.
> 
> -Original Message-
> From: B [mailto:lazyvi...@gmx.com]
> Sent: Mittwoch, 13. Dezember 2017 14:25
> To: backuppc-users@lists.sourceforge.net
> Subject: Re: [BackupPC-users] Trouble with restore
> 
> On Wed, 13 Dec 2017 14:01:46 +0100
> "Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:
> 
> > tar:1596 Can't mkdir Path to filename:
> > NT_STATUS_OBJECT_NAME_COLLISION
>   
> ^^ You obviously already have a file having the same name 
> in this restore DIR.


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


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

[Bzzzz]

On Wed, 13 Dec 2017 14:44:25 +0100
"Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:

Correction, the samba ML links this code to an inability to _create_
the destination DIR (should be a m$ signification; they love
Doublespeak :/)

> No, that's not the problem. Files should be overwritten. *But* even
> restoring to a new and empty directory fails with the same error.
> 
> -Original Message-
> From: B [mailto:lazyvi...@gmx.com] 
> Sent: Mittwoch, 13. Dezember 2017 14:25
> To: backuppc-users@lists.sourceforge.net
> Subject: Re: [BackupPC-users] Trouble with restore
> 
> On Wed, 13 Dec 2017 14:01:46 +0100
> "Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:
> 
> > tar:1596 Can't mkdir Path to filename:
> > NT_STATUS_OBJECT_NAME_COLLISION  
>   ^^
> You obviously already have a file having the same name in this restore
> DIR.

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

[Jens Potthast]

No, that's not the problem. Files should be overwritten. *But* even
restoring to a new and empty directory fails with the same error.

-Original Message-
From: B [mailto:lazyvi...@gmx.com] 
Sent: Mittwoch, 13. Dezember 2017 14:25
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] Trouble with restore

On Wed, 13 Dec 2017 14:01:46 +0100
"Jens Potthast" <jens.potth...@innovation.uni-bremen.de> wrote:

> tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION
  ^^ You
obviously already have a file having the same name in this restore DIR.


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


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

[Bzzzz]

On Wed, 13 Dec 2017 14:01:46 +0100
"Jens Potthast"  wrote:

> tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION
  ^^
You obviously already have a file having the same name in this restore
DIR.

--
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] Trouble with restore

[Jens Potthast]

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/