Solaris 10 Live Upgrade with Veritas Volume Manager 4.1

What is the latest version of Live Upgrade?
I need to upgrade our systems from Solaris 8 to Solaris 10. All our systems have Veritas VxVM 4.1, with the O.S disks encapsulated and mirrored.
Whats the best way to do the Live Upgrade. Anyone have clean documents for the same ?

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/

Similar Messages

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/

Solaris Live Upgrade with NGZ

Hi
I am trying to perform a Live Upgrade on my 2 Servers, both of them have NGZ installed and those NGZ are on an diifferent Zpool not on the Rpool and also are on an external disk.
I have installed all the latest patches required for LU to work properly but when i perform an <lucreate> i start having problems... (new_s10BE is the new BE i'm creating)
On my 1st Server:
I have a Global zone and 1 NGZ named mddtri.. This is the error i am getting:-
ERROR: unable to mount zone <mddtri> in </.alt.tmp.b-VBb.mnt>.
zoneadm: zone 'mddtri': zone root /zoneroots/mddtri/root already in use by zone mddtri
zoneadm: zone 'mddtri': call to zoneadm failed
ERROR: unable to mount non-global zones of ABE: cannot make bootable
ERROR: cannot unmount </.alt.tmp.b-VBb.mnt/var/run>
ERROR: unable to make boot environment <new_s10BE> bootable
On my 2nd Server:
I have a Global zone and 10 NGZ. This is the error i am getting:-
WARNING: Directory </zoneroots/zone1> zone <global> lies on a filesystem shared netween BEs, remapping path to </zoneroots/zone1/zone1-new_s10BE>
WARNING: Device <zone1> is shared between BEs, remmapping to <zone1-new_s10BE>
*.This happens for all the NGZ running.*
Duplicating ZFS datasets from PBE to ABE.
ERROR: The dataset <zone1-new_s10BE> is on top of ZFS pool. Unable to clone. Please migrate the zone to dedicated dataset.
ERROR: Unable to create a duplicate of <zone1> dataset in PBE. <zone1-new_s10BE> dataset in ABE already exists.
Reverting state of zones in PBE <old_s10BE>
ERROR: Unable to copy file system from boot environment <old_s10BE> to BE <new_s10BE>
ERROR: Unable to populate file systems from boot environment <new_s10BE>
Help, I need to sort this out a.s.a.p!

Hi,
I have the same problem with an attached A5200 with mirrored disks (Solaris 9, Volume Manager). Whereas the "critical" partitions should be copied to a second system disk, the mirrored partitions should be shared.
Here is a script with lucreate.
#!/bin/sh
Logdir=/usr/local/LUscripts/logs
if [ ! -d ${Logdir} ]
then
echo ${Logdir} existiert nicht
exit
fi
/usr/sbin/lucreate \
-l ${Logdir}/$0.log \
-o ${Logdir}/$0.error \
-m /:/dev/dsk/c2t0d0s0:ufs \
-m /var:/dev/dsk/c2t0d0s3:ufs \
-m /opt:/dev/dsk/c2t0d0s4:ufs \
-m -:/dev/dsk/c2t0d0s1:swap \
-n disk0
And here is the output
root@ahbgbld800x:/usr/local/LUscripts >./lucreate_disk0.sh
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
INFORMATION: Unable to determine size or capacity of slice </dev/md/RAID-INT/dsk/d0>.
ERROR: An error occurred during creation of configuration file.
ERROR: Cannot create the internal configuration file for the current boot environment <disk3>.
Assertion failed: *ptrKey == (unsigned long long)_lu_malloc, file lu_mem.c, line 362<br />
Abort - core dumped

Server up grade with Veritas Volume Manager.

Hello all,
First: I have SunUltra 420R with OS solaris 8, Veritas Volume Manger version 3.5 + Storage A5000 connect to it.
Now my question is: If I am going to up grade this server OS from 8 to 9, then will it just work? or some things that will break? Or any things that I sould know before the upgrade? So any advise the list will appreciated.
Thanks,
C-

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/

Sun QFS cluster file system with Veritas Volume Manager

Hi,
Can someone confirm whether it is possible to create a Sun QFS cluster file system (for Oracle RAC datafiles) using a VxVM volume?
Or must we use Solaris Volume Manager with QFS?
Thinking of storing the static part of the Oracle RAC DB on VxVM raw devices, and the dynamic part on a QFS file system to avoid the overhead of constantly adding new raw devices when i want to create datafiles.
Thanks,
Steve

Steve,
No, shared QFS is only supported on Solaris Volume Manager. I've not heard of any plans to test it on VxVM.
Why not keep the static parts of the DB on raw SVM devices? Why keep them on raw devices at all?
Tim
---

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.

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!

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

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 4.0 with Sun StorEdge 3310 D

I am running into a problem. The vxconfigd deamon always dump core when rebooting.
Our environment is listed below.
OS environemt.
     SunOS server1 5.8 Generic_117350-43 sun4u sparc SUNW,Sun-Fire-V240
Software installed.
     Sun Cluster 3.0
     Veritas Volume Manager 4.0 MP2.
Disk Array associated.
     Sun StorEdge 3310 D.
I looked up veritas.com and find Array Support Library (ASL) for Sun StorEdge 3xxx Series is recommended. But I didn't find this library is running on this server.
Please refer to this following link
http://support.veritas.com/docs/277923
As our system is one of critical systems and I'd like to confirm that I can follow up this procedure without doing harm things to our system.
Jeff

No problem Jeff :)
I took a look at the Veritas doc and you're right it does seem to cover everthing.
Has the vxconfigd core dumped since the start? ie from the moment it was installed?
I have installed VXVM 4.0 with Solaris 8 but without the ASL and this worked ok, I know that's not much help to you but I am not sure the ASL will help. Mind you I have not installed it with Sun Cluster 3.0.

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

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

Solaris 10 Live Upgrade with Veritas Volume Manager 4.1

Similar Messages

Maybe you are looking for