Backup / Restore to a server that isnt a NBU client

[bc1410]

Hello - 

So MASTER/MEDIA server is Windows Server 2012 R2.   We have Version 8.1.1 of Netbackup.

So I got a request to backup some data off of a shared directory off on a server we have located at a different site so they can delete the data.  Prior to deleting the data I would like to make sure I can restore a few files. This server isnt currently a NBU client..  The backup I did in which I used the Share UNC path -  \\s03-test-3.company.com\F\CAAT\indexes was successful.  So I created a Restore_test directory under the shared F: drive out on the s03-test-3.compnay.com server and attempted to restore a few small text files as a restore test.   The Restore ran for a good amount of time or so and came up as incomplete status 2850.   So I went back and added our NBU service account under the windows secrity tab and gave it FULL permissions.  Also even added the NBU service account to the Admin account for that server s03-test-3.company.com.   But still gave the same results - status 2850.   I have attached the detailstatus of the incomplete job which I just ended up canceling..   Any thoughts of why I cant restore these few files to this server..  I thought I would be able to restore/backup even though its not a NBU client..  Maybe we need to just add it as a client...  We dont forsee doing a lot of backups on this server so higher ups dont want to burn a NBU client license.

[bc1410]

Fail to mention that I used POLICY TYPE MS-Windows to do the backup and Im using the m using the NBU master/media  server as the source client for the restore and the destination client and uisng the option to "Restore everything to  a different location (maintaining existing structure) and then I use the UNC path of \\s03-test-3.company.com\F\restore-test\.

Thanks

[Marianne · Accepted solution]

@bc1410 

Seems you forgot to add the attachment? 

---

@bc1410 wrote:

 I have attached the detailstatus of the incomplete job which I just ended up canceling..   

---

When you logon to the master server to initiate the restore, your own access permissions will be used to write to  \\s03-test-3.company.com\F\restore-test\.
Have you tested the path to ensure that you can create files and folders?

If you are using another GUI to initiate the restore, please confirm that NBU Client Service and Legacy Client Services are started as an account with write permissions on the UNC path. 

For troubleshooting, please create 'tar' log folder under ...\veritas\netbackup\logs and set logging level to 3. 

Please share all text in Job Details, all text in 'Task Progress' tab of BAR GUI as well as tar log file (please copy to .txt extentions before uploading).

TN: https://www.veritas.com/support/en_US/article.100001580

[bc1410]

Hi Marianne - 

sorry about the attachment..  

I have Admin permissions and yes tested that I can create a folder and files..  As I created a folder under \\s03-test-3.company.com\F\ and named it "restore-test"..  Now I did that when I was logged into the server s03-test-3.company.com.

Now I just realized when I mapped the same path as a network drive on our Master server (mapped -  \\s03-test-3.company.com\F\restore-test to the Y: drive)  and tried to save a file this way I got the message "You dont have permission to save in this location. Contact sys admin to obtain permissions...."

I will see why I cant save a file to the network mapped share drive..  I will also do you what you said with regard to logging etc...

Thanks BC

Sorry but having problems uploading the *.txt file (detailed status)

here it is :

Mar 20, 2019 1:58:42 PM - begin Restore
Mar 20, 2019 1:58:44 PM - number of images required: 1
Mar 20, 2019 1:58:44 PM - media needed: K60998
Mar 20, 2019 1:59:18 PM - restoring from image s01-backup-1.company.com_1552266702
Mar 20, 2019 1:59:19 PM - Info bpbrm (pid=6420) s01-backup-1.company.com is the host to restore to
Mar 20, 2019 1:59:19 PM - Info bpbrm (pid=6420) telling media manager to start restore on client
Mar 20, 2019 1:59:19 PM - Info bpbrm (pid=17308) s01-backup-1.company.com is the host to restore to
Mar 20, 2019 1:59:19 PM - connecting
Mar 20, 2019 1:59:20 PM - Info bpbrm (pid=17308) start tar32 on client
Mar 20, 2019 1:59:20 PM - requesting resource  K60998
Mar 20, 2019 1:59:20 PM - granted resource  K60998
Mar 20, 2019 1:59:20 PM - granted resource  IBM.ULTRIUM-TD6.002
Mar 20, 2019 1:59:20 PM - Info bptm (pid=2700) Waiting for mount of media id K60998 (copy 1) on server s01-backup-1.company.com.
Mar 20, 2019 1:59:20 PM - started process bptm (pid=2700)
Mar 20, 2019 1:59:20 PM - mounting K60998
Mar 20, 2019 1:59:21 PM - Info bptm (pid=2700) INF - Waiting for mount of media id K60998 on server s01-backup-1.company.com for reading.
Mar 20, 2019 1:59:23 PM - Info tar32 (pid=18180) Restore started.
Mar 20, 2019 1:59:23 PM - connected; connect time: 0:00:00
Mar 20, 2019 2:00:04 PM - mounted K60998; mount time: 0:00:44
Mar 20, 2019 2:00:04 PM - Info bptm (pid=2700) K60998
Mar 20, 2019 2:00:04 PM - Info bptm (pid=2700) INF - Waiting for positioning of media id K60998 on server s01-backup-1.company.com for reading.
Mar 20, 2019 2:00:04 PM - positioning K60998 to file 10
Mar 20, 2019 2:01:00 PM - positioned K60998; position time: 0:00:56
Mar 20, 2019 2:01:00 PM - begin reading
Mar 20, 2019 3:51:02 PM - Info tar32 (pid=18180) done. status: 0
Mar 20, 2019 3:51:02 PM - Info tar32 (pid=18180) done. status: 5 - the restore failed to recover the requested files
Mar 20, 2019 3:51:02 PM - end reading; read time: 1:50:02
Mar 20, 2019 3:51:02 PM - Info bpbrm (pid=6420) child done, status 5
Mar 20, 2019 3:51:02 PM - Info bpbrm (pid=6420) sending message to media manager: STOP RESTORE s01-backup-1.company.com_1552266702
Mar 20, 2019 3:51:03 PM - Info bpbrm (pid=6420) media manager for backup id s01-backup-1.company.com_1552266702 exited with status 0: the requested operation was successfully completed
Mar 20, 2019 3:51:03 PM - restored from image s01-backup-1.company.com_1552266702; restore time: 1:51:45
Mar 20, 2019 3:51:03 PM - Warning bprd (pid=6920) Restore must be resumed prior to first image expiration on INFINITY      
Mar 20, 2019 3:51:04 PM - end Restore; elapsed time 1:52:22
Restore error  (2850)

[Marianne]

So, I guess that NBU is receiving the same permission error.

Could you please share all text in 'Task Progress' tab of BAR GUI for the failed restore attempt?

I am curious to know as to why you cannot upload files. 
What happens if you click on 'Choose Files'  below your reply?

[bc1410]

Thanks Marianne -  

Well I only had full permissions on the shared drive "security" tab.   Once I also added myself to the Sharing Tab of the shared drive properties under "Advance Sharing and then Permissions" I was able to save a file/folder on the mapped shared drive from the NBU master server.  So I ran the restore again to see if I could restore a few files to the "restore-test" directory and this time it was successfull...   So Thank you so much for waking me up on the permissions test with creating and saving a file to test the permissions.  A simple test on permissions and I only ran it on the one server and not the NBU server.  Thanks again for your HELP!!

BC