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 out, don't do it.
Also if you are running Oracle or some other DB, make sure your DBA's
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 smaller ones by
default. An upgrade basically tells VxVM that is okay to use newer
configuration database
I am curious to know what sort of experience there might be out there
moving from Solaris on Sparc to Solaris on x86 with Veritas products;
my particular interest is an HA (VCS) cluster that is currently sparc
based and could stand an update - I'm less concerned about the VCS part
than the
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?
Craig
--
Craig Simpson
Visto Corporation
Operations Team
[EMAIL PROTECTED]
If you have your data on CDS volumes that will make life simpler for
SPARC-x86.
If you are going from an old version such as 3.5 where you don't have
CDS then I would make new volumes and filesystems. I would send all data
with ncftp (because it will send a whole tree recursively; you could
also
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
