Sponsored Content
Operating Systems Linux SuSE Raid software besides Veritass Post 57889 by xtmeisel on Tuesday 9th of November 2004 12:02:39 PM
Old 11-09-2004
Raid software besides Veritass

Hello Lunix people,

I am looking for Raid software or solution besides Veritas. Veritas has some great software but are way too costly. Does anyone know of good raid software that but NOT Veritas. I need the funcations but not the cost.

[Note: No email permitted in posts- Neo]
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Software RAID ...

Hi all, I m just trying using software RAID in RHEL 4, without problem , then i wanna simulate if disk 1 is fail (thereis an bootloader), i plug off my 1st disk. My problems is the second disk cannot boot? just stuck in grub, the computer is hang. Sorry for poor concept in RAID? I use a RAID 1.... (0 Replies)
Discussion started by: blesets
0 Replies

2. HP-UX

Software RAID (0+1)

Hi! A couple of months ago a disk failed in our JBOD cabinett and I have finally got a new disk to replace it with. It was a RAID 0 so we have to create and configure the whole thing again. First we thought of RAID 1+0 but it seems you can't do this with LVM. If you read my last thread, you can... (0 Replies)
Discussion started by: hoff
0 Replies

3. Linux

Software RAID on Linux

Hey, I have worked with Linux for some time, but have not gotten into the specifics of hard drive tuning or software RAID. This is about to change. I have a Dell PowerEdge T105 at home and I am purchasing the following: 1GBx4 DDR2 ECC PC6400 RAM Rosewill RSV-5 E-Sata 5 bay disk enclosure... (6 Replies)
Discussion started by: mark54g
6 Replies

4. Red Hat

Software RAID doubt

hi friends, I am having issues with adding a spare device to a failed array. I have created RAID 1 with 3 partitions using mdadm command. Later I added a spare with mdadm --add /dev/md0 /dev/sdb6 This works fine and when I check this with mdadm --detail command it just sits there as a spare... (7 Replies)
Discussion started by: saagar
7 Replies

5. Filesystems, Disks and Memory

Software RAID

Hello, My company has inherited a Centos based machine that has 7 hard drives and a software based raid system. Supposedly one of the drives has failed. I need to replace the hardrive. How can I about telling which hard drive needs replacing? I have looked in the logs and there clearly is a... (5 Replies)
Discussion started by: mojoman
5 Replies

6. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

7. Red Hat

Software RAID configuration

We have configured software based RAID5 with LVM on our RHEL5 servers. Please let us know if its good to configure software RAID on live environment servers. What can be the disadvantages of software RAID against hardware RAID (4 Replies)
Discussion started by: mitchnelson
4 Replies

8. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

9. Solaris

Hardware to software RAID migration

We have hardware RAID configured on our T6320 server and two LDOMs are running on this server. One of our disk got failed and replaced. After replacemnt the newly installed disk not detected by RAID controlled so Oracle suggested to upgrade the REM firmware. As this is the standalone production... (0 Replies)
Discussion started by: rock123
0 Replies
vxtune(1M)																vxtune(1M)

NAME
vxtune - adjust Veritas Volume Replicator and Veritas Volume Manager tunables SYNOPSIS
vxtune [-r] vxtune [-r] tunable vxtune [-r] tunable value DESCRIPTION
The vxtune utility manages the various memory tunables that are used by Veritas Volume Replicator (VVR). It can also be used to change the value of the volpagemod_max_memsz tunable that is used by the instant snapshots feature of Veritas Volume Manager (VxVM). No other VxVM tunables are currently tunable using vxtune. You can use vxtune to display, set or change the memory tunables that are used by VVR. To maximize VVR performance, you can use this util- ity to experiment with different values before deciding on the optimal tunable values. The main advantage of using vxtune to change tunable values is that the new values are available immediately without needing to reboot the system. When invoked with no arguments, vxtune displays a list of the tunables whose values may be displayed or set. When invoked with the name of a supported tunable as the argument, vxtune displays the value of that tunable. When invoked with the name of a supported tunable and a value as arguments, vxtune attempts to set the tunable to that value. The specified value can take the following prefixes as base specifiers: 0 Value is in octal. 0x Value is in hexadecimal. By default, decimal is assumed. The specified value can take the following suffixes as unit multipliers: g or G The specified value is in gigabytes. k or K The specified value is in kilobytes. m or M The specified value is in megabytes. By default, the units are assumed to be bytes. The values of the following memory tunables may be displayed or set: vol_max_nmpool_sz Maximum memory that will be used by VVR on a secondary to hold the write requests coming from the primary. This memory is sys- tem-wide and restricts all secondary RVGs on the system. It may also be useful to increase this tunable if multiple Secondary RVGs are present on the system. vol_max_rdback_sz Maximum memory that will be used by VVR, when write requests are being read back from the SRL. You may need to increase this tun- able if you have multiple asynchronous RLINKS in one or more RVGs. vol_max_wrspool_sz Used in the clustered version of VVR. vol_min_lowmem_sz Minimum Threshold of available VVR memory needed to keep the write requests in memory on the primary RVG to send it to secondary. If available VVR memory is less than this threshold, write requests are freed early so that readbacks can be performed later. This tunable is used by asynchronous RLINKs. vol_rvio_maxpool_sz Maximum memory requested from the system by VVR for internal purposes. This tunable has a direct impact on the performance of VVR as it prevents one I/O operation from using all the memory in the system. The value of vol_rvio_maxpool_sz must be at least 10 times greater than the value of the maximum I/O size. volpagemod_max_memsz Maximum memory, measured in kilobytes, that is allocated for caching FastResync and cache object metadata by the instant snap- shots feature of VxVM. This tunable has a default value of 6144KB(6MB) of physical memory. The memory allocated for this cache is exclusively dedicated to it. It is not available for other processes or applications. Setting the value of volpagemod_max_memsz below 512KB fails if cache objects or volumes that have been prepared for instant snap- shot operations are present on the system. If you do not use the FastResync or DRL features that are implemented using a version 20 DCO volume, the value of volpage- mod_max_memsz can be set to 0. However, if you subsequently decide to enable these features, you can use vxtune to change the value to a more appropriate one. OPTIONS
-r (Raw) By default, tunable values are displayed in kilobytes. This option causes values to be displayed in bytes. EXAMPLES
Display the tunable parameters that vxtune supports: vxtune Display the value of vol_min_lowmem_sz on a host: vxtune vol_min_lowmem_sz Modify the value of vol_min_lowmem_sz to 2 megabytes on a host: vxtune vol_min_lowmem_sz 2M EXIT CODES
The vxtune utility exits with a non-zero status if the attempted operation fails. A non-zero exit code is not a complete indicator of the problems encountered but denotes the first condition that prevented further execu- tion of the utility. NOTES
The vxtune command only affects the tunable values on the host on which it is run. If required, you must run the command separately on each host for which you want to change the tunable values (for example, for the log-owner node and any of its failover nodes in a cluster). Values that have been specified using vxtune are persistent across reboots. SEE ALSO
vrport(1M), vxmemstat(1M), vxsnap(1M) Veritas Volume Replicator Configuration Notes Veritas Volume Manager Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxtune(1M)
All times are GMT -4. The time now is 12:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy