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?
Originally Posted by falko
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...