We are running NT server and mostly NT Clients, and are using client
polling
scheduling, and TCP/IP communications. (Now at V3 with mixed V2 and V3
clients).
We have never had any problems getting our scheduled backups to run.
Our process is as follows
1. Register the node on the server.
2. Define the schedule for the node.(We schedule each node separately)
3. Install ADSM client software.
4. Make sure DSM.OPT has correct information (including server tcp/ip
address)
5. Use the GUI to back up a few files to check the connection.
6. Install and start the scheduler service.
7. Verify that when the scheduler is started, we see a session start and
stop for the node. )This is the scheduler checking in for it's schedule)
8. Check the node's DSMSCHEDULE.LOG to be sure that the schedule is
picked up.
Should see an entry like the following:

03/26/1998 10:33:24 Node Name: CS14
03/26/1998 10:33:27 Session established with server ADSM: Windows NT
03/26/1998 10:33:28   Server Version 3, Release 1, Level 0.2
03/26/1998 10:33:28   Server date/time: 03/26/1998 10:32:42  Last
access: 03/26/1998 04:32:39

03/26/1998 10:33:28 Querying server for next scheduled event.
03/26/1998 10:33:29 Next operation scheduled:
03/26/1998 10:33:29
------------------------------------------------------------
03/26/1998 10:33:29 Schedule Name:         DAILY-CS14-BKUP
03/26/1998 10:33:29 Schedule Name:         DAILY-CS14-BKUP
03/26/1998 10:33:29 Action:                Incremental
03/26/1998 10:33:29 Objects:
03/26/1998 10:33:29 Options:
03/26/1998 10:33:29 Server Window Start:   22:30:00 on 03/26/1998
03/26/1998 10:33:29
------------------------------------------------------------
03/26/1998 10:33:29 Schedule will be refreshed in 6 hours.
03/26/1998 10:33:29 Schedule will be refreshed in 6 hours.

The only problems we have had are errors updating the registry during
the scheduler
service install. (Solved by uninstallin and reinstalling several times)
and one case where a node stopped checking in with the server, solved by
stopping and
restarting the scheduler service.


Shane Smith wrote:
>
> hi.. me again..
>
> i still have no luck in getting adsm to backup automatically an nt client 
> which is
> running the adsm schedular service. i have started the adsm schedular service
> automatically. it starts  fine - no errors. i set the schedular service to be 
> run
> under the local admin (system account) of the nt client. we  can run a manual 
> backup
> from the nt client to the adsm server, and alos can run remote adsm admin 
> from the
> client - which rules out comms problems.
>
> my adsm server (nt also, running adsm v2.1.06) shows the nt-client backup as
> pending. but after the expiration (set to 1 hour), the server says it missed 
> the
> backup.
>
> what is the problem here? my adsm setup is working like a charm for our notes 
> and
> os/2 clients, but i just cannot get the nt clients to run. due to our
> techo-security-mad-dog-audit-freaks i am only permitted to run adsm on our nt
> machines as a service. the service runs, but nothing happens.
>
> please.. please...  what am i doing wrong. have i setup the adsm client 
> options
> incorrectly? is it an nt thing with permissions on who can run the service? 
> does
> adsm v2.1.06 client not work properly when setting up the adsm schedular 
> service?
>
> any ideas from anyone would be greatly appreciated.
>
> shane the desparate :)