06-02-2005
Quote:
Originally Posted by frustrated1
no problem..
I could accept 20 mins downtime per day.
H/W not great - no raid controller that I know of..
Compaq Proliant DL380 P6 1390 MHz
I would like for the following:
2 disks.
1 is main disk (root disk)
1 is mirror of the root disk. This should be mirror all of the time.
ie. if root disk fails then mirror will be in sync up until time of failure.
I can then replace failed disk and new disk will re-sync with mirror.
Is this possible? do i need some software constantly updating the mirror with any changes on the root disk?
Would I be better just syncing once a day?
Its a server that will mainly have scripts on it - I could live with the data being 24 hours old if I have to.
Hold on guys, DL380 comes with hardware mirroring and hot-plug. Better go with it.
Tom
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know how to force these rogue logical volumes to mirror to there respective disks?
DISK:Logical Volumes
03:cw_p05,cw_p01_01,cw_p01_02,lv00
09:cw_p05,cw_p01_01,cw_p01_02
04:cw_p01_phyldbs,cw_p01_03,cw_op01_01,cw_od01
10:cw_p01_phyldbs,cw_p01_03,cw_op01_01 (1 Reply)
Discussion started by: Optimus_P
1 Replies
2. Solaris
Hello,
I need to get some details from my server like Internal hard disk details for my UNIX (Solaris 9) server like whether OS is mirrored or not, what type of mirror is used. Which hard disk are used for mirror ?
Regards (1 Reply)
Discussion started by: adel8483
1 Replies
3. Solaris
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies
4. Solaris
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies
5. Emergency UNIX and Linux Support
Hi guys.
I am gonna buy a dedicated server and make it a public mirror for some distributions.
but how much RAM, Hard Disk, Band Width, ... will suffice? It will be a mirror for CentOS and Ubuntu both. (3 Replies)
Discussion started by: majid.merkava
3 Replies
6. Solaris
Hi!
I would also like to know if I need first to create a pool before I can mirror my disks inside that pool.
My first disk is c7t0d0s0 and my second disk is c7t2d0s0 as seen in the figure below.
I would create a pool named rpool1 for this 2 disks.
# zpool create rpool1 c7t0d0p0 c7t2d0p0 ... (18 Replies)
Discussion started by: CarlosP
18 Replies
7. AIX
Is there any sort of best practice as to how many disks should be assigned to a VIO server? I currently have around 190-ish. All of my VIO servers can see those disks. Can anyone tell me how many you have on your VIO servers? (3 Replies)
Discussion started by: kah00na
3 Replies
8. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
9. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
LEARN ABOUT OSF1
volreattach
volreattach(8) System Manager's Manual volreattach(8)
NAME
volreattach - Reattaches disk drives that have once again become accessible
SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...]
/usr/sbin/volreattach -c accessname
OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the
failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the
name of the disk group and disk media name at which the disk can be reattached is displayed.
DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment.
This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical
Storage Manager is started, causing disks to enter the failed state.
If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the
reattach happens before any volumes on the disk are started.
The volreattach command is called from the voldiskadm menus as part of disk recovery.
The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching
disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists.
EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned.
SEE ALSO
volintro(8), voldiskadm(8), volrecover(8)
volreattach(8)