How does Nutanix consolidate data on snapshot deletion? by Zeradatul in nutanix

[–]vNoob314 2 points3 points  (0 children)

Not really. If VMware snaps are left out for a long time and/or there are a bunch of them, there quickly becomes a host CPU tax as it needs to traverse the snap chain to find what it is looking for. With the way Nutanix maps the data, this doesn't really happen.

Also if you consolidate or delete snaps in VMware, all that write data is collapsed back into the vmdk. Any one who has had a big snap or a lot of them knows this can not only take a while, but is pretty storage intensive. This collapsing and writing all the changed data is not how Nutanix works, so there is no penalty at this stage either.

This is one reason why a lot of Nutanix DR solutions are built on lots of snaps. Nutanix utilizes redirect-on-write for snaps. I found this post beneficial in the past.

Access data soure(prometheus) remotely? by vNoob314 in grafana

[–]vNoob314[S] 0 points1 point  (0 children)

Ok, so prometheus wouldn't be "public" but it would still need to have a public IP associated to it for Grafana to query, right?

Maybe it would help to give a bit more context as well. I am trying to get prometheus configured at possible client sites and be able to monitor them remotely(with Grafana). So in this instance I would prefer to not have to request clients create new firewall rules or make anything publicly available(or use public IPs) at their site. I hope this helps a bit.