The method we use to initialize Client Polling scheduling on Window NT
(Both ADSM server and Client are Windows NT)Comm. method is TCP/IP
1. Make sure that the central server scheduling mode is any or client
polling.
2.After installing the Client Software, Run the ADSM Scheduler Service
installation on the Client.
3.In the client control pannel, Open services and make sure that "ADSM
Central Scheduler Service is started and set to automatic.
4.Register the node with the server, and manually backup a few files
from the client using the Backup Archive GUI. This verifies that you can
connect.
5.Define the schedule on the server, and be sure to associate the Client
Node with the server.
6.At the client, go back into services and stop and restart the schedule
service. This forces the schedule to refresh.(a setting in the client
options file states how often the client contacts the server to update.
I think the default is every 6 hours. Stopping and starting the
scheduler forces the update.)
7. In the baclient subdirectory of the clients ADSM directory is a text
file called dsmsched.log
Open this file with a text editor. It should show an entry like the one
that follows.

08/14/1997 06:58:10 Querying server for next scheduled event.
08/14/1997 06:58:11 Next operation scheduled:
08/14/1997 06:58:11
------------------------------------------------------------
08/14/1997 06:58:11 Schedule Name:         <Name of Schedule>
08/14/1997 06:58:11 Schedule Name:         <Name of Schedule>
08/14/1997 06:58:11 Action:                Incremental
08/14/1997 06:58:11 Objects:
08/14/1997 06:58:11 Options:
08/14/1997 06:58:11 Server Window Start:   08:30:00  on 08/14/1997
08/14/1997 06:58:11
------------------------------------------------------------
08/14/1997 06:58:11 Command will be executed in 1 hour and 34 minutes.
08/14/1997 06:58:11 Command will be executed in 1 hour and 34 minutes.
08/14/1997 08:32:12

The start-time should be the time set at the server.

As for your other problems, It could be caused by NT-Permissions. Try
logging onto both the ADSM server and the Client with full
administrative authority and see if you still get the failure.

Rafael Goldschmidt wrote:
>
> Hi ADSMers!
> I have 2 questions: I am installing a Windows NT Client.
>
> 1) The scheduled backup does not initiate.  When I do: Q EV STANDARD
> PRUEBA (this last is the name of the schedule) i receive a status:
> PENDING.  Once the duration is over I receive the status: MISSED.  But I
> do not have a hint of why the schedule did not run.  Could somebody help
> me?
>
> 2) When I try to do an incremental backup of the entire disk, I first
> receive a message: SAVING SOFTWARE CONFIGURATION.  Immediately I receive
> the message: ANS7643E An error occured saving the registry key.  Another
> message ANS7641E Registry backup failed.  Another message: Active object
> not found.  Please Help!
>
> Thank you very much!
>
> Rafael Goldschmidt
> Buenos Aires, Argentina
> rafagold AT cano.com DOT ar