bbrown00
ADSM.ORG Member
I have just been informed that a document imaging system that has gone production this week has data on several optical juke boxes that will be migrating. We planned for the capacity on spinning disk, but the number of files were not known until today. There are 88+ million files existing, not including growth. The files will be migrating over the next 18 months. The system is a W2K3 MSCS with NTFS. I have a few questions about how to deal with this...
I have 2 TSM servers 1 with 51327206 files on it (used ...'select sum(num_files) from occupancy')and 20GB used DB, the other with 81796176 files on it and 29GB used DB.
1. If only 1 version is kept of the images, between primary and copy I should have 177+ million on just the existing data not including growth over the next year. I get roughly 60-65 GB TSM DB just for the existing data...where did I read that you shouldn't go over 80 GB for a TSM database, is that true?
2. Anybody ever used TSM journaling with a W2K3 NTFS system with88+ million files. Looks like that would be treading new waters from some of the posts I have read.
3. Any architecture suggestions...i.e. completely seperate TSM server, library, journaling config, etc... Current architecture is 2 W2K3 TSM servers connected to an IBM 3584 library logically split down the middle with 10 LTO3 fibre attached drives(5 per server).
I have 2 TSM servers 1 with 51327206 files on it (used ...'select sum(num_files) from occupancy')and 20GB used DB, the other with 81796176 files on it and 29GB used DB.
1. If only 1 version is kept of the images, between primary and copy I should have 177+ million on just the existing data not including growth over the next year. I get roughly 60-65 GB TSM DB just for the existing data...where did I read that you shouldn't go over 80 GB for a TSM database, is that true?
2. Anybody ever used TSM journaling with a W2K3 NTFS system with88+ million files. Looks like that would be treading new waters from some of the posts I have read.
3. Any architecture suggestions...i.e. completely seperate TSM server, library, journaling config, etc... Current architecture is 2 W2K3 TSM servers connected to an IBM 3584 library logically split down the middle with 10 LTO3 fibre attached drives(5 per server).
Last edited: