Your best bet is to look at the admin ref's manual and look at the format of
the commands. The sched you have is labeled daily_inc but you have the
action set as image backup. Also, you have a value in the objects which is
incorrect.
So go to a TSM command line and enter:
-q dom (to get the dom
I can speak, at least in part, to some of your issues.
1a. For the scheduled event problem, TSM creates two relevant logs:
dsmsched.log and dsmerror.log. Whenever you encounter problems, those
should be the first places to look. I suspect the dsmerror.log will
indicate a problem with the file syst
>My understanding of Mike´s sentences per se is:
>The schedules did not run untill 02:41.
>The schedules may have run later,
>but Mike is either not sure about or not exact at this point.
>
>Your understanding is: the schedules did run at 02:41.
>Is this fully clear from Mike´s sentences?
Normal
Simple answer - the fact that the schedule actually ran means there IS an
association - the fact that it does not run at the set time has to do with
the schedule randomization % that is set on the TSM server and the length of
the start-up window for the schedule for this client.
Simple example:
Sch
>My backups are scheduled to start at 01:00, but didn't start till 02:41
>Monday & 01:21 today. Any idea why?
See "Randomizing Schedule Start Times" in the Admin Guide.
Are you running POLLING or PROMPTED? I could see this in POLLING and the
schedule randomization percentage.
If you're running PROMPTED, i would check your server activity log to see if
you can identify the delay.
Bill Boyer
DSS, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mail
Neil,
We are running our client backups using this tool in a large environment. In
order for this to be succesfull you could create scripts for the client
platform to run the client backup. Use ECS to start and monitor the clients
backupprocess. We have it running succesfully for over 250 client
