GUI Restore Works, CLI Restore Fails
Hi,
We are running a restore in the GUI and it works perfect and then tried to script this restore, see script below but every time it throws this error - EXIT STATUS 2808: MS-windows policy restore error
cd "D:\Program Files\Veritas\NetBackup\bin"
.\bprestore.exe -B -w -C FileServer01 -D NBserver01.companyX.com -L "D:\Program Files\Veritas\NetBackup\logs\bprd\test.log" -s 26/04/2019 05:13:12 -e 26/04/2019 23:15:28 -R "D:\Program Files\Veritas\NetBackup\logs\user_ops\test03a_rename.txt" -f "D:\Program Files\Veritas\NetBackup\logs\user_ops\test03a_list.txt"
D:\Program Files\Veritas\NetBackup\logs\user_ops\test03a_rename.txt =
rename 142 "/Shadow Copy Components/User Data/Distributed File System Replication/DfsrReplicatedFolders/Departments/BlueEarth/Doc.docx" 171 "D:\doc.docx"
D:\Program Files\Veritas\NetBackup\logs\user_ops\test03a_list.txt =
142 /Shadow Copy Components/User Data/Distributed File System Replication/DfsrReplicatedFolders/Departments/BlueEarth/doc.docx
When I run the script, I see in the activity controller.....
17-Apr-2020 14:08:00 - begin Restore
17-Apr-2020 14:08:02 - Info bprd (pid=12996) Found (3,467,191) files in (10) images for Restore Job ID 75697.xxx
17-Apr-2020 14:08:02 - restoring from image fileserver01_1556305208
17-Apr-2020 14:08:02 - requesting resource @aaaaS
17-Apr-2020 14:08:02 - granted resource MediaID=@aaaaS;DiskVolume=_PhysicalLSU;DiskPool=dxi-qcloudprotect;Path=_PhysicalLSU;StorageServer=aws-qcloudprotect_172.31.23.33;MediaServer=nbserver01.companyx.com
17-Apr-2020 14:08:03 - Info bprd (pid=12996) Searched ( 2) files of (3,467,191) files for Restore Job ID 75697.xxx
17-Apr-2020 14:08:03 - Info bprd (pid=12996) Restoring from copy 2 of image created 04/26/19 20:00:08 from policy AA-FS01_Weekly
17-Apr-2020 14:08:03 - Info bpbrm (pid=10536) nbserver01.companyx.com is the host to restore to
17-Apr-2020 14:08:03 - Info bpbrm (pid=10536) reading file list for client
17-Apr-2020 14:08:03 - Info bpbrm (pid=10536) connecting to bprd to get file list
17-Apr-2020 14:08:03 - connecting
17-Apr-2020 14:08:03 - Info bpbrm (pid=10536) starting bptm
17-Apr-2020 14:08:07 - Info tar32 (pid=7288) Restore started
17-Apr-2020 14:08:07 - connected; connect time: 0:00:00
17-Apr-2020 14:08:07 - Info bptm (pid=13688) start
17-Apr-2020 14:08:07 - started process bptm (pid=13688)
17-Apr-2020 14:08:07 - Info bptm (pid=13688) reading backup image
17-Apr-2020 14:08:07 - Info bptm (pid=13688) using 64 data buffers
17-Apr-2020 14:08:08 - begin reading
17-Apr-2020 14:08:11 - Info bptm (pid=13688) waited for empty buffer 0 times, delayed 0 times
17-Apr-2020 14:08:11 - Info tar32 (pid=7288) done. status: 5
17-Apr-2020 14:08:11 - end reading; read time: 0:00:03
17-Apr-2020 14:08:17 - Info bptm (pid=13688) completed reading backup image
17-Apr-2020 14:08:17 - Info bptm (pid=13688) EXITING with status 0 <----------
17-Apr-2020 14:08:17 - Info tar32 (pid=7288) done. status: 5: the restore failed to recover the requested files
17-Apr-2020 14:08:17 - Error bpbrm (pid=10536) client restore EXIT STATUS 5: the restore failed to recover the requested files
17-Apr-2020 14:08:17 - restored from image fileserver01_1556305208; restore time: 0:00:15
17-Apr-2020 14:08:17 - Warning bprd (pid=12996) Restore must be resumed prior to first image expiration on 25/04/2020 20:00:08
17-Apr-2020 14:08:17 - end Restore; elapsed time 0:00:17
Windows File System policy restore error (2808)
Look at the rename file again - I think you may be missing a new line. From the commands reference guide (the emphasis is mine).
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.)Your rename file doesn't appear to to have a new line at the end. I think what may be happening is it is attempting to restore the file to the original location on the destination server hence the strange error (as I assume the destination server doesn't have DFSR running).
