Tried this. Worked just fine. Backed up the whole directory, no issues, no
failures, etc.




"Wheelock, Michael D" <Michael.Wheelock AT INTEGRIS-HEALTH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/27/2004 01:05 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: AIX backup failures - InsertSlashHack! and "System ran out of memory"
messages






Hi,

I am by far and away no expert, but here is what I would do....

Since "nothing" has changed on the server, I would guess that the
problem is in the file you are trying to back up.

Can you turn on tracing or backup by hand to see what file it is chewing
on when it dies?  There may be something corrupt about the file that is
being backed up.

This would explain why cycling the client processes yield the same
result (ie. It still thinks it needs to backup that file).

Tracing may also yield more info as well and would probably be one of
the first things that is asked for by support (along with the logs that
you sent the list).

Michael Wheelock
Integris Health

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, October 27, 2004 11:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: AIX backup failures - InsertSlashHack! and "System ran out
of memory" messages

We gleaned this but the answer is NOT ACCEPTABLE.

Nothing has changed that could explain this error.

We have another IDENTICAL system (same hardware, same OS level, same TSM
client level, etc) that has 3-5 MILLION MORE files and it backups up,
daily, just fine !

In fact, until this problem started occurring, the other IDENTICAL
system
would backup in 4-6 HOURS LESS than this system eventhough the amount of
files being inspected and backed-up (including GB transferred/backed-up)
on this system is LESS.

We can't afford to make this backup process any slower than it already
is
(usual run-time is 13-15 hours).

Any thoughts/feedback from IBM ?   We saw one tid about a restore issue
causing similar error messages but 1) this is not a restore, 2) the fix
was slated for 5.2.3.4 which we can not run since this is AIX 4.3 !




Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/27/2004 12:33 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: AIX backup failures - InsertSlashHack! and "System ran out of
memory"
messages






...
>ANS1225E Insufficient memory for file compression/expansion
...
>ANS1030E System ran out of memory. Process ended.
...

Zoltan - See the ANS1030E summary in ADSM QuickFacts.

IBM's message title harks back to Charlie Chaplin and the 1986 IBM PC,
where physical memory was all there was.  The message should be
titled like "Process memory limit reached. Process ended."

  Richard Sims
**************************************************************************************************
This e-mail may contain identifiable health information that is subject to
protection
under state and federal law. This information is intended to be for the
use of the
individual named above. If you are not the intended recipient, be aware
that any
disclosure, copying, distribution or use of the contents of this
information is prohibited
and may be punishable by law. If you have received this electronic
transmission in
error, please notify us immediately by electronic mail (reply).
**************************************************************************************************