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.
Configuring VCS with main.cf and types.cf files
From release 7.0 onwards, VCS is a component that is bundled with InfoScale Availability and InfoScale Enterprise products. When you configure VCS, the Veritas High Availability Engine needs to know definitions of the cluster, service groups, resources, and dependencies among service groups and resources. VCS uses the main.cf and types.cf configuration files to convey the cluster, service groups, and resource definitions. The main.cf file comprises include clauses and definitions for the cluster, systems, service groups, and resources. The SystemList attribute designates the priority order and the list of systems where a service group can come up online. The types.cf defines the standard resource types for the VCS engine and the data type that can be set for an attribute. It also defines the parameters that are passed to the VCS engine. These configuration files can be generated in a variety of ways. For more information, see VCS configuration language. By default, both these files reside in the /etc/VRTSvcs/conf/config file. Only the first online system in the cluster reads the configuration files and keeps it in memory. Systems that are brought online after the first system derive configuration information from the existing systems in the cluster. You can also define environment variables to further configure VCS. For more information, see VCS environment variables. You can find other versions of Cluster Server on the SORT documentation page.
Veritas InfoScale Enterprise 7.1: SmartIO caching profiler tool
The Smartassist tool analyzes the I/O on the specified target in the system for the specified time, and calculates the optimal cache size for the workload. To run the tool from Veritas InfoScale Operations Manager (VIOM), refer to VIOM administrator's guide. Smartassist tool supports following targets: List of device paths List of VxVM or LVM volumes paths List of VxVM or LVM volumes paths List of filesystem mount points Oracle/Sybase/DB2 database instance List of shared volumes/diskgroups of VxVM List of CFS mount points The tool works in two phases: Start phase The tool traces the I/O on the specified target for the specified time and stores the trace output in the specified directory. In case of disk devices, which have multiple paths, it is advisable to specify all the paths to get correct results. Using VxVM or LVM volume devices, in such cases, is more convenient. By default, the start phase runs for 3600 seconds. Analyze phase The tool parses the output generated in the start phase and uses the SmartIO algorithms to calculate the optimal cache size. The optimal cache size, read hits, latency gain, performance forecast and share in cache for each target are displayed on the terminal. For information on downloading and installing the tool, see the readme file on the SORT website. Veritas InfoScale documentation for other releases and platforms can be found on the SORT website.Veritas InfoScale Enterprise 7.1: Block-level encryption of VxVM data volumes
VxVM provides advanced security for data at rest through encryption of VxVM data volumes. Encryption is a technology that converts data or information into code that can be decrypted only by authorized users. You can encrypt VxVM data volumes to: •Protect sensitive data from unauthorized access •Retire disks from use or ship them for replacement without the overhead of secure wiping of content The implementation uses the Advanced Encryption Standard (AES) cryptographic algorithm with 256-bit key size validated by the Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2) security standard. You can encrypt volumes or disk groups in your storage environment. VxVM generates a volume encryption key at the time of volume creation. The volume encryption key is secured (wrapped) using a key wrap. The wrapped key is stored with the volume record. The volume encryption key is not stored on disk. You can secure the volume encryption key using one of the following methods: Using Passphrases (PBE) Using Key Management Server for encryption If you encrypt a disk group, all volumes in the disk group are encrypted. Any volume created later on the disk group will also be encrypted by default. Only new volumes that are created using disk group version 220 or later can be encrypted by VxVM. When you start an encrypted volume, VxVM uses the key wrap to retrieve the volume encryption key and enable access to the volume. Some of the administrative tasks you can perform are as follows: Creating encrypted volumes Viewing encrypted volumes Automating startup for encrypted volumes Configuring a Key Management Server Veritas InfoScale documentation for other releases and platforms can be found on the SORT website.Veritas InfoScale Enterprise 7.1: Managing application I/O workloads using maximum IOPS settings
When multiple applications use a common storage subsystem, it is important to balance application I/O requests in a way that allows multiple applications to co-exist in a shared environment. You can address this need by setting a maximum threshold on the I/O operations per second (IOPS) for the volumes of an application. The volumes of an application are grouped to form an application volume group. The maximum IOPS limit determines the maximum number of I/Os processed per second collectively by all the volumes in an application volume group. When an I/O request comes in from an application, it is serviced by the volumes in the group until the application volume group reaches the IOPS limit. When the group exceeds this limit for a specified time interval, further I/O requests on the group are queued. The queued I/Os are taken up on priority in the next time interval along with new I/O requests from the application. About application volume groups An application volume group is a logical grouping of volumes associated with an application. The group may contain one or more volumes. All the volumes in the application volume group must be selected from the same disk group. The volumes may belong to a private or shared disk group. Set the maximum IOPS threshold on the application volume group to balance multiple application I/O workloads. The IOPS value is set as a combined threshold for all the volumes in the application volume group. Some of the configuration and administrative tasks to manage application I/O workloads are as follows: Creating application volume groups Setting the maximum IOPS threshold on application volume groups Removing the maximum IOPS setting from application volume groups Adding volumes to an application volume group Removing volumes from an application volume group Viewing the IOPS statistics for application volume groups Additional helpful information about this feature can be found at: http://www.veritas.com/community/blogs/quality-service-maxiops-sla?utm_source=symconnect&utm_medium=forum&utm_campaign=socialmedia Veritas InfoScale documentation for other releases and platforms can be found on 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 Allaboutunix
Veritas 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.Understanding NFS and NFSRestart agent
Network File System (NFS) allows network users to access shared files stored on an NFS server. NFS allows you to manageshared files transparently as if the files were on a local disk.For more information about NFS and configuring NFS service groups, refer to the following sections: About NFS Configuring NFS service groups The NFSRestart agent is aCluster Server (VCS)bundled agent.This agent is installed on the system when you install VCS. The NFSRestart agent is configured in conjunction with theNFS agent for failover type shared service groups. The NFSRestart agent manages essential NFS locking services, network status manager, and network lock manager. The agent also manages NFS lock recovery service by recovering the NFS record locks after sudden server crash. The agent prevents potential NFS ACK storms by terminating NFS server services before closing all Transmission Control Protocol (TCP) connections with the NFS client. Refer to the following sections for more information about the NFSRestart agent: Dependencies Agent functions State definitions Attributes Resource type definition Notes for NFSRestart agent Sample configurations Debug log levels In a Veritas Cluster File System environment, instead of the NFSRestart agent, you must configure preonline and postonline triggers for managing NFS services. For more information, refer to the following section: Understanding how Clustered NFS works The links in this article are specific to the Linuxplatform.Veritas InfoScale documentation for other releases and platforms can be found on the SORT website.
Understanding the V-16-1-40130 error message for UNIX
Understanding the V-16-1-40130 error message for UNIX The hares command administers resources in a Veritas Cluster Server (VCS) cluster. Resources are individual representations of the elements that are required for a service group to be available, such as a volume, a database, or an IP address. Among the many hares options, -display and –state are frequently used to display resource information: # hares –display resource_name # hares -state resource_name Error conditions Sometimes, when you run theses commands, you get the following message: VCS WARNING V-16-1-40130 Resource name does not exist in the local cluster The error occurs when the resource is not configured in the local cluster. When the resource is configured in a remote cluster, the message is also displayed, but is followed with the resource state in the remote cluster. Investigating the error If you want to check the resources that are configured in the local cluster or in a global group, execute the following command: # hares –list Then you can examine the information of any resources appear in the output by re-entering either of the previous commands: For resources in the local cluster: # hares –display resource_name # hares -state resource_name For resources in a global group: # hares –display resource_name –clus local_cluster_name/remote_cluster_name # hares -state resource_name –clus local_cluster_name/remote_cluster_name If you need to, you can also administer the resources by: Adding resources Deleting resources Modifying resources Linking or unlinking resources Bringing resources online Taking resources offline You can find more Veritas InfoScale and SFHA Solutions documentation on the SORT website. 1871