- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok,
looks also ok.
Only cache is interresting. Hf
CP Ty : Consistency Point (CP) type is the reason that a CP started in that interval. The CP types are as follows:
- – No CP started during sampling interval (no writes happened to disk at this point of time)
- number Number of CPs started during sampling interval
- B Back to back CPs (CP generated CP) (The filer is having a tough time keeping up with writes)
- b Deferred back to back CPs (CP generated CP) (the back to back condition is getting worse)
- F CP caused by full NVLog (one half of the nvram log was full, and so was flushed)
- H CP caused by high water mark (rare to see this. The filer was at half way full on one side of the nvram logs, so decides to write on disk).
- L CP caused by low water mark
- S CP caused by snapshot operation
- T CP caused by timer (every 10 seconds filer data is flushed to disk)
- U CP caused by flush
- : continuation of CP from previous interval (means, A cp is still going on, during 1 second intervals)
The type character is followed by a second character which indicates the phase of the CP at the end of the sampling interval. If the CP completed during the sampling interval, this second character will be blank. The phases are as follows:
- 0 Initializing
- n Processing normal files
- s Processing special files
- f Flushing modified data to disk
- v Flushing modified superblock to disk
And in a 10G enviroment set options nfs.tcp.recvwindowsize to 64240
Without Memory the SnapShot Process is fast?
How large it the Memory of the VM?
Can you check the ESXTOP Memory counter %ACTV during Snapshot an in normal operation?
Interpreting esxtop Statistics
https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK