ADSM-L

Re: Virtual Volumes Not Being Deleted

2004-12-13 10:52:07
Subject: Re: Virtual Volumes Not Being Deleted
From: Mark Fergusson <mark AT TMSLTD.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 13 Dec 2004 15:50:46 -0000
Thanks Michael et al

It is now ok

Mark

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Wheelock, Michael D
Sent: 13 December 2004 14:54
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Virtual Volumes Not Being Deleted


Hi,

In order to reclaim space on a copy pool that is a server to server
virtual volumes you must:

1) run reclamation on the source copy pool.  It must finish reclaiming
and delete the volume.
2) run expire inventory on the target server.  This will show up as
deleting archives (because the virtual volumes come in as archive data).

I set the retention time on all of these pools to 0 days as there was no
real reason not to.

Michael

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bos, Karel
Sent: Sunday, December 12, 2004 4:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Virtual Volumes Not Being Deleted

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
****************************************************************************
**********************
This e-mail may contain identifiable health information that is subject to
protection
under state and federal law. This information is intended to be for the use
of the
individual named above. If you are not the intended recipient, be aware that
any
disclosure, copying, distribution or use of the contents of this information
is prohibited
and may be punishable by law. If you have received this electronic
transmission in
error, please notify us immediately by electronic mail (reply).
****************************************************************************
**********************

<Prev in Thread] Current Thread [Next in Thread>