Sponsored Content
Operating Systems Solaris Solaris Jumpstart and Flash Archives Post 77527 by rambo15 on Sunday 10th of July 2005 02:30:37 PM
Old 07-10-2005
Solaris Jumpstart and Flash Archives

Ladies and Gentlemen:
I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is why I am considering trying to implement a Jumpstart/Flash archive solution. As usual, the customer is strapped for time and funding and thus cannot afford me the luxury of experimental testing on my own to determine if a Jumpstart/Flash archive is a viable solution. So I am turning to all of you to help me determine if I should push this approach any further with the customer or should I just drop it. I need fairly technical answers to the following questions:
1. From what I have read, you can create a flash archive of a "master" system. Can this archive image be an image of the entire disk? If the answer is yes, then when you go to restore it using Jumpstart, does the disk you are restoring to have to be of the same disk geometry and size? I believe the answer is probably yes, however, the logic behind the question is: Say I am using a system with a 36GB disk as my "master" system image. After building it, the total disk space "used" by all partitions is only 15GB. Can I use Jumpstart and the 36GB Flash archive image to restore it to a 20GB disk? If the answer is 'NO", I need to restore it to a disk with the same geomentry and size, then is the real solution to this scenario to use flar create to create separate archives of all the master disk partitons?

2. When using Jumpstart to restore this "master" image (whether it be the entire disk archive image or each separate archive images of the master disk partitions), how does Jumpstart account for changing of the hostname, netmask, default route, IP addresses, domainname, etc.? (In other words, the unique system information that varies from system to system.)

3. Assuming that jumpstart can somehow reconfigure the system-unique parameters after installing the master system disk image/partitions and everything else remains equal, will using Jumpstart in conjunction with Flash archives be any faster than just using Jumpstart with finish scripts?

Thank You for your wisdom and help!
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Jumpstart and Flash Archives

Ladies and Gentlemen: I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is... (0 Replies)
Discussion started by: rambo15
0 Replies

2. UNIX for Dummies Questions & Answers

flash archives

HI, are you supposed to run flarcreate in multi user mode? or should you do it in single user? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

3. Solaris

bootable X86 dvd and flash archives

I have created a bootable DVD for X86 using a flash archive, the problem is that I have to specify the location at the beginning of the install. I have edited the any_machine profile under ./jumpstart_sample to contain the following install_type flash_install archive_location ... (4 Replies)
Discussion started by: eeisken
4 Replies

4. Solaris

zfs and flash archives

i had a situation where an app i was running just didn't have enough resources on a proliant dl365 (running sol10x86). so i ended up building out a dl385g2. the dl365 had zfs root file system which was managing the whole disk (smart array taking the raid 1+0). anyway, i figured i could migrate the... (2 Replies)
Discussion started by: pupp
2 Replies

5. Solaris

Flash installation with Jumpstart

I get following error while doing a flash installation. I 'm trying to deploy a flash archive created by our engineering team. I 'm trying to install it with ZFS root and the profile which i using is as following #more flash_profile_test install_type flash_install archive_location nfs... (3 Replies)
Discussion started by: fugitive
3 Replies

6. Solaris

Flash Archives - A little bit of help :-)

Hi all Okay, I know how to make flash archives, and I even know how to split them and extract files. But, Ive never used one to restore an OS drive and I might have to. Ive search around google, and seen different ideas / ways, but havent really come to a definate answer. So, lets... (3 Replies)
Discussion started by: sbk1972
3 Replies

7. Solaris

difference between flash archive and jumpstart

Hi, Can anyone explains me the difference between solaris flash archive and jumpstart installation. Both are used to install many systems frm a centralized location , correct me if am wrong,. Clear view on this is really appreciable. Thanks in advance (3 Replies)
Discussion started by: rogerben
3 Replies

8. Solaris

Jumpstart client flash archive error....

Hi , I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue . Extracted 100 %... (0 Replies)
Discussion started by: knl.sundeep
0 Replies

9. Solaris

Flash Archive Jumpstart with multiple ZFS Pools

Hi, I'm trying to get a Flash Archive Jumpstart Running with ZFS Filesystem. For Testing I set up a VirtualBox VM with 2 Disks attached. On the first disk I have the ZFS root pool, on the second Disk I have some more ZFS Pools which I use for 2 additional Zones I've set up. Restoring works fine if... (1 Reply)
Discussion started by: NoelzeN
1 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 11:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy