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
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.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.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.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.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.
SFHA Solutions 6.2: Support for centralized installations using the Deployment Server
The Deployment Server was introduced in the 6.1 release. The deploy_sfha script makes it easier to install or upgrade Storage Foundation and High Availability (SFHA) releases. The Deployment Server lets you store a list of patches and packages in one central location. This list of patches and packages are installed in an install template. You can deploy them to systems of any supported UNIX or Linux operating system (6.1 or later) using a DVD image of the binaries. In the 6.2 release, new features have been added to the Deployment Server. You can now: Define Install Bundles Create a combination of base, maintenance, and patch releases and install or upgrade in one operation. Directly install the latest base, maintenance, and patch releases on your system. Install Bundles can be used to install the 6.0.1 and 6.0.5 releases together, however incorporating patch releases with Install Bundles is not supported with version 6.0.5. From the SFHA version 6.1 release onwards, Install Bundles are supported with different release level combinations. Create Install Templates Discover installed components (RPMs, patches, products, or versions) on a system that you want to replicate. Install the discovered components on other systems by referencing the template. Connect the Deployment Server to SORT using a proxy server A proxy server is a server that acts as an intermediary for requests from clients, for connecting the Deployment Server to the Symantec Operations Readiness Tools (SORT) website. Before you launch the Deployment Server, enable the proxy access and run the necessary commands to set the shell environment variables. Filter platforms In the Set Preference menu, choose Selected Platforms to filter the platforms that are currently being used in the deployment environment. For information on the Deployment Server, see: SFHA Solutions 6.1: Support for centralized installations using the Deployment Server Defining Install Bundles Creating Install Templates Connecting the Deployment Server to SORT using a proxy server Using Install Bundles to Simplify Storage Foundation HA Install and Upgrade Using Install Bundles to Simplify Install/Upgrade (video) The Deployment Server is available only from the command line. The Deployment Server is not available for the web-based installer. Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.
upgrade Storage Foundation and VCS 4.1 to SFHA 6.X
HI All, I'm going to upgrade my production environment with VXVM,VXFS and VCS 4.1. My question are: 1) After upgrade to Solaris10 up11, it's possibile to remove all Veritas packages and reinstalling everything at version SFHA 6.1 (and recover vcs configuration)? Does it support? 2) I see from Admin Guide this extract: Currently, only the Version 7, 8, 9, and 10 disk layouts can be created and mounted. The Version 6 disk layout can be mounted, but only for upgrading to a supported version what does it mean? Thanks in advance RickSFHA Solutions 6.1: Performing a rolling upgrade of Storage Foundation and High Availability (SFHA)
A rolling upgrade is a method of upgrading the clusters in a system. A rolling upgrade has two main phases. In Phase 1, the installer upgrades the kernel packages and in Phase 2, the installer upgrades Symantec Cluster Server (VCS) and VCS agent packages. Since the process rolls over in phases, it is termed as a rolling upgrade. You can perform a rolling upgrade to minimize the downtime for the cluster. The advantage of this method is that it ensures that the service groups that are online, remain online throughout the upgrade process. You can plan the failover and selectively upgrade systems. This ensures that the failover service groups are never offline. The rolling upgrade process is as follows: The cluster is split into two subclusters. The failover service groups that are online on the first subcluster are failed over to the second subcluster. The parallel service groups on the first subcluster are taken offline. Phase 1 of the rolling upgrade starts on the first subcluster. The kernel packages are upgraded. Almost all of the packages are upgraded during Phase 1, except for VRTSvcs, VRTSvcsag, VRTScavf, VRTSvcsea and VRTSvbs. Once Phase 1 of the rolling upgrade is complete on the first subcluster, Phase 1 of the rolling upgrade is performed on the second subcluster. The applications are failed over to the first subcluster. The parallel service groups are brought online on the first subcluster and taken offline on the second subcluster. During Phase 2 of the rolling upgrade, all remaining packages are upgraded on all nodes of the cluster simultaneously. VCS and VCS agent packages are upgraded. Applications stay online during Phase 2. The High Availability daemon (HAD) stops and starts again. During Phase 1, the only downtime is the time required for the service groups to failover. The downtime is limited to the applications that are failed over and not the entire cluster. During Phase 2, downtime occurs when the VCS engine HAD restarts, but this does not include application downtime. Limitations: A rolling upgrade requires the previous version and target version products to work together. You can perform a rolling upgrade from 5.1 and later versions. If fencing is configured in the environment and an upgrade is done from 5.1SP1RP3 to 6.0 and above versions, the fencing protocol is not compatible between 5.1SP1RP3 and the target. A patch is required to correct this issue. The patch info can be found on sort: https://sort.symantec.com/patch/detail/7157 A rolling upgrade is not compatible with a phased upgrade. You should not attempt to combine a rolling upgrade with a phased upgrade. Symantec provides both a script-based and a web-based installer to perform a rolling upgrade of Storage Foundation and High Availability (SFHA). For more information about the rolling upgrade process, see: About rolling upgrades Supported rolling upgrade paths Performing a rolling upgrade using the script-based installer Performing a rolling upgrade of SFHA using the web-based installer Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.