Re: Automatic shutdown

Günther Schwarz wrote:
Yes, it is a networked backup where the process is initiated by the
backup server via xinetd. So the client has to wait until the server
calls. But it is rather well balanced and two hours are plenty for this
specific network.

And unneeded.

The proper solution would be to hack the amanda backup software so that
the server sets a wol command prior to initiate the backup process on a
given client. But I won't go into this as it is simply much to much
hazzle and I simply can't see how this could be done easily (same with
PCs running server processes like nfs which are up 7/24 because my
autofs script has no capability to wake up machines on request).

You have wake on LAN now, so use that. Have the server use the following
script
1) RunWakeOnLan
2) RunBackup
3) RunUpdate
4) RunShutdown

1 and 2 will be done localy
3 and 4 will be done via ssh and run on the remote machine and could
even be one script.

I could indeed replace the crontab entry '30 3 * * * root shutdown -h
now' with a more sophisticated script taking these and more additional
conditions into account. But then I was asking for a simple solutions
that does not need much scripting work to be done.

To me that IS a simple solution. ;-) You want a point-and-click
solution? That does not excist, as far as I know.
The advantage of a little bit of scripting is that adding extra machines
later is very easy and only requires adding the machines name to a list.

If the backup fails one night it will most likely complete the next one
without problems. So this is not really a concern as long as backups
are running nicely most of the time. I check the logs on the backup
server on a daily basis, so I'm well aware of was is going on. Also the
update script does send an email upon completion.

The error control in the script is just an added extra, not a necesity.
I have learned that it comes in handy to at least notify me that
something went wrong. It does not have to be complete recovery control.
A simple "Backup failed" message can be easier then reading all the
output each time.

And that is obviously up to you, but I would go with one script ran from
the server that steers all the other machines/ To me that is the easiest
solution.

the advantage of doing it vcia an ssh script is that you do not need NFS
running.

houghi
--
Knock-knock.
Who's there?
Under the Patriot Act, we don't have to tell you that.
.

Relevant Pages

  • Re: VBS will not run on some machines, NO errors
    ... Establish sorted file list pictures of good vs: bad machines. ... Alternatively invoke "context menu" inf install. ... "When I go to a command prompt on this server and type Wscript.exe" ... When I state that we tried to run the script manually, ...
    (microsoft.public.scripting.wsh)
  • Measuring System Utilization Over Time
    ... Our current server roster has grown to the point ... This step will identify which machines are good candidates ... I figure that sar is the best way to capture usage statistics over time. ... By default sar only holds reports for 7 days so I modified the sa2 script ...
    (SunManagers)
  • Re: Need experience/suggestions on backup product
    ... I'm posting here because all of the machines are AIX 5.2+, ... They will not backup over the WAN, ... Make one server a Storix Admin Server ... Servers with tape drives attached can be made Storix Backup Servers ...
    (comp.unix.aix)
  • Re: SBS 2003 Backup Failures
    ... I have used a recovery storage group on the server but that was last year ... I have loaded the "Small Business Backup Script.bks" file but there is no ... The RSG will be added to the script. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Scripting - To work with Virtual Server 2005
    ... See the MS 2003 Server whatever. ... I set up two machines to do remote scripting with wsh 5.6. ... I have a XP SP 2 machine that will execute the script. ...
    (microsoft.public.scripting.wsh)