cancel
Showing results for 
Search instead for 
Did you mean: 

can't restore file on HP-UX 11.23

Apitha
Level 4
Partner Accredited Certified

 

I use NetBakcup Master Server (DataCenter) 6.5.6 on Windows 2003 R2 Standard Edition x86.

Media Server 6.5.6 on DB1 and backupdb (both: HP-UX 11.23)

DB1 and backupdb use HP Service Guard for Oracle to make oracle cluster together.

 

I config local host file on Windows to solve name on HP-UX and it can ping between (windows  <--> HP-UX) successfully.

 

I configure policy to backup files on HP-UX on DB1, it can backup successfully.

I Configure policy to backup files on HP-UX on backupdb, it can backup successfully.

 

When I try to restore files on HP-UX on DB1, it can't restore

I get log from restore

 

---------------------------------------------------------------------------------------------------------------------------

12:26:27 29/11/2553: Restore Started

12:26:28 (1530.xxx) Restore job id 1530 will require 1 image.
12:26:28 (1530.xxx) Media id 000008 is needed for the restore.

12:26:34 (1530.001) Restoring from image created 29/11/2553 12:12:24
12:26:40 (1530.001) INF - If Media id 000008 is not in a robotic library administrative interaction may be required to satisfy this mount request.
12:26:44 (1530.001) INF - Waiting for mount of media id 000008 on server backupdb for reading.
12:27:02 (1530.001) INF - TAR STARTED
12:27:25 (1530.001) INF - Waiting for positioning of media id 000008 on server backupdb for reading.
12:27:34 (1530.001) INF - Beginning restore from server backupdb to client DB1.
12:27:36 (1530.001) TAR - testbackup:\
12:27:36 (1530.001) WRN - can't create directory: \\?\testbackup: (WIN32 2: Unknown error)
12:27:36 (1530.001) TAR - testbackup:\test1.txt
12:27:36 (1530.001) WRN - can't create file: testbackup:\test1.txt (WIN32 3: Unknown error)
12:27:36 (1530.001) TAR - testbackup:\test2.txt
12:27:36 (1530.001) WRN - can't create file: testbackup:\test2.txt (WIN32 3: Unknown error)

12:27:36 (1530.001) INF - TAR EXITING WITH STATUS = 0
12:27:36 (1530.001) INF - TAR RESTORED 0 OF 3 FILES SUCCESSFULLY
12:27:36 (1530.001) INF - TAR KEPT 0 EXISTING FILES
12:27:36 (1530.001) INF - TAR PARTIALLY RESTORED 0 FILES
12:27:38 (1530.001) Status of restore from image created 29/11/2553 12:12:24 = the restore failed to recover the requested files

12:27:38 (1530.xxx) INF - Status = the restore failed to recover the requested files.

----------------------------------------------------------------------------------------------------------------------------

 

I try to restore on backupdb, it can restore successfully.

I try to use IP address to restore instead name on DB1, it can restore successfully.

 

From restore log, I doubt windows can't solve name DB1, but it can backup by use DB1.

 

From Host Properties > Client, I can connected on DB1.

 

Please help.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

The problem does not seem to be with connectivity but with the path that you're trying to restore:

WRN - can't create directory: \\?\testbackup: (WIN32 2: Unknown error)

This looks like it's trying to create a Windows path, even resulting in a "Win32" error.

Please ensure that you have bprd log directory on the master (if not, please create it and restart NBU then retry the restore).

Please post the log as an attachment.

Also ensure that you have the following log directories:

On media server: bptm and bpbrm

On client: bpcd and tar

I'm pretty confident that bprd log will help to find the problem, but ensure you have all the other logs in case we need more logs.

I have a suspision that the Master is trying to restore the files to itself.

Look for entries like this in bprd:

... <2> restorefiles:    browse_client =
... <2> restorefiles:    requesting_client =
... <2> restorefiles:    destination_client =
... <2> restorefiles:    requesting_client_hostname =
... <2> restorefiles:    destination_client_hostname =

 

If you see that "requesting_client" is the master server name but "requesting_client_hostname" is that of the client, it means that the master's 'Configured' client name was changed to that of the client. That is a sure way of doing a redirected restore to the master.

View solution in original post

1 REPLY 1

Marianne
Level 6
Partner    VIP    Accredited Certified

The problem does not seem to be with connectivity but with the path that you're trying to restore:

WRN - can't create directory: \\?\testbackup: (WIN32 2: Unknown error)

This looks like it's trying to create a Windows path, even resulting in a "Win32" error.

Please ensure that you have bprd log directory on the master (if not, please create it and restart NBU then retry the restore).

Please post the log as an attachment.

Also ensure that you have the following log directories:

On media server: bptm and bpbrm

On client: bpcd and tar

I'm pretty confident that bprd log will help to find the problem, but ensure you have all the other logs in case we need more logs.

I have a suspision that the Master is trying to restore the files to itself.

Look for entries like this in bprd:

... <2> restorefiles:    browse_client =
... <2> restorefiles:    requesting_client =
... <2> restorefiles:    destination_client =
... <2> restorefiles:    requesting_client_hostname =
... <2> restorefiles:    destination_client_hostname =

 

If you see that "requesting_client" is the master server name but "requesting_client_hostname" is that of the client, it means that the master's 'Configured' client name was changed to that of the client. That is a sure way of doing a redirected restore to the master.