Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Unable\s+to\s+complete\s+backup\s+of\s+Window\'s\s+2000\,\s+client\s+failing\s+with\s+\-\s+PrivFindDir\:\s+No\s+memory\s+to\s+allocate\s+new\s+DirEntry\s*$/: 6 ]

Total 6 documents matching your query.

1. Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: David Browne <dbrowne AT HUMANA DOT COM>
Date: Tue, 10 Jan 2006 09:35:07 -0500
I have a Window's 2000 SP4 client (with 8 GB of system RAM) running TSM 5.3.0.8 that has two TB of data and around 22 million files in approximately 11 million directories. The data is on one drive a
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00166.html (12,442 bytes)

2. Re: Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: Rainer Holzinger <rainer_holzinger AT WEB DOT DE>
Date: Tue, 10 Jan 2006 16:30:43 +0100
Hello David, I've solved a similar case by implementing the TSM Journal Services, Elapsed backup time before was about 12:30 hours (45 seconds data transfer time)) and most of the time abends because
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00167.html (13,830 bytes)

3. Re: Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: "Brents, James" <James.Brents AT VALERO DOT COM>
Date: Tue, 10 Jan 2006 09:40:59 -0600
I believe you will have to break the backup into chunks and hit a certain number of high-level directories in each backup. Unfortunately if you add another high-level directory you will have to remem
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00168.html (13,259 bytes)

4. Re: Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: David W Litten <dlitten AT DUKE-ENERGY DOT COM>
Date: Tue, 10 Jan 2006 10:45:04 -0500
set MEMORYEFFICIENTBACKUP NO in the client option set or dsm.opt file. "Brents, James" <James.Brents@VAL ERO.COM> To Sent by: "ADSM: ADSM-L AT vm.marist DOT edu Dist Stor cc Manager" <[email protected]
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00169.html (14,295 bytes)

5. Re: Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: Richard Sims <rbs AT BU DOT EDU>
Date: Tue, 10 Jan 2006 10:26:18 -0500
I have a Window's 2000 SP4 client (with 8 GB of system RAM) running TSM 5.3.0.8 that has two TB of data and around 22 million files in approximately 11 million directories. The data is on one drive
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00170.html (13,269 bytes)

6. Re: Unable to complete backup of Window's 2000, client failing with - PrivFindDir: No memory to allocate new DirEntry (score: 1)
Author: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
Date: Tue, 10 Jan 2006 17:43:46 -0500
David, Having just gone through this type of "fix" in our environment (breaking multi-TB drives into smaller chunks), I totally agree with Richard - and we had to do it on W2k3 machines, which theore
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-01/msg00190.html (14,348 bytes)

Current List: 1 - 6
Page: [1]
This search system is powered by Namazu