Hi,
"failing back" essentially just turns off the MTA and Notifier service and starts it up on the "Primary" role holder. Replication remains active througout that transition and isn't affected by this act. The server running MTA and Notifier is responsible for message delivery and notifications (MWI, etc.)
Here are a couple commands for UC and the platform side that can verify replication on each server:
show cuc cluster status
utils dbreplication status
Hope that helps,
Brad