Hi
I guess its better to disable schedules before you start (by adding
disablescheds yes in dsmserv.opt file) the resorted server than to do
it after start (as some jobs can start just after startup).
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.srv.ref.doc/r_opt_server_disablescheds.html

Kind Regards
Krzysztof

2015-04-14 14:48 GMT+02:00 Steven Harris <steve AT stevenharris DOT info>:
> Hi Gregor.
>
> IBM used to offer a special service to get data off tape. Not sure if it
> is still available.
>
> Other than that the only way I know is to restore your DB to a point
> before expiration.  Start up the restored instance with NOMIGRECL and
> immediately stop your daily schedules, in particular stop running
> expiration.  At this point you can restore your file.  I would tend to
> mark the primary volumes as unavailable and restore from the copypool.
> That way you if you have restored to another instance you can keep your
> main instance running close to normal (except for copypool stuff) for
> however long the restore takes you.  But it is a lot of work and a lot
> of fiddling about.
>
> Regards and good luck.
>
> Steve
>
> Steven Harris
> TSM Admin
> Canberra Australia.
>
>
>
>
> On 14/04/2015 10:10 PM, Gregor van den Boogaart wrote:
>> Dear List,
>>
>> the retention settings in the copygroup were to strict... The version
>> of the file we would like to restore has already been expired. :-(
>> However it is very likely the desired version of the file is still on
>> tape, as no reclamation has taken place. So my understanding would be:
>> if the file is still on tape, the "only" thing missing is the database
>> entry. Correct?
>>
>> So the question would be: How to restore already expired objects from
>> a tape cartridge? Or: How to generate database entries for all
>> versions of all objects on a tape cartridge?
>>
>> I guess the first step would be to move the respective node to a
>> copygroup, with "better" retention settings. I looked on the
>> documentation for "audit volume", but I did not get the feeling this
>> would understand checking "for inconsistencies between database
>> information and a storage pool volume" in un-expiring previously
>> expired objects...
>>
>> Any tips, pointers, ideas?
>> Perhaps I am just searching for the wrong key words?
>>
>> Gregor
>>
>>
>>