It sounds like your directory entries are stored on tape, rather
than on disk or in the database. Look at setting up a directory
management class, so that all directories are stored in the
database or on disk, and so don't require a tape mount.
On Wed, 15 Mar 2000, Andreas Boesler wrote:
>The size of our DB is only 800 MB.
>
>I should tell: Last week we did an upgrade from 3.1.1.3 to 3.1.2.50.
>With 3.1.1.3 we had only "normal" restores.
>
>I did more tests:
>
> o If I restore files without the directory,
> ADSM works "normal":
>
> Client-GUI Sess State Comments
> ---------------------------------------------------
> Preparing MediaW ADSM mounts a tape
> Transferring sendW ADSM restores the objects
>
> o If I restore the same files including the directory,
> ADSM works "NOT normal":
>
> Client-GUI Sess State Comments
> ---------------------------------------------------
> Waiting for files Run for 15 minutes !!!
> Waiting for files MediaW/Run ADSM mounts 1-3 !!! tapes
> and restores NO objects
> Waiting for files MediaW ADSM mounts a tape
> Transferring sendW ADSM restores the objects
>
>There are NO other processes or sessions.
>The filesystem has got 500.000 files.
>Restores with small filesystems are OK !
>
>Questions:
>
>o How can I monitor, what ADSM does during the 15 minutes ?
>o What is the difference between "Waiting for files" and "Preparing" ?
>
>Thanks,
>Andreas.
>
>> Hello,
>>
>> What size is your DB.
>> Most likely your ADSM server searches in its database for the requested
>> file's, tape's, etc.
>>
>> Jelle
>>
>> Andreas Boesler wrote:
>>
>> > Hi ADSMers,
>> >
>> > Today I restored 10 files and the ADSM-Client-GUI says 20 !!! minutes:
>> > Waiting for files.
>> > Then ADSM mounts the first tape.
>> > There are no other processes or sessions and no other tape mounted.
>> >
>> > Any ideas ?
>> >
>> > Environment:
>> >
>> > ADSM-Server 3.1.2.50 on NT 4.0 SP5
>> > ADSM-Client 3.1.0.3
>> >
>> > Thanks
>> >
>> > Andreas.
>
|
