On 2019-09-27 20:24, Lee, Gary wrote: > Is this normal?Tsm 7.1.7.1, running on redhat 6.9. > > Deleting a windows 2008r2 node's data using delete filespace. Killed > the process after 5.5 hours ad 34 million ojects. Restarted this > morning, has been running for 6 hours and says it has deleted over 88 > million objects. > > There is only 500 gB of on-site data for the client. My vere=14 > verdel=14, rete=14, reto=30. Backups occur once per day, which should > allow point-in-time restores for up to two weeks. > > Where did all these objects come from, and will it ever get done? I > have never seen client with over 120 million objects.
All those objects probably come from that Windows node systemstate backup. I have seen up to 30 million objects deleted from systemstate while the Q OCC shows much less than that... There was an explanation, maybe even on this list, but I cannot find it...and don't remember the precise explanation. And yes, all those millions of files DON'T take space in your TSM DB. probably only the number of files which Q OCC shows is relevant for TSM DB occupancy. So, your file count is much bigger from what I have experienced, but I believe it is a system state backup which is somehow packing lots of files in some groups so for example if Q OCC shows 1 mill files, it means 10 or more mill files which would be deleted... Rgds, -- Sasa Drnjevic www.srce.unizg.hr/en/
