I would start with a QUERY OCCUPANCY for the node on the TSM server to figure out which filespaces have lots of objects, and whether the BA client was responsible for them, or some other client type. You could also try looking at the client logs, if you have access to them.
On Fri, Sep 27, 2019 at 06:24:24PM +0000, 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. -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
