All,
I am pretty sure that UNLOCK NODE can be used in order
to access the data.
I am checking on this to be sure and will post a response
once I get 100% verification.
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/28/2015
06:57:09 AM:
> From: Remco Post <r.post AT PLCS DOT NL>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 09/28/2015 06:57 AM
> Subject: Re: 7.1.3 Decomm changes
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Hi all,
>
> a decomm with a countdown without options to reverse te decomm seems
> quite useless indeed. So either development sort of missed the point
> or the communications around this new feature are not 100%…
>
> IBM? Anyone out there?
>
> > Op 28 sep. 2015, om 11:37 heeft Loon, EJ van (ITOPT3) - KLM <Eric-
> van.Loon AT KLM DOT COM> het volgende geschreven:
> >
> > Hi Steve!
> > I agree things are a bit unclear here. On her presentation on
> YouTube Tricia Jiang explicitly states that the decommission command
> locks the node and that it cannot be unlocked (https://
> www.youtube.com/watch?v=QZVyVp0QEIs at 35:16). One of the IBM-ers on
> the TSM Symposium in Germany last week however stated that the node
> can be unlocked if necessary... Maybe someone from development on
> this list can clarify this?
> > Kind regards,
> > Eric van Loon
> > AF/KLM Storage Engineering
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Steven Harris
> > Sent: maandag 28 september 2015 3:10
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: 7.1.3 Decomm changes
> >
> > Hi All
> >
> > Kudos to the TSM developers for the new decomm facilities in 7.1.
> 3. I put up an RFE once myself for something similar.
> >
> > As I read it, the decommissioned data is locked up in such a way
> that it can't be got at. Obviously I'm missing something as if it
> can't be accessed, there is no point in keeping the data and we
> might as well just delete.
> >
> > Can someone walk me through a restore scenario?
> >
> > Thanks
> >
> > Steve
> >
> > Steven Harris
> > TSM SME
> > Canberra, Australia
> > ********************************************************
> > 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
>
|
