tlbrittain
asked on
Veritas 9.1 Backup Exec failed jobs
I am new to veritas and recently had the pleasure of migrating our Veritas backup Exec 9.1 server (2000) from a legacy domain to our current domain. There was a trust between the domains and the Veritas server was backing up data on both domains. The backups are run through 2 Dell Powervault 132T tape libraries after the migration the jobs started to fail. All of them. The error that we receive is listed below:
Job ended: Monday, July 02, 2007 at 11:17:34 AM
Completed status: Failed
Final error: 0x574 - Logon Failure: The target account name is incorrect.
Final error category: Other Errors
Of course the first thing that this leads me to believe is the service account that this may be using had its credentials mixed up...this was not the case. This error also references the IDR, see below:
Backup - \\<SERVERNAME>\System?Stat
to alternate data path \\<SERVERNAME>\ncc\Veritas
Error: 1396
Logon Failure: The target account name is incorrect.
I gave the account rights to the folder that the error calls as well as the files inside...I am out of ideas for the moment and hope that someone can shed some light. I do not have a support agreement with Symantec so contacting them is out. I hope that I can find the answer on my own, but at this point it does not look like it...I appreciate your help
Thomas
I forgot to mention that upon attempting a restore it states "loading Media" and then remains in this state for an excessive period of time.
Job ended: Monday, July 02, 2007 at 11:17:34 AM
Completed status: Failed
Final error: 0x574 - Logon Failure: The target account name is incorrect.
Final error category: Other Errors
Of course the first thing that this leads me to believe is the service account that this may be using had its credentials mixed up...this was not the case. This error also references the IDR, see below:
Backup - \\<SERVERNAME>\System?Stat
to alternate data path \\<SERVERNAME>\ncc\Veritas
Error: 1396
Logon Failure: The target account name is incorrect.
I gave the account rights to the folder that the error calls as well as the files inside...I am out of ideas for the moment and hope that someone can shed some light. I do not have a support agreement with Symantec so contacting them is out. I hope that I can find the answer on my own, but at this point it does not look like it...I appreciate your help
Thomas
I forgot to mention that upon attempting a restore it states "loading Media" and then remains in this state for an excessive period of time.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was using a legacy domain account, but the trust is still in place and the server I am running all of my tests on is still in the legacy domain. I have changed the service account to the domain the server sits in now. My problem is the fact that the backup runs in its entirety up until it gets to the IDR file, and that is where it errs out.
Did you check the rights not only on the NTFS level, but on the Sharing level as well?
ASKER
I took care of that as well. After changing the service accts I was able to get the backup to run on the Veritas server itself and it was able to write the IDR file. I am now checking one of the jobs that runs in the legacy domain to see if with the new credentials it will run as well. So far so good, we will see if it can write the IDR file as well.
ASKER
It's always the simple things you don't check...this should have been caught when the server was migrated over. Thanks
ASKER