Skip to main content
Solved

Unable to change value of "sparse support" checkbox in Disk Library


ZachHeise
Byte
Forum|alt.badge.img+9

Hello,

We just added more storage to a mediaagent, via a new mount path in an existing disk library. The new mount path is an SMB share from a Dell Isilon, and the admin of the isilon confirmed they had enabled sparse support for the share - but he turned it on, after I’d already added the mount path.

As this user in the Commvault forums described, I should just be able to check/uncheck the checkbox for ‘sparse support’ right? It is not working for me though. What is the trick to changing the status of this checkbox? Are there other ways via the Web Command Center, or CLI, to do the same thing?

I also don’t see any means in the ‘properties’ of this mount path to enable this.

 

 

Best answer by ZachHeise

Yes, deleting device_59 and adding the mount path again (creating a new device_60) did the trick. Sparse support is now checked.

View original
Did this answer your question?

6 replies

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • July 18, 2022

Wondering if it will set this option when you cycle services on the media agent as it will check some basics regarding the mount path 🤔 Just a shot in the dark here.. Never had this enabled afterwards 


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

😑 hmm, not really something I can do while in the middle of an aux copy! If you’re pretty sure on that @Jos Meijer please confirm; I’d love to activate this setting WITHOUT a full service stop/start on this mediaagent.


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

There’s nothing IN this new device_59 right now. Would it be better if I just deleted it and made a new device on the SMB share, now that sparse is turned on? Commvault should detect sparse capabilities at time of creation, right, and check that properly this time?


Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • July 18, 2022

If the GUI allows you to delete it then go for it! Once deduplicated data is allocated you won't get a second chance.


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

Yes, deleting device_59 and adding the mount path again (creating a new device_60) did the trick. Sparse support is now checked.


Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • 638 replies
  • July 18, 2022

Awesome 👍👍


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