Re: deleting a directory container
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@VM.MARIST.EDU] On Behalf Of Remco Post Sent: donderdag 10 augustus 2017 16:57 To: ADSM-L@VM.MARIST.EDU Subject: Re: deleting a directory container and apparently, waiting for some time does help…. > On 10 Aug 2017, at 16:48, Remco Post wrote: > >> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM >> 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@VM.MARIST.EDU] On Behalf Of >> Remco Post >> Sent: donderdag 10 augustus 2017 16:26 >> To: ADSM-L@VM.MARIST.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.p...@plcs.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.p...@plcs.nl > +31 6 248 21 622 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.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
AW: deleting a directory container
Hallo, If your command sequence happend today, you only have to wait another day and the extents should be gone. If this ist the case BUT you would like to delete the unused container(s) earlier: Try: q extentupdates if you see „Extent Reuse Delay (Days) NOT equal to 0 please try to update update stgpool “ reusedelay=0 After 30 Minutes (sometime also more) the container should be gone (have also a look to the meaning of reusedelay). ++ Another general point regarding the update of a stgpooldir with "access=destroyed": In general, the commands you entered should work but in some of my customer cases this was not always true. The update of a stgpooldir with "access=destroyed" command should mark the objects as damaged . After that you should be able to see damaged objects - enter:„q damaged “ If not, you can also try to use the audit container command with „action=markdamaged“ and after that „ with action=removedamaged„ Rgds michael -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Remco Post Gesendet: Donnerstag, 10. August 2017 16:26 An: ADSM-L@VM.MARIST.EDU Betreff: 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 <mailto:r.p...@plcs.nl> r.p...@plcs.nl +31 6 248 21 622
Re: deleting a directory container
and apparently, waiting for some time does help…. > On 10 Aug 2017, at 16:48, Remco Post wrote: > >> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM >> 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@VM.MARIST.EDU] On Behalf Of >> Remco Post >> Sent: donderdag 10 augustus 2017 16:26 >> To: ADSM-L@VM.MARIST.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.p...@plcs.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.p...@plcs.nl > +31 6 248 21 622 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: deleting a directory container
> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM > 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@VM.MARIST.EDU] On Behalf Of > Remco Post > Sent: donderdag 10 augustus 2017 16:26 > To: ADSM-L@VM.MARIST.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.p...@plcs.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.p...@plcs.nl +31 6 248 21 622
Re: deleting a directory container
Hi Remco! Could it be that the reusedelay on the storagepool is preventing TSM from removing the containers? Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco Post Sent: donderdag 10 augustus 2017 16:26 To: ADSM-L@VM.MARIST.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.p...@plcs.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
Re: deleting a directory container
and, as long as we’re on the topic of directory container pools: it is suggested to define a next stg on e.g. tape, but then, how do I get the data from tape back into the directory container pool once I’ve added extra space? > On 10 Aug 2017, at 16:26, Remco Post wrote: > > 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.p...@plcs.nl > +31 6 248 21 622 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
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.p...@plcs.nl +31 6 248 21 622
