. In my experience, the only one of those you don't want to mess with is migration. Tape drives are our most scarce resource.
We do client-backup/expiration/reclamation together. (Our database is big, and is on extremely fast, highly tuned, disks.) Then we migrate, all by itself. Then we backup the database. We expire 22 hours/day or until it finishes, except during database backup. We do database backup/reclamation together. You can call me crazy, but this works and has evolved over many years as the best way to get it all done. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Tue, 15 Jan 2008, Zoltan Forray/AC/VCU wrote: >intentionally). Most of the time the biggest issue is database >transaction conflicts/deadlocks which TSM usually resolves on its own. Of >course, don't know who lost what in the "shoot-out" without doing serious >triage. > > > >TSTLTDTD <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" <[email protected]> >01/15/2008 02:14 PM >Please respond to >[email protected] > > >To >[email protected] >cc > >Subject >[ADSM-L] Spanking my data. > > > > > > >I'd like to hear some expert opinions on this forum. > >What happens when you attempt to backup, migrate, move data, reclaim the >same pools at the same time? > >Thanks in advance for your input. > >+---------------------------------------------------------------------- >|This was sent by [EMAIL PROTECTED] via Backup Central. >|Forward SPAM to [EMAIL PROTECTED] >+---------------------------------------------------------------------- >
