I agree with most of what Dana has to say about this. I would differ in
advise on point 4. If your SAN is EMC or Netapps (hope not), then I would
say let the SAN do all the mirroring for you. With bigger databases (
greater than 2 TB ), you need need all the CPU cycles and IO over FC to your
databa
This is how I mirror on Sun Solaris:
/etc/vx/bin/vxdisksetup -i c0t1d0
/usr/sbin/vxdg -g rootdg adddisk rootmirror=c0t1d0
/etc/vx/bin/vxmirror -g rootdg -a rootmirror
/etc/vx/bin/vxmirror -g rootdg -D
___
Veritas-vx maillist - Veritas-vx@mailman.eng.
Actually depending on what you've got going on and of course assuming
you have a license for 5 then you can go from 3.2 to 5. What you can't
do is an in-place upgrade. You can however take the volumes etc. you've
got under 3.2 and bring them up on a system running 5.0 or 4.1. I've
done this with 3.
Please read the Admin Guide and in particular the man page for vxassist.
vxassist -g dg_name mirror volume alloc=disk_name
- Original Message
From: ajay raghuraj <[EMAIL PROTECTED]>
To: VeritasUsers
Sent: Wednesday, 15 August, 2007 5:14:38 AM
Subject: Re: [Veritas-vx] mirroring exi
"This package, VxVM 3.2, is only supported on Solaris 2.6, 7,
and 8; however, you appear to be running Solaris 2.10.
That is not a supported version of Solaris."
The answer is rather obvious is it not ?
So yes you need to to got 4.x if you are going to go to Solaris 10 and no you
If folks are interested, the actual bug in this case is a pair of
missing quotes in the /usr/lib/vxvm/bin/vxroot script:
< if [ $? -eq 0 -a -n "$bus_drivers" ] ;
---
> if [ $? -eq 0 -a -n $bus_drivers ] ;
We put a fixed version onto our servers when they jumpstart so that we
can encap
Hi Gowtham,
This seems to be a common issue.
Refer the following technote
http://seer.support.veritas.com/docs/282808.htm
The bottomline is MP1 patch or the workaround mentioned in the doc.
Regards,
PP BIJU KRISHNAN
On 8/17/07, Gowthaman N <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I m doing enc
Hi,
I m doing encapusulation on a T2000 server with Veritas 4.1 and during the
second reboot of the server, it goes to
maintenance mode
Below is the error message from console. Any solutions
Hostname:
WARNING:
/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],2
