cancel
Showing results for 
Search instead for 
Did you mean: 

bprestore issues

Intore
Level 4

Hi all, I have some problems with a restore from command line with "bprestore".

I state that I can't restore using the GUI because the original folder contains more than 200,000 files and after some hours, the GUI is waiting with the hourglass.

Unfortunatelly this post (https://vox.veritas.com/t5/NetBackup/bprestore-CLI-command/td-p/366234/) didn't help me despite having the same problem as me.

I have to restore to an alternate client and alternate location.

This the command I'm using from the master server:

bprestore -B -L C:\Temp\restore\log.txt -C source_client -D destination_client -s 01/01/2019 00:00:00 -e 01/31/2019 23:59:59 -R C:\Temp\restore\rename.txt -f C:\Temp\restore\filelist.txt

This is the rename file, located on the master server with a return at the end o the row:

change /E/SOURCE_PATH/ to /C/Temp/restore/

This is the file list, located on the master server:

E:\SOURCE_PATH\file_1
E:\SOURCE_PATH\file_2
E:\SOURCE_PATH\file_3
E:\SOURCE_PATH\file_4
E:\SOURCE_PATH\file_5

The log file also is located on the master server

The output of the command line is:

Invalid line length in line: ■E

EXIT STATUS 144: invalid command usage

and the job details on the Activity monitor are:

Aug 26, 2019 11:47:21 AM - begin Restore

Aug 26, 2019 11:47:23 AM - end Restore; elapsed time 0:00:02

Aug 26, 2019 11:47:23 AM - Error bprd (pid=12064) Access to /C/Temp/restore/log.txt denied: The provided path is not whitelisted client process aborted (50)

Could you help me please?

Thanks

Intore

2 ACCEPTED SOLUTIONS

Accepted Solutions

Michal_Mikulik1
Level 6
Partner    VIP    Accredited Certified

Hello,

two tips:

- use the same format in both rename file and filelist file (E:\ or /E/)

- first, test the command with single-row filelist file, or with file specification directly in bprestore command (not using filelist). There is something wrong with this file.

Regards

Michal

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Intore 

You will need someone to have a look at your .txt files. 

Looking in my post that you are referring you, you will see that my 'filelist' file had the same format as my 'rename' file.

Try /E/SOURCE_PATH/file_1  in stead of E:\SOURCE_PATH\file_1

Link to Veritas TN:
https://www.veritas.com/support/en_US/article.100010417

Best to add the amount of characters ( filepathlen) in the rename file as well.
In my example, the source path had 12 characters  (/C/marianne/) and the destination path had 13 characters (/C/morejunk1/)

View solution in original post

6 REPLIES 6

Michal_Mikulik1
Level 6
Partner    VIP    Accredited Certified

Hello,

steps googable here: https://www.veritas.com/content/support/en_US/article.100031821.html

Regards

Michal

@Michal_Mikulik1 

I just added the path to the master server, in fact I no longer have that error message.

Anyway, the process is still failing:

Invalid line length in line:  ■E
EXIT STATUS 144: invalid command usage

and the details job are:

Aug 26, 2019 4:17:51 PM - begin Restore
Aug 26, 2019 4:17:53 PM - end Restore; elapsed time 0:00:02
client process aborted  (50)

 

Michal_Mikulik1
Level 6
Partner    VIP    Accredited Certified

Hello,

two tips:

- use the same format in both rename file and filelist file (E:\ or /E/)

- first, test the command with single-row filelist file, or with file specification directly in bprestore command (not using filelist). There is something wrong with this file.

Regards

Michal

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Intore 

You will need someone to have a look at your .txt files. 

Looking in my post that you are referring you, you will see that my 'filelist' file had the same format as my 'rename' file.

Try /E/SOURCE_PATH/file_1  in stead of E:\SOURCE_PATH\file_1

Link to Veritas TN:
https://www.veritas.com/support/en_US/article.100010417

Best to add the amount of characters ( filepathlen) in the rename file as well.
In my example, the source path had 12 characters  (/C/marianne/) and the destination path had 13 characters (/C/morejunk1/)

View solution in original post

quebek
Level 6
   VIP    Certified

Please see the exceprt from bprestore admin code...

When you restore to a Windows client, you can also use the following method
for specifying entries in the rename file. (Do not use this method for other
clients.)
rename bulength backup_filepath reslength
restore_filepath
Where:
bulength is the number of ASCII characters in the backup path.
reslength is the number of ASCII characters in the restore path.
The first backup_filepath that is matched is replaced with the restore_filepath
string.
For example, the following entry renames C:\fred.txt to C:\fred2.txt:
rename 11 /C/fred.txt 12 /C/fred2.txt
(Be sure to end the entry with a return.)

 

Is your master server Linux or Windows? If it's Linux and you created the filelist file with a Windows editor, you may have introduced carriage returns (^M) at the ends of lines. A Linux NetBackup master server won't process such a line.

As others have said, express your files in /E/path/file format. That's how the names are stored in the catalog. Bprestore may convert the Windows format for you; I don't remember.

For Windows clients, I second @quebek 's suggestion to make a habit of using the "rename n old path m new path" format. A Windows path can include " to ", which would cause NetBackup to parse the "change X to Y" format incorrectly.