the problem is we need to restore one more volume to a netware server.  When
we do the command, it goes thru the database and searches thru the files for
many hours and then dies...  On the mvs side, it affects the entire adsm
server and all the clients on that server. We have a ticket open with IBM.
We are now running traces from the mvs side to send to IBM.  All other  adsm
clients on other adsm servers are fine.  This individual netware server has
no other issues.  The cpu utilization goes to about 20% during the attempted
restore.

> -----Original Message-----
> From: Roger Hohmann [SMTP:Roger_Hohmann AT WESTLB DOT DE]
> Sent: Friday, October 09, 1998 10:55 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: adsm restore problems.
>
> Which problems? Network, media, cpu, ...?
>
> -----Original Message-----
> From:   Firl Debra K [SMTP:firl.dk AT MELLON DOT COM]
> Sent:   Wednesday, October 07, 1998 11:29 PM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        adsm restore problems.
>
> Has anyone out there seen this.
>
> We are using adsm ver 3 on mvs, Novell clients, nt clients.
>
> the novell client is ver 3.1.3 and we are doing a disaster recovery on
> some
> volumes.  The novell server crashed and died, so we are basically
> rebuilding
> it from backup.  .   We have been doing a restore of the last volume since
> last saturday and basically on the mainframe side, the adsm servers are
> having major difficulty.  It affects all the clients attached to that adsm
> and they basically have to cancel the restore.