cancel
Showing results for 
Search instead for 
Did you mean: 

VRTSvxvm 3.5 upgrade questions on Solaris 9

Mediis
Not applicable

I'm basically running Veritas Volume Manager 3.5 with the VRTSvxvm package on Solaris 9. I need to upgrade this to so I can see the newer Sun 6140 arrays. Because of the product name changes (Veritas Storage Foundation etc) and whatnot, I am not exactly sure which doc to use or which path to take. So far this doc seems to be the best path to take. And I am also running an encapsulated root. 

To complicate the issue one step futher, we are using Veritas Cluster Server (VRTSvcs) 3.5 as well. And I do not want to upgrade this package.

Do anyone have any idea what path I could take?

Mark A.
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Correct. Either upgrade to 4.x first or uninstall 3.5 and then install 5.x. Please remember to obtain your new license keys first.
Your local Symantec reseller will be able to assist you with correct product names/license keys to apply for. If your maintenance is up to date, the new license keys will be free of charge.

The product installation guides will guide you through the upgrade process, including unencapsulation of the boot disk. All installation and product documentation can be found here: http://sfdoccentral.symantec.com/ and https://vos.symantec.com/documents

Please also make use of the upgrade assistance offered on VOS: https://vos.symantec.com/home
Use this site to:

  • Determine if your systems are ready to install or upgrade
  • Download, search, and set up notifications for patches
  • Search for error code descriptions and solutions
  • Check product and system configurations for upgrade readiness and risk exposure
  • Gather license and product information
  • Get the latest information about your SFHA and VCS products

I'm pretty sure you will have to upgrade VCS as well. Depending on what you are clustering, the changes to VCS should be minimal. Again, your local reseller as well as Symantec Support (and this forum) will be more than willing to assist and guide you through the preparation and upgrade process. CHANGE IS GOOD!

View solution in original post

2 REPLIES 2

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Correct. Either upgrade to 4.x first or uninstall 3.5 and then install 5.x. Please remember to obtain your new license keys first.
Your local Symantec reseller will be able to assist you with correct product names/license keys to apply for. If your maintenance is up to date, the new license keys will be free of charge.

The product installation guides will guide you through the upgrade process, including unencapsulation of the boot disk. All installation and product documentation can be found here: http://sfdoccentral.symantec.com/ and https://vos.symantec.com/documents

Please also make use of the upgrade assistance offered on VOS: https://vos.symantec.com/home
Use this site to:

  • Determine if your systems are ready to install or upgrade
  • Download, search, and set up notifications for patches
  • Search for error code descriptions and solutions
  • Check product and system configurations for upgrade readiness and risk exposure
  • Gather license and product information
  • Get the latest information about your SFHA and VCS products

I'm pretty sure you will have to upgrade VCS as well. Depending on what you are clustering, the changes to VCS should be minimal. Again, your local reseller as well as Symantec Support (and this forum) will be more than willing to assist and guide you through the preparation and upgrade process. CHANGE IS GOOD!

joseph_dangelo
Level 6
Employee Accredited
When upgrading your keys from Foundation Suite HA 3.5 to Storage Foundation HA 4.x/5.x,  you will need to visit the following url:

http://vlicense.veritas.com


This is assuming you have the licenses registered under your account.  If they are not and you don't know who they are registerd to, you will have to contact Customer Care to assist.

You can upgrade your keys to 4.0 and then upgrade them to 5.0

3.5 Keys are were assigned based on the host ID of the system.  4.0 and later are no longer Node-Locked.

Hope this helps.