Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
About near real-time discovery of VMware events
The Infrastructure Management Server (IMS) uses VMware events to discover in near real-time a change in the state of a virtual machine (for example, virtual machine powered on) and changes occurring at the vCenter Server infrastructure level (for example, virtual machine created).
The near real-time discovery of VMware infrastructure enables the partial discovery of ESX servers managed under a vCenter Server. This discovery is triggered by the event notification from the VMware vCenter Server to the IMS using SNMP traps. For example, if an SNMP trap is received for a virtual machine (VM1) hosted on ESX1, the IMS runs the discovery cycle only for ESX1. Other ESX servers under that vCenter Server are not re-discovered.
The IMS component of near real-time discovery is xtrapd. After you configure a vCenter Server to send the SNMP traps to the IMS, you add the vCenter Server to the IMS. The xtrapd daemon now detects the SNMP traps that are sent from the specified vCenter Server. The Resiliency Platform database and console are updated with the latest state of the virtual machine or infrastructure changes.
Note:
SNMP version 1 (SNMPv1) and version 2 (SNMPv2) are supported.
For details on supported events, see the following table.
Table: Supported events for near-real time discovery
Discovered state | Event as shown in VMware vCenter Server |
---|---|
Virtual machine powered on | VM powered on |
Virtual machine powered off | VM powered off |
Virtual machine Distributed Resource Scheduler (DRS) powered on | DRS VM powered on |
Virtual machine suspended | VM suspended |
Virtual machine created | VM created |
Virtual machine migrated Hot migration: A powered-on virtual machine is migrated from one ESX server to another ESX server. | VM migrated |
Virtual machine relocated from one ESX server to another Cold migration: A powered-off virtual machine is migrated from one ESX server to another ESX server. | VM relocating |
Virtual machine renamed | VM renamed |
Virtual machine migrated to another host by VMware DRS (Distributed Resource Scheduler) | DRS VM migrated |