We've been trying to perform full system backup on our Solaris installed server (SunOS 10, 9/10). We have been following this procedure : http://documentation.commvault.com/hds/release_8_0_0/books_online_1/english_us/features/disaster_recovery/unix/solaris.htm
Since our SunOS is Update 6 and Above we are directed to use mini-root method which firstly requires performing the jump start method . So we have this another Sun server we are trying to configure as a Jumpstart server.
This is what we have done:
We copied the jump start software on our JS servers' /opt/boot , added the client, and created shareable /jumpstart dir with boot image for the client. Bootparams are modified respectfully, so the client can look up for /jumpstart as his root dir (hosts,system,serveces are modified as well as simbolic links for simpana).
We ignored creating /opt (step 10 Using the jump start server method ) because we allready had that slice and then we have successfully installed Simpana on our JS server.
Step 12-17 confuses me : It says I have to create partitions/slices on the disk , as well as root fs which I should mount on /mnt.
So here is the quiestion:
1. Why is this necessary for this procedure? Is this refering to creating partitions on the jumpstart servers side? If yes, how will it affect previously created filesystems?
As far as I can understand, these fs should be used by client during net boot.
2. Step 18: It says install the jumpstart server on the Boot server. Client and JS server are on the same subnet with the client so I could use the same machine for boot/jumpstart server?Then what implies installing the jumpstart server on the boot server?
Any help would be usefull.