[Samba] Questions on DRS replicate command

[Julien Ropé]

Hi,

Thanks for your feedback.

Here are some more information :

- what version of samba you're using.

4.7


- the actual error you're getting (e.g. a python exception?).

This is a timeout error in samba-tool

I've not seen it myself, but from the description, it looks like an 
exception raised from the samba-tool script.


- the exact options you're passing to the command, e.g. are you using 
--local?

samba-tool drs replicate DC2 DC1 dc=samdom,dc=example,dc=com

We're note using "--local"


- roughly how many records are in your DB.

There are more than 25000 objects


Best regards,

Julien




Le 25/03/2019 à 21:47, Tim Beale a écrit :
> Hi,
>
> We fixed a similar problem with the join command in v4.10 - see
> https://bugzilla.samba.org/show_bug.cgi?id=13612
>
> I think we've done some testing recently around 'samba-tool drs
> replicate' on large DBs without problems. So it might help if you tell us:
> - what version of samba you're using.
> - the actual error you're getting (e.g. a python exception?).
> - the exact options you're passing to the command, e.g. are you using
> --local?
> - roughly how many records are in your DB.
>
> 1. It depends a bit on what command options you specified.
>
> 2. The command should wait until replication completes, unless you use
> the --async-op option.
>
> 3. Not sure. Maybe try 'samba-tool drs showrepl'?
>
> Thanks,
> Tim
>
> On 26/03/19 5:10 AM, Julien Ropé via samba wrote:
>> Hi,
>>
>> I have some question about the command "samba-tool drs replicate"
>> command.
>>
>> On a server with a big number of objects to synchronize, the command
>> makes a timeout error. Now it looks like the sync actually occurs.
>>
>> I also see that there is an option to make the command asynchronous
>> (not waiting for the result of the replication), but then I'm not sure
>> how to confirm the process is complete and successful.
>>
>> 1) when the replication is synchronous, if the timeout occurs, is it
>> actually interrupted or is it just the client side tool that gives up
>> waiting for an answer ?
>>
>> 2) when you know the replication is going to be long, can you ask the
>> command to wait for the end (no timeout) ?
>>
>> 3) when you use the --async-op option, how can you check when the
>> command is complete ? Can you get a status for it, making sure it has
>> actually succeeded ?
>>
>>
>> Regards,
>>
>> Julien
>>
>> -- 
>> Message envoyé grâce à OBM, la Communication Libre par Linagora
>>
-- 
Julien ROPÉ

Mail : jrope at linagora.com
Tél : 06.38.99.80.22

--
Message envoyé grâce à OBM, la Communication Libre par Linagora