Hi Prasad, The above errors indicate that the "reperiodization" process did not finish successfuly and these temp files of the metadata were not deleted as expected.Usually you should see the following messages:12/14/09 11:33:12 AM PDT [VERBOSE] [Manager.SmartStor] Startup reperiodization of tier 1 took 0 seconds
12/14/09 11:33:12 AM PDT [VERBOSE] [Manager.SmartStor] Evaluating data tiers...
12/14/09 11:33:12 AM PDT [VERBOSE] [Manager.SmartStor] Evaluate tiering took 0 seconds
12/14/09 11:33:12 AM PDT [VERBOSE] [Manager.SmartStor] Reperiodize took 0 seconds
12/14/09 11:33:12 AM PDT [VERBOSE] [Manager.SmartStor] Reperiodize took 0 secondsFor now, you can safely remove these files.Reperiodization is not dependent on these temp files. They are created in the process of taking a backup of the metadata file and for some reason they did not get deleted.Please note that Reperiodization kicks off everytime the EM is restarted. Now, based on your latest comment, I believe we need to review your configuration in detail again, so I would suggest you to file a ticket with support and make sure to attach the zipped content of the EM_HOME/logs directories from all collectors, IntroscopeEnterpriseManager.properties, hardware details (#cpu, cpu spped, memory) and screenshot of the following supportability metrics: 1) EM | Smartstor | Metadata | Metrics with Data2) EM | Internal | Number of Connection Tickets3) EM | Internal | Number of Virtual Metrics4) EM | Tasks | Harvest Duration5) EM | Tasks | Smartstor Duration6) EM | GC Heap | Bytes in Use7) EM | GC Heap | GC Duration Make sure to enable VERBOSE logging level and also add to the incident a sample of one of your IntroscopeAgent.profile and log file. This is the minimum information we need to have a better understanding of the issue.It could be the case that the EMs are overloaded or a metric explosion on the EM side might be causing these issues. I hope this helps, Regards, Sergio