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 OS overhead involved in registering all those new files was immense. Daily backups used to take many many hours, since it was always at least 3+hours of time spent getting the list of files from the TSM server (both systems were old AIX so no journaling). Nobody wants to do image backups. Especially since this box is not local (e.g. 100mb) and has over 1TB of storage. Kelly Lipp <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 10/09/2008 11:43 AM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] ANS5013E Not enough memory for backup operation 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-100 hours to complete, if it completes... Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 www.storserver.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: Thursday, October 09, 2008 9:35 AM To: [email protected] Subject: Re: [ADSM-L] ANS5013E Not enough memory for backup operation 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:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, October 09, 2008 9:24 AM To: [email protected] 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 ---------------------------------------------------------------------
