Updating archdelete flag on busy node?

[edhacker]

Hi All, we run a TSM/SP shop that does mostly archiving. We have one node in particular that's exceptionally busy archiving files from several servers non-stop, but we need to switch its archdelete flag from no to yes to perform some cleanup. Of course, it says this can't be done because the node is in use. It's always in use. 24x7xForever, it seems. It could be literally months before the perfect confluence of multi-server idleness occurs long enough to get that bit flipped.

Wondering if any of you long-timer TSM/SP gurus might have picked up any tricks over the years for working around this specific problem. Or am I really going to have to wait til Spring 2021 (if I'm lucky!) to delete the bogus files that got archived?

Thanks for any suggestions you might be able to provide, no matter how outlandish or crazy-seeming!

 

[marclant]

You can lock the node, cancel active sessions for that node, do your update, then unlock the node.

Or talk to the admin of that box, and tell them to stop archiving for 5 minutes.

Or wait until Spring 2021.

 

[edhacker]

Thanks marclant, that's what I was afraid of!