In this article I am going to explain how to perform Database restore using NetBackup tool. I was fortunate enough to learn from experienced people, otherwise it was difficult to follow the materials provided. In this post I have tried to explain the database restore process in detail.
Launching NetBackup Tool and connecting to SQL Instance:
- Click on Start > All Programs > Symantec NetBackup > NetBackup Agents > Right Click on NetBackup MS SQL Client > Run as Administrator as shown in the following example:
Note: Run as Administrator is a very important step, otherwise the tool won’t connect to SQL Instance and throws ambiguous error messages.
- In the User Account Control Window click on Yes.
- In the NetBackup Database Extension Window click on Ok to select the connection properties.
Now let’s see the ways to connect default and named SQL instances through NetBackup tool.
To Connect Default Instance:
- In the SQL Server Connection properties window put the host name.
- For Instance field, leave it as default click on Apply and then Close.
Note: You do not have to put any credentials for UserId field. Leave it as default. SQL Server version, Security and Host Type will be populated once it is connected as shown in the above screen shot.
To Connect Named SQL Instance:
- If the SQL Instance name is HostName\SQLInstance, you need to put the host and Instance name as shown in the following screen shot.
- Click on Apply and then close.
Now you are connected to the target Instance. You can always verify if you are connected to the correct instance from File > Set SQL Server Connection properties.
Database Restore Steps using NetBackup:
Go to File > Restore SQL Server Objects
Provide the SQL Server Instance name from which backup has to be restored, i.e. Source SQL Server name.
You can use time filter to view the backups in particular date range.
Note: Unlike native backup of SQL Server, NetBackup tool does not create any .bak files which can be copied from source to destination. The backup files/images are scattered on storage. This is the reason you have to provide Source and Destination Server name during the restore process.
Click on Ok to go the next wizard “Restore Microsoft SQL Server Objects”.
In the below screen shot I have shown full and differential backup images. I am going to show you the steps for restore using full backup image.
For Scripting choose “Create a move template”. This will create a restore template (.bch file) and the Save radio button will get selected by itself.
Click on Restore.
Provide a meaningful filename for the .bch file.
Click on Save.
You’ll get a pop up message asking “Would you like to open it in notepad?”
Click on Yes.
In the below screen shot I have explained what all places you have to make the changes. This is very important and you have to pay attention:
Template/script showing different places to modify:
Note: If you choose differential backup image to restore, the tool will automatically choose the base full database backup image. So in that case you have to make the same changes for all the data and log file locations.
And same goes with log file restore as well. Once you are done with all the changes save the file.
Now go to File > Manage Script Files:
Select the created template. e.g. “DatabaseName_11072017” as shown in the below screen shot.
Click on Start.
It will ask for confirmation. Click on Yes.
Another self-explanatory message will pop up.
Clock on Ok.
It will take you back to the “Manage Script” wizard.
This is a bit confusing or rather a bug. Just click on Cancel.
Your restore process should start and can be viewed the progress in File > View Status.
Hope this is helpful.
You may like the below articles as well: