http:\/\/192.9.172.90\/bigadmin\/content\/submitted\/restore_netbackup.html<\/p>\n
<\/p>\n
Bradley T. Webb, February 2007<\/i><\/p>\n
Note:<\/b> This is a much simpler, revised method, resubmitted after the original document was published in August 2004.<\/p>\n
Contents:<\/b><\/p>\n <\/p>\n The situation is that you need to restore the Solaris Operating System on your client’s server system disk for whatever reason, and I assume that you are unable to boot normally from the Solaris system. I also assume that you have a backup of your client’s operating system on VERITAS NetBackup.<\/p>\n You are going to boot your client up from CD-ROM or JumpStart, and use NFS to share the disk partitions out, then mount them on a NetBackup Media Server, and restore your operating system files into the Media Server mount point. This will effectively restore the operating system onto your client’s system disk.<\/p>\n Note that by default it is not possible to share partitions natively through NFS when booting from CD-ROM or JumpStart.<\/p>\n You can choose either method to boot up, but in any case it is probably useful to follow the steps for preparing the OpenBoot PROM (OBP) environment.<\/p>\n <\/p>\n You will need to have this information on hand:<\/p>\n For the purposes of this document, the JumpStart server’s IP is 10.0.0.1 and the client has an IP of 10.0.0.2, and a subnet mask of 255.255.255.0. The NetBackup Media Server’s IP is 10.1.1.1.<\/p>\n <\/p>\n You can skip this step if you are booting from a CD-ROM.<\/p>\n I assume here that if you boot from JumpStart, the server has a router address that allows your client to reach the NetBackup Media Server. If that is not the case, see the section on booting from a CD-ROM for the commands to set up routing: An Alternative Method to Boot Your Client From a Solaris Boot CD-ROM.<\/p>\n On the JumpStart server, edit the Next, edit the Then go to the Important note:<\/i> You must share the NFS JumpStart files from the JumpStart server as read only<\/i>, ( Thus:<\/p>\n <\/p>\n From the OBP, you need to know which interface you will boot from, and create an alias to its hardware path. If needed, you can run the following commands to see which interfaces are connected to something at the other end:<\/p>\n To display any current aliases for network devices, use To set up a network device alias name (for the interface on the JumpStart backup LAN) do the following:<\/p>\n This lists the interfaces. Select the one you want (for example, This creates the alias called At this stage you need to make sure your chosen interface will use the MAC that you got from the banner command.<\/p>\n If it shows as Next, I recommend setting <\/p>\n Use <\/p>\n Use If you booted from a CD-ROM, on the client, run the commands necessary to configure the appropriate IP, netmask, and routing.<\/p>\n If your media server is on a different network, add a route in (according to the following example). Here, <\/p>\n On the client, type the following commands:<\/p>\n I am assuming you have connected to your client through some sort of remote console, and it needs If your client is connected to a switch that is set to run at 100 Mbit\/sec full duplex, you can change the duplex to be full, thus massively speeding up your restore time.<\/p>\n If you have a more modern interface such as bge or ce, you will need to check the Sun documentation for the syntax to use.<\/p>\n Determine the name of your interface with the following:<\/p>\n At this stage you should check that the subnet mask of your interface is correct. This is picked up from the subnet used for the same network range in If you look closely you will see that the broadcast address is probably wrong (it may or may not affect the network connection), so you should correct it. Here is an example:<\/p>\n This command determines the broadcast for you and corrects it on the fly.<\/p>\n Next, create and run a script similar to the one shown next. Modify the Add the following lines. (Note:<\/i><\/b> This example is for the <\/p>\n You are going to make the Next, in the Note that in this case it is Now that the In the The next step is very important. You will determine the real disk name of the root disk to which you are restoring.<\/p>\n <\/p>\n Important note:<\/i><\/b> If you are restoring a system with multiple disk controllers, when you boot from JumpStart or a CD-ROM, the controllers will almost certainly be probed in a different order than they would be probed when booting normally from UNIX. As a result, the controller names will be different. For example, Here is an example:<\/p>\n 1. While booted from JumpStart, issue the appropriate break signal ( 2. 3. This is what 4. Under JumpStart, the root disk you need to restore to is Because you are using fibre-attached internal disks, this example does not show you everything you need to know. Although the <\/p>\n Now use the format program to reformat your disk using the same partition sizes as the original system had, or use suitable alternative sizes.<\/p>\n Also, note that if you had your root disk mirrored under VERITAS Volume Manager, and you are restoring to the original system disk, due to the way VERITAS repartitions the disk, you will definitely have to reformat the original disk and reinstate VERITAS mirroring later on.<\/p>\n When you have reformatted the disk, create file systems on it.<\/p>\n <\/p>\n Now log on to the VERITAS NetBackup Media Server as root, and mount the client’s NFS share on it.<\/p>\n\n
\/tmp\/disk<\/code>, Share It Out With NFS, and Mount It Onto the Media Server<\/li>\n<\/a>Overview of the Basic Method<\/h5>\n
<\/a>Information You Need Before Starting<\/h5>\n
\n
<\/a>Example Instructions to Set Up a Basic JumpStart Boot<\/h5>\n
\/etc\/ethers<\/code> file so it contains the MAC address of your client’s system. (The MAC address is displayed with the banner<\/code> command from the OBP on the client.)<\/p>\n\/etc\/hosts<\/code> file so that it contains the client’s host name and its IP. (The client’s IP is the same subnet as the JumpStart server and should be on the backup LAN network.)<\/p>\ntools<\/code> directory of the JumpStart client and run the add_install_client<\/code> command, as in the following example:<\/p>\n# cd \/jumpstart\/solaris8\/february2002\/Solaris_8\/Tools\r\n# .\/add_install_client client_1 sun4u<\/pre>\n
-o ro<\/code>), or the JumpStart configuration will become corrupted. For more details, please see the SunSolve document SRDB ID: 22979 (editor’s note: available to registered SunSolve users with a valid Sun Service Plan).<\/p>\nshare -F nfs -o ro,anon=0 \/jumpstart<\/pre>\n
<\/a>Prepare Your Client’s Open Boot PROM Environment<\/h5>\n
OK watch-net-all<\/pre>\n
OK devalias<\/code>.<\/p>\nOK show-nets<\/pre>\n
b<\/code>).<\/p>\nOK nvalias jump-nic ctrl+y<\/pre>\n
jump-nic<\/code>. (ctrl + y<\/code> pastes in the interface you selected.)<\/p>\nOK printenv use-local-mac-address?<\/pre>\n
true<\/code>, change it to false<\/code>. (You can change it back after the restore.)<\/p>\nOK setenv use-local-mac-address? false<\/pre>\n
auto-boot?<\/code> to false<\/code> in case you have problems:<\/p>\nOK setenv auto-boot? false<\/pre>\n
<\/a>Boot Up the Client From JumpStart<\/h5>\n
OK boot jump-nic -s<\/code> or OK boot net -s<\/code>, and wait for the #<\/code> prompt.<\/p>\n<\/a>An Alternative Method to Boot Your Client From a Solaris Boot CD-ROM<\/h5>\n
OK boot cdrom -s<\/code> and wait for the #<\/code> prompt.<\/p>\n# ifconfig hme0 plumb 10.0.0.2 up netmask 255.255.255.0 broadcast +<\/pre>\n
10.0.0.254<\/code> is the router that you can use to reach the media server, with the destination as the IP address of 10.1.1.1<\/code>.<\/p>\n# route add net 10.1.1.1 10.0.0.254 1<\/pre>\n
<\/a>Whichever Method You Booted From, Prepare the Client Environment<\/h5>\n
# stty erase ^H\r\n# exec ksh -o vi \r\n# PS1='$PWD> '\r\n# export TERM=vt100<\/pre>\n
vt100<\/code> rather than sun<\/code> as a terminal type.<\/p>\n# ifconfig -a<\/pre>\n
\/etc\/netmasks<\/code> on the JumpStart server.<\/p>\n# ifconfig hme0 broadcast +<\/pre>\n
instance<\/code> and dev name<\/code> to suit your system. If you are using bge interfaces you will need to refer to other documentation, as a different syntax is used.<\/p>\n# vi \/tmp\/ndd<\/pre>\n
hme<\/code> interface, hme0<\/code>. hme1<\/code> would be used for instance 1, and so on.)<\/p>\nndd -set \/dev\/hme instance 0\r\nndd -set \/dev\/hme adv_100T4_cap 0\r\nndd -set \/dev\/hme adv_100fdx_cap 1\r\nndd -set \/dev\/hme adv_100hdx_cap 0\r\nndd -set \/dev\/hme adv_10fdx_cap 0\r\nndd -set \/dev\/hme adv_10hdx_cap 0\r\nndd -set \/dev\/hme adv_autoneg_cap 0\r\n\r\n# chmod 744 \/tmp\/ndd\r\n# \/tmp\/ndd<\/pre>\n
<\/a>Enable Your Client to Share Disk Partitions Using NFS<\/h5>\n
\/etc\/dfs<\/code> directory writable so that you can use NFS on the client to share out the disk partitions.<\/p>\n# cd \/etc\r\n# find dfs | cpio -pdumv \/tmp\r\n# mount -F lofs \/tmp\/dfs \/etc\/dfs<\/pre>\n
# cd \/etc\/init.d\r\n# .\/rpc start\r\n# .\/nfs.client start<\/pre>\n
# vi \/etc\/dfs\/dfstab<\/pre>\n
\/etc\/dfs\/dfstab<\/code> file, put in a line similar to the following:<\/p>\nshare -F nfs -o rw,anon=0 -d \"client restore\" \/tmp\/disk<\/pre>\n
READ \/ WRITE ( -o rw )<\/code>, as you want to use NFS to share the disk partition to which you are going to restore.<\/p>\ndfs<\/code> directory is mounted in the writeable swap file system (\/tmp<\/code> on your client), dfstab<\/code> and sharetab<\/code> are writeable files. This allows you to share disk partitions from your client using NFS, even though the directory is read only by default when the client is booted from CD-ROM or JumpStart. Note<\/i><\/b>: The boot directory on the JumpStart server is actually \/<\/code> (root) on your client.<\/p>\n\/tmp<\/code> directory, create the mount point you will share your disk partitions from:<\/p>\n# mkdir \/tmp\/disk\r\n# cd \/etc\/init.d\r\n# .\/nfs.server start\r\n# unshareall<\/pre>\n
<\/a>Determine the Real Disk Name<\/h5>\n
c2t0d0<\/code>, when booted from JumpStart, could refer to c1t0d0<\/code> booted from UNIX. To get the real device name, you need to issue the devalias<\/code> command from the OK<\/code> prompt. This will display the hardware path of the boot device and you can compare it to the output of the format<\/code> command.<\/p>\nstop+A<\/code>, or the equivalent, according to your connection type) to go to the ok<\/code> prompt.<\/p>\ndevalias<\/code> shows something like the following:<\/p>\nrootdisk \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/disk@0,0\r\nrootmirror \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/disk@1,0<\/pre>\n
format<\/code> would show the following when booted to full UNIX:<\/p>\nAVAILABLE DISK SELECTIONS:\r\n 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/ssd@w21000004cf7f2c6f,0\r\n 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/ssd@w21000004cf8febe7,0<\/pre>\n
format<\/code> shows when booted from the JumpStart server:<\/p>\nAVAILABLE DISK SELECTIONS:\r\n 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,700000\/scsi@2\/sd@0,0\r\n 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,700000\/scsi@2\/sd@1,0\r\n 2. c1t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,700000\/scsi@2\/sd@2,0\r\n 3. c1t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,700000\/scsi@2\/sd@3,0\r\n 4. c1t4d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,700000\/scsi@2\/sd@4,0\r\n 5. c2t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/ssd@w21000004cf7f2c6f,0\r\n 6. c2t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>\r\n \/pci@8,600000\/SUNW,qlc@4\/fp@0,0\/ssd@w21000004cf8febe7,0<\/pre>\n
c2t0d0<\/code>.<\/p>\ndevalias<\/code> controller path matches the format<\/code> controller path, it does not very effectively translate Fibre WWNs to the device ID name of devalias<\/code> output. However, it should be obvious that under a JumpStart boot, disk@0,0<\/code> and disk@0,1<\/code> relate to c2t0d0<\/code> and c2t1d0<\/code>, respectively. (Note that I did not show c2t1d0<\/code> in the preceding JumpStart format<\/code> printout.)<\/p>\n<\/a>Reformat Your Disks<\/h5>\n
# for i in 0 3 4 5\r\ndo\r\necho y | newfs \/dev\/rdsk\/c0t0d0s$i\r\ndone<\/pre>\n
<\/a>Mount the First File System on
\/tmp\/disk<\/code>, Share It Out With NFS, and Mount It Onto the Media Server<\/h5>\n# mount -F ufs \/dev\/dsk\/c0t0d0s0 \/tmp\/disk\r\n# shareall<\/pre>\n
# cd \/tmp\r\n# mkdir client_1<\/pre>\n