> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Shawn Drew
> Sent: Tuesday, March 30, 2010 3:00 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Virtual Volumes won't die!
> 
> I recently migrated about 5TB of data off of a VirtualVolume/Server
> based
> pool to a normal tape pool.
> 
> - TSM 5.5.4 on AIX
> - The Storage pools are all set to 0 days (for volume reuse)
> - "expire inv"'s were run on both servers
> - The volumes aren't present on the source server anymore
> - Reconcile Volumes shows:
> 0 volumes inspected, 0 invalid volumes found
> - show virtvols show a lot of volumes, but all marked for deletion:
> VIRTUAL VOLUME: 3
>   HL=ADSM/TSM-WB_LM.BFS.237199152,  LL=BFS.OBJ.1,  objId=1326,
> firstObjId=1326
>   objSize=2166075833,  numObjects=4,  when: 06:25:53 on 03/16/09
>   Marked For Delete: TRUE, when: 12:45:45 on 03/26/10
> - The occupancy of the source server is still 5TB at the target
> server:
> 
> 
> I've run into this problem before when I first set this up, but it
> turned
> out I just forgot to run expiration at the target server (since it was
> always a dedicated library manager)  That's not the case this time.
> 
> I can't find the reference, but if I remember right (which is always
> suspect) Virtual Volumes are stored using an archive copy group on the
> target server, but ignores the "Retain Version" of the copy group.
> The
> copy group for this is set to the default of 365 days, but I don't
> imagine
> it should affect virtual-volume data, right?
> 
> Any other suggestions?   The last resort is a "del fi", but I'd really
> like to figure this out.
> 
> 
> Regards,
> Shawn
> ________________________________________________
> Shawn Drew
> 
> 

Try:
q server f=d
Check delgraceperiod parameter



John Monahan