Hi Jack, This is because you have "compression on" in the clients *.opt file. When the fil grow more than the original file size this error will orcur. You can set "compression always no" and hopefully the problem will vanish.
- Michael -----Oprindelig meddelelse----- Fra: Coats, Jack [mailto:[EMAIL PROTECTED] Sendt: 7. oktober 2003 15:36 Til: [EMAIL PROTECTED] Emne: server out of data storage space TSM server 4.2.3.1 on Win2K I get this message on some of my clients. I have plenty of scratches, and the storage pools are set to allow 'plenty' of time for data migration before the pool gets full. Where should I look for clues or what are some hints to set things up 'right'? My disk storage pools are: Storage Device Estimated Pct Pct High Low Next Pool Name Class Name Capacity Util Migr Mig Mig Storage (MB) Pct Pct Pool ----------- ---------- ---------- ----- ----- ---- --- ----------- API_DISK DISK 40,000.0 83.9 0.0 50 5 TAPEDATA ARCHIVE LTOCLASS1 0.0 0.0 0.0 90 70 ARCHIVECOP- LTOCLASS1 0.0 0.0 YPOOL ARCHIVEPOOL DISK 100.0 0.0 0.0 50 10 ARCHIVE COPYPOOL LTOCLASS1 17,171,523 22.7 .5 DISKDATA DISK 200,000.0 99.8 0.0 20 3 TAPEDATA DISKDIRS DISK 2,048.0 4.7 0.0 90 5 TAPEDATA RECLAIM RECLAIM 0.0 0.0 0.0 0 0 TAPEDATA SPACEMGPOOL DISK 0.0 0.0 0.0 90 70 TAPEDATA TAPEDATA LTOCLASS1 12,807,596 30.5 48.0 100 0 .6 Where diskdata and diskdirs are my primary disk pools, tapedata is the onsite tape pool, and copypool is the offsite tape pool. TIA .. JC
