netinstall with ufsdump


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers netinstall with ufsdump
# 1  
Old 02-17-2005
netinstall with ufsdump

Hello all,

I was wondering is it possible to install Solaris over the network whit jumpstart and just ufsretore a dump file? The clinet's disk would totally be empty. I know that I can use the rules files, would I put the command to uferestore from the server in the pre install rules file. I just don't want to do a complete install then retore after. I guess my question is something on the line of Windows ghost cast server which would just dump an image to the client?


THANKS
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

ufsdump

Experts, Before patching am advised to take backup : so am going with: ufsdump -0uf /dev/rmt0 / ---> to take the whole / bkp to tape. some servers have /var in diff slice, In this case whether i need to take backup of /var also in tape? ufsdump -ouf /dev/rmt0 /var ---> to take... (3 Replies)
Discussion started by: fizan
3 Replies

2. Solaris

ufsdump a dir?

Is there a way to backup a single directory with ufsdump, or is tar better for that? (1 Reply)
Discussion started by: orange47
1 Replies

3. UNIX for Dummies Questions & Answers

How to do a ufsdump remote?

People i have 2 sun sparc solaris 10. I have one filesystem to 98% and i need to do a ufsdump of that filesystem. THe problem is that i don't have space to allocate the dump of the filesystem. Thats why i want to do it from the other sun and bring the ufs dump to de /FREE filesystem. ... (4 Replies)
Discussion started by: enkei17
4 Replies

4. UNIX for Dummies Questions & Answers

Ufsdump

Hi, I have 5 soraris boxes and i am trying to backup all to SAN.Which backup is more suitable tar or ufsdump? Also pls mention what are the important folders i need to back up. Thanks (3 Replies)
Discussion started by: solaris5.10
3 Replies

5. Solaris

Using ufsdump and ufsrestore

HI Gurus, I have a sunfire V445 server running SAP ECC 6.0 with an Oracle database on Solaris 9 (SunOS 5.9). I recently completed a ufsdump to tape of the following files:- /, /usr, /oracle, /export, /sapr3, I want to restore these files from tape onto a different server of the same... (5 Replies)
Discussion started by: charleywasharo
5 Replies

6. UNIX for Dummies Questions & Answers

ufsdump issue

I ran this dump (as root) and got the following............. # ufsdump 0f /dev/rmt/0n / DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Tue 11 Dec 2007 06:07:35 AM PST DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c2t1d0s0 (gambler:/) to... (1 Reply)
Discussion started by: shorty
1 Replies

7. Solaris

ufsdump

Hi, I want to how to take backup of File system From Disk to Disk using ufsdump? Wheather we can take the backup of root file system from one disk to another if tape drive is not available? wheather it is reliable to restore root file system? (2 Replies)
Discussion started by: manoj.solaris
2 Replies

8. UNIX for Dummies Questions & Answers

ufsdump

hi i would like to backup my OS what is the exact command to do? beside backup to tapes can i back up to a directory in another server? will the command be the same? thanks. :confused: (4 Replies)
Discussion started by: legato
4 Replies

9. UNIX for Dummies Questions & Answers

Ufsdump

I want to try using Ufsdump for backups . The man pages state that the file systems should be inactive or be in the unmounted state . But for that system should be in single User mode. My query is that can we perform Ufsdump in run-level 3 ? And if no should I have to reboot it in Single user... (3 Replies)
Discussion started by: DPAI
3 Replies
Login or Register to Ask a Question
stmsboot(1M)															      stmsboot(1M)

NAME
stmsboot - administration program for the Solaris I/O multipathing feature SYNOPSIS
/usr/sbin/stmsboot [-d | -e | -u | -L | -l controller_number] The Solaris I/O multipathing feature is a multipathing solution for storage devices that is part of the Solaris operating environment. This feature was formerly known as Sun StorEdge Traffic Manager (STMS) or MPxIO. The stmsboot program is an administrative command to manage enumeration of fibre channel devices under Solaris I/O multipathing. Solaris I/O multipathing-enabled devices are enumerated under scsi_vhci(7D), providing multipathing capabilities. Solaris I/O multipathing-disabled devices are enumerated under the physical controller. In the /dev and /devices trees, Solaris I/O multipathing-enabled devices receive new names that indicate that they are under Solaris I/O multipathing control. This means a device will have a different name from its original name (following installation) when it is under Solaris I/O multipathing control. The stmsboot command automatically updates /etc/vfstab and dump configuration to reflect the device names changes when enabling or disabling Solaris I/O multipathing. A reboot is required for changes to take effect. The following options are supported: -e Enables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this enabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -d Disables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this disabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -u Updates vfstab and the dump configuration after you have manually modified the configuration to have Solaris I/O multipathing enabled or disabled on specific fp(7D) controller ports. This option prompts you to reboot. During the reboot, vfstab and the dump configura- tion will be updated to reflect the device name changes. -L Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names. -l controller_number Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names for the speci- fied controller. Along with its primary function of enabling or disabling Solaris I/O multipathing, the stmsboot command is used to update vfstab and the dump configuration to reflect device name changes. For a system to function properly, you must configure the applications that consume the devices by old names to use the new names. The -L and -l options display the mapping between the old and new device names. These options work after the changes made to the Solaris I/O multipathing configuration have taken effect. For example, you can use these options following the reboot after invoking stmsboot -e. The old device names must exist in order to display the mappings. Example 1: Enabling Solaris I/O Multipathing Following OS Upgrade To enable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports run: # stmsboot -e Example 2: Disabling Solaris I/O Multipathing To disable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports, run: # stmsboot -d Example 3: Enabling Solaris I/O Multipathing on Selected Ports You want to enable Solaris I/O multipathing on some fibre channel controller ports and disable the feature on the rest. You edit the fp.conf file (see fp(7D)) to enable or disable Solaris I/O multipathing on specific controller ports. You then run the following command to have vfstab and the dump configuration updated to reflect the new device names: # stmsboot -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWcsu, SUNWcslr | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete | +-----------------------------+-----------------------------+ SEE ALSO
dumpadm(1M), ufsdump(1M), dumpdates(4), vfstab(4), fcp(7D), fctl(7D), fp(7D), qlc(7D), scsi_vhci(7D) Consult the Sun StorEdge Disk Tray [or Subsystem] Administrator's Guide for the T3, 3910, 3960, 6120, and 6320 storage subsystems. Sun StorEdge Traffic Manager Installation and Configuration Guide Solaris I/O multipathing is not supported on all devices. After enabling Solaris I/O multipathing, only those devices that Solaris I/O mul- tipathing supports are placed under Solaris I/O multipathing control. Non-supported devices remain as before. For Solaris releases prior to the current release, the -e and -d options remove the mpxio-disable property entries from fp.conf file (see fp(7D)) and add a global mpxio-disable entry to fp.conf. The current release of the Solaris operating system does not support the mpxio-disable property. Solaris I/O multipathing is always enabled. If you want to disable multipathing, you must use the mechanisms provided by the HBA drivers. See fp(7D). Enabling Solaris I/O Multipathing on a Sun StorEdge Disk Array The following applies to Sun StoreEdge T3, 3910, 3960, 6120, and 6320 storage subsystems. To place your Sun StorEdge disk subsystem under Solaris I/O multipathing control, in addition to enabling Solaris I/O multipathing, the mp_support of the subsystem must be set to mpxio mode. The preferred sequence is to change the subsystem's mp_support to mpxio mode, then run stmsboot -e. If Solaris I/O multipathing is already enabled but the subsystem's mp_support is not in mpxio mode, then change the mp_support to mpxio mode and run stmsboot -u. Refer to the Sun StorEdge Administrator's Guide for your subsystem for more details. ufsdump Users The ufsdump command keeps records of the filesystem dumps in /etc/dumpdates (see dumpdates(4)). Among other items, the records contain device names. An effect of the "active" stmsboot options (-e, -d, and -u) is to change the device name of a storage device. The stmsboot command does not modify the dumpdates file. Because of this, the dumpdates records will refer to the old device names, that is, the device names that were in effect before you ran stmsboot. The effect of this device name-dumpdates disagreement is that, following use of stms- boot, ufsdump will be processed as if no previous dump had ever been made, thus dumping the entire filesystem (effectively, a level 0 dump). Procedure to Use stmsboot in Sun Cluster Environment If possible, use stmsboot -e before you start installing Sun Cluster software. After you run stmsboot, you install Sun Cluster software as you normally would. If you install Sun Cluster software before running stmsboot, you must use the following procedure. On each machine in the cluster on which you want to enable the Solaris multipathing feature, enter: # stmsboot -e ...and allow the system to reboot. When the system comes up, enter the following two commands: 1. # /usr/cluster/bin/scdidadm -C 2. # /usr/cluster/bin/scdidadm -r The preceding commands update did mappings with new device names while preserving did instance numbers for disks that are connected to multiple cluster nodes. did instance numbers of the local disks might not be preserved. For this reason, the did disk names for local disks might change. 3. Update /etc/vfstab to reflect any new did disk names for your local disks. 4. Reboot the system. To disable the Solaris multipathing feature, use stmsboot -d (instead of stmsboot -e), then follow the procedure above. To view mappings between the old and new device names, run stmsboot -L. To view did device name mappings, run /usr/cluster/bin/scdidadm -L. 3 Mar 2005 stmsboot(1M)