ANR9999D when doing a DB Backup

Bekar

ADSM.ORG Member
Joined
Sep 12, 2008
Messages
21
Reaction score
0
Points
0
Hi,

I've got two TSM 5.5.1.1 servers, and in one direction can do network-based database backups, but when trying to do the same in reverse, I get a 9999.

Command issued:

Code:
TSM>BACKUP DB TYPE=FULL DEVCLASS=STK_TIVOLI WAIT=YES

It fails immediately, and here is the log from the console:

Code:
ANR2017I Administrator SYSADMIN issued command: BACKUP DB type=full devclass=stk_tivoli wait=yes
ANR0984I Process 264 for DATABASE BACKUP started in the FOREGROUND at 01:51:54 PM.
ANR2280I Full database backup started as process 264.
ANR9999D_0182861484 Authenticate(smserv.c:5833) Thread<169409>: Authentication failed - insufficient memory.
ANR9999D Thread<169409> issued message 9999 from:
ANR9999D Thread<169409>  0x0000000000b81892 OutDiagToCons+0x0x142
ANR9999D Thread<169409>  0x0000000000b84359 outDiagfExt+0x0x159
ANR9999D Thread<169409>  0x00000000009e8bdc SignOnToServer+0x0xdec
ANR9999D Thread<169409>  0x00000000009ea79d StartConversation+0x0x7d
ANR9999D Thread<169409>  0x00000000009f1e47 smServOpenVolume+0x0x127
ANR9999D Thread<169409>  0x000000000094f67d ServOpen+0x0x3bd
ANR9999D Thread<169409>  0x00000000008b6e35 AgentThread+0x0xcf5
ANR9999D Thread<169409>  0x0000000000beab96 StartThread+0x0x76
ANR9999D Thread<169409>  0x0000003a1de062f7 *UNKNOWN*
ANR9999D Thread<169409>  0x0000003a1d6d1e3d *UNKNOWN*
ANR4373E Session rejected by target server AUSREGSRV1, reason: Authentication Failure.
ANR1404W Scratch volume mount request denied - mount failed.
ANR4578E Database backup/restore terminated - required volume was not mounted.
ANR0985I Process 264 for DATABASE BACKUP running in the FOREGROUND completed with completion state FAILURE at 01:51:55 PM.

Running with the simple 'Authentication Failure' error, I updated the password on both ends (REMOTE: UPDATE NODE, LOCAL:UPDATE SERVER), and tried the command again, same error (with only the thread number changing).

Now, has anybody else seen this message before and had it resolved, or do I have to go poke IBM with this one?
 
How far apart are these two TSM Servers? LAN or WAN distance? Does both TSM Servers have tape libraries or tape drives attached locally?
 
10MBit WAN, both with tape libraries attached, but going to FILE based storage pools.

The bigger issue is using a COPY storage pool over the link. I see doing a BACKUP DB as a simple form of the same access issues.
 
I believe it is a password problem.

I would perform the following on all TSM servers from the command line

  1. set crossdefine on
  2. reset the virtual volume password and corresponding node name password
  3. update admin admin <password>
  4. set serverpassword <serverpassword>
  5. update server <servername> serverpassw=<serverpassword> forcesync=yes
  6. then check server-to-servercommunication using
    - ping server servername
    - <servername>: q stat
Hope this helps.
Regards. Wim.
 
Back
Top