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.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.
detaching vmdk files on vmware vm
When the application failover happens in VMware Guest enviorments, the VCS is responsible for failing over the application to other vm/vcs node on diffrent ESX host. In a scenario where the ESX/ESXi host itself faults, the VCS agents begin to fail over the application to the failover target system that resides on another host. The VMwareDisks agent communicates with the new ESX/ESXi host and initiates a disk detach operation on the faulted virtual machine. The agent then attaches the disk to the new failover target virtual machine. In this senario, how are the stale i/o from failing over guest/ESX host avoided? Are we on the mercy of VMware to take care of it? With SCSI3 PR this was the main problem that was solved. Moreover in such senario's even a garceful online detach wouldnt have gone through. I didnt find any references on VMware discussions forums as well. My customer wants to know about it, before he can deploy the application. Thanks, Raf
SFHA Solutions 6.1: Protecting & Restoring VxVM disk group configuration information
The disk group configuration information is stored on disk in the VxVM private region. The default size of the private region is 32 megabytes. Stored disk group configuration includes a disk header label, configuration records for VxVM objects (such as volumes, plexes and subdisks), and an intent log for the configuration database. Configuration information must be stored on at least one disk in a VxVM disk group. The disk group configuration backup and restoration feature allows you to save and restore all configuration data for VxVM disk groups. Configuration information is critical for the disk group. By using the configuration data from a backup, you can: Reinstall damaged private region headers of VxVM disks in a disk group. Recreate a corrupted disk group configuration. Recreate a disk group and the VxVM objects within it. Recreate a disk group on another system if the original system is not available. Backing up disk group configurations Whenever a configuration is changed, the vxconfigbackupd daemon automatically backs up information about a disk group’s new configuration. You can use the vxconfigbackup utility to manually back up the disk group configuration at any time for one or more disk groups by specifying the disk groups either by name or by identifier (ID). If you do not specify a disk group, all disk group configurations are backed up. For more information on backing up configurations, see: Backing up and restoring disk group configuration data (AIX, Linux, Solaris) About disk group configuration backup (AIX, Linux, Solaris) Backing up a disk group configuration (AIX, Linux, Solaris) vxconfigbackupd(1M) 6.1 manual pages: AIX Linux Solaris vxconfigbackup(1M) 6.1 manual pages: AIX Linux Solaris For information on restoring configuration data, refer to the following Symantec Connect article: SFHA Solutions 6.0.1: Restoring disk group configuration information using vxconfigrestore Symantec Storage Foundation and High Availability documentation for other releases can be found on the SORT website.SFHA Solutions 6.1 (Linux): Change replication direction using vfradmin job promote and vfradmin job recover commands
The File Replicator (VFR) vfradmin command now supports the job promote and job recoverkeywords that enable you to change the file replication direction with a single command. You can use the job recover command after a disaster occurrs, and the job promote command under normal circumstances. Use cases for the vfradmin job promote and vfradmin job recover commands include: Performing a VFR switchover Performing a VFR failover after a disaster Recovering a failed site if the failed source node comes up again Recovering a failed site if a new node is assigned as the target For more information regarding recovering after a site disaster or network disruption occurs, see: About error recovery after a site disaster or network disruption using VFR For more information on VFR, see the following sections in the Storage Foundation and High Availability Solutions Replication Administrator's Guide: About File Replicator How File Replicator works Administering File Replicator vfradmin (1M) manual page: Linux Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on theSORT website.SFHA Solutions 6.0.1: Performing volume recovery operations using vxrecover
The Veritas Volume Manager (VxVM) vxrecover utility performs volume recovery operations. The utility allows you to attach plexes, perform RAID-5 subdisk recovery, and perform data resynchronization operations for volumes. You can perform recovery operations on: Specified volumes All volumes under the specified volume sets Volumes residing on the disks specified by the medianame attribute If you do not specify a medianame, volume, or volume set, the recovery operation applies to all volumes, or all volumes in the specified disk group. You can also use vxrecover to start the volumes to make them available for use, and defer their recovery. vxrecover also provides options to perform recovery in the background and specify several attributes, such as the I/O size. By default VxVM enables and starts any disabled volumes in the disk group when you import the disk group. If automatic volume recovery is turned off volumes are disabled after a move, split, or join operation. You can use the vxrecover command to manually recover the volume. Another use case for the vxreover utility is to recover volumes after any issues with its storage or an unclean system restart. Additional use cases for using the vxrecover utility include: Recovering plexes - Partial disk failure mail messages Moving disk groups between systems Joining disk groups vxrecover (1M) 6.0.1 manual pages: AIX HP-UX Linux Solaris Veritas Storage Foundation and High Availability documentation for other releases and platforms can be found on theSORT website.SFHA Solutions: Administering a Recovery Plan using the Veritas Operations Manager Virtual Business Services Availability Add-on 5.0
A Recovery Plan is an automated set of steps that need to be run when a disaster or contingency arises. The Veritas Operations Manager Virtual Business Services (VBS) Availability Add-on 5.0 enables you to create and store a Recovery Plan, manually run a Recovery Plan, and monitor and log its progress and status. You can create a Recovery Plan by creating a group of multiple VBS and service groups, and then run predefined tasks on these entities in a desired sequence. You can specify the following tasks in a Recovery Plan: Start or stop VBS Bring a service group online, or take a service group offline Run custom scripts When you create a Recovery Plan, you can specify whether or not a step is critical. If a task is marked as critical and it fails, then the Recovery Plan execution is stopped and the remaining tasks are not performed. Using the Veritas Operations Manager console, you can perform the following tasks: Create a Recovery Plan Edit a Recovery Plan Delete a Recovery Plan Run a Recovery Plan Recovery Plan is not supported on the Management Server, the managed host, or VBS Availability Add-on versions prior to 5.0. Only domain administrators can create, edit, delete, and run the Recovery Plan. Other non-guest users can run only the Recovery Plan. For more information on administering Recovery Plans using the Veritas Operations Manager Virtual Business Services Availability add-on 5.0, see: Virtual Business Service–Availability User's Guide For more information on managing Virtual Business Services using VOM and the VBS command line interface, see: SFHA Solutions 6.0.1: About managing Virtual Business Services using VOM and the VBS command line interface Veritas Operations Manager documentation for other releases can be found on the SORT website.
SFHA Solutions 6.0.1: About managing Virtual Business Services using VOM and the VBS command line interface
Virtual Business Services (VBS) is a feature that represents a multi-tier application as a single consolidated entity in Veritas Operations Manager (VOM). It builds on the high availability and disaster recovery features provided by Symantec products, such as, Veritas Cluster Server (VCS) and Symantec ApplicationHA. VBS enables administrators to improve operational efficiency of managing a heterogeneous multi-tier application. You can control VBS from the VOM graphical user interface and the VBS command line interface (CLI). When you install SFHA, the VBS installation packages, VRTSvbs and VRTSsfmh, are automatically installed on the nodes. From the VOM interface, you can define a VBS that consists of service groups from multiple clusters. You can also use the VBS CLI to performcommand line operations on that VBS. The clustering solutions that are offered today can only manage applications running on the same operating system. So, deploying the clustering solutions for a multi-tier, cross-platform setup can be difficult to manage. VBS can work across a heterogeneous environment to enable IT organizations to ensure that the applications across tiers can be made highly available. A typical multi-tier environment comprises of a database on a UNIX server, applications running in a Kernel-based Virtual Machine (KVM) on a Linux server, and a Web server on a VMware virtual machine. VBS works across the heterogeneous environment to communicate between local operating systems to see the end-to-end state of multi-tier applications and to control start and stop ordering of the applications. With VBS there are relationships between tiers that you can customize to fit your environment. You can set up policies for the events that result in a failure or for the specific events that happen on tiers. For example, you can set up a policy that restarts the application service groups when the database service group fails over to another node. For more information about VBS features, components, and workflow, see: Features of Virtual Business Services Sample Virtual Business Service configuration Virtualization support in Virtual Business Services About the Veritas Operations Manager policy checks for Virtual Business Services About the Virtual Business Services components Virtual Business Services workflow Support matrix for VBS Prerequisites for using VBS Availability Add-on You can configure and manage a VBS created in VOM by using the VOM VBS Availability Add-on utility. You can also control a VBS from the VBS CLI, but you cannot create a VBS from the VBS CLI. The VBS Availability Add-on utility enables you to: Start or stop service groups associated to a VBS. Establish service group relationships that decide the order in which service groups are brought online or taken offline. Decide the reaction of application components in each tier when an event fault occurs on a tier. Recover a VBS from a remote site when a disaster occurs. For more information about installing the VBS add-on, packages, and configuring a VBS using VOM, see: Installing Veritas Operations Manager Virtual Business Services Availability Add-on Installing the VRTSvbs package using Veritas Operations Manager Configuring a Virtual Business Service For more information on managing VBS using VOM and the VBS command-line, see: Operations using Veritas Operations Manager and command line Starting and stopping Virtual Business Services Viewing the overview of a Virtual Business Service Viewing the Virtual Business Service status from the command line Enabling fault management for a Virtual Business Service Disabling fault management for a Virtual Business Service Fault management overview For more information on VBS commands, troubleshooting issues, and recovery operations, see: Virtual Business Services commands Troubleshooting Virtual Business Services Virtual Business Services log files For more information on managing VBS using VOM and the VBS command line, see: Virtual Business Service-Availability User's Guide Virtual Business Services documentation for other SFHA releases can be found on the SORT website.