I suspect that some sort of timeout is involved. Storage pool backups
use a lot of CPU, and a lot of db reads to generate a list of files that
need to be backed up. I suspect that it may take some time to ditch that
queued list of files before you can start another stg backup session
involving the same pair of storage pools (primary and copy).

 
--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Tyree, David
> Sent: Wednesday, November 12, 2008 11:26 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] backup stgpool issue
> 
> 
>             I've got something strange going on here. If I run a
backup
> storage pool command from my primary pool to one of my offsite copy
> pool
> everything is fine. It will finish whenever it is done. Same when I do
> a
> backup to my onsite copy pool. As long as let them finish everything
is
> ok.
> 
>             However, if for some reason I do a cancel on the process
> things get interesting. I do the cancel on the process and wait for it
> to finish. I do some q proc's to check to see if it's finished yet.
> Once
> it finishes I then go back and start another backup stgpool.  I get an
> error saying that a backup is already in progress.
> 
> The q proc is coming back with nothing and I do a q mount just for the
> heck of it and it comes back with nothing mounted. It's like a hidden
> process that I have no control over and can't monitor.
> 
> I end up having to halt and restart TSM to get control again.
> 
> I'm running TSM 5.4.1 on a Windows 2003 box.
> 
> Any ideas?
> 
> 
> 
> David Tyree
> Interface Analyst
> South Georgia Medical Center
> 229.333.1155
> 
> Confidential Notice:  This e-mail message, including any attachments,
> is
> for the sole use of the intended recipient(s) and may contain
> confidential and privileged information.  Any unauthorized review,
use,
> disclosure or distribution is prohibited.  If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of the original message.
> 
>