On 30 Aug 2001, at 14:48, Jeff Bach wrote: > 1. A single backups runs to a single volume as perceived by ADSM. The > first session runs to the first volume allocated to the storage pool. The > second session runs to the second logical volume allocated to the storage > pool. The third sessions to the third volume. Boy is this confusing, not not well documented. I thought (apparently wrongly) that the unit of allocation was a transaction. The first transaction for a session would go on one volume, the second tran would go on another, the third on still another. Thus, one session could spread it's backup data across all volumes. I'll have to try this on our test system - when we get it working someday! Rick
- Re: TSM DB/Disk Pool - Disk tuning question Robin Sharpe
- Re: TSM DB/Disk Pool - Disk tuning question Lindsay Morris
- Re: TSM DB/Disk Pool - Disk tuning question Tab Trepagnier
- Re: TSM DB/Disk Pool - Disk tuning question Lindsay Morris
- Re: TSM DB/Disk Pool - Disk tuning question Tab Trepagnier
- Re: TSM DB/Disk Pool - Disk tuning question Paul Zarnowski
- Re: TSM DB/Disk Pool - Disk tuning question Lindsay Morris
- Re: TSM DB/Disk Pool - Disk tuning question Miles Purdy
- Re: TSM DB/Disk Pool - Disk tuning question Richard Sims
- Re: TSM DB/Disk Pool - Disk tuning question Jeff Bach
- Re: TSM DB/Disk Pool - Disk tuning question Richard L. Rhodes
- Re: TSM DB/Disk Pool - Disk tuning question Lindsay Morris
- Re: TSM DB/Disk Pool - Disk tuning question Jeff Bach
- Re: TSM DB/Disk Pool - Disk tuning question Jeff Bach
- Re: TSM DB/Disk Pool - Disk tuning question Mark Stapleton
- Re: TSM DB/Disk Pool - Disk tuning question b290
- Re: TSM DB/Disk Pool - Disk tuning question Mark Stapleton
- Re: TSM DB/Disk Pool - Disk tuning question Richard Sims
