Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+DB\s+Max\s+Size\s+\(how\s+scalable\s+is\s+TSM\?\)\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: TSM DB Max Size (how scalable is TSM?) (score: 1)
Author: Gerald Wichmann <gwichman AT ZANTAZ DOT COM>
Date: Fri, 26 Apr 2002 13:31:05 -0700
Hmm at 66.5% you're using more like 7,820MB of DB space. With 22,760,941 files that's more like (7,820,000,000 / 22,760,941) 343 bytes per file. The TSM admin guide says for each backup version you c
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01518.html (11,284 bytes)

2. Re: TSM DB Max Size (how scalable is TSM?) (score: 1)
Author: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>
Date: Fri, 26 Apr 2002 15:35:06 -0700
I have two real-life examples: 110 GB on a Windows platform, 180 GB on a Mainframe platform. Backup times on the Windows system a little over two hours, 2.5 hours to restore the db. I don't know abou
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01520.html (11,099 bytes)

3. Re: TSM DB Max Size (how scalable is TSM?) (score: 1)
Author: Gerald Wichmann <gwichman AT ZANTAZ DOT COM>
Date: Fri, 26 Apr 2002 15:34:22 -0700
Good to know thanks. It seems like most of the postings I've read correlate the problem with TSM's DB growing to how long it takes to backup and restore the DB. Seems like this is directly proportion
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01525.html (11,668 bytes)

4. Re: TSM DB Max Size (how scalable is TSM?) (score: 1)
Author: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Date: Sun, 28 Apr 2002 12:12:30 +0300
Gerald, the main obstacles for unlimited growth of the TSM DB are DB backup/restore times, inventory expiration, usage of select statements over some huge tables. I would try to analyse with real wor
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01540.html (14,155 bytes)


This search system is powered by Namazu