Although the bkup wae taken successfully, The schedule return fail

[fanna]

Hii All

A successful script was written for taking a bkup for c:\* and when it is been executed it done in a successful way.

When adding that script as a command to run via a schedule also the bkup taken successfullly but the schedule is failed.
SO,
Although the bkup wae taken successfully, The schedule return fail.



When querying the schedule event in foreground the following data is issued.

Total number of objects inspected: 8,862
Total number of objects backed up: 8,770
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 12
Total number of subfile objects: 0
Total number of bytes transferred: 1.30 GB
Data transfer time: 30.32 sec
Network data transfer rate: 45,061.15 KB/sec
Aggregate data transfer rate: 9,640.38 KB/sec
Objects compressed by: 0%
Subfile objects reduced by: 0%
Elapsed processing time: 00:02:21
Finished command. Return code is: 8
ANS1909E The scheduled command failed.
ANS1512E Scheduled event 'FULL-BKUP' failed. Return code = 8.
Sending results for scheduled event 'FULL-BKUP'.
Results sent to server for scheduled event 'FULL-BKUP'.

Querying server for next scheduled event.
Node Name: TSMSVR
Session established with server TSMSVR54: Windows
Server Version 5, Release 4, Level 0.0
Server date/time: 06/10/2008 15:03:45 Last access: 06/10/2008 15:03:06

Next operation scheduled:
------------------------------------------------------------
Schedule Name: FULL-BKUP
Action: Command
Objects: c:\full.cmd
Options:
Server Window Start: 16:00:00 on 06/10/2008
------------------------------------------------------------
Command will be executed in 57 minutes.

Time remaining until execution: 00:48:53

 

[avolchonock]

when you run your script manually do you get some sort of an error?

doesn't need to be a tsm error maybe something like cd to a not existing directory or other windows\unix\linux shell commands that fails and sends their error code as the return value to the tsm wich later on translated to a TSM script error code 12 of a failed sched

Best Regards

 

[fanna]

when you run your script manually do you get some sort of an error?

doesn't need to be a tsm error maybe something like cd to a not existing directory or other windows\unix\linux shell commands that fails and sends their error code as the return value to the tsm wich later on translated to a TSM script error code 12 of a failed sched

Best Regards

NOOOO,

It didnot return me any errors when ran manually

By the way TSM script error code of a failed sched is 8

Regards

 

[heada]

Hii All

A successful script was written for taking a bkup for c:\* and when it is been executed it done in a successful way.

When adding that script as a command to run via a schedule also the bkup taken successfullly but the schedule is failed.
SO,
Although the bkup wae taken successfully, The schedule return fail.



When querying the schedule event in foreground the following data is issued.

Total number of objects inspected: 8,862
Total number of objects backed up: 8,770
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 12
Total number of subfile objects: 0
Total number of bytes transferred: 1.30 GB
Data transfer time: 30.32 sec
Network data transfer rate: 45,061.15 KB/sec
Aggregate data transfer rate: 9,640.38 KB/sec
Objects compressed by: 0%
Subfile objects reduced by: 0%
Elapsed processing time: 00:02:21
Finished command. Return code is: 8
ANS1909E The scheduled command failed.
ANS1512E Scheduled event 'FULL-BKUP' failed. Return code = 8.
Sending results for scheduled event 'FULL-BKUP'.
Results sent to server for scheduled event 'FULL-BKUP'.

Querying server for next scheduled event.
Node Name: TSMSVR
Session established with server TSMSVR54: Windows
Server Version 5, Release 4, Level 0.0
Server date/time: 06/10/2008 15:03:45 Last access: 06/10/2008 15:03:06

Next operation scheduled:
------------------------------------------------------------
Schedule Name: FULL-BKUP
Action: Command
Objects: c:\full.cmd
Options:
Server Window Start: 16:00:00 on 06/10/2008
------------------------------------------------------------
Command will be executed in 57 minutes.

Time remaining until execution: 00:48:53

See the line I marked in bold? That is what caused your scheduled backup to be listed as a failure. If you look at the schedule log, you should see it attempt to backup some files that it can't. Fix those and the failures should go away and the backup will be listed as successful.

-Aaron

 

[fanna]

When Ran Manually!!!

Shown what listed when it ran manually:



Selective Backup processing of '\\cli\c$\data\*' finished without failure.


Total number of objects inspected: 407
Total number of objects backed up: 407
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of subfile objects: 0
Total number of bytes transferred: 211.67 MB
Data transfer time: 2.67 sec
Network data transfer rate: 80,908.50 KB/sec
Aggregate data transfer rate: 10,344.76 KB/sec
Objects compressed by: 0%
Subfile objects reduced by: 0%
Elapsed processing time: 00:00:20

C:\PROGRA~1\Tivoli\TSM\baclient>

 

[fanna]

TO heada

Ok heada

I have change the directory to another one as listed in last post reply and it didnot return any errors or any failed backed up files.

AND ALSO

the schedule return me fail

 

[heada]

c:\* is not the same as '\\cli\c$\data\*' so you can't really compare them.

More than likely there are files in "C:\Documents and Settings\{user_name}" that can't be backed up and are causing the backup to fail. In your schedule log, you should see the failures. Look there and either change what you're backing up or exclude them from the backup.

 

[fanna]

Daer

c:\* is not the same as '\\cli\c$\data\*' so you can't really compare them.

More than likely there are files in "C:\Documents and Settings\{user_name}" that can't be backed up and are causing the backup to fail. In your schedule log, you should see the failures. Look there and either change what you're backing up or exclude them from the backup.

Dear heada

I know I know
I said that I made a new one for a new directory for some txt with 200 MB size files and it return me the same error.

By the way
the script syntax is as below:
set BA_DIR=c:\progra~1\tivoli\tsm\baclient\
c:
cd %BA_DIR%
%BA_DIR%dsmc sel C:\* -subdir=yes -optfile=C:\progra~1\Tivoli\TSM\baclient\dsm.opt

 

[heada]

What is the output from the schedule log? That should show why you're getting failures.

-Aaron