Hello list! After many hours of tests and research, I need your help. Here is a short-as-possible report of what is happening and what I've done already. Actually, I have three problems, but let's try to get the first one fixed first for a start.
Why read any further?
=====================
If my environment is similar to your environment, you should test a direct
restore operation on your hosts, just to be sure to have a valid
backup-system in case of emergency. (Ok, restore to zip/tar does work :-))
My environment
==============
Backup-Server: BackupPC 4.1.5 running on Debian 8.10 with smbclient 4.2.14
Host: Windows Server 2012 R2
The situation
=============
Backing up is no problem*, but doing a direct restore is impossible.
What happens?
=============
Using the (default) configuration for smb restore:
$Conf{SmbClientRestoreCmd} = '$smbClientPath \\\\$host\\$shareName
$I_option -U $userName -E -d 1 -c tarmode\\ full -mSMB3 -Tx -';
The operation stops with:
> tar:316 tarmode is now full, system, hidden, noreset, quiet
> tar:1596 Can't mkdir test: NT_STATUS_OBJECT_NAME_COLLISION
What I've done and checked so far
=================================
* As BackupPC user, I can connect to the windows host in an interactive
smbclient-session.
* While in smbclient-session: I'm able to create directories and put files
on the host.
* While in smbclient-session: Trying to create a directory, that already
exists, I get the same error as above, what seems legit, since the directory
exists.
* Swapped my smb.conf with the vanilla smb.conf
* Extracting files with BackupPC_tarCreate locally does work.
* Piping BackupPC_tarCreate-command to smbclient-command manually and change
path options: if the new path does not exists, it is successfully created,
but then instantly stops with the error as seen above (since BackupPC tries
to create the path as soon as it tries to put the actual file in the new
directory).
* Checked permissions for backuppc-smb-user on windows domain/filesystem.
Although this was not likely, since smbclient-sessions do work.
* Checked another environment: BackupPC 4.1.x on Debian 9.2 and Windows
Server 2012 R2 as host on a different subnet - same error occurs. This
system is only a couple of weeks old and does not serve any other purpose.
This is, why I think that other users are affected, too.
Possible solution
=================
Let BackupPC continue to work, if creation of a directory fails *just
because* it already exists. Alternatively do not try to create a directory,
if it already exists. (If smbclient is responsible for breaking the
operation, please guide me to someone to contact.)
*Since my setup has undergone some heavy migration work (moved from BackupPC
3.x to 4.x, moved my pool from v3 to v4), I have two other points to check
that might be something only existing for my setup:
- Filenames get chopped off after 97-99 characters. It's visible on the
web-frontend, if you navigate to a file in a backup.
- Some directories do net get backed up (yes, I checked permissions)
Any input is really appreciated!
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/
