Hello Michael,
On what type of media does the backup data reside? Does this restore issue
occur when the data is on:
* Disk (random access, device class DISK)
* Disk (sequential, device class FILE)
* Tape (a tape device class)
* Next generation storage pool
What type (operating system, e.g., Win
And another question:
I think the message is on the client, ANS4035W (not ANR4035W)? When the
problem occurs, are there any messages displayed in the server activity log
that would seem to correspond with this issue?
Andy
__
The TSM 6.3 reorganization server option default values are appropriate
most (but not all) of the time. In this environment the default values are
not optimal and you should continue to use the current values for the
reorganization server options.
Thank you,
Del
-
Agreed Neil !
-Rick Adamson
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Schofield, Neil (Storage & Middleware, Backup & Restore)
Sent: Tuesday, April 26, 2016 12:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Reg: tsm ba client autod
Hello Andrew,
yes, you are correct ANS4035W ist the correct message.
As of your suggestions, we did some backups and restores and found out that
this error only appears if the object resides on tape. It doesn't matter if
tape is primary, copy or nextstoragepool.
This error appears on Windows, L
Hello,
Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4 on
her servers. Many of them started receiving errors like
calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092
I looked this up and the indication is that the AIX server could not supply
enough memory to
Good morning Pam,
We encountered errors backing up filesystems with large numbers of files
until we set the root user ulimits to unlimited. That fixed the problem
but can have other consequences, obviously. Do you know if your AIX admin
tried changing the ulimits?
Regards,
_
Hi Matthew,
Yes, the root user ulimits is set to unlimited on all the AIX servers.
Regards,
Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177
From: ADSM: Dist Stor Manager [
Hi Michael,
I am looking further into this, but have you tried the latest 6.1 client
level? I tested 6.1.0.0, and I get the same error you do (backing up to LTO
tape). I tried the restore with 6.1.5.0 and it was successful.
server: 7.1.4 on AIX
client: 6.1.0.0 on Windows 7 (backup and first resto
This isn't really helpful for your specific situation, Pam (I don't think
I've had the specific errors you've seen). But I have noticed (with much
dismay) that the 7.x clients for AIX have required significantly more memory
than earlier versions. I have clients with 1+ million files in a filesyst
Hi Dave,
Thank you for the information. I, of course, could not get the person assigned
to my ticket to even acknowledge that this might be due to some different
memory requirements for the newer TSM clients. The only response I received was
that we just must not have enough memory on our syste
All this talk about server upgrade woes has me concerned, especially since
I am heading to 7.1.5 with my 6.3.5 servers. Being a university, we have
quite a few boxes that can't/wont upgrade (Solaris 5.8 running 5.3.6.6
client, old linux/2.4 kernel running 5.5 client, Solaris boxes running
Notes/
Hi Pam,
Do any of the file systems happen to have directories that contain large
numbers of files (say, more than a million)? You could try running this
SELECT statement from an administrative command line client to assess this.
Make sure to the node name RAIBECK with your node name (in all upper
Follow-up:
Can you put the QUIET option in the client options file, then try the
restore again? This is without upgrading the client software.
Let me know if this enables a successful restore from tape.
Best regards,
Andy
Andy,
Here is the top few entries from the select statement. From what I can tell,
none of the filesystems have more than 200K objects on this client.
FILESPACE_NAME: /gridfs
HL_NAME: /oraem/Oracle/admin/emrep/adump/
TOTAL_OBJECTS: 15551
FILESPACE_NAME: /gridfs
HL_NAME:
/oraem/
Hi Pam,
During incremental backup, the peak memory utilization usually occurs when
the client is processing the directory with the largest number of files. In
this case, unless your machine has only 8 MB of RAM ;-) I do not see how
~15K objects could cause memory to be exhausted. It doesn't pass t
Hi,
It should be fine to run the parallel backup on different databases
that are not on the same LUN/volumes.
For your problem, RC 418 means TSM API error, please check
dsmerror.log under baclient directory to see if there is any error
messages. Also you can contact support for hel
17 matches
Mail list logo
