Sponsored Content
Full Discussion: Unix Imaging for Redundancy
Top Forums UNIX for Advanced & Expert Users Unix Imaging for Redundancy Post 7080 by mstevenson on Tuesday 18th of September 2001 01:36:34 PM
Old 09-18-2001
Lightbulb Unix Imaging for Redundancy

I'm trying to come up with an "imaging" type solution (a.k.a. Norton Ghost, Imagecast) with standard unix utils. I'd like to just image one of our FreeBSD servers so I can use the hot swap HD's. If one fails, I could slide in an exact duplicate HD and the server would be back up. I've tried just doing something with dd like: dd if=(hd1) of=(hd2) but it's not going to be that simple. I don't think dd is happy about not having a filesystem on hd2 (it's a blank unused drive). I have had luck with tarring up the whole drive, installing a minimal FreeBSD install on the second drive, renaming the kernel, dropping to single user mode, and then untarring, but that takes away the point of having something quick and ready to deploy.

I've also thought about running two mirrored drives (just like scsi+raid) but in an IDE system. Then having the secondary drive deactivated, but ready to go in case the first one fails. Then just tell the bios (through remote console interface) to boot from the slave drive. Thanks in advance for any ideas.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Imaging of SCO-UNIX box

Does anyone know of any good imaging tools that can be used to create an image of a Sco-Unix box? (2 Replies)
Discussion started by: gmrfh1
2 Replies

2. UNIX for Advanced & Expert Users

Port Redundancy

Dears, I have server has two port's(Enet0,Enet1) what I want as follows: Make the two port's has same IP address where, if the port Enet0 became down automaticly Enet1 become up :confused: . Amen (4 Replies)
Discussion started by: amen00
4 Replies

3. UNIX for Advanced & Expert Users

network redundancy with software

Here we want to implement the network redundancy on UNIX with the software. The two network interface cards are configured on the UNIX node,once one card is down or unnormal,the other can take over. Those aplications that used the tcp ,udp,multicast protocol can also been switched at the same... (2 Replies)
Discussion started by: Frank2004
2 Replies

4. UNIX for Dummies Questions & Answers

email redundancy between two servers

We have had some email outages in the last few months and my boss is asking is it worth going with one of those email redundancy/filtering sites. The thing is, we have a backup server on a remote location, so I am pretty sure we can set something up with what we have already. At the moment... (1 Reply)
Discussion started by: edzillion
1 Replies

5. Red Hat

Imaging solution?

Can anyone recommend an imaging solution for RedHat Linux that would allow base imaging with the ability to do incremental updates and encryption? I know Acronis has a version available, but it is rather pricey. Thanks. (0 Replies)
Discussion started by: here2learn
0 Replies

6. Solaris

dd - imaging drives. Oh boy!

Hello, Yes, it's me again. Running around getting this done! My current problem is I'm trying to image one drive 0 (/dev/dsk/c1t0d0s0) to drive 1 (/dev/dsk/c1t1d0s0). I know that drive1 came out of a Sun Server and it is a Sun drive. Solaris 10 recognized drive1 after the devfsadm command. The... (8 Replies)
Discussion started by: adelsin
8 Replies

7. AIX

VIO Redundancy

Hi Guys, I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards... ... (2 Replies)
Discussion started by: kkeng808
2 Replies

8. AIX

VIOS redundancy....basics...

Have been learning a lot off late and am a little unclear about the VIOS setup particularly with regards to redundancy. Would appreciate your help. My question is very basic. Lets say I have setup a VIOS and 3 LPARs on only one hdd (non scsi). On what do I setup the second VIOS? Could I for... (7 Replies)
Discussion started by: theaixeman
7 Replies

9. AIX

Can EtherChannel be a redundancy config?

I have one p5 server, no lpar, 2 physical network adapter, bundle as one EtherChannel. The two 2 physical network adapter connect to 2 network switches. How to make this as a redundancy config? Current is if one physical network adapter down, the seond one will go through the network. but if... (2 Replies)
Discussion started by: rainbow_bean
2 Replies
CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME
cd -- CDROM driver for the CAM SCSI subsystem DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com- mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags. QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver. The following is a list of quirks that the driver recognize. CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what size it is. This flag is currently unimplemented in the CAM cd driver. CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag. CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with multiple luns that are not a part of a changer. CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto- matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial read capacity command for LUN 0 of the changer through the changer scheduling code. CD_Q_10_BYTE_ONLY This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam- ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6 byte commands. FILES
/sys/cam/scsi/scsi_cd.c is the driver source file. SEE ALSO
cd(4), scsi(4) HISTORY
The cd manual page first appeared in FreeBSD 2.2. AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry <ken@FreeBSD.org>. BSD
September 2, 2003 BSD
All times are GMT -4. The time now is 12:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy