Try this APAR: IC63373: DB2 CONFIGURATION PARAMETER NUM_LOG_SPAN DOES NOT GET UPDATED CORRECTLY WHEN THE ACTIVELOGSIZE IS CHANGED IN DSMSERV.OPT
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, April 05, 2010 12:29 PM To: [email protected] Subject: Re: TSM Active Log --- Trouble I haven't paid much attention to the CPU/Memory usage. There are only 5-really active and 24-semi active clients on this box. The biggest issue is the DB load since there are over 100M objects for the 5-active clients. I think the recommendation for memory is at least 8GB. I just received 2-new servers, "loaded for bear" - 48GB RAM, 8-600GB 15K RPM (which raid/mirrored will only be used for OS, DB and LOGS - LZ will be in SAN), 2-Quad CPU, etc. If this doesn't handle the load, then nothing will! From: "Allen S. Rout" <[email protected]> To: [email protected] Date: 04/05/2010 11:54 AM Subject: Re: [ADSM-L] TSM Active Log --- Trouble Sent by: "ADSM: Dist Stor Manager" <[email protected]> >> On Mon, 5 Apr 2010 10:43:26 -0400, Zoltan Forray/AC/VCU <[email protected]> said: > I schedule 3-FULL DB BACKUPS and DAILY VOLHIST BACKUPS on my lone V6 > server. This is the only way I have been able to keep my sanity 3 fulls a day? Owie. I'm currently doing 1-2 fulls a week. This is nicht gut. Applying your math, I'd have 2TB of various TSM databases; backing that up daily would make me my second-biggest database customer, exceeded only by the central WebCT installation at 3.mumble TB. What's about CPU/Memory; how much has that grown for you? - Allen S. Rout
