You have to look at things like grace period on the target server. For
some reason (disaster recovery?) virt volumes are not deleted on the
target server based on the action of the source, but on the grace
retention period of the management class of the target server.

Regrads,

Karel 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mark Fergusson
Sent: zaterdag 11 december 2004 21:56
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Virtual Volumes Not Being Deleted

Hi TSM'rs

I have two TSM servers TSM1 and TSM2 running TSM 5.2.3.2 on Redhat ES3.

TSM1 is the primary server having a copypool on TSM2 as file based
virtual volumes.

When reclamation runs on the source server the volumes, also file based,
are deleted.

Even though the activity report indicates that the volumes are deleted
on the target server the associated physical files on the target server
are not deleted.

For example a volume called TSM2.BFS.095437768 on the source server has
an associated volume on the target server called 00000003.BFS. The
TSM2....
file is deleted from the storage pool but the volume 00000003.BFS on the
target server is not deleted.

I have tried running "reconcile volumes", "audit volume" "expire
inventory"
etc etc and nothing has worked.

The file still indicates a size of 5GB on disk and is now obviously
casuing a space problem.

Help!!

Mark