Hi

I'd like to see this answered also.  We are making , a lot , of VPSnaps of LUNs, they aren't in a seperate pool and we would very much like to know how much space they are really allocating within the pool.    Although all 'flyers', presentations mentioning VPSnaps 'space-efficient'  benefits it nowhere states 'how'  you can easily report on the snaps actual space allocation within the pool. 

Kind regards

Patrick

There are no commands that will help you to do that other than normal symcfg commands for TDEVs

so if you run symcfg -sid xxx list -tdev -range xxx:xxx this will give the allocated tracks for your VP SNAPs.

To get the amount of your shared tracks "that is the idea of VP Snaps" then you will need to run symcfg -sid xx show -pool -thin -detail -all | more

The output should look something like this:

# of Devices in Pool	: 557
# of Enabled Devices in Pool	: 557
# of Usable Tracks in Pool	: 2190360168
# of Allocated Tracks in Pool	: 487511484

# of Tracks saved by compression :  0

# of Shared Tracks in Pool

: 25632

There is a very useful whitepaper from support.emc.com describing the VP snaps with detailed explanation.

https://support.emc.com/docu40346_White_Paper:_Implementing_TimeFinder_VP_SNAP_for_Local_Replication.pdf?language=en_US

Hi Patrick,

Having had another look around

Within Unisphere  -> Performance -> Analyze   There is a Storage Group counter "total tracks", this appear to be the actual allocated tracks to the SG as opposed to the sum of all tdev sizes.

As all our clones are assigned to backup servers this gives an idea of what is going on,  i can certainly see the counters climb an fall as i would expect on activation and termination.   I can't as yet find a counter that show me this data for each tdev.

Hi Guys,

Thanks for your support and reply, still not a 1,2,3 in terms of getting a quick overview on allocated storage used by the VP Snaps. Also caused by the way we use it i guess.   But you pointed me into the right direction.

Thanks.

Kind regards

Patrick