Upgrade

133 Topics

Maxuproc not get updated even after reboot
Hi, Got a update to change the "maxuproc for wt82369 by 1.5 times" , While verifying we make necessary modification on the Global (wt81958). Normally there is a relation between max_nprocs value and maxuproc value. FYI.. maxuprc = max_nprocs – reserved_procs (default is 5) In this case we modified the max_nprocs value from 30000 to 50000 FYI.. [root@wt81958 GLOBAL] /etc # cat /etc/system | grep max_nprocs set max_nprocs=50000 After the global zone reboot the value is not updated while we hit sysdef [root@wt81958 GLOBAL] /root # sysdef | grep processes 30000 maximum number of processes (v.v_proc) 29995 maximum processes per user id (v.v_maxup) Can anyone please assist us if any thing we missed in this to make the necessary changes to replicate. Awaiting for your valuable suggestions. Thanks, senthilsam
Solved
senthilsam
5 years ago Place Storage Foundation
3.2KViews
0likes
3Comments
Doubts on VxVM,VCS Upgrade & root disk encapsulation
Hi All, I have the below queries please 1) In order to stop VxVM to load at system boot time, we need to modify /etc/system file. What entries are to be commented out ? Is it only rootdev:/pseudo/vxio@0:0 set vxio:vol_rootdev_is_volume=1 (OR) also below entries are to be commented out ? forceload: drv/vxdmp forceload: drv/vxio forceload: drv/vxspec 2) My current version of SFHA is 4.1. Once vxfen, gab & llt modules are unloaded to upgrade to 4.1MP2, should i again unload these modules to further upgrade to 5.1SP1 and again to 5.1SP1RP4 (OR) 6.0 ? After each upgrade should i stop the services in /etc/init.d and unload modules (OR) stopping services & unloading modules only once is enough to further upgrade to other versions ? My Plan is to upgrade from 4.1---> 4.1 MP2---> 5.1SP1--->5.1SP1RP4 (OR) 6.0 3) Before upgrading should i also stop & unload the below listed modules 24 12800a8 26920 268 1 vxdmp (VxVM 4.1z: DMP Driver) 25 7be00000 2115c8 269 1 vxio (VxVM 4.1z I/O driver) 27 12a4698 13f0 270 1 vxspec (VxVM 4.1z control/status driver) 213 7b2d7528 c40 272 1 vxportal (VxFS 4.1_REV-4.1B18_sol_GA_s10b) 214 7ae00000 1706a8 20 1 vxfs (VxFS 4.1_REV-4.1B18_sol_GA_s10b) If yes, should i stop & unload after each upgrade (OR) doing it once is enough ? 4) Once the OS comes up with native disks (c#t#d#s#), In order to bring it under VxVM control we need to encapsulate using vxdiskadm. My doubt is will rootdg, rootvol, plexes & subdisks be created automatically? Need a little clarification regarding this please. Response is highly appreciated as always, Thank you very much. Regards, Danish.
Solved
M_Danish
7 years ago Place Storage Foundation
1.9KViews
0likes
1Comment
how to upgrade ApplicationHA guest componet from 6.2 to 6.2.1
Does any one know how to upgrade how to upgrade ApplicationHA RedHat guest componet from 6.2 to 6.2.1? https://sort.veritas.com/patch/detail/10105 In the patch document, it did not mentinon anything how to upgrade ApplicationHA. my question is do we upgrade from inside the guest OS via installer like ./installmr ? or Upgrade from Symantec HA console via vSphere Client?
ylin-123
9 years ago Place ApplicationHA
2.3KViews
0likes
0Comments
Veritas InfoScale 7.0.1 (for AIX/Linux/Solaris): Documentation Available
The Veritas InfoScale 7.0.1 patch for AIX/Linux/Solaris is a maintenance-level release, which provides several updates on top of the InfoScale 7.0 products. The highlights of this release are: Upgrade bundled OpenSSL from 1.0.1m to 1.0.1p IPM protocol is no longer supported for CP server and InfoScale Availability clusters. The following platforms are newly supported: Linux: SLES11SP4 and RHEL6u7, OL 6u7 Solaris: Solaris10x64 is supported on InfoScale Availability Virtualization: VMware vSphere 6.0 u1 The documentation for Veritas InfoScale 7.0.1 is now available at the following locations: PDF and HTML versions: SORT documentation page Late Breaking News: http://www.symantec.com/docs/TECH230620 Hardware Compatibility List: http://www.symantec.com/docs/TECH230646 Software Compatibility List: http://www.symantec.com/docs/TECH230619
Vivian_Wu
9 years ago Place Storage and Clustering
509Views
0likes
0Comments
Upgrade of server
Hi all ! I have some outdated RHEL5 installations with older vxfs 5.xx on. Some weeks back I popped out one of the mirrored OS disks and installed both RHEL7 and vxfs 6.2.1. I found no way to mount the old filsystems after the installation was done. No devices under /dev/vx/dsk or /dev/vx/rdsk. I could see the disks with 'vxdisk list' and the older diskgroups with vxdg ( don't remember the exact syntax I used ). Disk layout was already 7 on all filsystems, wich seems to be supported in 6.2.1. At this moment - I felt lost, wasn't going to risk loosing any of the data by experimenting. So, I reverted the changes and booted up in RHEL5 again. I'm quite sure that the task above could be solved - could someone please point me in the right direction ? /Sverre.
Solved
sverrewl
9 years ago Place Storage Foundation
1.6KViews
0likes
6Comments
InfoScale 7.0 for Windows: Transitioning from one InfoScale product to another InfoScale product
To transition to an InfoScale product, on the system where you already have an InfoScale product installed, run the product installer for the InfoScale product you want to transition to. The following table lists the supported paths to transition from one InfoScale product to another InfoScale product: For information about installing an InfoScale product, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Shweta_Naresh
9 years ago Place Storage and Clustering
708Views
0likes
0Comments
InfoScale 7.0 for Windows: Upgrading Storage Foundation and High Availability Solutions to InfoScale 7.0
To upgrade to an InfoScale product, your systems must have a corresponding Symantec Storage Foundation and High Availability Solutions product of version 6.x or 6.0.x already installed. If your current installation does not meet this minimum required level, you must manually apply the appropriate product upgrades before you proceed with the upgrade. The following table lists the supported upgrade paths: For information about upgrading to InfoScale 7.0, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Shweta_Naresh
9 years ago Place Storage and Clustering
730Views
0likes
0Comments
InfoScale 7.0 for Windows: Upgrading VCS Java Console and VEA to 7.0
If you had installed Storage Foundation for Windows (SFW) or Veritas Cluster Server (VCS) clients only (VCS Java Console or VEA), you cannot upgrade them to 7.0 version. To install the latest version of clients-only, uninstall its earlier version and then install the current version. For information about installing the clients only, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Shweta_Naresh
9 years ago Place Storage and Clustering
789Views
0likes
0Comments
InfoScale 7.0 for Windows: Performing a roll back to a previous installation after upgrading to InfoScale 7.0
The Symantec Storage Foundation and High Availability products included support to perform a rollback from the upgraded version to the original version. The rollback process allowed you to revert back to its earlier installation and restore the configuration and tunable parameters. The InfoScale products (7.0 release for Symantec Storage Foundation and High Availability products with new packaging) do not support the rollback process. If you upgrade to an InfoScale product, you cannot revert back to its earlier installation and restore the configuration. In this case, you must uninstall the InfoScale product and then install the previous version of the product. For information about uninstalling an InfoScale product, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Shweta_Naresh
9 years ago Place Storage and Clustering
716Views
0likes
0Comments
InfoScale 7.0 for Windows: Upgrading VCS to a corresponding InfoScale product using the wizard-based rolling upgrade method
With the 7.0 release, the wizard that was used to upgrade Veritas Cluster Server (VCS), in a rolling upgrade manner is not available. That wizard upgraded the passive nodes first, failed over service groups to the upgraded nodes, and then upgraded the active nodes. Now, to upgrade VCS, you need to bring the application service groups offline on all the cluster nodes. Then, run the product installation wizard to begin the upgrade. For information about upgrading to InfoScale products and the supported upgrade paths, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.
Shweta_Naresh
9 years ago Place Storage and Clustering
450Views
0likes
0Comments