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 for disk 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 on Veritas Volume Manager disks Veritas Storage Foundation and High Availability documentation for other releases and platforms 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.SFHA Solutions 6.0.1: Using Veritas Cluster Server Simulator
Veritas Cluster Server (VCS) Simulator enables you to simulate and test cluster configurations. You can use VCS Simulator to view and modify service group and resource configurations and test failover behavior. VCS Simulator can run on a stand-alone system and does not require any additional hardware. You can install VCS Simulator only on a Windows operating system. VCS Simulator runs an identical version of the VCS High Availability Daemon (HAD) as in a cluster, ensuring that failover decisions are identical to those in an actual cluster. Using VCS Simulator, you can test configurations from different operating systems. For example, you can run VCS Simulator to test configurations for VCS clusters on Windows, AIX, HP-UX, Linux, and Solaris operating systems. VCS Simulator also enables you to create and test global clusters. You can administer VCS Simulator from the Java Console or from the command line. To download VCS Simulator, see: http://go.symantec.com/vcsm_download For more information on installing and administering VCS Simulator, see: Installing VCS Simulator on a Windows System Upgrading VCS Simulator Administering VCS Simulator Predicting VCS behavior using VCS Simulator Administering VCS Simulator from the Java Console Administering VCS Simulator from the command line interface VCS documentation for other releases and platforms can be found on the SORT website.SFHA Solutions 6.0: Use Cases for administering VxFS file systems using fsadm
The fsadm command performs online administration functions on Veritas File System (VxFs) file systems, Storage Checkpoints, or individual files and directories. The fsadm command supports file system resizing, extent reorganization, directory reorganization, querying or changing the largefiles flag, Thin Storage Reclamation, and free space defragmentation. The following are use cases for administering VxFS file systems using fsadm: Extending a file system using fsadm Shringing a Veritas File System (VxFS) file system - considerations for success Reorganizing a file system Reclaiming space on a file system maintaining Then Storage with Thin Reclamation fsadm_vxfs (1M) 6.0 manual pages: AIX HP-UX Linux Solaris fsadm (1M) manual pages for other releases can be found on the SORT website.
Veritas InfoScale 7.0: Storage management feature support matrix for Veritas InfoScale products on Oracle
In the Veritas InfoScale 7.0 release, the Storage Foundation High Availability (SFHA) product portfolio has been replaced with a more simplified, robust, and comprehensive Veritas InfoScale portfolio that includes the following four products: Veritas InfoScale Foundation Veritas InfoScale Storage Veritas InfoScale Availability Veritas InfoScale Enterprise The core features of SFHA, storage management and availability, are consolidated in the Veritas InfoScale portfolio. This simplifies product licensing, installation, and performance. With this release, the storage management feature support map for Veritas InfoScale products on Oracle has been rearranged to suit the new Veritas InfoScale product model. The following table provides a mapping of the features for each product: For information on the use cases of the storage management features, see the Veritas InfoScale™ 7.0 Storage and Availability Management for Oracle Databases document. For more information on Veritas InfoScale products, see the following sections in the Veritas InfoScale What's new in this release document: About the Veritas InfoScale product suite About Veritas InfoScale Foundation About Veritas InfoScale Storage About Veritas InfoScale Availability About Veritas InfoScale Enterprise Veritas InfoScale documentation can be found on the SORT website.Symantec High Availability 6.1 Solution: Configuring disaster recovery in a VMware environment with non-shared storage
You can use the Symantec High Availability 6.1 Solution to configure disaster recovery (DR) in a VMware environment with non-shared disks, which are managed using Storage Foundation for Windows (SFW). The replication is configured using Symantec Volume Replicator (VVR) or Hitachi TrueCopy (HTC)/ EMC SRDF solution. For information about configuring disaster recovery in a VMware environment using the Symantec High Availability Solution, see: Configuring disaster recovery in a VMware environment using the Symantec High Availability solution This quick reference guide provides: A typical disaster recovery setup in a VMware environment involving non-shared storage Configuration differences between VVR and HTC/SRDF-based replication A DR configuration workflow for HTC/SRDF-based replication Sample service group dependency graphs for VVR and HTC/SRDF-based replication A list of reference documents and where you can download them Storage Foundation and High Availability and ApplicationHA documentation for other releases and platforms can be found on the SORT website.Symantec High Availability 6.1 Solution: Configuration in VMware Site Recovery Manager (SRM) environment
The Symantec High Availability 6.1 Solution provides scripts to perform some of the configuration tasks required for application monitoring continuity in a VMware SRM environment. In the event of a failure, when the SRM recovery plan is executed, the Symantec High Availability recovery command retrieves the application status, and the Symantec Cluster Server (VCS) network and application-specific agents bring the network and application components online. This ensures application monitoring continuity after the failover. For information about configuring the Symantec High Availability Solution in a VMware SRM environment, see: Configuring Symantec High Availability Solution in VMware SRM environment This quick reference guide provides: A complete workflow of the configuration tasks involved A quick start for each high-level task A list of reference documents and their download location Storage Foundation and High Availability and ApplicationHA documentation for other releases and platforms can be found on the SORT website.SFW 6.1: Configuring high availability for Microsoft failover cluster quorum
A Microsoft failover cluster uses a single physical disk resource and a basic disk volume resource for a quorum. If the physical disk fails, the quorum resource fails and the cluster becomes unusable. To avoid this failure, you must use a dynamic disk group resource. Unlike a physical disk resource that contains a single disk, a dynamic disk group resource can contain multiple disks. A dynamic disk group resource provides a high level of redundancy by allowing the mirroring of disks. With Storage Foundation for Windows (SFW) a Microsoft failover cluster can use dynamic disks as a quorum disk resource. This lets you make your cluster quorum highly available by using host-based mirroring. To use SFW to configure a Microsoft failover cluster quorum, you must perform the following tasks: Configure a Microsoft failover cluster. Install SFW. Create a cluster dynamic disk group with a volume created on it. This disk group should be separate from the disk group that you create for the application data. Use the Microsoft Failover Cluster Manager to: Add the clustered disk group as a resource to the cluster. Configure cluster quorum settings. For a quick reference guide to configure a dynamic quorum resource, see: Configuring high availability for Microsoft failover cluster quorum Storage Foundation for Windows documentation for other releases and platforms can be found on the SORT website.Symantec Data Insight 4.5.1: Documentation Available
Symantec Data Insight 4.5.1 product guides (PDF and HTML pages) are now available on the SORT documentation page. The Symantec Data Insight 4.5.1 documentation set includes the following manuals: Symantec Data Insight Release Notes Symantec Data Insight Self-Service Portal Quick Reference Guide Symantec Data Insight Installation Guide Symantec Data Insight User's Guide Symantec Data Insight Administrator's Guide Third-Party Legal NoticesSymantec Cluster Server (VCS) 6.1 for Windows: Encrypting VCS agent passwords and user passwords
When you edit the VCS "main.cf" configuration file to perform any of the following tasks, you must encrypt the user passwords and the VCS agent passwords: Add VCS users Configure agents that require user passwords You can use the vcsencrypt utility to encrypt the passwords. To encrypt the user passwords, type the following command: vcsencrypt –vcs To encrypt the VCS agent passwords, type the following command: vcsencrypt –agent The VCS 6.1 for Windows release introduces a mode to generate a security key to create more secure passwords, for VCS agents. By default, security key-based encryption is not enabled. To generate a security key, you must add the "SecInfo" cluster attribute to the main.cf file, with a security key as the attribute value. By default, only administrators can generate security keys. Note: You can perform security key-based encryption only using the CLI. The service group configuration wizards do not use security keys to encrypt the agent passwords. For more information about encrypting the agent passwords using security keys, see: Encrypting agent passwords using security keys Generating a security key Encrypting the agent password VCS documentation for other releases and platforms can be found on the SORT website.