This monitor tracks the VMware vSphere Profile-Driven Storage Service Health Alarm.
By default, the alarm is triggered by the following event:
- vim.event.HealthStatusChangedEvent: Health status of the VMware vSphere Profile-Driven Storage Service changed.
Check whether the VMware vSphere Profile-Driven Storage Service is running. If the service is stopped, try starting it again. For more information on stopping, starting, or restarting VMware vCenter Server 6.0 services, see this VMware KB article. Try re-installing the Profile-Driven Storage Service, as described in this VMware KB article. If the VMware vSphere Profile-Driven Storage Service fails to start, see these VMware KB articles for additional troubleshooting guidelines:
- VMware vSphere Profile-Driven Storage service fails to start after rebooting vCenter Server (KB2074505)
- Profile-Driven Storage stops working after system restart (KB2001804)
- Profile Driven Storage service fails to start after upgrading to vCenter Server 5.5 (KB2081420)
- Upgrading to vCenter Server 5.0 Update 1, 5.1, or 5.5 fails and the installation wizard is interrupted (KB2017147)
For more information on the issue, check vSphere Profile-Driven Storage logs.
See the Help Center for more information including reference lists of all Rules and Monitors and full set of User Guides for the Veeam MP for VMware.
See the VMware Online Documentation for more information on VMware vSphere, in particular: