Complete the steps in this procedure to configure an email server.
The SMTP Server core settings appear.
|SMTP Server||Enter the name of the email server to be used by the email notification template. The naming convention includes the host name, domain, and suffix; for example, smtp.gmail.com.|
|From||Enter a return email address. It is used to specify the return email address for the email notification template; for example, email@example.com.|
|User name||Enter a user name for the email server.|
|Password||Enter the password associated with the user name required to access the email server.|
|Port||Enter a port number. It is used to identify the port for the email server; for example, the port 587 for Gmail.
The default is 25.
|Timeout (seconds)||Enter an integer value to specify how long to try to connect to the email server. It is used to establish the time in seconds before a timeout occurs.
The default is 60 seconds.
|TLS||Select this option if the mail server uses a secure connection such as Transport Layer Security (TLS) or Secure Sockets Layer (SSL).|
When you enable notifications of Rapid Recovery events by email, a default template is created for you by default. The SMTP email server defined for the Core uses this template to send notifications regarding Rapid Recovery events by email.
This topic describes the process of configuring the default email notification template or customizing the content. Using the Restore Default option, you can restore changes to the default notification template at any time.
Complete the steps in this procedure to configure an email notification template.
The Notifications page appears.
The Edit Email Notification Configuration dialog box appears.
|Enable email notifications||
This setting enables or disables the email notification template.
The contents of this text field control the subject line for email messages sent as notifications of system events. The default email subject line is as follows:
<hostName> <level>: <name> for <agentName>
The contents of this text area control the body for email messages sent as notifications of system events. The default email body message is as follows:
<shortCompanyName> <coreProductName> on <hostName> has reported the <level> event "<name>" Date/Time: <localTimestamp> <message> <if(details.errorDetails)> <details.ErrorDetails.Message> <details.ErrorDetails.Details> <endif> --- About this event: <description> <coreAdminUrl>
|Send Test Email||Clicking this button sends a test email message to the email address you specify in the resulting Send Test Email dialog box.|
|Restore Defaults||Clicking this button removes any customized changes from the email template, and restores the Email Subject and Email fields with the default contents described in this table.|
|OK||Clicking this button confirms and saves the settings in the Edit Email Notification Configuration dialog box.|
|Cancel||Clicking this button cancels any changes in the Edit Email Notification Configuration dialog box.|
|hostName||The host name of the Core|
|details||The details object of the specific event.|
|agentName||The name of the protected machine associated with this event, if the event has a scope of a single protected machine.|
|repositoryName||The name of the repository associated with this event, if the event has repository scope.|
|jobSummary||The summary of the job associated with this event, if the event has job scope.|
|remoteSlaveCoreName||The name of the remote target core associated with this event, if the event has target core scope.|
|remoteMasterCoreName||The name of the remote source core associated with this event, if the event has source core scope.|
|productName||The name of the product, for example 'AppAssure Core' or 'Rapid Recovery Core.' This product name can be changed for branding using white labeling.|
|companyName||The name of the company selling the product.|
The Email Subject is used to define the subject of the email notification template, for example, <hostname> - <level> <name>.
You can configure more than one notification group with different notification parameters.
Notification groups can be set at the Core level, or for each specific protected machine.
Complete the steps in this procedure to configure notification groups for alerts.
The Notifications page appears.
The Custom Notification Groups page appears.
The Custom Notification Groups page appears.
The Add Notification Group dialog box appears.
Notification groups let you define sets of specific events for which users are alerted, and the manner in which that notification takes place. You can configure alerts to be sent by the following methods:
The Add Notification Group dialog box contains a general description area and two tabs:
|Name||Enter a name for the event notification group. This information is required.
The value you enter for the notification group name cannot be changed later.
|Description||Enter a description that clarifies the purpose for the event notification group. This information is optional.|
|All Alerts||To create alerts for all events, select All Alerts.|
|Errors||To create alerts for errors, from the Select Types menu, click Error. This is represented by a red X.|
|Warning||To create alerts for errors, from the Select Types menu, click Warning. This is represented by a yellow exclamation point icon.|
|Info||To create alerts for informational messages, from the Select Types menu, click Info. This is represented by a blue i.|
|Restore Default||To restore alert types to the default, from the Select Types menu, click Restore Default. This is represented by a dark blue left-facing arrow.|
|Notify by email||Designate the recipients of the email notification. You can choose to specify separate multiple email addresses as well as blind and carbon copies.
You can choose:
|Notify by Windows Event Log||Select this option if you want alerts to be reported through the Windows Event Log.|
|Notify by syslogd||Select this option if you want alerts to be reported through syslogd. Specify the details for the syslogd in the following text boxes:|
|Notify by Toast alerts||Select this option if you want the alert to appear as a pop-up in the lower-right corner of your screen.|
|Notify by Alerts||Select this option if you want alerts to appear as pop-up windows located at the bottom right side of the Core Console.|
|Notify by SNMP trap||The Rapid Recovery Core serves as an SNMP agent, sending traps (notifications about specific events) to an SNMP manager. The result is the reporting of Core information such as alerts, repository status, and protected machines. Select this option if you want to notify Core events by SNMP trap. You must also specify a trap number. For example, the default trap number used by the Rapid Recovery Core is 162.|
The ability for administrators to receive alerts upon certain events is critical. Nonetheless, in certain circumstances, receiving repeated notification of events that you are aware of can also be frustrating or inconvenient. Even if an alert is generated due to an environmental failure that you wish to know about immediately, it is possible for the same error condition to generate hundreds or thousands of events in the event log. To reduce repetition in the event log, and reduce the inconvenience of receiving repeated e-mail notifications for the same event in the Core Console, Rapid Recovery includes a repetition reduction setting, which is enabled by default and set at 5 minutes. This setting can be set as low as 1 minute and as high as 60 minutes. It can also be disabled entirely.
When repetition reduction is disabled, then every time an event of the same type and scope occurs, it is logged in the database. Regardless of how much time passed since that event previously occurred, each new occurrence is shown in the Alerts portion of the Events tab.
When repetition reduction is enabled (for example, with the default time of 5 minutes), then the first time that specific event occurs, it is logged in the events database and shown in the alerts log. If subsequently an event of the same type and scope is again logged within the threshold of time established, then the count for the event in the database increases by 1 for each repeat occurrence within that threshold. The log shows in the Alerts portion of the Events page. However, it displays the event only once, with the date and time of the most recent occurrence. The events log is not updated with the same event until the threshold of time from the first occurrence expires. For example, if set for 5 minutes and the event occurs again 6 minutes later, it appears in the log and you receive another email message.