Hi Leigh,
The TSM server is NOT large-address aware. (Current client levels, 5.3.3.0
and higher, are linked with /LARGEADDRESSAWARE.)
You're almost certainly know this already, but I'll mention it anyway for
the benefit of others following this thread: The boot.ini parms affect not
just TSM, but the OS as a whole. This, in turn, can impact your
applications. The ramifications can be profound, depending on what else
the TSM server is used for, since it changes not only the kernel/user
memory split from 2 GB/2 GB to 1 GB/3 GB, but also the sizes of various
memory subpools that Windows manages. An example of one "mystery" case:
backup of very large files (> 100 GB) failed with Windows RC 1450 (Windows
resource shortage, not to be confused with "out of memory") when /3GB was
in use; but after removing that flag and rebooting, backup problem went
away.
So for anyone trying this at home: make *sure* you thoroughly understand
what this setting does. If your knowledge of the /3GB setting extends as
far as, "cool! We can get an extra gig of memory for TSM, let's try it!",
then a consultation with Microsoft (or other Windows internals specialist)
is in order.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 12/11/2006
10:27:10 AM:
> Does anybody have any experience of configuring the following windows
> boot.ini parameters in conjunction with TSM server;
>
> /PAE /3GB
>
> With regards to being able to allocate >2GB to the TSM database
> bufferpool with Windows 2003 Enterprise Edition (32 bit)
>
> I have a Windows 2003 EE (32-bit) server with 8GB of RAM. Have applied
> the /PAE and /3GB switches to the boot.ini, but the TSM server will not
> start with >2GB.
>
> From the reading I have done, it appears that for non-MS apps to take
> advantage of these switches, they must be LARGEADDRESSAWARE. Does
> anybody know if the 32-bit TSM server for Windows is Large Address
> Aware.
>
> I know that a solution would be to go to a native 64-bit MS OS or non-MS
> 64-bit OS, however, there are some management issues preventing this at
> the moment.
> Thanks
>
> Leigh
|
