Hello all,

Jeff, Pete, Hans, Charles, Ben & Richard

Thanks for all of your Responses!

We are going try the "memoryefficient backup= yes" in the dsm.sys file
suggestion first to see if that
clears up the issue.

Tim

Nast, Jeff P. wrote:

Or add "memoryefficientbackup yes" in the dsm.sys file.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Ben Bullock
Sent: Thursday, January 24, 2008 13:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANS1030E The operating system refused a TSM request form
memory allocation[-UNSECURE-]

The TSM client must receive a list of files for each filesystem before
it can start backing up. It looks like this host got about 1.5 million
files of the listing and then ran out of memory.

One way to fix this would be to turn on Journalled backups if possible
on your system. Either that or add more memory to the host.

Ben

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, January 24, 2008 12:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] ANS1030E The operating system refused a TSM request
form memory allocation

Hello all,


One of our AIX clients is failing, The dsmerror.log shows the ANS1030E
The operating system refused a TSM request for memory allocation message
below. I found some information but I am still confused to according
what I found this is some sort of "Fat Binary issue" I assume this is
not a TSM problem? Or does it varies in possibilities?

Thanks in Advance!


01/24/08 01:34:09 --- SCHEDULEREC STATUS BEGIN
01/24/08 01:34:09 Total number of objects inspected: 1,543,630
01/24/08 01:34:09 Total number of objects backed up: 777
01/24/08 01:34:09 Total number of objects updated: 0
01/24/08 01:34:09 Total number of objects rebound: 0
01/24/08 01:34:09 Total number of objects deleted: 0
01/24/08 01:34:09 Total number of objects expired: 60
01/24/08 01:34:09 Total number of objects failed: 3
01/24/08 01:34:09 Total number of bytes transferred: 8.34 GB
01/24/08 01:34:09 Data transfer time: 169.83 sec
01/24/08 01:34:09 Network data transfer rate: 51,528.86 KB/sec
01/24/08 01:34:09 Aggregate data transfer rate: 1,690.76 KB/sec
01/24/08 01:34:09 Objects compressed by: 100%
01/24/08 01:34:09 Elapsed processing time: 01:26:16
01/24/08 01:34:09 --- SCHEDULEREC STATUS END
01/24/08 01:34:09 ANS1030E The operating system refused a TSM request
for memory allocation.
01/24/08 01:34:09 --- SCHEDULEREC OBJECT END MIDNIGHT 01/24/08 00:00:01
01/24/08 01:34:09 ANS1512E Scheduled event 'MIDNIGHT' failed. Return
code = 12.
01/24/08 01:34:09 Sending results for scheduled event 'MIDNIGHT'.
01/24/08 01:34:09 Results sent to server for scheduled event 'MIDNIGHT'.



TSM Server 5.3.3.4
AIX 5.3
AIX Client 5.3.4


The Blue Cross of Idaho Email Firewall Server 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

========================================================================
======


This e-mail communication and any attachments may contain confidential and 
privileged information for the use of the designated recipients named above. If 
you are not the intended recipient, you are hereby notified that you have 
received this communication in error and that any review, disclosure, 
dissemination, distribution or copying of it or its contents is prohibited. As 
required by federal and state laws, you need to hold this information as 
privileged and confidential. If you have received this communication in error, 
please notify the sender and destroy all copies of this communication and any 
attachments.