Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

New Reporting with 2.5.3?

Created: 03 Sep 2013 • Updated: 04 Sep 2013 | 3 comments
This issue has been solved. See solution.

Has anyone that upgraded to 2.5.3 started seeing some new monitoring reports on hardware?

Ive started getting this report every 12 hours and Im not sure if this is something that is actually working or has been working all along and something happened during the upgrade that has rehydrated my deduped data to put me over the warning threshold.

Compute Node

Time Monitoring Ran: Sun Sep 1 2013 07:15:03 AST

+-----------------------------------------------------------------------------+

|                           Disk Space Information                            |

|+---------------------------------------------------------------------------+|

||ID |      Partition      |   Total   | Used |   State   |   Acknowledge    ||

||---+---------------------+-----------+------+-----------+------------------||

||2  |Deduplication        |31.1 TB    |81 %  |Warning    |No                ||

|+---------------------------------------------------------------------------+|

+-----------------------------------------------------------------------------+

Operating Systems:

Comments 3 CommentsJump to latest comment

Mark_Solutions's picture

I see that 2.5.3 added detailed telemetry reports every 12 hours - see P13 of the release notes so i guess that is why you get this.

I don't see anything in the notes about rehydration changes - maybe queue processing is just working better which always tends to reduce disk space initially as it runs

Of course it could also just be that it has finally reached that level of disk usage

A crcontrol --dsstat should give more information on its actual usage - but maybe that is just where you are with storage usage now

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
Stanleyj's picture

Thanks Mark,

I looked thru that dang release not and saw a brief comment on reports but was unsure if this one was a result of that.  I tried running crcontrol --dsstat and it sat there for about 20 minutes before i cancled out of it.  I think im just retaining that much data and the telemetry reports that are refrenced in the release notes are the emails im getting.

Thanks for looking out for me again.  :)

Mark_Solutions's picture

20 minutes on a dsstat - must be busy / getting full !!

Keep an eye on your queue processing then, it may need a few runs to speed it up and that may also free you some space up after a few runs

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.