The basic problem is the limit of addressable virtual memory available to a Win32 process.
The virtual address space of a Win32 process is 4 gigabytes (2 ^ 32). By default, only 2 gigabytes of this address space may be allocated as virtual memory (the limit can be increased to 3 gigabytes by using the /3GIG boot.ini setting). TSM full incremental backup requires loading the entire list of active objects for a file system from the TSM server into memory, and then loading each local directory branch into memory one at a time in order to perform the backup. A large enough file system (the exact number of objects depends a few variables such as the length of file names and the directory depth) will eventually cause the TSM client process to run out off addressable memory and not to be able to complete the backup. The MemoryEfficient client option somewhat mitigates the process memory utilization by loading active files from the server a directory at a time (instead of loading the entire filespace at once). Functions such as Incremental By Date and Journal Based Backup are only available after an initial full incremental backup has completed. The virtual address space of a Win64 process is much larger (2 ^ 64) than that of a Win32 process, so to answer your question, upgrading to Win64 and installing the Win64 TSM client would solve the problem of running out of memory. Development is also working on a disk caching solution in a future release which minimizes the amount of virtual memory required during a backup and should allow most file systems to backed up regardless of size (the trade off of course being that the backup may take longer to complete). Hope this answers your questions .... Pete Tanenhaus Tivoli Storage Manager Client Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 06/26/2006 06:25 PM --------------------------- Please respond to "ADSM: Dist Stor Manager" <[email protected]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> To: [email protected] cc: Subject: Can 64bit TSM client on 64 bit os overcome backing up large filesytems?? I am having problems backing up a large filesystem on a win2003k server. The backup is failing because its running out of memory which IBM says is because of the 32bit os limitation. Tried journaling but the server is very busy and continuously gets buffer overflows and the journal fails and I have tried tuning it as well but it still fails. I have not tried the image snapshot backup but I don't trust doing it on a 1 TB windows filesystem. So I was thinking of upgrading the server to win2003k 64bit and loading the tsm 64bit client to backup the server to overcome the 32 bit limitations. Do any of you guys see a problem with that or will I still have the same problems as before? **************************EMAIL DISCLAIMER*************************** This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.413.4947.
