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.1.9KViews1like0Comments
Service group concurrency violation
I have two groups for the VCS cluster, App_Cluster & App_Notifier setup in an active/passive setup. The App_Notifier runs the vcs notifer server and send out e-mail on Error level events. The App_Cluster contains all the service to be monitored. Everything is running fine, but recently with all our appliances in development we have seen an issue when we reboot the standby box we get a VCS SevereError. I am trying to track down what suddenly is causing this e-mail to be triggered. --- Email sent --- Sent: Sunday, October 14, 2012 11:41 PM Subject: VCS SevereError for Service Group App_Cluster, Service group concurrency violation Event Time: Sun 14 Oct 2012 11:41:06 PM PDT Entity Name: App_Cluster Entity Type: Service Group Entity Subtype: Failover Entity State: Service group concurrency violation Traps Origin: Veritas_Cluster_Server System Name: app-49-59 Entities Container Name: App Entities Container Type: VCS ThanksSolved1.6KViews0likes3Comments
Alerting feature in ApplicationHA
We have the product deployed in vSphere 4.1 but could't see anything related to alerting. When something needs attention as per ApplicationHA for a configured service (in a fault state), how do you get notified ? Didn't see anything except the status info from the ApplicationHA tab.Solved1.6KViews0likes5Comments
