Hi Remco!
Yes, there is a small delay of a few minutes before containers are actually
removed, I noticed that behavior too.
You stated "it should not, there is no use in retaining damaged containers".
True, but if you roll back your database for some reason, you want all
containers to be there too, even the damaged ones, otherwise you can't fix them
(and your database) with an audit.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Remco Post
Sent: donderdag 10 augustus 2017 16:57
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: deleting a directory container
and apparently, waiting for some time does help….
> On 10 Aug 2017, at 16:48, Remco Post <r.post AT PLCS DOT NL> wrote:
>
>> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM <Eric-van.Loon AT
>> KLM DOT COM> wrote:
>>
>> Hi Remco!
>> Could it be that the reusedelay on the storagepool is preventing TSM from
>> removing the containers?
>
> it should not, there is no us in retaining damaged containers. But to make
> sure, I’ve set the reusedelay to 0 and retried the audit etc. unfortunately,
> that didn’t help.
>
>> Kind regards,
>> Eric van Loon
>> Air France/KLM Storage Engineering
>>
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>> Of Remco Post
>> Sent: donderdag 10 augustus 2017 16:26
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: deleting a directory container
>>
>> Hi all,
>>
>> On our new tsm 8.1.1 server I have a directory container pool CC_COM that I
>> no longer want to use. It has been used as a target pool for protect stg
>> once, but when I saw that a subsequent repl node again copies all data
>> because the stgpool in the copygroup is CP_COM (which also exists), I
>> decided to do away with the CC_COM pool.
>>
>> So I updated the stgpooldir to destroyed and ran audit container …
>> action=removedamaged
>>
>> unfortunately, there are still containers in the directory and no matter
>> what I do… the server insists that the container directory still has active
>> data. How do I get rid of this directory container?
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post AT plcs DOT nl
>> +31 6 248 21 622
>> ********************************************************
>> For information, services and offers, please visit our web site:
>> http://www.klm.com. This e-mail and any attachment may contain confidential
>> and privileged material intended for the addressee only. If you are not the
>> addressee, you are notified that no part of the e-mail or any attachment may
>> be disclosed, copied or distributed, and that any other action related to
>> this e-mail or attachment is strictly prohibited, and may be unlawful. If
>> you have received this e-mail by error, please notify the sender immediately
>> by return e-mail, and delete this message.
>>
>> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
>> employees shall not be liable for the incorrect or incomplete transmission
>> of this e-mail or any attachments, nor responsible for any delay in receipt.
>> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
>> Airlines) is registered in Amstelveen, The Netherlands, with registered
>> number 33014286
>> ********************************************************
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post AT plcs DOT nl
> +31 6 248 21 622
--
Met vriendelijke groeten/Kind Regards,
Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
