Sponsored Content
Operating Systems Solaris Why Veritas is not used for root file system. Post 302424450 by Rowley on Tuesday 25th of May 2010 08:57:19 AM
Old 05-25-2010
SDS or SVM is easy to set up either manually or through jumpstart, troubleshoot, maintain, and is the de-facto software disk manager solution on Solaris, and it works perfectly well.

Why bother going through the bother of encapsulating the root disk with VxVM? Save it for your data volumes....

My ha-pennies worth, anyway.
This User Gave Thanks to Rowley For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas File System

Hello All. I have a question concerning VFS (Veritas File System). I are attempting to upgrade Solaris 2.6 UFS to the VFS (Veritas File System). We use Veritas to perform all our backups. I have been unable to find any documentation on SUN's or Veritas's website. The server's are SUN 4500 and... (3 Replies)
Discussion started by: KaEH
3 Replies

2. Filesystems, Disks and Memory

veritas vcs \ file system docs req.

hi if anyone has docs (corporate internals on how to setup vcs mfor example, especially with Veritas VM, pleas let me know..i need exposure experience in this area of Enterprise Administration thanks jasmine (SCSA & MCSE) (2 Replies)
Discussion started by: jasmine_uk
2 Replies

3. HP-UX

Root File system Space

Hi I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine? Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 ... (2 Replies)
Discussion started by: cgege
2 Replies

4. Solaris

Veritas root disk mirroring

Hi there, My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct. 1. Break the sub-disks, plexes of the root mirror. 2. Remove the sub-disks,plexes of the root mirror. 3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies

5. Solaris

swap space in veritas file system

hi every one , i know how to add swap space in ufs file system. but i m facing problem in veritas file system . i wants to know how will i create swap or add new swap space in existing swap space . Note: disk under veritas volume manager control . please help me to solve this issue . (5 Replies)
Discussion started by: samy123
5 Replies

6. UNIX for Dummies Questions & Answers

Root File System

Hi, Please someone tell me, what are the contents of root file sysytem? and significance of it, what are all possible ways to mount root file system? (5 Replies)
Discussion started by: laxmi Sharma
5 Replies

7. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

8. Solaris

restore dump from veritas format using ufs file system

hi all i have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. (3 Replies)
Discussion started by: nikhil kasar
3 Replies

9. Solaris

how to restore backup from veritas vm in ufs file system

Hi all I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies

10. UNIX for Dummies Questions & Answers

Question on Veritas file system..

Hi, I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server. When I do iostat -E. I see this. sd0... (4 Replies)
Discussion started by: samnyc
4 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 02:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy