The approach to architecting client schedules often depends upon the structure of the organization in which you work. The computer systems within an organization may be exclusively within the purview of the administrators of those machines, where they should be the only ones formulating TSM client operations through client options file contents. Other organizations may have a more centralized structure and commonality, where the TSM administrator is allowed to use DEFine CLIENTOpt and DEFine CLOptset to set up sets of governing options residing in the TSM server which help define client processing, as then associated with the TSM node. The apportionment of responsibilities will help determine the approach taken, where the responsible party can then set up the appropriate regiment for DOMain specs to govern backups, and client schedule OBJects to define archiving.
Richard Sims http://people.bu.edu/rbs
