Ahmed,

I have no answer for you, but we a re currently facing the exact same question. For sure, the path isn't stored anywhere (that we could find) it must be somehow calculated....

The reason we need this is, that our customer has NetApp Snaplock where only fixed retention is possible (at least from a CPe standpoint, OnTap 9.3 introduced event based retention, I posted this support as an idea and it will be considered for a future release).

But the customer has the requirement to delete them earlier and we want to delete the documents from CPE first (fortunately the storage is unaligned) and then use privileged delete to delete them from the NetApp. For this we would need the path...

One could figure it out by illegal means (decompilation), but I will probably open a ticket with IBM and see how much L3 is willing to share that info.

No help, but shared pain...

/Gerold

Gerold,

Thank you for sharing, we have almost the same case.

Please let me know if you find anything.

BR,

Ahmed

Ahmed

The answer to both questions is "no". This is not information we share.

Ruth,

I appreciate all the efforts you take , with all those training materials and answering in the forums.

I'm tempted to put a small correction on your statement 'This is not information we share'. You might not share it with everyone :-)

As kinda discussed in a thread here 'Support for NetApp Indefinite retention', NetApp itself put out a document where the claim to have done exactly what I have described (actually I stole this idea). This was from times when OnTap did not support EBR.

So either someone did share (maybe the client was big enough for IBM) or someone did a reverse engineering (which is prohibited by the license agreement).

Either IBM comes forward when they intend to support EBR on OnTap >=9.3 (I put this to ideas and it is considered for a future release) so that customers have a chance to plan or help by releasing that info in a very limited environment...

Not IBMs fault though... We *strongly* advised the customer IN WRITING against using infinite retention on NetApp, he insisted and now he regrets it...

Kind regards,

Gerold

Gerold

Thanks for the compliment.

With regard to indefinite retention.  This capability can actually be used with any type of storage as long as it is just enforced at the CPE level. If you want to coordinate the retention with an underlying fixed content device, such as NetApp, then there can, as you note, be limitations.

Thank-you for putting the support request as an Idea. Since ideas are visible to all customers, the more people that vote for an item, the more likely that item will, if feasible, get addressed.