Well, actually it does "work". A "command" in TSM at the admin console is more of a "suggestion" with TSM. When you request a cancel of a process it wants to finish what it's doing if it can so as not to have a partially processed file. Killing out a process in the middle of a file transfer messes up the tape by creating fragmented space.
Not only that, but I wouldn't get that worked up over a tape drive claiming to need cleaning. Unless you start seeing tape errors, you're not going to suffer from that nearly as much as you are going to suffer by killing TSM in the middle of a process. See Ya' Howard > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of Kauffman, Tom > Sent: Monday, March 30, 2009 10:07 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Question for the TSM 6.1 beta testers > > If you're allowed to answer it. > > With the new database design and the new architecture, is it possible > to terminate a process before it finishes the file it is processing? > > Explicityly, can I kill a reclaim or storage pool backup immediately, > without waiting for the current file to be finished. This comes up ont > or two times a month, where a tape drive indicates it needs cleaning - > and I've only got another 200 GB to process on the current file. The > current workaround is to shut TSM down. I'd rather kill the process, > but it doesn't work currently. > > Thanks -
