I am in general agreement with Jeff. I frequently reboot my test
servers with backupserver running. I'm not aware that I've ever
encountered any problems
due to restarting ASE with Backupserver still running; if there were
problems I'd only expect them if there was something active like a dump
going on - that might cause some backupserver resources to be in an odd
state. But in general the backupserver should eventually detect the
situation (if nothing else when TCP KEEPALIVE kicks in) and clean up.
Note that to shutdown ASE while a dump was active, it would have to
be an impolite shutdown (i.e. with nowait, or a KILL, or an involuntary
shutdown), as ASE would otherwise wait for the dump to complete.
-bret
Post by Jeff TallmanI don't think this is safe in the middle of a backup....or if there is
an active connection to the backupserver (i.e. sitehandler has connected
to backupserver - ala someone recently did a SYB_BACKUP...sp_who or
something...but if the connection has faded out and no backups in
progress, then you may get away with it. However, as a best practice,
I always suggest shutting down the aux servers first and then restarting
them with ASE.
Post by Michael PepplerPost by Heinz MüllerHi,
I was asked if dataserver and backupserver are running and I would
restart _only_ dataserver
if backupserver is able to do his job ( dumping and loading) or if
there are any known issues.
I checked it with 12.5.4 and it (backupserver) worked but may be
there are any circumstances
it would not.
I've never had a situation where the backup server didn't work after the
dataserver was restarted. AFAIK there is no dependency, and the backup
server can stay up when you restart the dataserver.
Michael