LogonUser failed

[KDR]

I'm trying to restore an old backup to a Linux system. When I go through the Restore Wizard and test the account it says it was successful but when the restore runs it fails with an authentications error. When I look at the beremote log file on the Linux system, I see the following.

428db90 Mon Jan 24 14:01:13 2011 : Control connection accepted : connection established between end-points 1.2.3.4:10000 and 1.2.3.5:2502
7054b90 Mon Jan 24 14:01:13 2011 : LogonUser failed for user:  because LogonUser: Password is Null for user
7054b90 Mon Jan 24 14:01:13 2011 : LogonUser failed for user:
7054b90 Mon Jan 24 14:01:13 2011 : LogonUser failed for user:  because LogonUser: Password is Null for user
7054b90 Mon Jan 24 14:01:13 2011 : LogonUser failed for user:
 

I tried a new backup and restore and it works correctly. So, it would appear to be something related to the old backup but logging in doesn't seem like it should have anything to do with that.

Any ideas?

[itsmeaffinity]

Hi

Seems intersting & but strange issue can you please click on link below to give me more verbose logging for beremote on linux & also run sgmon at same time on media server so that we can check what is going on from both side

http://www.symantec.com/docs/TECH35477

Also please let me know what is version of backupexec like BE 12.0 or 12.5 with what updates like sp4 or sp5 & what is version of linux like RHEL 4.0 or 4.1 or SUSE

Thank You

[KDR]

We're running BE 12.5 rev 2213 on both. The OS on the media server is Windows Server 2003 SP2 Standard Edition. The OS on the Linux server is RHEL 5.3.

[itsmeaffinity]

Hi

Thanks for your response on same & I will wait for your further update to get the log that is sgmon from media server & beremote log from linux machine as per link

Keep posted

Thank You

[pkh]

BE 12.5 does not support RHEL 5.3, only 5.2.  Check the SCL below.

http://www.symantec.com/business/support/index?page=content&id=TECH62301&actp=search&viewlocale=en_U...

You got to upgrade to BE 2010.

[KDR]

beremote log file with debug level set to 2

[KDR]

sgmon log file with logging set to verbose from the same restore job as the previous beremote log file.

[itsmeaffinity]

Hi

I will check & see if I find anything & as also rightly said by pkh upgrade backup exec to 2010 r2 sp1 & then update remote client to check see if that work as last chance I will see in mean while if I find anything on same

Again thanks for all your responses & will update you soon

Cheers

Thank You

[itsmeaffinity]

Hi,

Here is the error in sgmon I found

Can you please try deleting the root account by going to network log on account & verify all entries for root are removed & then try recreating the root account again

Then restart remote agent service on linux server & also restart all backupexec services & then check to see if that works

FYI

BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_process_messages: reply_expected:TRUE
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_recv_msg
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_readit: len:4000
BENGINE:  [01/24/11 20:55:05] [4936]     got expected reply     msg: 0x901
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_process_messages: no more messages in stream buffer
BENGINE:  [01/24/11 20:55:05] [4936]     ERROR: 4 Error: Connection has not been authorized
BENGINE:  [01/24/11 20:55:05] [4936]     ndmpFreeMessage: message:0x901
BENGINE:  [01/24/11 20:55:05] [4936]     ndmpSendRequest: message:0x103
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_writeit: len:32
BENGINE:  [01/24/11 20:55:05] [4936]     sent          seq#: 6 msg: 0x103
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_process_messages: reply_expected:TRUE
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_recv_msg
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_readit: len:4000
BENGINE:  [01/24/11 20:55:05] [4936]     got expected reply     msg: 0x103
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_process_messages: no more messages in stream buffer
BENGINE:  [01/24/11 20:55:05] [4936]     ndmpFreeMessage: message:0x103
BENGINE:  [01/24/11 20:55:05] [4936]     ndmpSendRequest: message:0xf33b
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_writeit: len:32
BENGINE:  [01/24/11 20:55:05] [4936]     sent          seq#: 7 msg: 0xf33b
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_process_messages: reply_expected:TRUE
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_recv_msg
BENGINE:  [01/24/11 20:55:05] [4936]     ndmp_readit: len:4000
BENGINE:  [01/24/11 20:55:05] [0216]     Updating status for: 'Restore 00098' (0x0 0x0)
BENGINE:  [01/24/11 20:55:05] [0216]     Status for: 'Restore 00098' updated

Thank You

[pkh]

@KDR - Even if you get it working, i.e. BE 12.5 and RHEL 5.3, you would be running an unsupported configuration which means that you would not be able to open a support case with Symantec.  Also, there is no guarantee that you would not run into problems when you try to restore your server.

[itsmeaffinity]

Hi

Any updates here

Thank You

[KDR]

I deleted the root logon account in BE then restarted all BE services on both servers. I then went through the restore wizard, creating and testing a new root logon account. Unfortunately, the restore job failed with the same error.

[KDR]

I opened a case with Symantec support Monday night. I got an e-mail from them last night. Hopefully, I'll hear back from them this morning (when I told them I'd be available).

[itsmeaffinity]

Hi

Thanks for update on same as you have open a case with symantec see what happen about this particular thread you can mark this solved as we have done few steps which has not resolved has intially said it is not supported configuration you have for this as per by my above post

Please mark this solved

Thank You

[KDR · Accepted solution]

I just got off the phone with Symantec support. When I created the restore jobs, I went through the Restore Wizard or selected Retry Job Now option from the Job History display. However, if I went to the Job Setup tab, right-clicked on one of the restore jobs and selected Properties, then selected Resource Credentials, there was nothing there. So, I set and tested the credentials and clicked Submit and the job ran successfully. It looks like a bug in setting/saving the resource credentials in the Restore Wizard. Regardless, it's working now.