Are the ANR9999D 'session not allowed' messages the only messages
you see?

I've seen instances where, during a restore db, nodes attempt to
contact the server for scheduled sessions. One way to prevent
this is to edit your dsmserv.opt and change your TCPPort value
temporarily. That way nodes will not actually reach your ADSM
server. I wouldn't think that these errors would prevent a
'restore db' to come to a successful conclusion, though.

On Thu, 2 Jul 1998, Kelly J. Lipp wrote:

>We're getting the message ANR9999D SMEXEC.C [586] Session not allowed in 
>Standalone mode
>
>Any ideas?  Server won't start.
>
>We tried the dsmserv install and got the server must be started to do this.  
>Huh?
>
>So, we're confused.  Me and John Stephens.  Any ideas?
>
>Kelly Lipp
>Storage Solutions Specialists, Inc.
>lipp AT storsol DOT com
>www.storsol.com
>(719) 531-5926
>
>-----Original Message-----
>From:   Donald W. Daniels/FFIC [SMTP:Donald_W._Daniels/FFIC AT FFIC DOT COM]
>Sent:   Thursday, July 02, 1998 6:31 PM
>To:     ADSM-L AT VM.MARIST DOT EDU
>Subject:        Bare-metal recovery of ADSM Server (WinNT version 3)??
>
>I would appreciate input/comments from anyone with experience in performing
>disaster recovery of a Windows NT ADSM Server.  In my case, this server is the
>only ADSM Server currently installed.  Following are the steps that I think
>would work:
>
>folllowing are backed up and stored offsite:
>
> $   Volume history file
>  $   Device configuration file
>  $   Server options file
>  $   Database and recovery log set up
> .  Full db backup and incrementals
>.   Copy storage pool volumes
>
>
>To restore to a fresh machine:
>
>. Install WinNT Server
>. Install ADSM
>. restore ADSM information using procedures defined in "6.1.7.1 Restoring a
>Database to a Point in Time" of the Admin Guide.
>
>Also,  any  thoughts about utilizing Forward Recovery?
>
>Thanks,
>
>Don
>ddaniels AT ffic DOT com
>