Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+ANS5013E\s+Not\s+enough\s+memory\s+for\s+backup\s+operation\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+ANS5013E\s+Not\s+enough\s+memory\s+for\s+backup\s+operation\s*$/: 12 ]

Total 12 documents matching your query.

1. [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Thu, 9 Oct 2008 11:23:56 -0400; Is there a "realistic" maximum number of files a Windows client can handle before having this kind of problem? This system has 30-40 MILLION objects/files. Not sure if this error is caused by the lar; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00110.html (12,674 bytes)
2. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Ben Bullock <BBullock AT BCIDAHO DOT COM>; Date: Thu, 9 Oct 2008 09:35:08 -0600; That first error about DRM can be easily resolved by opening that entry using 'regedit' and closing it without making any changes. Regedit will correct it by itself. I have to do that simple trick ab; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00111.html (14,864 bytes)
3. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Wanda Prather <wprather AT JASI DOT COM>; Date: Thu, 9 Oct 2008 11:38:57 -0400; Hi Zoltan, I've seen the problem on clients with as few as 10m files. When you do a typical incremental backup, the first thing that happens is that the server pushes down to the client a list of the; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00112.html (13,947 bytes)
4. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Thu, 9 Oct 2008 09:39:18 -0600; What does one think will happen if one needs to restore all of these files? Are you coupling traditional TSM backup with backup image? I'm thinking a restore of 10M files will take something like 50-; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00113.html (15,591 bytes)
5. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Wanda Prather <wprather AT JASI DOT COM>; Date: Thu, 9 Oct 2008 11:40:28 -0400; Correction: When I said "active backup set, that was a bad thing to call it. What I meant was a list of the active versions stored on the server for that client. The client compares against that list; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00114.html (14,788 bytes)
6. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Cory Heikel <cheikel AT HMC.PSU DOT EDU>; Date: Thu, 9 Oct 2008 11:50:02 -0400; I had previously had some trouble with the journaling. May have been fixed in a subsequent release. We just use the memoryeff with diskcachemem. That first error about DRM can be easily resolved by o; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00116.html (15,151 bytes)
7. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Thu, 9 Oct 2008 11:48:39 -0400; Are there any hidden controls on where it puts the "diskcache"? The book doesn't seem to indicate anything for MEMORYEFFICIENT other than YES/NO/DISKCACHEMETHOD? The node hasn't been backing up. That; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00117.html (14,781 bytes)
8. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Wanda Prather <wprather AT JASI DOT COM>; Date: Thu, 9 Oct 2008 12:12:46 -0400; You get to pick the location: MEMORYEFFICIENTBACKUP DISKCACHEMETHOD DISKCACHELOCATION \path On Thu, Oct 9, 2008 at 11:48 AM, Zoltan Forray/AC/VCU <zforray AT vcu DOT; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00118.html (15,901 bytes)
9. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Thu, 9 Oct 2008 13:44:25 -0400; Restore????? Whoever thinks about that ;--))) I would predict a lot longer than that. When we had a major SAN failure on our old email server (25M objects), it took 15-days to completely restore. The; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00120.html (16,419 bytes)
10. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Thu, 9 Oct 2008 13:45:13 -0400; Thanks for the info. Wanda Prather <wprather AT JASI DOT COM> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 10/09/2008 12:13 PM Please respond to "ADSM: Dist Stor Manager" <ADSM-L; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00121.html (16,199 bytes)
11. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 9 Oct 2008 15:13:35 -0500; Restoring is not the biggest problem, properly setting expectations is the real problem. If you can get the data back you are doing your job, if the user understands the consequences of having a file; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00126.html (17,839 bytes)
12. Re: [ADSM-L] ANS5013E Not enough memory for backup operation (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Fri, 10 Oct 2008 07:28:36 -0400; Zoltan - This, of course, is the historic "Many small files" challenge. Recommendations on it are summarized in ADSM QuickFacts, based upon our communal pursuit of it in our shops. You've provided no; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-10/msg00133.html (12,614 bytes)

Current List: 1 - 12
Page: [1]