Failed to login to TSA Arcserve 9.0

Same tree, same NetWare version, different server?  

Is the backup happening on, say, a Windows server, using the push agent on NetWare?  See this TID: http://support.novell.com/cgi-bin/search/searchtid.cgi?10097606.htm

Or, is it a different tree (since you say "my own server") with a different set of credentials.

fffeffd7 is, simply stated, a login failure (as the error message states.)  Perhaps you need to override the backup user login in your restore to make sure the login happens with your server's Arcserve user.  Alternatively, use Admin in your restore job to log in.

If it's a different tree, different server, then you probably have different credentials (and may have a loss of trustee assignments on the restore, due to different NDS/eDirectory databases, but that wouldn't cause the login failure for the restore.)

is a Different Tree, Same Netware Version, Different Server
I also try with the admin account and receive the same error

wath could be the solution? you finall statement seems to describe the problem

Are you using the GUI management console, or are you trying the restore using the character-based utilities on the server?

I'm using the Arcserve GUI

I assume you accidentally accepted my question as answer, so I un-accepted it.

When you create the backup job, before you submit it, are you editing the authentication line to verify that you're using the appropriate login and context for the target server?

Are you making sure to uncheck "restore to original location" and specifying the server to which you're restoring?

I agree with ShineOn's assessment. The most likely cause is that the login credentials used by the backup job are not valid now. Override them with valid credentials.

If the server that was backed up resided in a different NDS tree, then you'll probably be able to restore the data, but Trustee assignments will be lost.

I'm using the admin user of the server ,,, and still have the error

What syntax are you using for the user ID?  ARCserve 9 liked to see .CN=admin.O=<yourorg> (with the leading dot) if I recall correctly.

If I remember right, if you don't specify the full user context, using absolute notation, it won't work.

the problem is that I'm able to make a backup and then a restore from the server... but still unable to restore the backup that was made in the other server...

But the problem isn't necessarily the backup, or the backup/restore process same-to-same, but the "special" restore *JOB* from the foreign tape.

Have you merged the other server's tape's catalog into the ARCserve database?  

After merging, you should be setting up a custom restore job, selecting only the files you want from the merged data session (not the whole tape) and choosing where on your server to put the data, by unselecting "restore to original location" and browsing to the server/volume/directory you want the stuff to land in.  

At the end of that restore job configuration process, after you hit the "run" button, you get a screen that has a line or 2 on it, specifying the source, the target, and the password for the target.  Are you hitting the "edit" button and setting the login and password for the restore session(s) in that screen?  When you do that, are you using absolute, typeful notation when specifying the user ID?

You could possibly try doing the restore without SMS, too.  You shouldn't need the TSA if you're not restoring trustee rights.

Look into that - there should be an option in one of the screens where you'd choose not to restore trustees (or something to that effect)... maybe the restore job will simply do a straight restore without trying to hit the TSA's.

I did everthing you guys said... same error...  I did the 'Restore Data Only' option ,, same error...

Any other suggestions... I also recreate the SMS and nothing... same error...    I have no problem restoring data that was backup from the current server... I only have the error when trying to restore the data that was backup in the other server..

Today I found that if I do the restore to 'Original Location'  it work... but If I use 'Alternate Location' in the same server it fails..

Odd.

Makes me think it's something on the options page.  I haven't used AS9 for a while now (using 11.1 now) so I can't bring up the tool and run a test restore to see what's all available as options, but there's gotta be something somewhere causing your grief.  You should be able to put the data wherever you want to...

I vote PAQ/refund...