Query for VMs that have been discovered but not backed up

Hey @christopherlecky !  Have you checked out the GET vm API call?

I’m not sure if you’ll see discovered but NOT backed up, though it should be easy enough to find out.

https://api.commvault.com/#f51801e5-1d9d-4561-83de-37c487b4987c

I have actually, the problem is that its alot more work because the api does not have the ability to filter by name.

I would either have to convert to xml and use an xmlpath query to get the vm or convert the output to a resultset. There is also the issue of pagination, because of the size of the return the response comes in several pages. So it becomes little mini project to parse out what I want 😥

Ill look into this. Maybe I just steal the dataset to find the mystery tables.

@Mike Struening , can you unmark this as solved.

I am browsing on a phone and clicked it by mistake.

Done!

😂

Maybe I should just log off for the day.

@Mike Struening , please unmark that for me.

This is the last time today, I promise.

HAHAHA!  I saw that and was about to fix it for you 🤣

Im going to take my time clicking from now on 😂😭

I give up. Just leave it like that.

Good candidate for my favorite thread of all time!

If you get a better answer and reply here, I’ll move the answer 🤣

Update:

I pulled the dataset and I am deconstructing the query and I know what I need is in here somewhere…. that said I’m going to do some complaining aimed at the devs.

Would it hurt to add some comments to your queries?

That is all.

Thanks. Chris. 

edit: Just to be clear, you guys do great work but comments people! comments!

@christopherlecky , I can happily pass along your feedback as an MR.  You want to give me specifics to share with them?

No need, im sure some of them are reading this and my guess is that is an issue with every dataset, I just want them to know that customers have to read them. So more comments = less tickets and complaining.

All good, then.  Let me know if there’s anything else I can do!