Restore

Solaris
NetBackup BMR

Using

Here we are going to restore a Solaris client using NetBackup Bare Metal
Restore. Before we are able to do that we have to enable this option in
the
NetBackup
policy
for
the
client:

When the backup was done successfully you're ready for a NetBackup
Bare Metal Restore.

Considerations
Bare Metal Restore Infrastructure
When performing a Bare Metal Restore you'll have to keep a few things
in mind. Originally a bare metal restore is intended to restore to the
original machine form which the backup was taken. However, in our
environment we use the Bare Metal Restore to restore the production
environment to our acceptance environment for Continuity Planning
reasons. That means that the original server is still online when the
restore takes place.

Network Configuration

The Solaris environment we're restoring is Install Solaris 10 Update 8,

and as explained in that article that edition of Solaris does not have
native support for the VMXNET3 network adapter. That card is however
supported after installing the VMware Tools. That means that the backup
we made is for a VMXNET3 card, which we cannot use because the boot
media uses the native solaris installation media. Remember to create
the VM to restore to with an e1000 network adapter and configure the
network after reboot accordingly.

DNS
NetBackup is heavily dependent on a working DNS environment. You
MUST change the hostfile on all NetBackup servers that have a role in
this Bare Metal Restore action. In our environment that is:

bckmaster01b

bckmaster01a

bckmedia01 (media server appliance)

bckmedia02 (media server appliance)

Add this line to the hostfile (open the file in notepad while opening
notepad as administrator)(C:\WINDOWS\system32\drivers\etc\hosts):
10.10.10.40 solarixbox

Running the Restore

Because the VM we're going to restore to is not the original VM the
hardware we're going to restore is never the same, plus that we have to
consider the changed network card. That means we'll first have to get
the new hardware configuration into NetBackup. Easiest way is to start a
discovery on the server and than use that discovered hardware to create
a
new
profile
to
restore
with.
So, as a overview, these are the steps:
1. Create a discovery task of the client
2. Start the client so hardware discovery can take place

3. Create a New Client Configuration using the current configuration

as source
4. Edit the newly created client configuration for the new network
card and the changed disks
5. Prepare to restore the client
6. Restore the client

Create a Discovery Task

In the Bare Metal Restore Clients section in the NetBackup
Administration console expand the client you're about to discover and

select Prepare to discover and enter all required information:

Start the Client Hardware Discovery

Start the client using the created media boot cd and select Solaris:

Select option 2:

Enter the name of the client you are restoring (do not use the FQDN
name):

Enter the temporary IP address which you also entered in the hosts files
on the NetBackup servers:

Select yes to be able to enter a subnet mask:

Enter the subnet mask:

Do not use IPv6:

Select to specify a default route:

Enter the default route:

Review your settings:

NOTE THIS SCREENSHOT uses the FQDN name of the NetBackup server
which will result in network errors. Be sure to enter just the short
hostname: bckmaster01a. Also note that you can't use backspace
here, be sure to make no typos:

After the discovery has been done reboot the client:

NOTE THIS SCREENSHOT is from a automatic discovery instead of a
manual one, so your screen might be a little different:

Create and Edit a New Client Configuration

In the Bare Metal Restore Clients section in the NetBackup

Administration console expand the client you're about to restore and
select the New Client Configuration:

Select the current configuration as the source to copy from:

Right click the newly created profile and select Change:

Configure the hosts, network configuration and routes to your needs:

NOTE THESE SCREENSHOTS are from after initialization and mapping:

Here you have to initialize the volumes with the discovery you created in
steps one and two. After initialization there is one disk under the native
part. This disk has a restriction which has to be removed after which you
can map the disk/volumes/filesystems:

Prepare to Restore

Now you're ready to prepare the systen for restore. Right click the client
and select Prepare to Restore:

Fill in the fields to use the configuration you adjusted for restore:

You'll get an warning about the running kernels. As long the the kernel in
the SRT is newer than the kernel of the system you're restoring you'll be
fine:

Restore the Client

Now boot the client the same way as you did in step two. If you did
everything successful the restore will start running:

Which you can check on the NetBackup master server:

Post Restore
Don't forget to clean up the restore in the tasks panel. To do so right
click the task and select Clean Up. This has to be done manually since
the client will boot (without network) or at least with a different IP
address than the NetBackup servers have listed in their hosts file.
Also don't forget to:

Configure the network

Check all the filesystems

Remove the hosts file listing on the NetBackup server you created