12.07.2015 Views

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

If the current directory is not in your PATH environment variable, enterthe following comm<strong>and</strong>:./dsmc scheduleWhen you start the client scheduler, it runs continuously until youclose the window, end the process, or log off your system.To run the schedule comm<strong>and</strong> in the background <strong>and</strong> to keep the clientscheduler running, even if you log off your system, enter the following:nohup dsmc schedule 2> /dev/null &If you are using the CAD to manage the scheduler, you must set the recoveryproperties <strong>for</strong> the ″TSM Client Acceptor″ service, but leave the settings <strong>for</strong> the″TSM Client Scheduler″ to take no action <strong>for</strong> first, second, <strong>and</strong> subsequent failures.Managing multiple schedule requirements on one machineIn certain situations it is preferable to have more than one scheduled activity <strong>for</strong>each client system. Normally, you can do this by associating a node with morethan one schedule definition. This is the st<strong>and</strong>ard method of running multipleschedules on one machine. You must ensure that the schedule windows <strong>for</strong> eachschedule do not overlap. A single client scheduler process is not capable ofexecuting multiple scheduled actions simultaneously, so if there is overlap, thesecond schedule to start will be missed if the first schedule does not completebe<strong>for</strong>e the end of the startup window of the second schedule. Suppose that most ofthe drives on your client system must be backed up daily, <strong>and</strong> that one drivecontaining critical data must be backed up hourly. In this case, you would need todefine two schedules to h<strong>and</strong>le this requirement. To avoid conflict between thehourly <strong>and</strong> daily backup schedule, the starttime of each schedule needs to bevaried.In certain cases, it is necessary to run more than one scheduler process on asystem. Multiple processes require a separate options file <strong>for</strong> each process <strong>and</strong>must contain the following in<strong>for</strong>mation:v Define a unique node name <strong>for</strong> each processv Specify unique schedule <strong>and</strong> error logs <strong>for</strong> each processv When running in prompted mode, you must use the tcpclientport option tospecify a unique port <strong>for</strong> each process.The advantages of using multiple schedule processes:v You can run more than one scheduled backup at the same time.v You can specify different backup criteria <strong>for</strong> each schedule started, via <strong>Tivoli</strong><strong>Storage</strong> <strong>Manager</strong> client option file or <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server overrideoptions.The disadvantages of using multiple schedule processes:v A unique file space <strong>for</strong> each node name on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server iscreated.v When restoring the data, you must use the same node name associated with thebackup.||||Multiple schedule processes can run on <strong>UNIX</strong> <strong>and</strong> <strong>Linux</strong> plat<strong>for</strong>ms with either theCAD managed method, or the traditional method of running the scheduler. Ineither case, there are certain setup requirements:v Each process must run using a different node name.Appendix A. Using the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> central scheduler 505

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

Saved successfully!

Ooh no, something went wrong!