Hi John,

Below is the Mac client developer's response to your follow-on questions.

Regards,

Andy

John,
An administrator on Mac OS X is really just a normal user.  They do not
have real root authority, but can do root authority tasks by entering the
admin password when prompted.

The purpose of 'TSM Backup for Administrators' is to run the TSM Backup
GUI as a root process so TSM has full access to everything.

You can get the same authority for the command line interface by using the
'sudo' command.  For example:

sudo ./dsmc incr

Will run dsmc as root so you should not have access issues.

As for the issues with the disk upgrade, there is no way of knowing,
without more information, if the two are related.  If you encounter
problems similar to this, please contact IBM support for assistance.

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

Date:    Fri, 3 Jun 2005 11:10:10 -0600
From:    John Bremer <jbremer AT LANL DOT GOV>
Subject: Re: TSM Macintosh client "...out of memory"

Andy,

Thank you very much for this lead.  I checked the APAR and indeed running
as root fixes the out of memory condition (caused by inadequate access
privileges).  However, I don't think any of our Mac OS X users run as
root,
rather as administrators or general users.

A couple of months ago we saw a problem where the TSM backup for
Administrators could not read the Macintosh HD and perform a backup.  We
would see backup completion statistics like 31 objects inspected, 0
objects
backed up (on a system with 10's of thousands of user files).

When we first encountered this problem, the Mac client had recently
replaced their hard drive.  The backups from GUI always failed when
writing
to the "old" filespace (Macintosh HD), which happened to be the volume
name
of the new.  We tried re-naming the old Macintosh HD filespace, and the
GUI
for Administrators backup would then succeed when backing up to the new
TSM
filespace.

I confess I do not remember seeing any ANS1030E messages associated with
the above situation.

Do you know if there is any connection between the two?

So I have tried the same "fix" here in the "out of memory" condition, and
yes, the TSM Backup for Administrators backup succeeds in backing up to a
new filespace.  However, running as an administrator, ./dsmc incr fails
with "out of memory" after inspecting only a few objects.  These results
are confusing to me.

Thanks again for your response(s)

John