ADSM-L

Re: [ADSM-L] ANS5013E Not enough memory for backup operation

2008-10-09 11:50:55
Subject: Re: [ADSM-L] ANS5013E Not enough memory for backup operation
From: Cory Heikel <cheikel AT HMC.PSU DOT EDU>
To: ADSM-L AT VM.MARIST 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.

>>> Ben Bullock <BBullock AT BCIDAHO DOT COM> 10/9/2008 11:35 AM >>>
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 about every time I upgrade/install the 
TSM client lately. Search through the archives to get more information about 
this innocuous error.

As for the millions of files. I have one with about 20 million and the issue I 
kept getting was that the Windows host ran out of memory. What I have done to 
get around it is to turn the journaling backups on, and for those times when it 
has to do a full backup, I have set the "MEMORYEFF" to "DISKCACHEM" and then 
set the "discacheloc" to some area on the drive (in the dsm.opt file).

The downside is that this does chew up a lot of disk space for both the journal 
and the cache area, but it will let the host actually get a complete backup 
without dying.

Ben


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Thursday, October 09, 2008 9:24 AM
To: ADSM-L AT VM.MARIST DOT EDU 
Subject: [ADSM-L] ANS5013E Not enough memory for backup operation

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 large number of files or a client 
problem.  They are currently running the 5.5.0.6 client. Recommended at least 
going to the 5.5.1.1 level before we troubleshoot this problem, further, since 
they are also getting the dreaded "
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM.
RC = 13." error which IIRC, the 5.5.1.x client resolves/addresses.

If this doesn't help, what other recommendations are there to handle this
situation?  MEMORYEFFICIENTBACKUP ?   Multiple backup/node definitions to
run different backups for each drive (1-drive has 26M and another has 11M).

The BCI Email Firewall made the following annotations
---------------------------------------------------------------------
*Confidentiality Notice: 

This E-Mail is intended only for the use of the individual
or entity to which it is addressed and may contain
information that is privileged, confidential and exempt
from disclosure under applicable law. If you have received
this communication in error, please do not distribute, and
delete the original message. 

Thank you for your compliance.

You may contact us at:
Blue Cross of Idaho 
3000 E. Pine Ave.
Meridian, Idaho 83642
1.208.345.4550

---------------------------------------------------------------------