We use TCP/IP for all clients, method POLLING, and use the Win95, WinNT, or
UNIX schedulers to trigger backups.
.
If we lose the ADSM server for some reason (or have a network problem) while
clients are backing up, after the server comes back the clients reconnect
and complete their backups with no problem.

In the client options file, we set:
MAXCMDRETRIES 99
RETRYPERIOD 20

That causes the client to retry the connection every 20 minutes, up to 99
times.

But, as Jennifer said, you have to still be in your defined schedule window
when the server comes back.

And I don't know what happens if you are using PROMPTED scheduling mode.


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think." 
              - Scott Adams/Dilbert
===============================================================
 

> ----------
> From:         Roger Hohmann[SMTP:roger_hohmann AT westlb DOT de]
> Sent:         Wednesday, August 26, 1998 12:13 PM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Recoverable backup sessions
> 
> Hi,
> 
> I would like to recover (better: continue) my backup sessions when my adsm
> server crashes and is coming up afterwards. Today, all sessions are down
> after a crash, and I have to start the backups again manually. It would be
> nice if the client is able to wait until the server is up again and
> continue the backup session.
> 
> Did I miss anything in ADSM to customise this (commtimeout or so?) or am I
> the only one who miss this?
> 
> Regards
> 
> Roger Hohmann
> 
> WestLB
> Division: 009 Services
> Abteilung: 001-80633
> Herzogstraße 15
> D - 40217 Düsseldorf
> Tel.: +49211 826 8155
> mailto:roger_hohmann AT westlb DOT de
>