DLT object purge batch arguments


greetings all.

i have couple of quick questions related to dlt purge. have 60,000 objects purge in child domain empty root.

my question way ad process's batches. says default  delete 1000 objects every 15 minutes. mean run 4 times hour total of 4000 objects , take 15 hours default? if true how override default settings -b argument i have listed dltpurge arguments below.....also has ever run problems deleting alot of these objects. ive done in dev without issues hard reproduce w/o having dlt objects there. thanks!

*******************************************************************

purpose:   delete active directory objects distributed link tracking
           server service (assumes dlt server has been disabled
           on dcs)

usage:     dltpurge.vbs <arguments>

arguments: -s server
           -d fullyqualifieddomain
           -b batchsize batchdelayminutes (default 1000 , 15)
           -t (optional test mode, nothing deleted)

note:      objects deleted in batches, delay between each
           batch.  size of batch defaults 1000 objects, and
           length of delay defaults 15 minutes.  these
           values can overridden using -b option.

example:   dltpurge.vbs  -s  myserver  -d distinguishedname dc=mydomain,dc=mycom
pany,dc=com

*********************************************************************************************

 

i believe understanding correct , take around 15 hours.  should able incorporate changes syntax:

dltpurge.vbs  -s  myserver  -d distinguishedname dc=mydomain,dc=mycompany,dc=com -b 5000 15

this remove 5000 objects every 15 mins.

give thought how many objects think might safe.  see spike in replication traffic during changes , dcs pretty busy, presumably why script batches them , incorporates delay.  after-hours task rather during working day.

alexei



Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file