Skip to main content
Solved

Unable to delete old client, says snapshots are still mounted


ZachHeise
Byte
Forum|alt.badge.img+9

It’s finally been a year (our retention period) for the old file server, which was running on a windows failover cluster, i.e. they needed to have the mediaagent component installed in order for them to work. Now when I try to retire the client “WinFSCluster”, it is showing me the following error - “Failed to delete Client. Snapshots are still mounted.”

Nothing comes up in a web search for this error message, so I hope you can assist me, commvault forum folks!

 

Best answer by ZachHeise

The ticket was 220322-699 - got it resolved today. The solution was that I had some jobs still listed under the “primary snap” storage policy that I didn’t know about (I had only been looking under ‘primary’ policy) - I assumed everything had been moved out of the primary snap → primary but was incorrect. Once the tech had my database staged and was able to see that, he suggested I just delete these ancient snaps from the storage policy, and after I did so - and ran a Data Aging job - I was able to delete the client fully.

 

The error message was just confusing is all. Telling me that the “snapshots are still mounted” made me look for mounted snapshots, obviously. When really it was a matter of snapshots just still existing at all that hadn’t been moved to primary backup storage that needed to be moved/deleted.

View original
Did this answer your question?
If you have a question or comment, please create a topic

5 replies

byates
Vaulter
Forum|alt.badge.img+3
  • Vaulter
  • 19 replies
  • March 21, 2022

Hello ZachHeise,

 

I would try checking the Backup History of the Client and selecting Include Backup Copy and Catalog Snapshot Jobs.
 

 

Then check for them in Array Management.

 

 

 

Then follow the documentation: Deleting Snapshots (commvault.com)

 

 


ZachHeise
Byte
Forum|alt.badge.img+9
  • Author
  • Byte
  • 67 replies
  • March 23, 2022

Hmm, unfortunately this didn’t solve the problem. All my snapshots for this client already show as unmounted. I have staged my commserve database and uploaded it to commvault support - I have a paid support contract with them. Once they have found the solution for me I will post it here on the public forums, so hopefully it might help someone else in the future.


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

Thanks for the update @ZachHeise !  Can you share the case number here so I can track it?


ZachHeise
Byte
Forum|alt.badge.img+9
  • Author
  • Byte
  • 67 replies
  • Answer
  • March 24, 2022

The ticket was 220322-699 - got it resolved today. The solution was that I had some jobs still listed under the “primary snap” storage policy that I didn’t know about (I had only been looking under ‘primary’ policy) - I assumed everything had been moved out of the primary snap → primary but was incorrect. Once the tech had my database staged and was able to see that, he suggested I just delete these ancient snaps from the storage policy, and after I did so - and ran a Data Aging job - I was able to delete the client fully.

 

The error message was just confusing is all. Telling me that the “snapshots are still mounted” made me look for mounted snapshots, obviously. When really it was a matter of snapshots just still existing at all that hadn’t been moved to primary backup storage that needed to be moved/deleted.


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

Awesome share, thanks!!!


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