flarcreate for disaster recovery
I'm trying to put together a BMR solution for two Solaris 9 servers we have, neither has an internal tape drive. I was trying to follow the flash archive/jumpstart documentation but it is not very detailed. I installed a jumpstart/archive server to hold the images of these two servers.
On one of the servers I created a flar image with:
flarcreate -n servername -S -R / -x /export/home -x /opt/applic
-x /backups servername.flar (the excluded directories are filesystems on the SAN)
Then I sftp'd that file to the archive server.
I followed the directions to restore the flar image from the nfs mount point on the archive server. At first, the directory containing the images is mounted correctly. But when it installs the image, I get an error that it can't mount the mount point for the images. The image directory gets unmounted when this error occurs. I'm not sure why it is trying to mount it twice or if this is even why it is failing. Does anyone have any ideas or has anyone ever gotten something like this to work? The archive server is Solaris 10.
# 1
if you can't mount the mountpoint that contains the image, then it means you're on net, and the first part of the jumpstart handshake has worked
check to ensure the filesystem with the image is properly shared out
and make sure you have route (from your jump client) to the jumpstart server (in the event you're using a boot helper instead of the jumpstart machine being on the same subnet as your client)
can you try a
boot net -v install
and if it shows anything fun, let us know?
# 2
Well, I tried it again and set the route to the jumpstart server. This is on a test network so there is no actual router. Anyway it failed. When I tried it before, saying there wasn't a default route, it would also fail.
I can mount the jumpstart server and image directory on the system I am trying to install manually using a console window, so the share seems to be okay. When I choose the flar location, at that point the filesystem gets mounted, the next step, the installation is where it fails.
When I do a boot net -v install from the server I'm trying to install at the ok> prompt, I get this message: Timeout waiting for ARP/RARP packet
and it goes on and on
# 3
the Timeout waiting for ARP/RARP is the normal process with jumpstart
if you don't have
-bootp server on the subnet
-connection from your client on the network
-correct configuration of your client in the bootparams/ethers/tftpboot areas on the boot server that exists on that subnet
You probably know all that, but just in case, I'll point you to the docs area - http://docs.sun.com/app/docs/doc/819-5778/6n7rbgt6c?q=add_install_client&a= view
