Restoration Error

[kakaluru]

Hi Team

Good Morning

I am trying to restore data from last 3 days but it's giving an error. Tapes are available. Plese look in to below and help me out of this.

7/23/2015 10:28:53 AM - positioning 0244L3 to file 2
7/23/2015 10:30:08 AM - positioned 0244L3; position time: 00:01:15
7/23/2015 10:31:00 AM - begin reading
7/23/2015 10:31:06 AM - Warning bpbrm(pid=3220) from client 10.174.0.12: WRN - can't create file: F:\Restore_Logs\ATM questions-RNB-0.1.doc (WIN32 3: Unknown error)
7/23/2015 10:31:07 AM - end reading; read time: 00:00:07
7/23/2015 10:31:07 AM - restored image 10.174.0.12_1437147538 - (the restore failed to recover the requested files(5)); restore time 00:03:06
7/23/2015 10:31:07 AM - Warning bprd(pid=1588) Restore must be resumed prior to first image expiration on 10/18/2015 9:08:58 PM
7/23/2015 10:31:07 AM - end Restore; elapsed time: 00:03:10
the restore failed to recover the requested files(5)

7/23/2015 10:50:53 AM - connected; connect time: 00:00:15
7/23/2015 10:52:03 AM - mounted; mount time: 00:01:25
7/23/2015 10:52:03 AM - positioning 0049L3 to file 1
7/23/2015 10:52:03 AM - positioned 0049L3; position time: 00:00:00
7/23/2015 10:52:18 AM - begin reading
7/23/2015 10:52:19 AM - Warning bpbrm(pid=3288) from client 10.174.0.12: WRN - can't create file: F:\Restore_Logs\080118 Resource Status Report.xls (WIN32 3: Unknown error)
7/23/2015 10:52:25 AM - restored image 10.174.0.12_1437368661 - (the restore failed to recover the requested files(5)); restore time 00:01:48
7/23/2015 10:52:25 AM - end Restore; elapsed time: 00:01:57
the restore failed to recover the requested files(5)

[sdo]

The warning re "restore must be resumed prior..." can be ignored for now.

The restore fails with a Win32 status code of '3' which is ERROR_PATH_NOT_FOUND.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

.

It would seem to me that the F: drive does not exist at the client.

To debug this further set client side logging to level 5, and create the log folders, i.e. run mklogdir.bat in the NetBackup Client install path \logs\mklogdir.bat

...then re-try the restore, and then check the log folder in the \logs\tar folder path.

[Marianne]

Are you restoring to the source client or to another client?

Have you checked that this path exists on the destination client?

 F:\Restore_Logs\

Does the NetBackup Client Service logon account have write access to the drive?

Any reason why you are restoring to an IP address and not to a client hostname?

[kakaluru]

Hi sdo/marianne

F:\Restore_Logs\ path is available on the server machine where i am restoring the file.

I logged in as admin account only.

No reasons, just i am restong on server.

But, when i tried to restore on the client machine it was successfull. Let me know the specific reasons for this ????

[kakaluru]

Hi sdo/marianne

F:\Restore_Logs\ path is available on the server machine where i am restoring the file.

I logged in as admin account only.

No reasons, just i am restong on server.

But, when i tried to restore on the client machine it was successfull. Let me know the specific reasons for this ????

[Marianne · Accepted solution]

When you restore from the master, then the logon account for NetBackup Client service is used to perform the restore.
If this account does not have write permission, the restore will fail.

If the restore is started from the client, then the permissions of the user performing the restore is used.

So, the user who performed the restore has the correct permissions and the account used for the Client Service probably does not have sufficient permissions.

For future troubleshooting, ensure all of these log folders exist before you start another restore:

On master: bprd (NBU must be restarted when this folder is created.)

On media server: bpbrm and bptm

On client: tar

bprd and tar logs are the ones I would first look at.

[kakaluru]

Just i have created both logs under respective places. I will give updates on this.
 

[kakaluru]

Hi

Logs attached one by one.

[kakaluru]

Hi
 

[Marianne]

Firstly all text in Details tab so that we can see what time and which PIDs to look for.

[Marianne]

Is the F-drive a Cifs share? I see the following in the tar log: WRN - unable to set short name on restore: \\10.174.0.12\d$\RES\SKI-Contacts.xls (err=0000007b) This says to me the NBU Client Service logon account (normally LocalSystem) does not have any write permissions on Network drives. As per my previous post : you need to check Client Service logon account and carefully look at the file permissions that you select in the last screen. Be sure that the Client Service account has the correct AD rights.

[kakaluru]

Thanks for the information.

But when i restored in server location its giving above error.

When restored in client locatin its working fine.

[Marianne]

I don't know how else to say this...

Which user name do you use to logon when you do the restore on the client?

When you logon to the client, the permissions for your user name is used.

When you restore from the server, the NBU Client Service account is used for the restore.

If you still do not understand what I am trying to say, please show your Windows Admin person this post and ask him/her to change the Service account to a domain user with write permission on the network share.

[kakaluru]

Thx for your information.