General discussion

Locked

Arcserve Problem

By joshg ·
I am having a problem at a client site, the backup fails to run nightly. The server is Netware 4.11, running ArcServe 6.10. Whenever a scheduled job runs to backup the server volumes it fails with error "E3123 FALIED TO LOGIN TO TSA... ffdffd7" Ihave looked this up with Computer Associates and have tried there fix which was that the TSA directory did not exist, I deleted this dir and recreated. I have rebooted the server several times, the admin account is allowed to login multiple times (no restrictions)still no resolution. Would like to know if anyone has experienced this or can help.

This conversation is currently closed to new comments.

19 total posts (Page 2 of 2)   Prev   01 | 02
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Arcserve Problem

by miller6010 In reply to Arcserve Problem

I have seen a couple of problems regarding backing up remote servers with Arcserve that might help.
1. The TSA nlm's TSA410.nlm and TSANDS.nlm shold be the same version on both the backup server and remote server.
2. If SMDR.NLM does not load youcan get this
error. SMDR requires a specifix SAP type when backing up across segments. Check CA's website for the proper SAP number and verify it is not filtered out.

Collapse -

Arcserve Problem

by joshg In reply to Arcserve Problem

Poster rated this answer

Collapse -

Arcserve Problem

by cogtek In reply to Arcserve Problem

The TSA and TSANDS NLM's are the first place to look. If they are not loaded, not loading correctly or the wrong version, you will have these problems.
The second place to look is the actual Backup job you are running. You have to provide a Login account and password for each device to be backed up. Multiple volumes, multiples servers, Directory Services, all are considered different devices and must be verified seperately. Check the Job Queue tab in ArcServe Manager and you will notice that for each item you highlight in the Source tab, you must provide authentication.
The NDS authentication is often overlooked.
Try running a job that does not include the NDS and see if the error still occurs.

Collapse -

Arcserve Problem

by joshg In reply to Arcserve Problem

Poster rated this answer

Collapse -

Arcserve Problem

by jeff_hurst In reply to Arcserve Problem

It may be to easy.
the login for admin must be dinstinguished
CN=Admin.O=whatever

CA never states this anywhere and it caused me a problem with backups failing because of improper login.

Collapse -

Arcserve Problem

by joshg In reply to Arcserve Problem

Poster rated this answer

Collapse -

Arcserve Problem

by pdavis In reply to Arcserve Problem

I've also ran into this problem. It took a while, but we figured out that the password had changed for the user creating the job.

Collapse -

Arcserve Problem

by joshg In reply to Arcserve Problem

All of the jobs submitted were submitted by the Admin user, the admin users password got changed at some point and the jobs wouldn't run.

Collapse -

Arcserve Problem

by joshg In reply to Arcserve Problem

This question was closed by the author

Back to Networks Forum
19 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums