similar to: safe to replace just one ldb file?

Displaying 20 results from an estimated 11000 matches similar to: "safe to replace just one ldb file?"

2024 Jul 17
1
dbcheck gets uncaught exception
>> The only additional output I get from running with debug >> >> samba-tool dbcheck --cross-ncs --fix -d 10 >> >> is >> >> ndr_pull_dom_sid: ndr_pull_error(Range Error): value out of range at >> ../../librpc/ndr/ndr_sec_helper.c:329 OK I think I'm at least a small step further. I realized that tdbbackup failed on
2015 Sep 01
1
Samba 4 DC backups
On 2015-09-01 18:48, L.P.H. van Belle wrote: > and most important... > > If you have 2 DC's ... > ! NEVER USE THE BACKUP SCRIPT TO RESTORE ONE OF THE DC's ! > > This wil corrupt your AD databases.. > Just remove the old DC from the domain and add a new one if needed . > > .. Rowland. > This is also a nice to have in your backup script. > Auto detect
2019 Jun 18
1
some questsions to online backup and a failiure with offline backup
Hi, first online backup works, but why some parts are missing? Online: root# samba-tool domain backup online --targetdir=/mnt/backup/online/ --server=DC -UAdministrator Backup created 2019-Jun-18 11:04:19 Using samba-tool version: Samba 4.10.2 Domain online backup, using DC 'DOMAIN' Backup for domain DOMAIN (NetBIOS), DOMAIN (DNS realm) Backup contains domain secrets: True missing
2015 Jan 05
2
backup using the packages of Sernet
dear, I made the installation of Samba4 in centos6, now I need to back up the structure, tried using the script that samba.org offers more he is giving this error. See the error through the bash -x bash -x samba_backup.sh + FROMWHERE = / var / lib / samba + WHERE = / root / backups + '[' N '' ']' + '[' -n '' -a -d '' ']' + '[' -n
2012 Feb 02
1
Error in provisioning Samba4 Alpha 18 from git
Hi, I have a problem. The prerequisites are: * Vanilla Ubuntu 10.04 install * Followed the http://wiki.samba.org/index.php/Samba4/HOWTO In step 4, after running the command: ./source4/setup/provision --realm=samdom.example.com --domain=SAMDOM --adminpass=SOMEPASSWORD --server-role='domain controller' i get the following error when the provisioning run tdbbackup from the script
2015 Sep 01
2
Samba 4 DC backups
Mark Ok so you doing the exact opposite of what the samba_backup script does with regards to ldb and tdb files, but then you are shutting down Samba to do a backup anyway so it doesn't really matter what you are doing in this regard. I want a consistent backup while Samba is running. Regards Mike On 2015-09-01 16:08, Mark Foley wrote: > Here's what I do before tar'ring: >
2010 Dec 07
3
Samba4 LDAP LDB Indexes
I have a system running Samba 4 Alpha 11, and I seem to have a corrupted LDB file in my directory. (Probably the result of taking a backup without using tdbbackup). Right now, running tdbbackup on the file produces an error message similar to the following: Failed to insert into DC=WWW,DC=EXAMPLE,DC=COM.ldb.bak.tmp failed to copy DC=WWW,DC=EXAMPLE,DC=COM.ldb If I run ldbsearch -H
2015 Sep 01
7
Samba 4 DC backups
I have a few Samba 4.2 DC in production now and figured that I should do something about backups. I have read https://wiki.samba.org/index.php/Backup_and_restore_an_Samba_AD_DC and had a look through the samba_backup script and have a few questions. Firstly I am using the Sernet packages on Centos7. I am assuming the following mappings from the script for my set up /usr/local/samba/etc is
2020 Feb 11
1
ldb errors after upgrade, cause?
Hi list, for future reference: we haven't been able to fix it. Upgrading to 4.9.18 didn't help, so in the end we decided to downgrade to our previous version (4.5.12) which doesn't have this problem. Hooray for tdbbackup! Thanks Louis for thinking with us. Best regards, Roel And for Google: smbd[16461]: ldb: Failure during ltdb_lock_read(): Locking error ? Busy smbd[16461]:
2019 Aug 10
2
Standalone Server User Import / Export
Am Freitag, den 09.08.2019, 13:41 +0100 schrieb Rowland penny via samba: > ayers at vmbuster:~$ sudo tdbdump samba.tdbsam-export > > { > > key(19) = "INFO/minor_version\00" > > data(4) = "\00\00\00\00" > > } > > { > > key(9) = "NEXT_RID\00" > > data(4) = "\E8\03\00\00" > > } > > { > > key(13) =
2014 Jul 08
2
samba4 replication issues | sam.ldb inconsistency
Hi all, We seem to have some issues with our samba4 ad setup. I posted about this last week already but had received no replies at all so far. :-( What is our situation: two domain controllers (dc1 and dc2), one (separate) fileserver, all running sernet-4.1.7. From the workstations perspective, everything is running as it should, there appear to be no issues. However: something in my
2015 Sep 01
1
Samba 4 DC backups
On 2015-09-02 08:22, Mark Foley wrote: > Mike, > > I thought I pretty much did the same thing as the backup script: backup > ldb, do > tar. Also, I am stopping Samba for good measure, but I don't think I > need to. > What makes you say I'm doing the "exact opposite" of what the samba > script does? > Please explain, I want to be consistent with
2016 May 13
3
Invalid data for index DN=@INDEX:OBJECTCLASS:DNSNODE
We have a Samba primary domain controller "empire", which seems to have DNS update issues. We can seem to query all records on empire just fine, and we can modify IPs for existing records, but it will not delete or add new records. Attempting to delete via the AD tools shows "Local security authority database contains an internal inconsistency". Adding a record on the command
2024 Jul 18
1
dbcheck gets uncaught exception
> Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of the > other files in the same directory) directly, do all changes through > sam.ldb, otherwise you have a very good risk of further damaging your > database. I'm not sure if the dup keys in the 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' is my root issue and why the dbcheck fails with that
2004 Feb 26
2
Trouble with install, still
I've tried building it on a server that I know has pretty much every library possible for a program to need, but I'm still not getting a good samba install. I'm on white-dwarf linux (kernel 2.4.25), gcc 3.3.2, Samba 3.0.2a White-dwarf is home-grown, very much like slackware. When I configure and make and make install, I don't get any errors, but I when I look for some files
2024 Jul 18
1
dbcheck gets uncaught exception
On Thu, 18 Jul 2024 10:29:04 +0200 Heiko Robert via samba <samba at lists.samba.org> wrote: > > Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of > > the other files in the same directory) directly, do all changes > > through sam.ldb, otherwise you have a very good risk of further > > damaging your database. > > I'm not sure if
2020 Feb 06
2
ldb errors after upgrade, cause?
L.P.H. van Belle via samba writes: > Is samba-dsdb-modules installed ? Yes, I checked again, and all packages are installed, all of them with the proper version, and no leftovers. This server works fine for a half a day, and then these errors happen, so I think it's unlikely that it's related to the install itself. I have already made a backup of all tdb files with tdbbackup and
2019 Aug 09
2
Standalone Server User Import / Export
Am Freitag, den 09.08.2019, 08:45 +0100 schrieb Rowland penny via samba: > On 09/08/2019 07:38, David Ayers via samba wrote: > > Am Donnerstag, den 08.08.2019, 20:01 +0100 schrieb Rowland penny > > via > > samba: > > > > > But what I could do, is copy the setup incl. the tdb files to a > > test VM to try to reproduce it, upgrade that test VM in the hope
2010 Jul 08
2
How to regenerate passdb.tdb
Hi, I was having problem with the tdbsam backend in which a particular user got listed twice with pdbedit. (http://www.mail-archive.com/samba at lists.samba.org/msg109110.html) Without much hope in fixing it, I am planning to re-generating passdb.tdb on my PDC by: (1)exporting tdbsam to smbpasswd backend (2)delete passdb.tdb (3)re-import smbpasswd to tdbsam backend With the command `
2007 Dec 06
2
How to repair corrupt ntprinters.tdb?
Hi, we are using samba 3.0.24 as a printspooler for 80 network printers with a 500kB ntprinters.tdb for some years now. When we recently restarted samba we noticed that the ntprinters.tdb automatically shrinked to 24kB and printing was no longer possible. tdbdump of the original tdb-file is impossible too: "Failed to open ntprinters.tdb" The strange thing about this: we can solve