Re: Archive deletion

[Loon, Eric van (ITOPT3) - KLM]

Hi Thomas!
>From what I read from my output files I collected after each expiration you 
>are spot on!
We have a customer that complains that TDP for SAP backups which were removed 
by BACKINT are still visible afterwards for the BACKFM command. But in that 
case this can be explained by the fact that expiration hasn't run yet. I expect 
that as soon as expiration has finished, BACKFM doesn't show them anymore. I 
will test that.
Thanks for your 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 Thomas 
Denier
Sent: dinsdag 25 oktober 2016 16:02
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Archive deletion

My best guess is that inventory expiration won't remove an archived directory 
if archived copies of any of the directory's contents still exist, and that the 
order of events in inventory expiration prevents a single expiration process 
from working its way up the directory tree. If this theory is correct, the 
successive expirations behave as follows:

1.Remove files and empty directories (if any).
2.Remove directories that had files but no sub-directories.
3.Remove directories that had one level of sub-directories.
4.Remove directories that had two levels of sub-directories.

and so on.

Thomas Denier
Thomas Jefferson University

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, 
Eric van (ITOPT3) - KLM
Sent: Tuesday, October 25, 2016 07:57
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Archive deletion

Hi guys!
I was always under the impression that deleted archives were delete immediately 
from TSM. I just discovered that this is not the case. Although a client can no 
longer retrieve an archive after deletion, the archive files are still present 
in TSM. A select * from archives where node_name='MYNODE' confirms this.
The strange thing is that the archive object of type=file are removed by the 
first running expiration process, but the archive objects of type=dir are not! 
I had to run multiple consecutive expirations on my server to get rid of all of 
them. Each run removed a few of them and after the 5th run all archive objects 
were gone. I really don't understand this behavior...
Thanks in advance for any explanation!
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.

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: Archive deletion

[Loon, Eric van (ITOPT3) - KLM]

Hi Chavdar!
Yes, but in this case I deleted the archives. So the managementclass should not 
play no more role, right?
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 
Chavdar Cholev
Sent: dinsdag 25 oktober 2016 17:06
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Archive deletion

Hello Eric,
from TSM (ISP) docs:
"If you do not use the archmc option, the server binds archived directories to 
the default management class. If the default management class has no archive 
copy group, the server binds archived directories to the management class with 
the shortest retention period."

HTH
Chavdar

On Tue, Oct 25, 2016 at 5:01 PM, Thomas Denier 
wrote:

> My best guess is that inventory expiration won't remove an archived 
> directory if archived copies of any of the directory's contents still 
> exist, and that the order of events in inventory expiration prevents a 
> single expiration process from working its way up the directory tree. 
> If this theory is correct, the successive expirations behave as follows:
>
> 1.Remove files and empty directories (if any).
> 2.Remove directories that had files but no sub-directories.
> 3.Remove directories that had one level of sub-directories.
> 4.Remove directories that had two levels of sub-directories.
>
> and so on.
>
> Thomas Denier
> Thomas Jefferson University
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Loon, Eric van (ITOPT3) - KLM
> Sent: Tuesday, October 25, 2016 07:57
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Archive deletion
>
> Hi guys!
> I was always under the impression that deleted archives were delete 
> immediately from TSM. I just discovered that this is not the case. 
> Although a client can no longer retrieve an archive after deletion, 
> the archive files are still present in TSM. A select * from archives 
> where node_name='MYNODE' confirms this.
> The strange thing is that the archive object of type=file are removed 
> by the first running expiration process, but the archive objects of 
> type=dir are not! I had to run multiple consecutive expirations on my 
> server to get rid of all of them. Each run removed a few of them and 
> after the 5th run all archive objects were gone. I really don't understand 
> this behavior...
> Thanks in advance for any explanation!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
> The information contained in this transmission contains privileged and 
> confidential information. It is intended only for the use of the 
> person named above. If you are not the intended recipient, you are 
> hereby notified that any review, dissemination, distribution or 
> duplication of this communication is strictly prohibited. If you are 
> not the intended recipient, please contact the sender by reply email 
> and destroy all copies of the original message.
>
> CAUTION: Intended recipients should NOT use email communication for 
> emergent or urgent health care matters.
>

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: Archive deletion

[Chavdar Cholev]

Hello Eric,
from TSM (ISP) docs:
"If you do not use the archmc option, the server binds archived directories
to the default management class. If the default management class has no
archive copy group, the server binds archived directories to the management
class with the shortest retention period."

HTH
Chavdar

On Tue, Oct 25, 2016 at 5:01 PM, Thomas Denier 
wrote:

> My best guess is that inventory expiration won't remove an archived
> directory if archived copies of any of the directory's contents still
> exist, and that the order of events in inventory expiration prevents a
> single expiration process from working its way up the directory tree. If
> this theory is correct, the successive expirations behave as follows:
>
> 1.Remove files and empty directories (if any).
> 2.Remove directories that had files but no sub-directories.
> 3.Remove directories that had one level of sub-directories.
> 4.Remove directories that had two levels of sub-directories.
>
> and so on.
>
> Thomas Denier
> Thomas Jefferson University
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Loon, Eric van (ITOPT3) - KLM
> Sent: Tuesday, October 25, 2016 07:57
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Archive deletion
>
> Hi guys!
> I was always under the impression that deleted archives were delete
> immediately from TSM. I just discovered that this is not the case. Although
> a client can no longer retrieve an archive after deletion, the archive
> files are still present in TSM. A select * from archives where
> node_name='MYNODE' confirms this.
> The strange thing is that the archive object of type=file are removed by
> the first running expiration process, but the archive objects of type=dir
> are not! I had to run multiple consecutive expirations on my server to get
> rid of all of them. Each run removed a few of them and after the 5th run
> all archive objects were gone. I really don't understand this behavior...
> Thanks in advance for any explanation!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
> The information contained in this transmission contains privileged and
> confidential information. It is intended only for the use of the person
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
>
> CAUTION: Intended recipients should NOT use email communication for
> emergent or urgent health care matters.
>

Re: Archive deletion

[Thomas Denier]

My best guess is that inventory expiration won't remove an archived directory 
if archived copies of any of the directory's contents still exist, and that the 
order of events in inventory expiration prevents a single expiration process 
from working its way up the directory tree. If this theory is correct, the 
successive expirations behave as follows:

1.Remove files and empty directories (if any).
2.Remove directories that had files but no sub-directories.
3.Remove directories that had one level of sub-directories.
4.Remove directories that had two levels of sub-directories.

and so on.

Thomas Denier
Thomas Jefferson University

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, 
Eric van (ITOPT3) - KLM
Sent: Tuesday, October 25, 2016 07:57
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Archive deletion

Hi guys!
I was always under the impression that deleted archives were delete immediately 
from TSM. I just discovered that this is not the case. Although a client can no 
longer retrieve an archive after deletion, the archive files are still present 
in TSM. A select * from archives where node_name='MYNODE' confirms this.
The strange thing is that the archive object of type=file are removed by the 
first running expiration process, but the archive objects of type=dir are not! 
I had to run multiple consecutive expirations on my server to get rid of all of 
them. Each run removed a few of them and after the 5th run all archive objects 
were gone. I really don't understand this behavior...
Thanks in advance for any explanation!
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.

Archive deletion

[Loon, Eric van (ITOPT3) - KLM]

Hi guys!
I was always under the impression that deleted archives were delete immediately 
from TSM. I just discovered that this is not the case. Although a client can no 
longer retrieve an archive after deletion, the archive files are still present 
in TSM. A select * from archives where node_name='MYNODE' confirms this.
The strange thing is that the archive object of type=file are removed by the 
first running expiration process, but the archive objects of type=dir are not! 
I had to run multiple consecutive expirations on my server to get rid of all of 
them. Each run removed a few of them and after the 5th run all archive objects 
were gone. I really don't understand this behavior...
Thanks in advance for any explanation!
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

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