On 20 Mar 2002 at 14:19, Joni Moyer wrote, in part: > I've been studying the TSM manual and changing administrative schedules > by trial and error, but I just wanted to know if I have the order of > procedures down right. 1. Backup disk to offsite tape pool 2. Backup > onsite tape pool to offsite tape pool 3. Migration of the disk pools 4. > Expire Inventory 5. Reclamation 6. Client Backups (run at night)
Others have spoken about DB/VolHist/DevConfig backups (after 2). I'll add that 4 and 5 can be done any time in that they are independent of offsite protection and getting initial backups. They can be thought of as controlling the utilization of your storage pools and DB. I note that, unless you monkey with reclamation levels, Expire Inventory will tend to kick off reclamations. In my experience with ADSM V3.1 and a relatively small (and even) number of tape drives, reclamations can block other tape activities (restore, migration, etc.) for long periods of time. You might also consider that "6. Client Backups" is really step 0, at least it is to my way of thinking. I'm trying to provide a risk management service. I can't restore something until it's backed up, hence "Client Backups" are step 0 (most important and first ... even if at night!). Everything else *SM does must provide for restoration at almost any time, and backups at expected times. This means I may try to delay migrations (disk to tape copy) as long as possible, but I really want my disk pools migrated by the time the next significant backups occur. *SM's offsite backups (backup to copypool tapes, db backup *after* copypool tapes are built, VolHistory and Devconfig) allow rebuilding of your *SM operations after some backup server location disaster. This backup is good up to the point of the DB backup, with caveats. The caveats include: (1) if you backup to copypool tapes after your offsite DB backup, those copypool tapes are worthless wrt reconstruction of your backup server after a disaster (loss of *SM DB), and (2) it's important to keep your "Delay Period for Volume Reuse" at least as long as you consider any one DB backup useful. Hope this helps, wayne Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
