Veritas Access 7.2: Documentation available
The documentation for Veritas Access 7.2 is now available at the following locations: PDF versions: SORT documentation page Late Breaking News: http://www.veritas.com/docs/000116052 Hardware Compatibility List: http://www.veritas.com/docs/000019707 The Veritas Access 7.2 documentation set includes the following manuals: Getting Started Veritas Access Quick Start Guide Release Notes Veritas Access Release Notes Installation Guide Veritas Access Installation Guide Administrator's Guide Veritas Access Command-Line Administrator's Guide Troubleshooting Guide Veritas Access Troubleshooting Guide Legal Notices Veritas Access Third-Party License Agreements
Veritas InfoScale 7.2: Documentation available
The documentation for Veritas InfoScale 7.2 is now available at the following locations: PDF and HTML versions: SORT documentation page Late Breaking News: https://www.veritas.com/support/en_US/article.000116047 Hardware Compatibility List: https://www.veritas.com/support/en_US/article.000116023 Software Compatibility: https://www.veritas.com/support/en_US/article.000116038 Manual pages: AIX,Linux,Solaris The Veritas InfoScale 7.2 documentation set includes the following manuals: Getting Started Veritas InfoScale What's New Veritas InfoScale Solutions Getting Started Guide Veritas InfoScale Readme First Release Notes Veritas InfoScale Release notes Installation guide Veritas InfoScale Installation guide Configuration and Upgrade guides Storage Foundation Configuration and Upgrade guide Storage Foundation and High Availability Configuration and Upgrade guide Storage Foundation Cluster File System High Availability Configuration and Upgrade guide Storage Foundation for Oracle RAC Configuration and Upgrade guide Storage Foundation for Sybase ASE CE Configuration and Upgrade guide Cluster Server Configuration and Upgrade guide Legal Notices Veritas InfoScale Third-party Software License Agreements For the complete Veritas InfoScale documentation set, see the SORT documentation page.
Veritas Risk Advisor: Working with Reports
Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime. VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches. VRA’s Report Generator automatically generates detailed reports describing your configuration and the gaps that it detected from information extracted from the VRA database. VRA allows you generate multiple reports at the same time. Also you can export the content into the MS Word, PDF, and MS Excel format. VRA Report Types VRA has the following reports: Scan Status System Event Log Ticket Details Storage Allocation Optimization Unreplicated Data on Replicated Hosts NetApp Filer Replication Summary Unsynchronized Remote Replication Old Replicas Standby Pairs and so on Report scheduling VRA also lets you schedule when reports are automatically generated and sent to one or more email destinations that you configure. New reports automatically generate each time before they are sent. You may also choose to save the generated reports in the file system and access them later. Learning More For more information on working with Reports, see “VRA reporting” in the Veritas Risk Advisor User’s Guide. You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.
Query regarding stopping of vcs
Hi Team, Could you please suggest on this, To stop the vcs and leaves the application running we use, hastop -all -force and then start the vcs with hastart. But, under which condition do we have to use this command "hastop -all -force." when this operation will require to keep the application running and do VCS stop and start. When this is required to use" hastop -local " OR hastop -all to stop the VCS and application. Please explain. Thanks AllaboutunixVeritas InfoScale 7.1: Documentation available
The documentation for Veritas InfoScale 7.1 is now available at the following locations: PDF and HTML versions:SORT documentation page Late Breaking News: https://www.veritas.com/support/en_US/article.0001072139 Hardware Compatibility List: https://www.veritas.com/support/en_US/article.000107677 Software Compatibility: https://www.veritas.com/support/en_US/article.000107212 Manual pages: AIX,Linux,Solaris The Veritas InfoScale 7.1 documentation set includes the following manuals: Getting Started Veritas InfoScale What's New Veritas InfoScale Solutions Getting Started Guide Veritas InfoScale Readme First Release Notes Veritas InfoScale Release notes Installation guide Veritas InfoScale Installation guide Configuration and Upgrade guides Storage Foundation Configuration and Upgrade guide Storage Foundation and High Availability Configuration and Upgrade guide Storage Foundation Cluster File System High Availability Configuration and Upgrade guide Storage Foundation for Oracle RAC Configuration and Upgrade guide Storage Foundation for Sybase ASE CE Configuration and Upgrade guide Cluster Server Configuration and Upgrade guide Legal Notices Veritas InfoScale Third-party Software License Agreements For the complete Veritas InfoScale documentation set, see the SORT documentation page.Veritas Risk Advisor: Working with the Comparison Module
Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime. VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches. What is Comparison Module The Comparison module helps you identify the host configuration drifts hiding in your IT. Such drifts often fail cluster failover processes, and reduce the availability of your organization’s applications. In this module, you can create comparison groups that include hosts, clusters, or business entities, and easily track configuration differences between them. The Comparison module uses worksheets and comparison groups. Worksheet A worksheet is a logical container of comparison groups. It also contains all suppressions and difference monitoring information. Worksheets are defined and saved at the user level, which means that each user has his/her own worksheet. Comparison Groups A comparison group is a dynamic group of hosts that you want to compare. The following types of comparison groups are available: Hosts Clusters Business Entities Golden Copy Each group type behaves differently in terms of the group scope and comparison functionality. You begin by creating a worksheet, and then by creating comparison groups. Once defined, comparison groups can be assigned to a worksheet. Once the worksheets and comparison groups are created, you can compare the host configurations with the following options: Hardware Software Operating System Users and Groups OS Kernel Parameters / Limits Learning More For more information on working with Comparison Module, see “Using the Comparison module” in the Veritas Risk Advisor User’s Guide. You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.
Veritas Risk Advisor: Working with tickets
Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution. VRA lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce risk of downtime. VRA scans your environment and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches. What is a ticket? When VRA detects a gap in your disaster recovery and/or high availability, it issues a ticket. The ticket specifies the problem and the environment entities associated with that problem. For example, VRA can identify: Critical data that is not protected properly. Standby hosts that do not have access to the replicated data. Service Level Agreements (SLAs) that are too strict or too lenient. Inconsistent access to storage by cluster nodes. Searching for tickets The VRA Tickets module lets you filter the list of tickets in your system to find a specific ticket or ticket type. After VRA displays your query search results, you can: Group the results by criteria that you specify. Drill down to see ticket details. View the network topology related to the ticket in the Topology module. Group the results by criteria that you specify. A full description of the ticket is provided, including an explanation of the problem and the items in your environment that are involved. The impact on your system is also shown with suggestions on how to resolve the ticket. Working with tickets You can perform a variety of operations on a ticket during its lifecycle. Mark the ticket as resolved. The next time VRA scans your system, it will consider this issue closed. Suppress a ticket. A suppressed ticket indicates that you are aware of this problem, but you do not want to be informed about it again during the next full system scan. Open the Topology module. You can open the topology module displaying the items relevant to the ticket. Add a note to a ticket. You can add a note to a ticket that describes it in more detail. You can filter by note text to make it easier to find a specific ticket(s). Add a star rating to indicate its level of important. (One star is the lowest ticket rating and five stars the highest.) You can then sort your tickets by rating to quickly see your most important issues. You can also perform operations on multiple tickets. Learning more For more information on working with tickets, see “Using the Tickets Module” in the Veritas Risk Advisor User’s Guide. You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.Veritas Resiliency Platform 1.1: Using virtual business services
Any business service is typically made up of multiple components, databases, applications, and web servers. For a business service to work properly, all of its tiers and components must be up and working together. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop. To ensure business continuity, make sure that not just the individual tiers are up and running but also the entire business service. For example, a payroll business service might include a web server, a database, and a payroll application. The payroll application requires the web server, application, and the database to be up and running to provide payroll service. Even if one component were down, the payroll service would be down. From a business perspective, the payroll service is unavailable without the web server and the database also being available. The logical dependencies between the parts of the business service determine the relative order in which they must start and stop to continue to provide the service. A virtual business service (VBS) is a multi-tier business service. In Veritas Resiliency Platform, a VBS lets you group multiple services as a single unit for visualization, automation, recovery, and controlled start and stop in the desired order. A VBS is composed of resiliency groups, the unit of management and control in Resiliency Platform. You organize related assets into a resiliency group and manage and monitor them as a single entity. Within a VBS, resiliency groups are arranged in tiers. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop. For example, you can group a web server resiliency group, a database resiliency group, and a payroll business logic resiliency group into a VBS called payroll. The database resiliency group must start first, so the database resiliency group must go in the lowest tier. The application server resiliency group must start after the database resiliency group, so it goes in the next tier. The web server resiliency group must start last, so it goes into the top tier. The Resiliency Platform console lets you create a VBS by dragging and dropping resiliency groups into tiers. The console also includes a graphic representation of the order in which they start and stop. Creating a virtual business service Resiliency Platform also lets you customize a VBS to speed up start and stop operations of the resiliency groups within it if some dependencies are not required. Customizing a virtual business service Veritas Resiliency Platform documentation can be found on the SORT website.
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.Veritas SFHA 6.2: SmartIO support for SF Oracle RAC environments
The SmartIO feature of Storage Foundation and High Availability Solutions (SFHA Solutions) enables data efficiency on your SSDs through I/O caching. With SmartIO, you can optimize the cost per IOPS. SmartIO does not require in-depth knowledge of the hardware technologies underneath. SmartIO uses advanced, customizable heuristics to determine what data to cache and how that data gets removed from the cache. The heuristics take advantage of SFHA Solutions' knowledge of the characteristics of the workload. SmartIO supports read and write caching for VxFS file systems mounted on VxVM volumes, in several caching modes and configurations. In SF Oracle RAC environments, when SmartIO is enabled on multiple nodes, the Group Lock Manager (GLM) library keeps cache on each node coherent. Read caching for applications running on VxVM volumes Read caching for applications running on VxFS file systems Database caching on VxFS file systems Database caching on VxVM volumes Note: SmartIO writeback caching is not supported in SF Oracle RAC environments. To use SmartIO, you set up a cache area on the target device. You can do this task simply with one command, while the application is online. When the application issues an I/O request, SmartIO checks to see if the I/O can be serviced from the cache. As applications access data from the underlying volumes or file systems, certain data is moved to the cache based on the internal heuristics. Subsequent I/Os are processed from the cache. You can also customize which data is cached, by adding advisory information to assist the SmartIO feature in making those determinations. For more information, see the Storage Foundation and High Availability Solutions SmartIO for Solid State Drives Solutions Guide. Veritas SFHA documentation for other releases and platforms can be found on the SORT website.