(540-480BC)
From: Ronald S Karr [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2008 9:33 AM
To: Craig Simpson
Cc: Veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
This is most likely something normal. Most likel
This is most likely something normal. Most likely a mirror
consistency build after creating a mirrored volume, adding a mirror,
or after importing a disk group.
Out of curiosity, which release of VxVM did you say you were running?
--
Ronald S. Karr
tron |-<=>-|[EMAIL PROTECTED]
I notice this running on one of my servers, but am not sure what it is?
What does this mean? Should I care? Server is up and happy.
[EMAIL PROTECTED]:/root#ps -ef |grep vxvol
root 26070 799 0 06:52:45 ?0:00
/usr/lib/vxvm/type/fsgen/vxvol -U fsgen -g 1161384358.15.orarac03 -o
iosi
You can run in down-graded disk groups for extended periods of time,
if you just want to make sure that the release works for you. In
most cases, we don't do a lot of version-dependent emulation, so if a
feature works in the down graded disk group, it is very unlikely to
break just because
On Fri, Mar 28, 2008 at 02:04:04PM -0700, Craig Simpson wrote:
>
> OK so basically have your tapes ready just in case.
*always* a good idea.
But I've never heard of a vxdg upgrade having problems before. But it
does make the diskgroup non-importable on older versions that can't deal
with versi
PROTECTED]
Sent: Friday, March 28, 2008 1:56 PM
To: Ronald S Karr; Hudes, Dana
Cc: Asim Zuberi; Veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
So a rollback would be possible after vxdg upgrade, if Volume management
was not changed
PROTECTED] On Behalf Of A Darren
Dunham
Sent: Friday, March 28, 2008 1:42 PM
To: Veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
On Fri, Mar 28, 2008 at 10:56:18AM -0700, Craig Simpson wrote:
>
> So a rollback would be possible after
On Fri, Mar 28, 2008 at 10:56:18AM -0700, Craig Simpson wrote:
>
> So a rollback would be possible after vxdg upgrade, if Volume management
> was not changed?
>
> Volume management since the upgrade would be messed up, but not anything
> prior if it was not changed?
No. You can't do a downgrad
Veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
I am pretty sure that an upgrade doesn't change the size of the private
region. Also, VxVM has always supported the larger private regions used
in 4.0 and now 5.0. We just created
-Original Message-
From: Craig Simpson [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 12:10 PM
To: Hudes, Dana; Asim Zuberi; Veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
Make sure you have mirrored rootdg and can back out if n
as-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
Make sure you have mirrored rootdg and can back out if needed. 100% of
this upgrade is a good back out plan. IF you don't have mirrored
rootdisks, then DD the drives. If you are not 100% SURE you can back
m Zuberi; Veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Upgrading VxVM and VxFS on clustered nodes!
VCS is part of Storage Foundation, the HA part. It relies on VxVM and
VxFS. Even if you could get away with 'just' upgrading those two
packages you would have lots of odd things goi
VCS is part of Storage Foundation, the HA part. It relies on VxVM and
VxFS. Even if you could get away with 'just' upgrading those two
packages you would have lots of odd things going on. For example, the
GUI is now VEA not VMSA. The latter won't work with v5.
My recommendation is that you take t
13 matches
Mail list logo
