Sponsored Content
Full Discussion: dd vs. ufsdump / restore
Operating Systems Solaris dd vs. ufsdump / restore Post 82805 by reborg on Tuesday 6th of September 2005 07:05:12 PM
Old 09-06-2005
It's not really a question of better or worse, but rather of media or filesystem based.

I have a personal preference for the ufs(dump&&restore) because I would usually have dissimilar media.
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ufsdump and restore

I just completed a level 0 ufsdump of the following files:- ufsdump 0uf /dev/rmt/0n / ufsdump 0uf /dev/rmt/0n /usr ufsdump 0uf /dev/rmt/0n /export/home ufsdump 0uf /dev/rmt/0n /oracle ufsdump 0uf /dev/rmt/0n /sapr3 I need to restore ALL the files onto a different machine and continue... (1 Reply)
Discussion started by: charleywasharo
1 Replies

2. AIX

mksysb restore - Wrong OS level for restore

Hi all, I am still working on my mksysb restore. My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored. 0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies

3. Solaris

Restore a server from a ufsdump

Hi guys i tried to restore a server from a ufsdump. For your information, the ufsdump was created on a v440 and i have to restore it to a v240... is it supported? should it work? don't know but i try! the problem is after restoring the filesystem, modify the vfstab, system file and install... (5 Replies)
Discussion started by: beta17
5 Replies
removable-media(9P)					   Kernel Properties for Drivers				       removable-media(9P)

NAME
removable-media - removable media device property DESCRIPTION
A device that supports removable media--such as CDROM, JAZZ, and ZIP drives--and that supports power management and expects automatic mounting of the device via the volume manager should export the boolean (zero length) property removable-media. This property enables the system to make the power state of the device dependent on the power state of the frame buffer and monitor. See the power.conf(4) discussion of the device-dependency-property entry for more information. Devices that behave like removable devices (such as PC ATA cards, where the controller and media both are removed at the same time) should also export this property. EXAMPLES
Example 1: removable-media Entry An example of a removable-media entry from the .conf file of a driver is shown below. # This entry keeps removable media from being powered down unless # the console framebuffer and monitor are powered down # removable-media=1; Example 2: Implementation in attach() Below is an example of how the entry above would be implemented in the attach(9E) function of the driver. xxattach(dev_info_t *dip, ddi_attach_cmd_t cmd) { ... if (ddi_prop_create(DDI_DEV_T_NONE, dip, DDI_PROP_CANSLEEP, "removable-media", NULL, 0)) != DDI_PROP_SUCCESS) goto failed; ... } ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
power.conf(4), pm(7D), attach(9E), detach(9E), ddi_prop_create(9F) Writing Device Drivers SunOS 5.10 15 Jun 2001 removable-media(9P)
All times are GMT -4. The time now is 10:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy