# Slave synchronization with notification "Slave Initialized"
**URL:** https://dmap-community.ductus.global/t/slave-synchronization-with-notification-slave-initialized/242
**Category:** CDB and CDB API
**Created:** [October 12, 2015, 7:13am UTC](https://dmap-community.ductus.global/t/slave-synchronization-with-notification-slave-initialized/242 "2015-10-12T07:13:49Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@yogevc](https://dmap-community.ductus.global/u/yogevc)
#### Post date: [October 12, 2015, 7:13am UTC](https://dmap-community.ductus.global/t/slave-synchronization-with-notification-slave-initialized/242/1 "2015-10-12T07:13:49Z")
From the ConfD user guide (5.4)
> CONFD\_HA\_INFO\_SLAVE\_INITIALIZED A slave node has just finished its initialization and synchronization
> of the database. The slave is now fully operational. Only sent at slave nodes. The field
> cdb\_initialized\_by\_copy is set to 1 if ConfD concluded that the entire CDB database has to
> be copied and 0 if a copy was avoided.
What are the causes for which the `cdb_initialized_by_copy` won’t be `1` (won’t be copied)?
- If the data base is already synchronized?
- What if the data base is half synchronized? (I’m relating to the bold words: “The field cdb\_initialized\_by\_copy is set to 1 if ConfD concluded that **the entire CDB database has to be copied** ”)
Thanks!
---
### Author:  [@cohult](https://dmap-community.ductus.global/u/cohult)
#### Post date: [October 12, 2015, 9:32pm UTC](https://dmap-community.ductus.global/t/slave-synchronization-with-notification-slave-initialized/242/2 "2015-10-12T21:32:58Z")
From the UG:
> If the order is to be a slave, the node will contact the master and possibly copy the entire configuration from the master. This copy is not performed if the master and slave decide that they have the same version of the CDB database loaded, in which case nothing needs to be copied. This mechanism is implemented by use of a unique token, the “transaction id”