Veritas volume manager needed?

any one has veritas volume manager for unix systems? can you make me a copy? i'll pay you some money too? i need it for a practice only?
my email address is : [email protected]
thanks.

Getting an image to you will mean nothing if you don't get a license key anyway, and that you have to get from Veritas.

Similar Messages

IO issues on Red Hat Linux SAN storage and veritas volume manager

Oracle 11.0.1.7:
We recently moved from Solaris Sparc box to linux box and since then we are seeing IO issues. And it's quite obvious in iostat that the io goes as high as 100ms. So I am wondering if someone can advice if there are any mount options we need to give or if we need to use vxodmfs file system. Below are the details of this environment:
1. It's using veritas volume manager. (Same as solaris)
2. It's using vxfs file system (Same as solaris)
3. It's using veritas ODM libraries that helps us in IO. (Same as solaris)
4. SAN EMC storage (Same as solaris)
5. Mount options /dev/vx/dsk/orapdata1dg/oradata1vol1 on /u01/oradata type vxfs (rw,delaylog,largefiles,ioerror=mwdisable)
Edited by: user628400 on Aug 7, 2009 5:48 PM

Not sure if this really applies here but, from Metalink note 359515.1, parameters should be like follows on NAS devices:
Linux x86 #*
Mount options for Binaries
rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp, vers=3,
timeo=600, actimeo=0
Mount options for Oracle Datafiles
rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600
Linux x86-64 #*
Mount options for Binaries
rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,vers=3,
timeo=600, actimeo=0
Mount options for Oracle Datafiles
rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600
Give it a try and let us know....
Edited by: JRodriguez on Aug 10, 2009 6:35 PM

How to break Veritas Volume Manager mirrors and wipe disks

I have an old Solaris 10 server that is ready to be decommissioned. I would like to go in and break the Veritas Volume Manager mirrors and still be able to go in and wipe each of the two internal disks by using dd or something similar. Below is my Veritas Vol. Mgr. layout. I would greatly appreciate it if someone can post the exact commands (both for the Veritas Vol. Mgr. mirror break and the dd) I would need to run to perform the above tasks. I want to wipe the disks clean as to remove any company proprietary information prior to releasing the system.
Note: I will be logged into a remote console session to perform these actions as the system is in a datacenter and is located in a rack which does not have a monitor.
vxdisk list*
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced rootmirror rootdg online
vxdg list_
NAME STATE
rootdg enabled
vxprint -htr_
Disk group: rootdg
dg rootdg default default 0 1113432795.1025.dh22020
dm rootdisk c0t0d0s2 sliced 2632 71121402 -
dm rootmirror c0t1d0s2 sliced 2888 71124291 -
v appsvol - ENABLED ACTIVE 27262976 SELECT - fsgen
pl appsvol-01 appsvol ENABLED ACTIVE 27263493 CONCAT - RW
sd rootdisk-04 appsvol-01 rootdisk 41948280 27263493 0 c0t0d0 ENA
pl appsvol-02 appsvol ENABLED ACTIVE 27263493 CONCAT - RW
sd rootmirror-04 appsvol-02 rootmirror 41948280 27263493 0 c0t1d0 ENA
v rootvol - ENABLED ACTIVE 16779312 ROUND - root
pl rootvol-01 rootvol ENABLED ACTIVE 16779312 CONCAT - RW
sd rootdisk-01 rootvol-01 rootdisk 0 16779312 0 c0t0d0 ENA
pl rootvol-02 rootvol ENABLED ACTIVE 16779312 CONCAT - RW
sd rootmirror-01 rootvol-02 rootmirror 0 16779312 0 c0t1d0 ENA
v swapvol - ENABLED ACTIVE 8389656 ROUND - swap
pl swapvol-01 swapvol ENABLED ACTIVE 8389656 CONCAT - RW
sd rootdisk-02 swapvol-01 rootdisk 16779312 8389656 0 c0t0d0 ENA
pl swapvol-02 swapvol ENABLED ACTIVE 8389656 CONCAT - RW
sd rootmirror-02 swapvol-02 rootmirror 16779312 8389656 0 c0t1d0 ENA
v var - ENABLED ACTIVE 16779312 ROUND - fsgen
pl var-01 var ENABLED ACTIVE 16779312 CONCAT - RW
sd rootdisk-03 var-01 rootdisk 25168968 16779312 0 c0t0d0 ENA
pl var-02 var ENABLED ACTIVE 16779312 CONCAT - RW
sd rootmirror-03 var-02 rootmirror 25168968 16779312 0 c0t1d0 ENA
Thanks much for any assistance on this.

I would boot off of a cdrom and then simply use the format command to wipe the disks individually.
alan
http://www.sun.com/blueprints/0600/scrub.pdf

SVM equivalent command for veritas volume manager "VXEVAC" command

Hi All
I am working on a major migration project , where servers are heterogenous with part of servers with Veritas volume manager and rest with Solaris volume manager.
Migration is quite easy on Veritas servers using "VXEVAC COMMAND " i can easily move my data to new luns
But need to know any equivalent procedure in SVM. ..
all servers with latest solaris 10
Quick reply is highly appreciated.
Rgds
Md

Hello,
I�m not an expert on volume management, but maybe these considerations that come to my mind can help you to improve your performance:
1.- The interlace size of the striping. You should adjust the size of the striping to match the I/O requests made by the Operating System or by the database management software (is the data access in a raw mode?). For example, if the data access is made through normal ufs access, the stripping size should match the block size of the file system.
2.- Are those disks on different controlers? Maybe a saturation of the controler, of the bus, etc... could slow down your I/O read/writes.
Bye,
jmiturbe

Veritas Volume Manager Upgrade Hints?

We are considering upgrading from Veritas VM 3.0.4 on Solaris 2.6 to 3.1 on Solaris 2.6.
o Has anyone else gone through this upgrade?
o Did you follow the steps in the "Veritas Volume Manager 3.1 Installation Guide" with success?
I notice that under the section "Upgrading VxVM Only", it asks you to use "pkgrm" to remove "VRTSvmsa", followed by "pkgadd" of "VRTSvxvm". Is this an error? That is, why are we removing "vmsa", but then installing "vxvm"? The next paragraph (in the Veritas installation document) states: "Using the pkgadd command, install any or all of the following additional packages: VRTSvmsa, VRTSvmdoc, VRTSvmman, and VRTSvmdev".
Any help to make this upgrade smooth, is appreciated.
Thanks in advance.

The steps mentioned in the are correct ..vmsa is storage administrator pkg and needs to be upgraded along with vxvm - volume manager binaries .The veritas recommanded path for upgrading is removing the old pkg and adding the new ones so nothing wrong in it.
Hemant
http://www.adminschoice.com
We are considering upgrading from Veritas VM 3.0.4 on
Solaris 2.6 to 3.1 on Solaris 2.6.
o Has anyone else gone through this upgrade?
o Did you follow the steps in the "Veritas Volume
Manager 3.1 Installation Guide" with success?
I notice that under the section "Upgrading VxVM Only",
it asks you to use "pkgrm" to remove "VRTSvmsa",
followed by "pkgadd" of "VRTSvxvm". Is this an error?
That is, why are we removing "vmsa", but then
installing "vxvm"? The next paragraph (in the
Veritas installation document) states: "Using the
pkgadd command, install any or all of the following
additional packages: VRTSvmsa, VRTSvmdoc, VRTSvmman,
and VRTSvmdev".
Any help to make this upgrade smooth, is appreciated.
Thanks in advance.

Veritas Volume Manager errors

I am running a Solaris Ultrasparc Enterprise 450 Server with Solaris 8 operating system. This past weekend, I received the following errors relating to Volumen Management on our disks.
I need help in understanding what happened and how to fix it. The only thing I found was that 2-3 filesystems were over 90% and I was able to have files removed, and thus reduce the capacity by 20%. But I still would like to know what happened and how to prevent these errors from happening again. I am new to storage management.
"Failures have been detected by the VERITAS Volume Manager: failed disks: disk04 failed plexes: vol02-02 vol04-02 vol06-P04 These volumes are still usable, but the the redundancy of those volumes is reduced. Any RAID-5 volumes with storage on the failed disk may become unusable in the face of further failures. VERITAS Volume Manager is preparing to relocate for diskgroup rootdg. Saving the current configuration in: /etc/vx/saveconfig.d/rootdg.060312_032923.mpvsh Relocation was not successful for subdisks on disk disk04 in volume vol04 in disk group rootdg. No replacement was made and the disk is still unusable."
Please advise. Thanks.

Out of the 11 or 12 disk drives on the system in question, disk# 8 (c3t1d0) was labeled "unformatted", when I ran the format, analyze, and read commands. Does this mean the disk can be re-formatted or replaced? I will dig into the documenation in the meantime.
This is the result I get when I run the vxprint -g rootdg -thf command:
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
V NAME RVG KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
dg rootdg default default 0 1043163330.1025.cstep2
dm disk01 c2t2d0s2 sliced 4711 35358848 -
dm disk02 c2t3d0s2 sliced 4711 35358848 -
dm disk03 c3t0d0s2 sliced 4711 35358848 -
dm disk04 - - - - NODEVICE
dm disk05 c3t2d0s2 sliced 4711 35358848 -
dm disk06 c3t3d0s2 sliced 4711 35358848 -
v vol01 - ENABLED ACTIVE 24576000 SELECT - fsgen
pl vol01-01 vol01 ENABLED ACTIVE 24577792 CONCAT - RW
sd disk01-01 vol01-01 disk01 0 24577792 0 c2t2d0 ENA
pl vol01-02 vol01 ENABLED ACTIVE 24577792 CONCAT - RW
sd disk02-01 vol01-02 disk02 0 24577792 0 c2t3d0 ENA
v vol02 - ENABLED ACTIVE 15360000 SELECT - fsgen
pl vol02-01 vol02 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk03-01 vol02-01 disk03 0 15361120 0 c3t0d0 ENA
pl vol02-02 vol02 DISABLED NODEVICE 15361120 CONCAT - RW
sd disk04-01 vol02-02 disk04 0 15361120 0 - NDEV
v vol03 - ENABLED ACTIVE 15360000 SELECT - fsgen
pl vol03-01 vol03 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk05-01 vol03-01 disk05 0 15361120 0 c3t2d0 ENA
pl vol03-02 vol03 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk06-01 vol03-02 disk06 0 15361120 0 c3t3d0 ENA
v vol04 - ENABLED ACTIVE 15360000 SELECT - fsgen
pl vol04-01 vol04 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk03-02 vol04-01 disk03 15361120 15361120 0 c3t0d0 ENA
pl vol04-02 vol04 DISABLED NODEVICE 15361120 CONCAT - RW
sd disk04-02 vol04-02 disk04 15361120 15361120 0 - RLOC
v vol05 - ENABLED ACTIVE 15360000 SELECT - fsgen
pl vol05-01 vol05 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk05-02 vol05-01 disk05 15361120 15361120 0 c3t2d0 ENA
pl vol05-02 vol05 ENABLED ACTIVE 15361120 CONCAT - RW
sd disk06-02 vol05-02 disk06 15361120 15361120 0 c3t3d0 ENA
v vol06 - ENABLED ACTIVE 15360000 SELECT - fsgen
pl vol06-03 vol06 ENABLED ACTIVE 15360000 CONCAT - RW
sv vol06-S01 vol06-03 vol06-L01 1 10781056 0 2/2 ENA
sv vol06-S02 vol06-03 vol06-L02 1 4578944 10781056 1/2 ENA
v vol06-L01 - ENABLED ACTIVE 10781056 SELECT - fsgen
pl vol06-P01 vol06-L01 ENABLED ACTIVE 10781056 CONCAT - RW
sd disk01-03 vol06-P01 disk01 24577792 10781056 0 c2t2d0 ENA
pl vol06-P02 vol06-L01 ENABLED ACTIVE 10781056 CONCAT - RW
sd disk02-03 vol06-P02 disk02 24577792 10781056 0 c2t3d0 ENA
v vol06-L02 - ENABLED ACTIVE 4578944 SELECT - fsgen
pl vol06-P03 vol06-L02 ENABLED ACTIVE 4578944 CONCAT - RW
sd disk03-04 vol06-P03 disk03 30722240 4578944 0 c3t0d0 ENA
pl vol06-P04 vol06-L02 DISABLED RECOVER 4578944 CONCAT - RW
sd disk05-03 vol06-P04 disk05 30722240 4578944 0 c3t2d0 ENA

Solaris upgrade with Veritas Volume Manager

I have to upgrade Solaris from 7 to 8 on a server which has Veritas Volume Manager. OK, I already found the necessary information to make this upgrade, but I have not found any answers on my problem.
It is quite possible that after VVM was installed, some of the filesystems like /, /opt, /usr or /var were increased or that additional filesystems were added on the rootdisk. This will prevent the upgrade_start to run correctly. One way to overcome this problem is to boot the machine in single-user mode, create all the root filesystems as standard ufs filesystems on a free disk with the same size as the VVM filesystems and then use ufsdump to copy all data over. When that is done, install a bootblock on the new disk and boot the machine from this disk. Then, start the Solaris upgrade. The problem with this is that when there is no free disk available, then I clearly have a problem.
Does anyone have experience with this or has a better plan ?
Should I completely de-install VVM or is it enough to convert all rootfilesystems to ufs filesystems ?
Please reply to me individually at [email protected]
Thanks,
Bruno

There are more things that you need to do.
Read veritas install guide -- it has a pretty good section of what needs to be done.
http://www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software/VERITAS_Volume_Manager/

Multiple LUN support with Veritas Volume Manager

I want to encapsulate some disks in a HITACHI disk array using Veritas Volume Manager 3.1 and therefore need DMP active.
DMP only sees the first lun 0, but doesn't see the other lun's. How can I make DMP to see the other lun's ?
Please reply to me individually at [email protected]
Thanks,
Bruno

There are more things that you need to do.
Read veritas install guide -- it has a pretty good section of what needs to be done.
http://www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software/VERITAS_Volume_Manager/

Veritas volume manager for solaris 10

Hi All
which version veritas volume manager will support solaris 10 06/06.
can you just update a link for reference
Regards
RPS

Hello,
we are currently using solaris 9 with veritas volume manager 3.5.So i would like to know if i upgrade to solaris 10 06/06.whether i can use 3.5 or not.
Using the Veritas (Symantec) support site, I have found the following document
VERITAS Storage Solutions 3.5 Maintenance Pack 4 for Solaris
http://seer.support.veritas.com/docs/278582.htm
The latest supported version listed for VxVM 3.5 with MP4 applied is Solaris 9. That means the answer is NO.
I understand that searching the Veritas knowledge base might be tough and time consuming, but it's their product ...
Michael

Veritas volume manager on Solaris 10(X86)

is it possible to install veritas volume manager on solaris 10 (x86) ?

You should check the supported operating system matrix for Storage Foundation to see what they support. But yes, Solaris x64 is supported. I don't think they support 32-bit x86.
Darren

WebStart Flash and Veritas Volume Manager

I would like to use WebStart Flash for backup of the system
disk. The goal is to be able to recover the system disk rapidly.
It works perfectly for systems without Veritas Volume
Manager on the system disk.
However, if Veritas Volume Manager is installed and used
for mirroring the root disk, the system is not able to boot using
WebStart Flash. This is probably because the "private region"
of the disk is not included in the flash archive.
Does anybody have a solution for this, or does any of
you successfully combine WebStart Flash and Veritas
Volume Manager?
I use Jumpstart and the install_type is configured to
flash_install.
The question was also asked in the newsgroup
comp.unix.solaris.
Rgds,
Henrik

For many reasons, today you cannot save the VxVM
private region information as an implicit part of a
flash archive. The procedure would likely be to
unencapsulate the root drive, create the flash archive,
then re-encapsulate the root drive. This is an ugly
procedure and may cause more pain than it is worth.
When a root disk is encapsulated, an entry is put
into the /etc/system file which says to use the VxVM
or SVM logical volume for the rootdev rather than
the actual device from which the system was originally
booted. When you create a flash archive, this modification
to the /etc/system is carried along. But, when you install
it on a new system which doesn't have VxVM properly
installed already (a chicken-and-the-egg problem)
then the change of the rootdev to the logical volume
will fail. The result is an unbootable system (without
using 'boot -a' and pointing to a different /etc/system
file like /dev/null).
The current recommended process is to use a prototype
system which does not have an encapsulated root
to create the flash archive.
VxVM also uses the ELM license manager which will
tie the VxVM runtime license to the hostid. This makes
moving flash archives with VxVM to other machines
impractical or difficult.
The long term solution would be to add logical volume
management support to the JumpStart infrastructure.
I'm not counting on this anytime soon :-(
-- richard

Solstice DiskSuite or Veritas Volume Manager

With regards to Solaris 8,
I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

apologies my original post was incorrectly posted to the wrong forum.

How to install veritas volume manager in zones

Hi folks,
I wanna learn veritas volume manager. Is it possible to install VXVM packages on solaris Zones? how can i create virtual disk? Is there any simulator for VXVM for solaris. ?
Thanks in advance.

See [http://sfdoccentral.symantec.com/sf/5.0/solaris/html/sf_install/ig_ch_install_sol_vm_fs4.html|http://sfdoccentral.symantec.com/sf/5.0/solaris/html/sf_install/ig_ch_install_sol_vm_fs4.html]
"On Solaris 10, the packages must be installed while in the global zone"

DiskSuite or Veritas Volume Manager

With regards to Solaris 8,
I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

Hi,
You've already got volume manager, so why not use it? If you install ODS as well as VXVM, you're just complicating the setup of the machine.
You've got veritas already installed, just use this!

Poor Veritas Volume Manager performance?

I apologize if this is a basic question.
Environment:
Solaris 8
Veritas Volume Manager 3.0.4
Oracle 9iR2
Based on Oracle's recommendation, I turned on the mincache=direct,convosync=direct,largefiles options for the file system Oracle will reside. Then I install Oracle 9iR2. I notice the installation process takes considerably longer than before when I installed it on the other identical machine(E250, dual CPUs, 1280M RAM, RAID 5 with no logging under Vxvm).
Other than the mounting options shown above, I don't see any difference as far as Vxvm is concerned. The other fine system has option: mincache=closesync,largefiles set for the file system.
Can someone shed some lights on this as to how to identify what went wrong?
Appreciated!

Jeffrey,
thanks for the info.
Here is the output of my iostat -En: (they, including the boot disk, all have one Soft Error/Illegal Request)
# iostat -En
c0t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST318404LSUN18G Revision: 4207 Serial No: 3BT0XZ3J000
02105
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t6d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA Product: XM6201TASUN32XCD Revision: 1103 Serial No: 12/12/97
Size: 18446744073.71GB <-1 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t8d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST318404LSUN18G Revision: 4207 Serial No: 3BT10VP9000
02109
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t9d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST318404LSUN18G Revision: 4207 Serial No: 3BT10ZNG000
07108
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t10d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAJ3182M SUN18G Revision: 0804 Serial No: 01P08417
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t11d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAJ3182M SUN18G Revision: 0804 Serial No: 01P13137
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t12d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST318404LSUN18G Revision: 8507 Serial No: 3BT0KZRQ000
07051
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0

Veritas volume manager needed?

Similar Messages

Maybe you are looking for