you have to differentiate between the UCS domains and Windows domains. Both domain types use similar terms but with different meaning.
A UCS domain consists of the LDAP servers. If you’re running a pure Linux/Unix domain then those LDAP servers are enough for authentication. The role of »UCS Domain Controller Backup« refers to this LDAP domain. It means, among other things, that the UCS DC backup containts an always up-to-date copy of the whole LDAP tree and all other domain-related data (e.g. the SSL certificates). Additionally a DC backup can be converted to a DC master manually should the DC master suffer a fatal error (e.g. total hardware failure).
A UCS Domain Controller Slave, on the other hand, only contains a sub-set of the whole domain data (e.g. not the SSL certificates). A UCS DC slave can obviously not be converted to UCS DC master.
None of this has anything to with a Windows domain yet. An Active Directory Windows domain only knows »Domain Controllers« and does not differentiate between master and slave AD DCs (unlike an NT domain). All Active Directory Domain Controllers are equal.
The important thing to know is that a UCS Domain Controller (no matter which role) does NOT automatically offer Windows Domain services. It only does if Samba v3 or v4 is installed on that server (keep in mind that for an Active Domain style Domain Controller you need Samba v4).
So in order to answer your question: your UCS DC Backup and UCS DC Slave will only be able to offer Windows Domain services if Samba is installed, too. Judging from your description I’d guess that you either do not have Samba installed or only Samba v3 and that you’re using an Active Directory style Windows Domain.
A Samba server installed on a UCS DC Backup/Slave will of course use the LDAP directory installed on the same server. That’s one of the advantages of running UCS DC Backup/Slave in remote locations.
So the typical use case is to have both the UCS DC master and UCS DC backup in the same location (e.g. the main office) and use UCS DC slave in remote locations (e.g. branch offices).
See the UCS Administration Manual section 3.3 »UCS system roles« and following.