Backup works fine , Network restores fail.

[Bob_Richardson]

When ever I try and restore over the network I get this error.

Completed status: Failed
Final error: 0xa00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agent.

All backups run normally every night but the restore only works locally then the files have to be moved.

Any suggestions to troubleshoot this issue?

[Bob_Richardson]

Bump

[Gauri_Ketkar]

Hi,

-Please explain the Environment
-Refer the technote given below >

Common Job Log Error Codes (with Error Description) in Backup Exec 9.x
http://support.veritas.com/docs/256057

Update us on the same and revert for any further Query
Hope this will help you


Thank you
Gauri


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Bob_Richardson]

Media Server

Windows Server 2003
Standard Edition
Service Pack 1

Backup Exec 9.1

Remote Servers are
Windows Server 2000
Service Pack 4

Like I mentioned the Backup Jobs run fine, the problem is running a restore of data anywhere on the network gives the aforementioned error. Those tech notes refer to failed backup jobs. This problem is failed data restore.

[Ajit_Kulkarni]

Hello,

Please refer to the below mentioned technote :

When backing up or restoring local or remote media servers with Backup Exec for Windows Servers, the job fails with "A communications failure has occurred between the Backup Exec job engine and the remote agent."
http://support.veritas.com/docs/263776

Hope this helps you.

Regards


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Bob_Richardson]

Well that didn't work and my log looks nothing like the technote you gave me.

Here is what I see in the remote agent log file.

204 2/2/2006 13:17:33: Successfully impersonated XXXXXXXX\XXXXXX
204 2/2/2006 13:17:33: WhoAmI( ) reports: XXXXXXXX\XXXXXX
204 2/2/2006 13:17:35: ERROR: ndmpdDataStop: invalid state to process stop request.

First question.
Why do I have to go into the properties and select redirect credentials?

Send question.
What does 204 2/2/2006 13:17:35: ERROR: ndmpdDataStop: invalid state to process stop request, mean?

Here is my Backup Server log.

1270 2/2/2006 13:17:50: Job::Mount: media mounted
1270 2/2/2006 13:17:50: Media Label: Tuesday's Tape
1270 2/2/2006 13:17:50: Media GUID: {24D56D21-8D68-4E64-B516-25F84E9CA0FC}
1270 2/2/2006 13:17:50: Overwrite Protected Until: 2/20/2006 8:23:30 AM
1270 2/2/2006 13:17:50: Appendable Until: 12/31/9999 12:00:00 AM
1270 2/2/2006 13:17:50: Block size: 65536
1270 2/2/2006 13:17:50: Buffer size: 65536
1270 2/2/2006 13:17:50: Num buffers: 10
1270 2/2/2006 13:17:50: High water: 0
1270 2/2/2006 13:17:51: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1270 2/2/2006 13:17:51: TAPEALERT: TapeAlert Device Flag = 0X0
1270 2/2/2006 13:17:51: TAPEALERT: TapeAlert Changer Flag = 0X0
1270 2/2/2006 13:17:51: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1270 2/2/2006 13:17:51: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1270 2/2/2006 13:17:52: Informational: Subnet Address 10.0.101.0 specified
1270 2/2/2006 13:17:52: Informational: Subnet Mask 255.255.255.0 input
1270 2/2/2006 13:17:52: Informational: Local network address 10.0.101.104 returned
1270 2/2/2006 13:17:52: Informational: Local network address 10.0.101.104 obtained in the subnet specified
1270 2/2/2006 13:17:52: NDMP version 3 connection CONNECTED
1270 2/2/2006 13:17:52: TF_OpenTape()
1270 2/2/2006 13:17:52: TF_GetDriveContext ...
sessionId = \\BILBO\SESSION\{1E2E526C-0561-46E5-B539-30BF66E8703F}
initAsync = 1
1270 2/2/2006 13:17:52: HARDWARE COMPRESSION ===> Compression is configurable.
1270 2/2/2006 13:17:52: GET_DRV_INF: bsize = 65536
1270 2/2/2006 13:17:52: HARDWARE COMPRESSION ===> Setting compression off.
1270 2/2/2006 13:17:52: TF_GetDriveContext returning 0, context = 1D2D8B0
1270 2/2/2006 13:17:52: Allocated 2 buffers, size 65536 bytes, total used: 131256
1270 2/2/2006 13:17:52: HARDWARE COMPRESSION ===> Compression is configurable.
1270 2/2/2006 13:17:52: GET_DRV_INF: bsize = 65536
1270 2/2/2006 13:17:52: NDMPEngine::Run(): calling ProcessBSD()
1270 2/2/2006 13:17:52: TF_OpenSet( )
1270 2/2/2006 13:17:52: FreeFormatEnv( cur_fmt=65535 )
1270 2/2/2006 13:17:52: RewindDrive mover ret = 0 (0x0)
1270 2/2/2006 13:17:52: ret_val = 0
1270 2/2/2006 13:17:52: Requested Set: ID = 338db823 Seq = 1 Set = 172
1270 2/2/2006 13:17:52: Attempting to VCB storage media
1270 2/2/2006 13:17:52: TpRead( :(
1270 2/2/2006 13:17:52: Error = 0 Req = 65536 Got = 65536
1270 2/2/2006 13:17:52: HARDWARE COMPRESSION ===> Compression is configurable.
1270 2/2/2006 13:17:52: GET_DRV_INF: bsize = 65536
1270 2/2/2006 13:17:52: FreeFormatEnv( cur_fmt=65535 )
1270 2/2/2006 13:17:52: SetupFormatEnv( fmt=0 )
1270 2/2/2006 13:17:52: TpRead( :(
1270 2/2/2006 13:17:52: Error = 0 Req = 65536 Got = 65536
1270 2/2/2006 13:17:52: ReadThisSet( cur_fmt=0 )
1270 2/2/2006 13:17:52: ReadThisSet() return=0
1270 2/2/2006 13:17:52: Current VCB: ID = 338db823 Seq = 1 Set = 1
1270 2/2/2006 13:17:52: End of TF_OpenSet: Ret_val = 0 Buffs = 2 HiWater = 7
1270 2/2/2006 13:17:53: Informational: Subnet Address 10.0.101.0 specified
1270 2/2/2006 13:17:53: Informational: Subnet Mask 255.255.255.0 input
1270 2/2/2006 13:17:53: Informational: Local network address 10.0.101.104 returned
1270 2/2/2006 13:17:53: Informational: Local network address 10.0.101.104 obtained in the subnet specified
1270 2/2/2006 13:17:53: OpenListenSocketSpNic: Specific address sent: 6865000a
1270 2/2/2006 13:17:53: OpenListenSocket: Media server IP address: 0
1270 2/2/2006 13:17:53: OpenListenSocket: Media server port: 1a04
1270 2/2/2006 13:17:54: ERROR: Error: Cannot connect / not connected
1270 2/2/2006 13:17:54: TF_InitMediaServerConnection: dataConnect failed with error code : 23
1270 2/2/2006 13:17:54: ERROR: Error: Invalid state to process request
1270 2/2/2006 13:17:54: TF_CloseSet
1270 2/2/2006 13:17:54: - Read Buffer Left Over
1270 2/2/2006 13:17:54: NDMPEngine::Run(): ProcessBSD() returned 0
1270 2/2/2006 13:17:54: RewindDrive mover ret = 0 (0x0)
1270 2/2/2006 13:17:54: ret_val = 0
1270 2/2/2006 13:17:54: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1270 2/2/2006 13:17:54: TAPEALERT: TapeAlert Device Flag = 0X0
1270 2/2/2006 13:17:54: TAPEALERT: TapeAlert Changer Flag = 0X0
1270 2/2/2006 13:17:54: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
d00 2/2/2006 13:17:54: DeviceManager: incoming event fired
d00 2/2/2006 13:17:54: DeviceManager: processing pending requests
d00 2/2/2006 13:17:54: DeviceManager: going to sleep for 61000 msecs
1270 2/2/2006 13:17:54: Job thread terminating
d00 2/2/2006 13:18:55: DeviceManager: timeout event fired
d00 2/2/2006 13:18:55: DeviceManager: processing pending requests
d00 2/2/2006 13:18:55: Tossing drive:
d00 2/2/2006 13:18:55: DELL 2 {1e1f0554-102d-439a-809a-e8047694c8e5}
d00 2/2/2006 13:18:55: TF_FreeDriveContext( 1D2D8B0 )
d00 2/2/2006 13:18:55: TF_FreeTapeBuffers: from 2 to 1 buffers
d00 2/2/2006 13:18:55: FreeFormatEnv( cur_fmt=0 )
d00 2/2/2006 13:19:35: DeviceManager: going to sleep for 900000 msecs
d00 2/2/2006 13:19:35: DeviceManager: dismount event fired
d00 2/2/2006 13:19:35: DeviceManager: processing pending requests
d00 2/2/2006 13:19:35: DeviceManager: going to sleep for 900000 msecs

Hear from you in 5 days.

[Renuka_-]

Hello,

- Please add the fqdn for both servers in the host file on the opp server.

- Check the option to check the consistency of the backups in the backup job.

- Try another network card if possible during restore.

- If the data from the remote server is restored to a folder on the local server is it successful?

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Bob_Richardson]

I have added the servers to the host file already.

I began the post stating that the remote files will back up to the local host. The files will not backup to the remote location.

This issue has not been resolved.

Can you send this to a level 2 technician?

[Bob_Richardson]

After changes to some of the options here are the new errors.

Final error: 0xa000fe29 - Authentication failed on connection to the server.


As well as the Device Server log.

14dc 2/7/2006 15:09:39: JobEngine::LaunchJob
14dc 2/7/2006 15:09:39: RunJobWithGuidAndServer( {04DA4243-647E-411A-AC2E-B9A6DCE424DC}, ) = 0
1374 2/7/2006 15:09:39: Thread for job Restore 0056 ({04DA4243-647E-411A-AC2E-B9A6DCE424DC}) starting
1374 2/7/2006 15:09:39: SQL2_FindDrives - the default SQL Service is not running on BILBO.
1374 2/7/2006 15:09:39: SQL2_FindDrives - checking named instance BKUPEXEC.
1374 2/7/2006 15:09:39: SQL2_FindDrives - Sorry, SQL 2000 Agent not autherized.
1374 2/7/2006 15:09:39: Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
1374 2/7/2006 15:09:39: No utility partitions found on any of the disks
1374 2/7/2006 15:09:39: ENGSCRPT: ConvertDeviceName osId = 0Xe
1374 2/7/2006 15:09:39: ENGSCRPT: IN - oldDeviceName = \\172.16.32.3\E:
1374 2/7/2006 15:09:39: ENGSCRPT: OUT - newName = \\172.16.32.3\E:
d00 2/7/2006 15:09:39: DeviceManager: incoming event fired
d00 2/7/2006 15:09:39: DeviceManager: processing pending requests
d00 2/7/2006 15:09:39: DeviceManager: query cache miss
d00 2/7/2006 15:09:39: DeviceManager: query result = 0x00000000
d00 2/7/2006 15:09:39: Available and held drives from the pool
d00 2/7/2006 15:09:39: DELL 2 {1e1f0554-102d-439a-809a-e8047694c8e5}
d00 2/7/2006 15:09:39: Drives not in use by the Engine
d00 2/7/2006 15:09:39: DELL 2 {1e1f0554-102d-439a-809a-e8047694c8e5}
d00 2/7/2006 15:09:39: Drives available (not in use and not held)
d00 2/7/2006 15:09:39: DELL 2 {1e1f0554-102d-439a-809a-e8047694c8e5}
d00 2/7/2006 15:09:39: Handing out drive:
d00 2/7/2006 15:09:39: DELL 2 {1e1f0554-102d-439a-809a-e8047694c8e5}
d00 2/7/2006 15:09:39: DeviceManager: going to sleep for 900000 msecs
1374 2/7/2006 15:09:39: Job::Mount: acquired device
1374 2/7/2006 15:09:39: Job::Mount: mounting tape
1374 2/7/2006 15:10:30: Job::Mount: media mounted
1374 2/7/2006 15:10:30: Media Label: Monday's Tape
1374 2/7/2006 15:10:30: Media GUID: {23685C04-D1FF-4BC1-87FD-9654046C80E6}
1374 2/7/2006 15:10:30: Overwrite Protected Until: 2/26/2006 6:39:46 AM
1374 2/7/2006 15:10:30: Appendable Until: 12/31/9999 12:00:00 AM
1374 2/7/2006 15:10:30: Block size: 65536
1374 2/7/2006 15:10:30: Buffer size: 65536
1374 2/7/2006 15:10:30: Num buffers: 10
1374 2/7/2006 15:10:30: High water: 0
1374 2/7/2006 15:10:30: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1374 2/7/2006 15:10:30: TAPEALERT: TapeAlert Device Flag = 0X0
1374 2/7/2006 15:10:30: TAPEALERT: TapeAlert Changer Flag = 0X0
1374 2/7/2006 15:10:30: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1374 2/7/2006 15:10:30: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1374 2/7/2006 15:10:31: Informational: Subnet Address 10.0.101.0 specified
1374 2/7/2006 15:10:31: Informational: Subnet Mask 255.255.255.0 input
1374 2/7/2006 15:10:31: Informational: Local network address 10.0.101.104 returned
1374 2/7/2006 15:10:31: Informational: Local network address 10.0.101.104 obtained in the subnet specified
1374 2/7/2006 15:10:31: NDMP version 3 connection CONNECTED
1374 2/7/2006 15:10:32: ERROR: Error: Connection has not been authorized
1374 2/7/2006 15:10:32: ERROR: Error: Connection has not been authorized
1374 2/7/2006 15:10:32: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
1374 2/7/2006 15:10:32: TAPEALERT: TapeAlert Device Flag = 0X0
1374 2/7/2006 15:10:32: TAPEALERT: TapeAlert Changer Flag = 0X0
1374 2/7/2006 15:10:32: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
d00 2/7/2006 15:11:07: DeviceManager: dismount event fired
d00 2/7/2006 15:11:07: DeviceManager: processing pending requests
d00 2/7/2006 15:11:07: DeviceManager: going to sleep for 900000 msecs
1374 2/7/2006 15:11:07: Job thread terminating

[shweta_rege]

Hello,


This problem may occur due to insufficient access rights to the account, used for connecting to the target system . This account should have administrative privileges. You may refer following steps for configuring backup of remote machines:

1) Create a new user on the remote machine. Make newly created user a member of local Administrator group only.

2) Start Backup Exec, create a Logon account with same username and password as that of newly created user. You may refer to following:

-Start Backup Exec
-Select Tools > Wizards > Logon account wizard
-Add new logon account, type in the credential for the new account.
-Make this account a common logon account.
-Complete the wizard.

3) Create new backup job by selecting remote machine and select this newly created account from window.

If while selecting the remote machine, it does not prompt for the credentials then after selecting the remote machine | select "resource credentials" | select existing logon account | click change and select the newly created logon account

For more information you can refer the following tech note:
How to change the designated logon account for a selected resource

http://seer.support.veritas.com/docs/250649.htm


******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.


Thanks.

[Bob_Richardson]

Hello,

I can run backups with no problems at all. No need to config login credentials.

What needs to be configed so that the Back up Exec 9.1 uses the same login credentials to restore as it does when doing a backup?

Why not ask to view my log then tell me where the problems is by explaining the section of the log that is showing the conflict?

Lets get me someone with some answers to my questions instead of more questions.

Still looking for some support. Might want to pass this along to a higher level technician instead of reading from the tech note sheets.

[Bob_Richardson]

2 weeks still no reply?

Bump

[Shilpa_pawar_2]

Hi,

Please verify if the system logon account is present under Network> Logon accounts. If not please create it. If it is already present, please delete and re-create the System Logon Account. The following Tech Note's explain how to do this:

http://support.veritas.com/docs/257256

http://seer.support.veritas.com/docs/274012.htm

Also refer: http://support.veritas.com/docs/273528

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.