View Single Post
  #14  
Old 20th September 2010, 15:44
tester321 tester321 is offline
Member
 
Join Date: Jul 2009
Posts: 34
Thanks: 7
Thanked 2 Times in 2 Posts
Default Is it a specific table?

OK,

Can you suggest a Table within ISPConfigdb that should not be replicated then, so the Slave can act on the .run but not have the completion flag set via replication before it acts?

Thanks

Quote:
Originally Posted by falko View Post
Oh... I think that happens because the update status in the master database gets deleted after the backend has run, and that deletion of the update status gets replicated to the salve database before the backend on the slave server could do its job...
Reply With Quote