Skip to main content
Solved

Exchange DAG Databases are not being discovered correctly


Kamil W
Commvault Certified Expert
Forum|alt.badge.img+11
  • Commvault Certified Expert
  • 83 replies

Hello guys,

 

I need your help.

 

The Customer has an Exchange DAG pseudo-client with subclient ‘databases’ configured as a subclient that contains all DAG databases.

They have removed some databases from Exchange DAG nodes (on server level).

However, after click on ‘Discover’ button, deleted databases are still visible as a content.

 

 

The CS and Exchange nodes are running 11.20.46. Exchange version is 2016.

 

I cannot find any hotfix regarding to this issue.

 

As a workaround, the Customer put deleted databases to default subclient and disabled activity on subclient level.

 

Any ideas how to fix it?

 

Rgds,

Kamil

Best answer by Mike Struening RETIRED

@Kamil W , confirmed the above is correct.  We don’t ‘forget’ databases.  Moving them to a separate subclient is the right path.  We don’t want to lose that discovery so we err on the side of caution.

View original
Did this answer your question?

4 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Kamil W , I’ll look into this for you, though I know we keep content around even if they are deleted (because they might be down and coming back later).

You’re essentially looking to have content ‘undiscovered’ if I understand?


Mike Struening
Vaulter
Forum|alt.badge.img+23

@Kamil W , confirmed the above is correct.  We don’t ‘forget’ databases.  Moving them to a separate subclient is the right path.  We don’t want to lose that discovery so we err on the side of caution.


Kamil W
Commvault Certified Expert
Forum|alt.badge.img+11
  • Author
  • Commvault Certified Expert
  • 83 replies
  • August 4, 2021

Many thanks Mike! I can always count on you :)

 

Rgds,

Kamil


Mike Struening
Vaulter
Forum|alt.badge.img+23

Happy to help!!!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings