[Samba] Error samba backup 4.10.5

[Tim Beale]

On 4/07/19 7:50 PM, Trenta sis via samba wrote:
> Hi,
>
> We were using samba_backup from 4.4.5 and after upgrade to 4.10.5 we
> are trying to configure new method, but is not working, tried:
>
> offline with samba stopped:
> # samba-tool domain backup offline --targetdir=/local/test/
>
>
> ERROR(ldb): uncaught exception - partition_metadata: Migrating
> partition metadata: create of metadata.tdb gave: partition_metadata:
> Unable to create /usr/local/samba/private/dns/sam.ldb.d/metadata.tdb:
> Device or resource busy
>
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/netcmd/__init__.py",
> line 185, in _run
>     return self.run(*args, **kwargs)
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/netcmd/domain_backup.py",
> line 1072, in run
>     ldb_obj = Ldb(path, lp=lp)
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/__init__.py",
> line 115, in __init__
>     self.connect(url, flags, options)
It looks like the offline backup doesn't work with a Bind DLZ DNS
backend. I've raised a bug for this:
https://bugzilla.samba.org/show_bug.cgi?id=14027
> online with samba started
> samba-tool domain backup online --targetdir=/local/test/
> --server=samba4-test-UAdministrator
> ERROR(runtime): uncaught exception - (3221225506, '{Access Denied} A
> process has requested access to an object but has not been granted
> those access rights.')
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/netcmd/__init__.py",
> line 185, in _run
>     return self.run(*args, **kwargs)
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/netcmd/domain_backup.py",
> line 264, in run
>     backup_online(smb_conn, sysvol_tar, remote_sam.get_domain_sid())
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/ntacls.py",
> line 512, in backup_online
>     ntacl_sddl_str = smb_helper.get_acl(r_name, as_sddl=True)
>   File "/usr/local/samba/lib/python3.4/site-packages/samba/ntacls.py",
> line 334, in get_acl
>     smb_path, SECURITY_SECINFO_FLAGS, SECURITY_SEC_FLAGS)
> signed SMB2 message
>
This problem is occurring backing up the sysvol share. There's a
particular GPO that it's having trouble accessing over an SMB
connection. Another samba user has debugged this problem previously, and
managed to work around it by removing the problematic GPO (because it
was old/unnecessary).
https://lists.samba.org/archive/samba/2019-April/222417.html

I'm not sure, but it's possible that bug #13917 might help. You could
try samba v4.10.6 when it's released.
https://bugzilla.samba.org/show_bug.cgi?id=13917

Cheers,
Tim