Hi,
we create new client (Exchange DAG) and the discovery works fine. But one of the member servers found was not available. I can select olny of them.
Our AD User accout is correctly configured. Any ideas?
Thank you.
Solved
Exchange DAG
+2Best answer by fred minig
fred minig wrote:
Sujay kumar wrote:
following can be reasons
-- host name mismatch
-- missing exchange ida
-- duplicate entries present in GUI of missing member node
--in some case ping from from cs to member server using fqdn and short name both does not work so try that if any issue add hostfile entry (if required)
--check for the MonadCCRProxy.log and EvMGrs.log in Debug 10 during DAG discovery for additional details
-- some case after reconfiguraiton CS GUI needs to be closed open
-- one of the option using resetdag script , to clear any previous association if it is locked (for this we need to reveiw csdb and suggest support case may be helpfull)
Okay, thanks. I'll try
resetdag script，How does it work? Is there a statement
+13Have you installed the Exchange Agent on that second member server?
If the Exchange Agent were installed, I would have expected the second member server to be selectable.
+1Yes, the Exchange Agent has been installed on the second member server
Erase4ndReuseMedia wrote:
Have you installed the Exchange Agent on that second member server?
If the Exchange Agent were installed, I would have expected the second member server to be selectable.
- Vaulter
- 70 replies
+1Sujay kumar wrote:
I have checked and found no valid information, and I have checked that the FQDN of the two nodes is no problem, and the ports of CS and CS can also be accessed normally. This problem is caused after CS upgrade
- Vaulter
- 70 replies
following can be reasons
-- host name mismatch
-- missing exchange ida
-- duplicate entries present in GUI of missing member node
--in some case ping from from cs to member server using fqdn and short name both does not work so try that if any issue add hostfile entry (if required)
--check for the MonadCCRProxy.log and EvMGrs.log in Debug 10 during DAG discovery for additional details
-- some case after reconfiguraiton CS GUI needs to be closed open
-- one of the option using resetdag script , to clear any previous association if it is locked (for this we need to reveiw csdb and suggest support case may be helpfull)
+1Sujay kumar wrote:
following can be reasons
-- host name mismatch
-- missing exchange ida
-- duplicate entries present in GUI of missing member node
--in some case ping from from cs to member server using fqdn and short name both does not work so try that if any issue add hostfile entry (if required)
--check for the MonadCCRProxy.log and EvMGrs.log in Debug 10 during DAG discovery for additional details
-- some case after reconfiguraiton CS GUI needs to be closed open
-- one of the option using resetdag script , to clear any previous association if it is locked (for this we need to reveiw csdb and suggest support case may be helpfull)
Okay, thanks. I'll try
+1fred minig wrote:
Sujay kumar wrote:
following can be reasons
-- host name mismatch
-- missing exchange ida
-- duplicate entries present in GUI of missing member node
--in some case ping from from cs to member server using fqdn and short name both does not work so try that if any issue add hostfile entry (if required)
--check for the MonadCCRProxy.log and EvMGrs.log in Debug 10 during DAG discovery for additional details
-- some case after reconfiguraiton CS GUI needs to be closed open
-- one of the option using resetdag script , to clear any previous association if it is locked (for this we need to reveiw csdb and suggest support case may be helpfull)
Okay, thanks. I'll try
resetdag script，How does it work? Is there a statement
+13I suggest that you raise this with Commvault Support.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.