Sponsored Content
Top Forums UNIX for Dummies Questions & Answers what is disk mirroring in unix? Post 1712 by Neo on Monday 26th of March 2001 04:51:04 PM
Old 03-26-2001
In a nutshell, disk mirroring is when two disks are written with the same data at the same time. So, when you have critical data (critical SQL databases are a good example) the disks are often mirrored so if one disk crashes, a minimal amount of data is lost. You are correct, disk mirroring is related to system backup and recovery. Usually, backups are performed daily for critical systems. Disk mirroring provides for disk crash protection between backups, in almost real time.

BTW: Does anyone know of any good mirroring software for Linux? I think I'll mirror this site in the future! Many someday, the UNIX For Dummies archives will be 'critical' for users Smilie
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Disk Mirroring?? have any idea???

After reading some books, I came across this idea of having a duplicate of your current hard drive on another second hard drive so that if the first hard drive happens to crash, the system can be up and running in quickly now, is there anybody in here who uses this method at work?? If there is,... (3 Replies)
Discussion started by: IMPORTANT
3 Replies

2. UNIX for Dummies Questions & Answers

Disk mirroring under RedHat 8

I would like to build a new box that has the disk mirrored to another IDE disk on a different channel. Does anyone know if a RAID controller like the Promise is supported under RedHat 8, or should I use a software RAID. (1 Reply)
Discussion started by: 98_1LE
1 Replies

3. Shell Programming and Scripting

Disk mirroring

Good Morning :) I have a new challenge to solve, I am going to write a new backup disk mirroring script. The current one, whcih is useing 'dd' caused some stalled systems :( Currently I am in the phase of experimenting with different methods, I was thinking about dump/restore afio/cpio or... (3 Replies)
Discussion started by: malcom
3 Replies

4. Solaris

Disk mirroring

Hi I have two raw disk that I want to mirror and then create soft partition on that. Could someone please help in the steps required c0t1d0 c0t0d0 Thanks Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies

5. Solaris

Help !! disk Mirroring

Hi I have a Sunfire X4100 box with a 4 disk Chassis (although I only have 2 disks in it). I have been asked to add two more disks into the chassis so that I can mirror the original two using SVM .....Ive read through a couple of SVM docs but am finding it a little confusing, and if any of you... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

6. UNIX for Advanced & Expert Users

Mirroring Disk Geometry

How can one mirror disk geometry from one hard disk to another in Solaris. Is disk snapshot same as a mirror? Pls explain. (3 Replies)
Discussion started by: lexusujx
3 Replies

7. Solaris

Solaris 10 Disk Mirroring

Has anyone managed to set up disk mirroring in Solaris 10 yet? If so can you point me in the direction of some useful documentation please. Cheers (25 Replies)
Discussion started by: korfnz
25 Replies

8. Solaris

Disk Mirroring on solaris 5.8

Hi Friends, I am having Sun Solaris 5.8 OS installed having 2 different size hard disk, sizes are c0t0d0s0(160 GB) and c0t2d0s0 (40GB). I have installed Sun Solaris 5.8 OS in c0t0d0s0 (160GB) harddisk. I have configured all the parameters required for disk mirroring. But when executing... (4 Replies)
Discussion started by: Vijayakumarpc
4 Replies

9. Solaris

disk mirroring

hi every body I'm new to solaris and I need your help in how to configure disk mirroring for 4 hard disks so that two of them will be replica to the other two ...??? Thanxx (7 Replies)
Discussion started by: mm00123
7 Replies

10. Red Hat

Disk Mirroring

Hi, How to identify whether the disk is being mirrored or not in RHEL (2 Replies)
Discussion started by: gsiva
2 Replies
DISKLIST(5)						   File formats and conventions 					       DISKLIST(5)

NAME
disklist - List of partitions to back up for Amanda DESCRIPTION
The disklist file determines which disks will be backed up by Amanda. The file usually contains one line per disk: hostname diskname [diskdevice] dumptype [spindle [interface] ] All pairs [ hostname diskname ] must be unique. Lines starting with # are ignored, as are blank lines. The fields have the following meanings: hostname The name of the host to be backed up. If diskdevice refers to a PC share, this is the host Amanda will run the Samba smbclient program on to back up the share. diskname The name of the disk (a label). In most case, you set your diskname to the diskdevice and you don't set the diskdevice. If you want multiple entries with the same diskdevice, you must set a different diskname for each entry. It's the diskname that you use on the commandline for any Amanda command. Look at the example/disklist file for example. diskdevice Default: same as diskname. The name of the disk device to be backed up. It may be a full device name, a device name without the /dev/ prefix, e.g. sd0a, or a mount point such as /usr. It may also refer to a PC share by starting the name with two (forward) slashes, e.g. //some-pc/home. In this case, the program option in the associated dumptype must be entered as GNUTAR. It is the combination of the double slash disk name and program GNUTAR in the dumptype that triggers the use of Samba. dumptype Refers to a dumptype defined in the amanda.conf file. Dumptypes specify backup related parameters, such as whether to compress the backups, whether to record backup results in /var/lib/dumpdates, the disk's relative priority, etc. spindle Default: -1. A number used to balance backup load on a host. Amanda will not run multiple backups at the same time on the same spindle, unless the spindle number is -1, which means there is no spindle restriction. interface Default: local. The name of a network interface definition in the amanda.conf file, used to balance network load. Instead of naming a dumptype, it is possible to define one in-line, enclosing dumptype options within curly braces, one per line, just like a dumptype definition in amanda.conf. Since pre-existing dumptypes are valid option names, this syntax may be used to customize dumptypes for particular disks. A line break must follow the left curly bracket. For instance, if a dumptype named normal is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype: hostname diskname [ diskdevice ] { normal holdingdisk never } [ spindle [ interface ] ] The { must appear at the end of a line, and the } on its own line possibly followed by the spindle and interface. SEE ALSO
amanda(8), amanda.conf(5) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 DISKLIST(5)
All times are GMT -4. The time now is 03:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy