My Schedule not Run on TSM Client ?

hungng89

ADSM.ORG Member
Joined
May 25, 2010
Messages
115
Reaction score
2
Points
0
Location
VietNam
Hi all
In policy domain i have created two schedule daily and weekly backup of the system .


I check In the ba command line interface :

Code:
tsm > q sched 

Schedule Name : DB_X 

....
Schedule Name : WB_X
.....

but when i check on dsmsched
Code:
08/18/2010 14:07:26 Scheduler has been started by Dsmcad.
08/18/2010 14:07:26 TSM Backup-Archive Client Version 6, Release 1, Level 0.0   
08/18/2010 14:07:26 Querying server for next scheduled event.
08/18/2010 14:07:26 Node Name: VTHMPWRWS1
08/18/2010 14:07:26 Session established with server TSM: Windows
08/18/2010 14:07:26   Server Version 6, Release 1, Level 2.0
08/18/2010 14:07:26   Server date/time: 08/18/2010 14:06:31  Last access: 08/18/2010 14:06:30

08/18/2010 14:07:26 --- SCHEDULEREC QUERY BEGIN
08/18/2010 14:07:26 --- SCHEDULEREC QUERY END
08/18/2010 14:07:26 No schedule returned from server.
08/18/2010 14:07:26 Scheduler has been stopped.

It show that no schedule associate to this client node .? I wonder can the schedule run or not .?

And one more question , i set up the schedule via admin control center [ gui]
and the archive option i specific is
"c:\*; "d:\*"
Will it backup all the subdir ? or i need to specific like this
"c:\* -subdir=yes"; "d:\* -subdir=yes"

Thanks a lot
 
Hi

You need to associate the node to the schedule on the tsm server with the "define association" command

Syntax
>>-DEFine ASSOCiation--domain_name--schedule_name--------------->
.-,---------.
V |
>----node_name-+-----------------------------------------------><


Your second question, yes you need the -subdir=yes

Cheers
 
Hi
tsm: TSM>define association vthmpwrwx_domain DB_X VTHMPWRWS1
ANR2622E DEFINE ASSOCIATION: No new node associations added.
ANS8001I Return code 10.
It seem that i have add the assosication with my node .
In my client bacommandline interface
i can query the sched
tsm > q sched

Schedule Name : DB_X

....
Schedule Name : WB_X
.....

But still on the dsmsched.log
08/18/2010 19:37:03 --- SCHEDULEREC QUERY BEGIN
08/18/2010 19:37:03 --- SCHEDULEREC QUERY END
08/18/2010 19:37:03 Next operation scheduled:
08/18/2010 19:37:03 ------------------------------------------------------------
08/18/2010 19:37:03 Schedule Name: DB_X
08/18/2010 19:37:03 Action: Archive
08/18/2010 19:37:03 Objects: "C:\*" ;" D:\*"
08/18/2010 19:37:03 Options: dsm.opt
08/18/2010 19:37:03 Server Window Start: 12:00:00 on 08/19/2010
08/18/2010 19:37:03 ------------------------------------------------------------
08/18/2010 19:37:03 Scheduler has been stopped.

08/18/2010 19:38:56 ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE.
08/18/2010 19:38:56 Scheduler has been stopped.

It seem the errors is different .
I read document , it show that there 2 way to manage client schedule , and i some confusion in them :(
Does they both support 2 schedule of daily and weekly backup on my one node client ?

Thanks
 
You need to read Appendix A on the client manual, "Using the TSM Central Scheduler"

But in essence it looks like you have configured the client acceptor daemon (CAD) to control the scheduler service, which means it will automatically stop and start the scheduler service when it needs to, hence the scheduler service will not be running all the time.

This will be fine with two schedules associated with the node.
 
HI

Thanks you so much again . The schedule are up running now .

I also have one little question about the tape recycle method of TSM :

Some old backup software i use has the ability to take X day of backup then start delete the oldest version and write again.
I wonder what replace that function in term of TSM .

Thanks you so much
 
guess you are talking about "Expiration" process ......
 
Yes that was what i expected to .

Is it backup retention in TSM ?
 
no it is not backup retention .. this process checks for the files for which backup retention no more applies and marks them as expired in the server database .. so that they can be overwritten...
 
Hi sakiran
Can you provide me some reference link for expiration and backup retention .. i have trouble understanding them :D

Thanks so much
 
Back
Top