Veritas SFHA 6.2: Layered volume enhancements for recovery and snapshots
SFHA 6.2 introducesa new enhancement for layered volumes. A layered volume is a virtual Veritas Volume Manager object that is built on top of other volumes. The layered volume structure tolerates failure better and has greater redundancy than the standard volume structure. The enhancement ensures that when storage disconnection and subsequent reconnection happen, only inconsistent regions in the affected sub-volume are synchronized using the FastResync feature. In case of a storage failure, the mirror of the sub-volume on that storage will be detached and the future I/Os on the sub-volume will be tracked by the DCO associated with the parent volume. When such a detached mirror is reattached after restoring storage connectivity, only regions that are inconsistent in the mirror will be synchronized using the FastResync feature. Prior to this release, for a layered volume, if the storage within a mirror of a sub-volume became inaccessible, it led to full synchronization of that mirror when the storage was reconnected. For more information about FastResync and layered volumes: About FastResync About layered volumes Veritas SFHA documentation for other releases and platforms can be found on the SORT website.
SFHA Solutions/InfoScale: How to clean up the operating system device tree
A device tree is a data structure that describes the LUNs in your environment. When you remove LUNs dynamically from an existing target ID, the operating system SCSI device tree must be cleaned up. This is to release the SCSI target ID for reuse if a new LUN is added to the host later. In Storage Foundation/InfoScale, there are two ways to do this: one if you are using Storage Foundation and High Availability (SFHA) version 6.0 or earlier you must clean up the device tree manually. In SFHA 6.0.1 and later, the device tree is cleaned up dynamically. For SFHA 6.0 and earlier For SFHA 6.0 and earlier, you need to clean up the operation system device tree manually after you remove LUNs from an existing target ID. To completely remove LUNs from an existing target ID, you need to perform the following steps: Remove LUNs. Clean up the operating system device tree. Scan the operating system device tree. The following diagram shows the process of removing LUNs dynamically from an existing target ID. For SFHA 6.0.1 and later, and InfoScale Since SFHA 6.0.1, the Dynamic Reconfiguration operations option (DR tool) is introduced in the vxdiskadm menu to simplify the removal of LUNs from an existing target ID. It saves the manual work of device scanning and cleaning up. Through the DR tool, Dynamic Multi-pathing (DMP) updates and cleans up the operating system device tree automatically. For more information about using DR tool to remove LUNs, please see:Removing LUNs dynamically from an existing target ID. The following diagram shows the process of using DR tool to remove LUNs dynamically from an existing target ID. The process is simplified by using this tool. Related links: Reconfiguring a LUN online that is under DMP control. (SFHA 6.0.1 and later) Reconfiguring a LUN online that is under DMP control. (SFHA 6.0 and earlier) The links in this article are specific to Linux platform. You can find SFHA Solutions/InfoScaledocuments for other versions and platforms on the SORT documents page.
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: Installing InfoScale Availability on a machine where InfoScale Storage is already installed
To use Storage Foundation for Windows (SFW) for storage management and Veritas Cluster Server for Windows (VCSW) for high availability, you can install InfoScale Availability on a machine where InfoScale Storage is already installed or vice-a-versa. The co-existence of VCSW and SFW however has the following limitations: If Keyless licensing type is selected during the product installation, checks performed to monitor the number of days of product installation are based on the SFW component. As a result, if you do not enter a valid license key or do not add the host as a managed host within 60 days of InfoScale Storage installation, a non-compliance error is logged every 4 hrs in the Event Viewer. After InfoScale Storage is installed, the VCS configuration wizards discover only SFW dynamic disks for configuring storage resources in an application service group. If you have already configured NetApp or native disk (LDM) resources, you can continue to use them. However, you cannot add or remove any of these resources using the VCS configuration wizards. Then, you must manually modify the service group to add or delete the NetApp or LDM resources. For information about installing the InfoScale products, 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.InfoScale 7.0 for Windows: About the product correlation between Symantec Storage Foundation and High Availability Solutions and Veritas InfoScale Family
In the 7.0 release, the following products from Symantec Storage Foundation and High Availability Solutions are rebranded and repackaged under the Veritas InfoScale family. Storage Foundation (SFW) Storage Foundation and High Availability Solutions (SFW HA) Cluster Server (VCS) Dynamic Multi-Pathing for Windows (DMPW) The Veritas InfoScale family consists of the following products: Veritas InfoScale Foundation Veritas InfoScale Availability Veritas InfoScale Storage Veritas InfoScale Enterprise The following table depicts the existing-to-new product correlation: Existing product New product SFW Basic Veritas InfoScale Foundation VCS Veritas InfoScale Availability SFW Veritas InfoScale Storage SFW HA Veritas InfoScale Enterprise As a result of repackaging the following changes apply: DMPW and VBS are not available as separate products. The following product options are not available as user-selectable options during the product installation. All these features are now available by default with the concerned InfoScale product. FlashSnap Replace Disk Management Snap-in with SFW VEA GUI Volume Replicator (VVR) Fast failover Global Cluster Option For information about the simplified product packaging, changes to the user-selectable product installation options, and the components that are offered in each InfoScale product, see: Veritas InfoScale™ What's New Guide InfoScale documentation for other platforms can be found on the SORT website.InfoScale 7.0 for Windows: Installing InfoScale client-only components
The InfoScale products have server and client components; VCS Cluster Manager (Java Console) and Veritas Enterprise Administrator (VEA). The client components are installed by default when you install the server components. To install the client components only, you must download the client-specific .msi file from SORT and then follow the install program instructions to complete the installation. Note: Client components cannot be installed on server core systems. For information about installing the InfoScale client components, see: Veritas InfoScale™ Installation and Upgrade Guide InfoScale documentation for other platforms can be found on the SORT website.