This is not normal and the reason you are seeing this message is because the servers were individually restored. This is not the correct procedure.
Here is what you have to do,
Restore the Publisher server from a backup taken from the old Publisher server.
Run the 'utils cuc cluster overwritedb' command on the subscriber server - this will copy the database from the Publisher server and establish replication.
This procedure is documented in the DRS guide.
What you have done may work, but not tested or documented anywhere. Since both databases have the required data, it may work if replication is reset. Follow the steps mentioned in this document to fix replication:
many thanks for the information. I will make this / test this by this evening or tomorrow when I`m back in the office.
Is there any need to make an own backup from Subsriber when I don`t have to restore the Subscriber but overwrite the db from pub to sub?
When I compare it with CUCM I can see in DRS schedule from CUCM pub both CUCM servers CUCM pub and CUCM sub as registered components to backup and when I restore CUCM from the pub I can restore both CUCM servers pub and sub.
In the DRS schedule of Unity pub I only can see the Unity pub as registered components but not components of Unity sub. So therefore the question if there is any need to take a own DRS backup from Unity sub?
Or do I only have to restore the unity pub from his own backup and make the overwritedb?
You do not need a backup from the Subscriber Server. A subscriber backup is not normally taken. Just the Publisher backup will do. Sometimes the Backup may get corrupted due to network disruptions during the transfer or if the channel is not closed correctly after the transfer of data. In these scenarios, a backup from subscriber will help. But these are really rare scenarios.
Even if you loose the Publisher server, you can reinstall the Publisher server and run the renegotiate command to copy the database from Subscriber to Publisher. So you really dont need a back. The only scenario you need a backup is for migrations or when both servers fail.
The Call Manager back up does not backup the data from the subscribers. You'll see the components as registered. All it does is backup the platform related information to identify the nodes. If the components are not registered there could be issues with the AMC or RIS data collector service. There could also be issues with replication. This does not prevent the backup from being successful. I believe it should work fine even if the components of the other servers are not registered.
In Unity Connection, you'll find registered components for only that node.
CUCM and Unity Connection are designed by two different teams and hence (I believe) the difference.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...