ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [ADSM-L] removing copystg keeps data on copy volumes

2010-08-18 07:00:14
Subject: Re: [ADSM-L] removing copystg keeps data on copy volumes
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 18 Aug 2010 06:57:30 -0400 
On Aug 18, 2010, at 5:54 AM, Mehdi Salehi wrote:

> Hi everyone,
> stg1 has stg2 as copy pool and they are synced. If you set the copystg of
> stg1 to null, why stg2 still has copy data of stg1? Why doesn't TSM
> delete/expire the copy data?

Because it should not, according to the architecture.
The role of a copy storage pool is to retain a copy of data as long as that 
data is in the primary pool from which it was copied.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [ADSM-L] cancel a session with MediaW, Mehdi Salehi
Next by Date:  [ADSM-L] TSM Reporting & Monitoring, Richard van Denzel
Previous by Thread:  [ADSM-L] removing copystg keeps data on copy volumes, Mehdi Salehi
Next by Thread:  Re: [ADSM-L] removing copystg keeps data on copy volumes, Mehdi Salehi
Indexes:  [Date] [Thread] [Top] [All Lists]