ADSM-L

Re: TSM Schedule

2004-04-15 21:33:10
Subject: Re: TSM Schedule
From: nghiatd <nghiatd2 AT FPT.COM DOT VN>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 16 Apr 2004 08:32:27 +0700
You should open and read dsmsched.log file in the directory 
"\tivoli\tsm\baclient\dsmsched.log". This file contains information relative to 
active schedules

Best regard,

Nghiatd

  ----- Original Message ----- 
  From: Andrew Raibeck 
  To: ADSM-L AT VM.MARIST DOT EDU 
  Sent: Thursday, April 15, 2004 9:00 PM
  Subject: Re: TSM Schedule


  If you have done the basic steps that I have outlined, then there is
  something wrong in your setup. I am unable to answer your question with a
  simple "perform step x to achieve the backup."

  To back up only the C: drive, you would put

     DOMAIN C:

  in your client options file (dsm.opt). You do not need the -SUBDIR=YES in
  the schedule definition, although its presence is not the problem.

  So now the issue becomes trying to identify where the problem lies.

  It would help to know the following:

  - Content of client options file (dsm.opt)

  - Version of TSM client you are using.

  - Output from the following client command:

     dsmc query schedule

  - Output from the following admin commands:

     query node client3 format=detailed
     query event standard daily_incr
     query association standard daily_incr

  (note: the last two commands assume that the domain name is STANDARD;
  specify the correct domain name if my assumption is wrong.)

  If the "dsmc query schedule" command returns a schedule, then it is likely
  that the scheduler service is not running on the client. If "dsmc query
  schedule" does not return a schedule, then you probably need to use the
  DEFINE ASSOCIATION command to associate node CLIENT3 with the DAILY_INCR
  schedule.

  Regards,

  Andy

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

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



  jianyu he <andyhe1218 AT YAHOO DOT CA>
  Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
  04/15/2004 06:35
  Please respond to
  "ADSM: Dist Stor Manager"


  To
  ADSM-L AT VM.MARIST DOT EDU
  cc

  Subject
  Re: TSM Schedule






  Hi Andrew,

  I am studying TSM now, so I  want to achieve the automatic backup task.  I
  have finished the manual backup, archieve, restore, and retrieve, but when
  I try to achieve the function of shcedule, the client doesn't backup
  during the execution.


  tsm> query session
  TSM Server Connection Information
  Server Name.............: HJY3
  Server Type.............: Windows
  Server Version..........: Ver. 5, Rel. 2, Lev. 2.0
  Last Access Date........: 04/15/2004 09:16:14
  Delete Backup Files.....: "Yes"
  Delete Archive Files....: "Yes"
  Node Name...............: CLIENT3
  User Name...............:

  I had done the step that you mentioned. Is there another step I should do
  if I want to backup the data of C$ of CLIENT3.

  Normally, what should I do in the OBJECTS setting.

  thanks

  Andy


  Andrew Raibeck <storman AT US.IBM DOT COM> wrote:
  Hello Jianyu,

  In general, in order for the scheduler to work, you must do the following:

  - Define a schedule on the TSM server.

  - Associate the client nodes with that schedule (using the DEFINE
  ASSOCIATION command). For example:

  DEF ASSOC STANDARD DAILY_INCR MYNODENAME

  - Install and configure the TSM client software on the machine you wish to
  back up, then start the scheduler on that client machine.

  If the above outline does not help, then please provide more detail on
  your problem. The detail in the solution can only be proportional to the
  detail in the problem description. For instance, some questions that occur
  to me:

  1) Your given schedule definition is not very typical. You have
  -subdir=yes in the OPTIONS setting, but no OBJECTS specified. You also
  have the backup running hourly, with a duration of 10 minutes per
  instance. It would help if you could indicate what exactly it is you are
  trying to accomplish, including information on what exactly you want to
  back up. Knowing *why* you want to do this might also provide some useful
  insight.

  2) When you say "my client doesn't work", what exactly does that mean?
  Have you tried performing manual (nonscheduled) backups? If so, what are
  the results? If not, then try testing a manual backup. One useful test
  after installing and configuring the client is to run the command line
  client like this:

  dsmc query session

  This will demonstrate basic connectivity to the TSM server (and it is
  often good to make sure you can walk before you try to run).

  3) Have you configured and started the scheduler? Examine dsmsched.log and
  see whether the scheduler is successfully obtaining information about the
  next scheduled event.

  Regards,

  Andy

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

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



  jianyu he
  Sent by: "ADSM: Dist Stor Manager"
  04/14/2004 15:03
  Please respond to
  "ADSM: Dist Stor Manager"


  To
  ADSM-L AT VM.MARIST DOT EDU
  cc

  Subject
  TSM Schedule






  Hi,

  I want to achieve TSM Client Schedule function, but my client doesn't
  work. could you tell me how to do it?

  Schedule Name: DAILY_INCR
  Description: Daily incremental backup
  Action: Incremental
  Options: -subdir=yes
  Objects:
  Priority: 1
  Next Execution: 0 Minutes
  Duration: 10 Minutes
  Period: 1 Hour
  Day of Week: Any
  Expire: Never



  ---------------------------------
  Post your free ad now! Yahoo! Canada Personals


  ---------------------------------
  Post your free ad now! Yahoo! Canada Personals

<Prev in Thread] Current Thread [Next in Thread>