Log in

No account? Create an account

Josh-D. S. Davis

Xaminmo / Omnimax / Max Omni / Mad Scientist / Midnight Shadow / Radiation Master

Previous Entry Share Next Entry
A blast from the past
Josh 201604 KWP
On Thu, 7 Feb 2002 14:41:06, I posted this to ADSM.ORG. Amazingly, other than the DB volume portion and the TIVOLI URL, it still pretty much applies today.

I've found out that IBM *and* consultants are using this text verbatim but stripping my name from it. I never put a copyright on this, but it's still very poor form not to give credit to your sources. You can search the web and find my post of this archived on ADSM.ORG, among other places.

Anyway, reposting here with a few minor tweaks below. I'm not really adding in the stuff for TSM 6.x base install due to complexity and platform variability. Ok, because I'm being lazy.

Basic In-Order TSM Server Setup Checklist
I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.


Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
      349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
      all others use TSM drivers

Make a larger database and log: (Pre 6.x style)
   define dbvolume        (make space)
   define dbcopy          (mirror elsewhere)
   extend db              (tell tsm to use the new space)
   define logv            (make space)
   define logc            (mirror elsewhere)
   extend log             (tell tsm to use the new space)
   define spacetrigger    (auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license       (see the server/bin directory)

Storage setup inside TSM:
   define library          (top level of tape storage)
   define devclass         (points to a library)
   define drive            (points to a library)
   define stg              (points to a device class)
   define vol              (points to a devclass and storage pool)
   label libvol            (prepares a tape for TSM use)
   checkin libv            (makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain           (top level of policy information)
   define policyset        (contained within a policy domain)
   define mgmtclass        (contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy         (only one policyset active per domain)
   register node           (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
      Virtual Volumes
      Library Sharing
   Administrator's Guide, Chapter 1: Introduction
      Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
      Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
      Integrated, licensed tool for server protection
      client backup schedules
      server administrative schedules (don't overlap these)
         BACKUP STG (sync up copy pool)
         UPDATE STG RECLAIM=50 (reclaim free space from tapes)
         UPDATE STG RECLAIM=100 (turn off reclaimation)
         UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
         UPDATE STG HI=90 LO=70  (migrate only during overflow)
         BACKUP DB (TSM database is critical to server function)
         BACKUP DEVCONFIG (Device config DB in text format for DB recovery)
         BACKUP VOLHISTORY (List of volumes used in DB recovery)

In all procedures WATCH FOR ERRORS.

If you have questions, see Documentation at:
   * TSM v5.5: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1
   * TSM v6.1: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
   * TSM v6.2: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2

TSM Administrator's Guide is procedural information
TSM Administrator's Reference is command syntax
TSM Messages Guide is decyphering for ANR/ANS messages

Also, *the* reference from Richard B. Sims:
Tags: , ,

  • 1
I'm really disappointed that this has seemingly nothing to do with BDSM

Bondage Distributed Storage Manager?

Asphyxiated Domination Sado-Masochism?

(Deleted comment)
Yup, I figured it was a good thing for other people to use and got good feedback on it back then.

IBM Support gave it verbatim to a consultant, who put it verbatim into a document for a government customer's post-install guide. No reference to me. It was attributed to the installing tech.

I don't mind people using it, but it bothers me if it's being passed off as someone else's work.

(Deleted comment)
ADSM.ORG mirrored a listserv, so the rules in effect for the listserv would apply.

Regardless, I did implicitly release the information to the public domain.

Even so, quoting of large portions of text requires a bibliographical reference.

Failure to provide reference is an implicit declaration that the work is original.

Passing off duplicated works as original is plagiarism, regardless of whether the source document is public domain or all rights reserved.

Plagiarism is bad form and reflects poorly on the plagiarist.

Or a cheap summary would be this: If it would fail you when writing a college paper, it's inappropriate for the professional world.

So there's a mix here. Some of it is that I feel slighted, but that wouldn't be an issue if proper literary form had been used.

  • 1