Hello,

Thanks everybody for response. I'm glad to know that I'm not the only
one with this problem.

I would vote for Andy's solution (sorry Richard, your solution is even
better, because it stops backup gracefully, but it requires changing
storage pool, and I don't want to do that).

Until now customer implemented very simple solution. He created two
Windows scheduled tasks; one that says 'net start tsmsched' at 10pm and
another one 'net stop tsmsched' at 4am. Problem with that is backup just
got killed at 4am and there is no record in server activity log that
backup is finished. We are sending emails to all customers every morning
by browsing the activity log and extracting those 13 lines about
finished job, so he doesn't receive any emails.
I will try Andy's solution and post test results.


Thanks again,


Joe Crnjanski
Infinity Network Solutions Inc.
Phone: 416-235-0931 x26
Fax:     416-235-0265
Web: www.infinitynetwork.com
 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: Thursday, June 01, 2006 5:16 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: weird request for schedule

You could probably script something up that runs at 4am that does
something like this:

Use SELECT to identify sessions for this node, and create CANCEL SESSION
commands. The output can be redirected to a file. Then use the dsmadmc
MACRO command to run the commands in the file to which the output was
redirected.

Simple example for Windows of a file named cancelsession.cmd


-----
dsmadmc -id=storman -pa=xxxxx -dataonly=yes -commadelimited
-outfile=cancelsession.macro "select ' cancel session ' ||
cast(session_id
as varchar(20)) from sessions where session_type='Node' and
client_name='STORMAN'"

dsmadmc -id=storman -pa=xxxxx -outfile=cancelsession.out macro
cancelsession.macro
-----

The drawback is that the cancellations are indiscriminate; any client
session for the named node will be cancelled, regardless of what
operation
it is doing. If it is unlikely that the node will be doing anything
other
than scheduled backup, then this should work.

I'm sure others have more sophisticated methods, but this is my "what
can
I whip up in 5 minutes" answer.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorag
eManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-06-01
13:21:29:

> Hello,
>
> I have a customer who wants to run backup only during specific time
> window; from 10pm to 4am.
>
> That means when backup starts at 10pm, and runs until 4am, and even if
> at 4am there are more files to be backed up, he wants backup to stop
and
> to be rescheduled for next backup cycle.
>
> Any ideas appreciated.
>
> Joe Crnjanski
> Infinity Network Solutions Inc.
> Phone: 416-235-0931 x26
> Fax:     416-235-0265
> Web: www.infinitynetwork.com
>