4.1 is out of support. Go to 5. ________________________________ From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of John Wong Sent: Friday, June 11, 2010 2:16 PM To: veritas-vx@mailman.eng.auburn.edu Cc: j w Subject: [Veritas-vx] Fw: Question on VxVM upgrade from 3.1 to 4.1 with VCS1.3.0
Hi Team, I sent it to the wrong email address. Hope someone has done the VxVM upgrade from 3.1 to 4.1 and is willing to share the experience. Thanks much! john --- On Tue, 6/8/10, John Wong <j_w_...@yahoo.com> wrote: From: John Wong <j_w_...@yahoo.com> Subject: Question on VxVM upgrade from 3.1 to 4.1 with VCS 1.3.0 To: "veritas-vx-requ...@mailman.eng.auburn.edu" <veritas-vx-requ...@mailman.eng.auburn.edu> Cc: "j w" <j_w_...@yahoo.com> Date: Tuesday, June 8, 2010, 5:15 PM Hi Team, We are planning to upgrade VxVM 3.1 to 4.1 on a 2-node VCS cluster version 1.3.0. The OS is Solaris 5.8 on SUN Enterprise E4500. There are about 30 vxfs file systems in different disk groups being managed by VxVM and being activated and mounted by VCS. The file systems are accessed by Oracle, httpd, and Tibco Documentum server. Does anyone know of any real-life issues with this major upgrade of VxVM? What is the best way to perform the upgrade? What kind of changes in vxfs from 3.1 to 4.1. Will these changes cause problems in the vxfs file systems managed by VCS? Is VCS version 1.3.0 still supported? I don't seem to be able to find this info on Veritas website. VCS will not be upgraded. Your insights/suggestions/information will be greatly appreciated! Please don't ask me why we have not upgraded VCS because I just got onboard and was given this task. By the way, we can fall back to the old boot disks if vcs will not start or experience problems. Thanks, john
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
