Hi Roger

I've not done it but....

There is a "wake on lan" function available.  Send an appropriately crafted
packet to the ethernet port and the machine will boot, if configured
properly.  If you use a schedule with a long window, then the backup will
start as soon as the cad/scheduler is initialized after the boot.  A
preschedule command to simply wait for 5 minutes may be needed to make sure
things are stable before you start really moving data.

As to the shutdown part, you need to determine if any users are logged in,
and only shutdown if none are.  I'm reasonably sure you can do this from
windows with vbscript/jscript and the WMI api.

So, in short do-able,  but there are some details to work out.  A quick
google search indicates there are a lot of people doing this for non-TSM
reasons.

Regards

Steve.

Steven Harris
TSM Admin, Sydney Australia





             Roger Deschner
             <rogerd AT UIC DOT EDU>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       [ADSM-L] Green issue: How to avoid
                                       leaving clients on all night
             22/04/2009 10:55
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






We're getting requests from a number of people who have their desktop
computers (mix of Macs and Windows XP/Vista) backed up to TSM, for a way
to avoid leaving them on all night.

The issue is simple energy conservation. Even with the monitor off, and
the disk drives spun down, a live PC still consumes quite a bit of
electricity. If you put it into either Hibernate or Standby mode, the
TSM Scheduler cannot run the backup.

We had thought of setting a POSTSCHEDULECOMMAND of "shutdown", but that
has a severe problem. What if you were working late, because of an
urgent project, and backup ran. Your computer would then shut down
without saving what you were working on, and precisely because it was
urgent enough for you to be working on it late, this would be very
valuable work that would be lost.

Has anybody figured out a way around this basic problem?

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
==== "Research is what I'm doing when I don't know what I'm doing." ====
========================= -- Wernher von Braun =========================