Recovery Profile Prompt Display means that the recovery plan has stopped, and is waiting for you to to confirm something. So a protected VM where something is done to it that makes it NOT protected. It will fire if you add a VMDK to a VM and it is held on a non replicated LUN. VM Not Protected is also an important one. This means if someone who should know better, migrates a VM to a protected LUN you will be alerted on it! It means that a VM has just been copied to a LUN that is protected by SRM. Recovery Plan Started / Recovery Plan Execute Test begin are good in the beginning but not really necessary later. Recovery Plan Destroyed – since you lose history when you delete a recovery plan, most users I know don't like to lose the recovery plans.
This is NOT really a good safe way to know if you need to trigger a DR event, but it is still good info. Remote Site Down – this watches the remote side, which should be the protected site, and will fire when the SRM service stops running. For example, if you configure the Remote Side Down alarm to email you when it triggers, and you configured it on the Protected side will it alert you when the Protected side is down? No, it will only alert you when the recovery side is down! You need to think about where to configure alarms. Remember that these alarms exist on both the protected, and recovery sites. You can find the alarms, in SRM, on the Alarms tab, which is next to the Summary tab. Once your vCenter can send email we are ready to check out the alarms. This is important since you will need to configure SRM alarms on both sides. Note that if you are working in Linked Mode, like I am, you can change your vCenter server (from the drop down list at the top of the screen) so you can easily make the change to both sides. See the screen below for what it should look like, and where to add in your SMTP server and the sender account. This is done in the Administration vCenter Server Settings area. The first thing we need to do is to make sure that vCenter can send email. I will also give you ideas of what will trigger them if there is any doubt. I will help you get started with what I think are important and mostly standard alarms. There is a lot of different alarms, and I suspect no one needs all of them, but I also suspect everyone will need a few of them. I have been asked before about which of the SRM alarms should users configure and watch for.