Veritas InfoScale 7.0: Configuring I/O fencing
I/O fencing protects the data on shared disks when nodes in a cluster detect a change in the cluster membership that indicates a split-brain condition. In a partitioned cluster, a split-brain condition occurs where one side of the partition thinks the other side is down and takes over its resources. When you install Veritas InfoScale Enterprise, the installer installs the I/O fencing driver, which is part of the VRTSvxfen package. After you install and configure the product, you must configure I/O fencing so that it can protect your data on shared disks. You can configure disk-based I/O fencing, server-based I/O fencing, or majority-based I/O fencing. Before you configure I/O fencing, make sure that you meet the I/O fencing requirements. After you meet the requirements, you can refer to About planning to configure I/O fencing to perform the preparatory tasks and then configure I/O fencing. For more details about I/O fencing configuration, see: Cluster Server Configuration and Upgrade Guide Veritas InfoScale documentation for other releases andplatforms can be found on the SORT website.
SFHA Solutions 6.0.1 (Solaris): Troubleshooting the dgdisabled error flag
The dgdisabled error flag indicates that configuration changes on a disk group are disabled. This can occur due to any error that prevents further configuration changes on the disk group. For example, this can occur if no good disks are found during the disk group import operation, if no valid configuration copies are found on the disks in the disk group, or if writes to all configuration copies fail during an update to the disk group configuration. The dgdisabled error flag displays when the Veritas Volume Manager configuration daemon, vxconfigd loses access to all enabled configuration copies for the disk group. Configuration copies let you back up and restore all configuration data fordisk groups, and for objects such as volumes that are configured within the disk groups. Loss of access can occur if power is disrupted or a network cable is disconnected. To recover from loss of access, fix any disk connectivity issues, then deport and re-import the disk group. Beginning with the Storage Foundation and High Availability (SFHA) Solaris 6.0 release, a node can join the cluster even if there is a shared disk group that is in the DGDISABLED state. In earlier releases the node failed to join the cluster. For more information on troubleshooting the dgdisabled error flag, see: Removing the error state for simple or nopriv disks in non-boot disk groups vxdarestore(1m) 6.0.1 manual page: Solaris For more information on using the vxdisk list command to display status and troubleshoot disk errors, see the following Symantec Connect article: SFHA Solutions 6.0.1: Using the vxdisk list command to display status and to recover from errors onVeritas Volume Manager disks Veritas Storage Foundation and High Availability documentation for other releases and platforms can be found on theSORT website.
Suggestion Regarding Icons in Documentation
Hi team, I just wanted to share this link to a recent discussion in the SF Windows forum, which talked about icons and had a couple of suggestions for documentation: http://www.symantec.com/connect/forums/veritas-enteprise-administrator-icon-meanings Best, Kimberley
SmartIO blueprint and deployment guide for Solaris platform
SmartIO for Solaris was introduced in Storage Foundation HA 6.2. SmartIO enables data efficiency on your SSDs through I/O caching. Using SmartIO to improve efficiency, you can optimize the cost per Input/Output Operations Per Second (IOPS). SmartIO supports both read and write-back caching for the VxFS file systems that are mounted on VxVM volumes, in multiple caching modes and configurations. SmartIO also supports block-level read caching for applications running on VxVM volumes. The SmartIO Blueprint for Solaris give an overview of the benefits of using SmartIO technology, the underlying technology, and the essential configuration steps to configure it. In the SmartIO Deployment Guide for Solaris, multiple deployment scenarios of SmartIO and how to manage them are covered in detail. Let us know if you have any questions or feedback!
Veritas InfoScale 7.0: Licensing Veritas InfoScale 7.0
You require a license to install and use Veritas InfoScale products. There are two ways you can register the Veritas InfoScale product license keys: Use key-based licensing When you purchase a Veritas InfoScale product, you receive a License Key certificate. The certificate specifies the product keys and the number of product licenses purchased. Use keyless licensing The license is registered based on the product you install. Within 60 days of choosing this option, you must install a valid license key corresponding to the license level, or continue with keyless licensing by managing the systems with Veritas InfoScale Operations Manager. You can register the product license keys either manually or by using the installer. You can use the vxlicinstupgrade utility, if you want to: Upgrade to another Veritas InfoScale product Upgrade a temporary license to a permanent license Manage co-existence of multiple licenses For more information on licensing Veritas InfoScale products, see: About Veritas InfoScale product licensing Registering Veritas InfoScale using product license keys Registering Veritas InfoScale product using keyless licensing Updating your product licenses Using the vxlicinstupgrade utility Veritas InfoScale documentation can be found on the SORT website.SFHA Solutions 6.2: Configuring secure shell or remote shell communication between nodes when installing Symantec products
To install and configure Symantec software, you need to establish secure shell (ssh) or remote shell (rsh) communication with superuser privileges between the nodes where the installer is running and the target nodes. You can install products to remote systems using either ssh or rsh. Symantec recommends that you use ssh as it is more secure than rsh. You can set up ssh and rsh connections in the following ways. You can use UNIX shell commands to manually set up the connection.Using this method, you can log into and execute commands on a remote system. You can run the installer directly to set up the ssh/rsh connection interactively during the install procedure. You first create a Digital Signature Algorithm (DSA) key pair. From the key pair, you can append the public key from the source system to the authorized keys file on the target systems. You can run the installer -comsetup command.Using this method, you can interactively set up the ssh and rsh connections using the installer -comsetup command. You can run the pwdutil.pl password utility.If you want to run the installer with the response file present in your own scripts, then the ssh connection should be set up prior to running installer. The password utility, pwdutil.pl, is bundled in the Symantec Storage Foundation and High Availability (SFHA) Solutions 6.2 release under the scripts directory. You can run the utility in your script to set up the ssh and rsh connection automatically. Both the script-based and web-based installers support establishing passwordless communication. For more information about configuring secure shell or remote shell communication between nodes, see: Manually configuring passwordless ssh Setting up ssh and rsh connection using the installer -comsetup command Setting up ssh and rsh connection using the pwdutil.pl utility SFHA documentation for other releases andplatforms can be found on theSORTwebsite.SFHA Solutions 6.0.1: Using vxcdsconvert to make Veritas Volume Manager (VxVM) disks and disk groups portable between systems for Cross-platform Data Sharing (CDS)
The vxcdsconvert command makes disks and disk groups portable between systems running VxVM with the Cross-platform Data Sharing (CDS) feature. For more information on the CDS feature, see: Overview of the CDS feature Setting up your system to use CDS You can resize the CDS disks to larger than 1 TB. For more information, see: Dynamic LUN expansion You can use the vxcdsconvert command to: Check whether disks and disk groups can be made portable (using the –A option). Convert disks and disk groups to be CDS-compatible. For more information on the conversion procedure, see: Converting non-CDS disks to CDS disks Converting a non-CDS disk group to a CDS disk group Note the following points: The vxcdsconvert command requires that disk groups be version 110 or greater. When a disk group is made portable, all disks within the disk group are also converted. Converting a disk group that contains RAID-5 volumes and logs fails, if there is insufficient space in the disk group to create an additional temporary RAID-5 log. The default private region size increased from 512 KB to 1 MB in SFHA release 3.2, and from 1 MB to 32 MB in release 5.0. vxcdsconvert (1M) 6.0.1 manual pages: AIX HP-UX Linux Solaris VxVM documentation for other platforms and releases can be found on the SORT website.SFHA Solutions 6.0.1: Maximizing storage utilization using thin provisioning
Thin provisioning helps you save SAN/NAS storage space. In thin provisioning, instead of provisioning full storage space to a user, the thin provisioning software allocates disk space in a flexible manner based on the minimum space that is required by each user at the given time. Thin provisioning saves considerable storage space in contrast with the conventional storage, where storage is allocated beyond the current requirements of the application. For more information on the advantages of using thin provisioning, refer to: Why Thin Provisioning and Thin Reclamation? Thin provisioning - addressing the problems with over allocation How does Veritas Operations Manager help you reclaim underutilized storage? Veritas Operations Manager offers different solutions for using thin provisioning and thin reclamation. These solutions are listed below: Thin Provisioning Reclamation Add-on You can use the Thin Provisioning Reclamation Add-on to optimize storage space by using Veritas File System (VxFS) thin capabilities and Storage Foundation Thin Reclamation API. You can run thin reclamation on the following objects in Veritas Operations Manager: Storage array: Select thin pools or LUNs in the context of an array. Business entity: Specify a flexible reclamation boundary based on a business entity. Since a business entity can include many objects and is inherently dynamic, the LUNs that are reclaimed change automatically whenever changes occur within that business entity. Hosts: Select multiple file systems in context of the hosts. The associated LUNs are reclaimed. You can configure thin reclamation processes to run at regular scheduled intervals. If you have not scheduled the process run, you can also run it manually. For more information about configuring and running the Thin Provisioning Reclamation Add-on, see: Veritas Operations Manager Thin Provisioning Reclamation Add-on Configuring a thin reclamation process for an array Configuring a thin reclamation process for a business entity Configuring a thin reclamation process for host Running reclamation processes manually Veritas Storage Foundation Add-on for Storage Provisioning You can use the Storage Foundation Add-on for Storage Provisioning to migrate the volume from thick to thin Logical Unit Number (LUN). Using this add-on, you can select a specific volume to migrate, and optionally change its layout before migration. For more information on using the Storage Foundation Add-on for Storage Provisioning, see: Moving volumes from thick to thin LUNs Impact Analysis report Veritas Operations Manager policy checks Veritas Operations Manager policy check feature uses individual rules to validate if the datacenter configuration conforms to a pre-defined standard. You can create policy templates to check the performance, availability, and utilization of the storage objects in your datacenter. For more information on policy checks, see: About policy checks Storage reclamation and thin provisioning reports Veritas Operations Manager provides extensive reporting capabilities centered around Storage Foundation and High Availability products. It includes reports related to storage utilization, storage reclamation, and inventory. For more information on thin provisioning reports, see: Storage reclamation and thin provisioning reports For more information about Storage Foundation thin reclamation and thin provisioning features, see: Veritas Storage Foundation Administrator’s Guide Veritas Storage Foundation and High Availability Solutions 6.0.1 Solutions Guide Storage Foundation and High Availability and Veritas Operations Manager documentation for other releases and platforms can be found on the SORT website.
