How does the multiple repository synchronization process work?
VigilEnt Policy Center 5.0
Overview of the Synchronization Process
When you synchronize an external database with VPC, VPC updates the timestamp on all users and groups within the VPC database. Once the synchronization completes successfully, VPC marks as "retired" all users and groups that still have the old timestamp as if they were still in the newer synched-database, the timestamp would be current. The retired object in inactive and VPC includes the extension .retired. You cannot search within VPC for objects marked retired so you cannot add these users and groups to access control lists. However, you can include these users and groups in reporting by selecting the option Include deleted users and group in the Scope page.
User and Group Synchronization Order
During the synchronization process, VPC synchronizes all groups first, and then synchronizes all users. VPC addressed any circular references in the groups when synchronizing the groups.
VPC starts each synchronization as a separate thread. Although VPC can run all the threads simultaneously, system performance would suffer. As a result, VPC runs each synchronization separately. When VPC begins synchronizing the first repository in the queue, it starts a new thread. If another repository is in the queue, VPC waits until it completes the first thread before beginning to synchronize the second repository. The process repeats for each additional repository in the queue.
VPC displays a failure message if a synchronization fails. A failure occurs when the connection between VPC and the synchronizing repository fails. You can identify the failure cause if your audit logs are enabled to log the failure.