Skip to main content
Question

Metro Container Storage Missmacht

  • February 14, 2023
  • 6 replies
  • 116 views

Forum|alt.badge.img

Hey guys,

I made a quite new discovery that is totally new to me and I try to understand where this is comming from, maybe someone can help :)

Scenario: There are 2 ESX clusters, connected via Metro. The DataStore on the source site is ~2TB, the datastore on the destination is about 1TB and I have no clue why :)

Both DataStores only use compression, there are no other snapshots on the source side and this is for a couple of days now, so no curator run should be involved.

 

Ideas anyone?

 

Cheers, Flo

This topic has been closed for replies.

6 replies

JeroenTielen
Forum|alt.badge.img+8

How are the containers configured (advertised size??) What is the storagepool size on both clusters?


Forum|alt.badge.img
  • Author
  • Adventurer
  • February 15, 2023

Hi Jeroen,

both containers are configured with 8TB advertised and reserved, storage pools are both about 125TiB


JeroenTielen
Forum|alt.badge.img+8

Got it. But the 2TB and 1TB is that what is being used or available then?


Forum|alt.badge.img
  • Author
  • Adventurer
  • February 15, 2023

2TB / 1TB is the used space shown in Prism Central


JeroenTielen
Forum|alt.badge.img+8

Got it. This can be due to dataprotection snapshots or recovery points (leap) in Prism Central. Or maybe not all vm's are protected by the protection policy (metro). 


Forum|alt.badge.img
  • Author
  • Adventurer
  • February 15, 2023

We don’t have any other Data Protection in these clusters than metro. I also had a look into the local snapshots on the PD, there is one expired snapshots of 9,x GiB..

I don’t get it :-D