12.07.2015 Views

Installation and User's Guide

Installation and User's Guide

Installation and User's Guide

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

vvThe backup-archive client is installed to the c:\program files\tivoli\tsm\baclient directory.The communication parameters in the backup-archive client options file(dsm.opt) are appropriate for the Tivoli Storage Manager server.On the server:1. Enter the following comm<strong>and</strong> on the server console or from an administrativeclient to define the schedule: def sched bacliwnt wnt_daily_incr desc="DailyIncremental Backup" priority=2 starttime=21:00 duration=15durunits=minutes period=1 perunits=days dayofweek=any. The administrativeclient does not have to be running on the same system as the Tivoli StorageManager server. Tivoli Storage Manager displays this message: ANR2500ISchedule WNT_DAILY_INCR defined in policy domain BACLIWNT.2. To associate the backup-archive client to this schedule, issue the followingcomm<strong>and</strong>: define association bacliwnt wnt_daily_incr mars. Tivoli StorageManager displays this message: ANR2510I Node MARS associated with scheduleWNT_DAILY_INCR in policy domain BACLIWNT. At this point, a schedule thatperforms an incremental backup is defined on the Tivoli Storage Managerserver. The schedule starts around 9:00 pm. The schedule is re-executed once aday <strong>and</strong> can start on any day of the week. If you want to confirm that theschedule <strong>and</strong> association are set correctly, you can use the Query Schedulecomm<strong>and</strong>.On the backup-archive client:This example assumes that you installed the Tivoli Storage Managerbackup-archive client in the c:\program files\tivoli\tsm\baclient directory. Italso assumes that the options files in each of these directories are updated so thatthe communication parameters point to the Tivoli Storage Manager server.1. Login using an account with administrative privileges.2. Open a comm<strong>and</strong> prompt window <strong>and</strong> issue the following comm<strong>and</strong>: cd /d"c:\program files\tivoli\tsm\baclient". If the path contains a space, forexample c:\program files\tivoli\tsm\baclient, enclose the name in doublequotation marks.3. In the window, issue the following comm<strong>and</strong>: dsmcutil inst scheduler/name:"TSM Client Scheduler" /node:mars /password:marspswd/clientdir:"c:\program files\ tivoli\tsm\baclient" /optfile:"c:\programfiles\tivoli\tsm\ baclient\dsm.opt" /autostart:yes. Your system is nowready to run automatic daily incremental backups. The /autostart:yes optionspecifies that the scheduler service starts automatically each time the system isrebooted. You can use the /startnow:[Yes|No] option to specify whether to startthe scheduler service after executing the comm<strong>and</strong>; the default is Yes.Ifyouspecify /startnow:No you must start the service manually using the servicescontrol panel applet on NT, or issue the following comm<strong>and</strong>: net start "TSMClient Scheduler".4. The scheduler uses the backup-archive client options file to validate the node<strong>and</strong> password, <strong>and</strong> to contact the server for schedule information. This exampleassumes that the dsm.opt file is updated so that the communication parameterspoint to the Tivoli Storage Manager server. If you see the following message: Acommunications error occurred connecting to the TSM server. You shouldensure that the options file contains entries that point to the correct TivoliStorage Manager server. You should also ensure that the server is running. Usethe dsmcutil update comm<strong>and</strong> to correct one of the parameters which wasincorrectly specified during the dsmcutil install. For example, to update the248 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: <strong>Installation</strong> <strong>and</strong> <strong>User's</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!