Configure Backup Actions
Open an SFTP account and select Actions. Community supports high-level CUCM DRS validation. Essentials+ actions can validate components, notify a team, and retain an additional supported cloud copy after an upload.
Essentials+ — detailed validation, cloud storage, and notification actions.
Build the Success Workflow
Under On Success, select Add Action and choose one or more supported actions:
| UI Label | Tier | Use It To |
|---|---|---|
| CUCM Backup Validation | Community high-level; Essentials+ component detail | Parse DRS metadata and verify the entitled level of backup detail |
| Email Notification (No Attachment) | Essentials+ | Send a compact receipt or validation result |
| Email with Attachment | Essentials+ | Forward a small uploaded file with the notification |
| Webex Teams - Send with Attachment | Essentials+ | Notify a Webex room or direct recipient |
| Upload to Amazon S3 | Essentials+ | Retain a copy in an S3 bucket and key prefix |
| Upload to Azure Blob Storage | Essentials+ | Retain a copy in an Azure container and blob prefix |
For CUCM DRS, put CUCM Backup Validation in the success workflow. On Essentials+, add notification or cloud-storage actions according to the recovery and evidence policy for that cluster.
The Replicate to Remote SFTP action is supported for the dedicated CDR duplication workflow. It is not described here as CUCM DRS backup replication.
Keep remote SFTP replication limited to that supported CDR duplication workflow; do not configure it as a second CUCM DRS backup path.
Add a Failure Workflow
Under On Failure, add a notification that reaches the team responsible for backup recovery. A failure workflow should identify the account and file without exposing credentials or other secrets.
Select Save after changing either group. The Unsaved changes toolbar remains visible until the account configuration is stored.
Personalize Notifications in the Editor
Email actions use the appliance's configured SMTP service. Before adding recipients, configure and test delivery under Appliance Notifications.
Expand CUCM Backup Validation to edit Email Recipients, Webex Room, Email Subject, and Message Body while keeping the Template Variables picker visible. These Essentials+ delivery fields and the substitution preview share one workspace.
Essentials+ — proactive email delivery and validation template variables.
Insert a Template Variable
- Place the cursor in Email Subject or Message Body.
- Find the value under File Context or CUCM Backup.
- Select + beside the variable, or drag it into the editor.
- Confirm the variable appears as a labeled chip, then select Save.
You can also type a supported value such as {{filename}}. The editor converts recognized syntax into the same token chip. When the action runs, Call Telemetry replaces each token with data from that upload or CUCM validation; the saved template remains reusable for later backups.
Use File Context Tokens
These variables are available to Email Notification (No Attachment), Email with Attachment, Webex Teams - Send with Attachment, and CUCM Backup Validation.
| Token | Substituted Value | Fictional Example |
|---|---|---|
{{username}} | SFTP account username | cucm-drs-primary |
{{filename}} | Uploaded file name | DRFComponent_2026-06-18.tar |
{{filepath}} | Full path to the uploaded file | /sftp/cucm-drs-primary/DRFComponent.tar |
{{timestamp}} | Time of the upload event | 2026-06-18 07:08:00 UTC |
Add CUCM Validation Results
The CUCM Backup Validation action adds these variables after it parses the DRS validation data. This concise list contains the variables operators most often need for a pass/fail notification. The in-product picker remains the authoritative list for the installed release.
| Token | Substituted Value |
|---|---|
{{server_name}} | CUCM publisher hostname |
{{version}} | CUCM software version |
{{overall_status}} | Overall backup pass or fail result |
{{success_count}} | Number of successful components |
{{failed_count}} | Number of failed components |
{{failed_components_list}} | Formatted list of failed components and details |
For a concise SMTP alert, use a subject such as CUCM backup {{overall_status}} — {{server_name}}. In the body, combine {{failed_count}} with {{failed_components_list}} so a warning identifies both the count and the affected components.
Only use variables offered for that action. A normal email or Webex upload notification has file context but does not have CUCM validation results. Run a controlled backup after editing a template and review the delivered message before relying on it for recovery alerts.
Useful notification content includes:
- Which account received the upload.
- Which backup file was evaluated.
- Whether validation passed.
- How many components failed.
- Where an operator should review the detailed result.
Use the previewed UI fields rather than pasting API payloads. Passwords, storage keys, and remote credentials belong only in their protected input fields.
Verify the Saved Actions
Run a controlled backup and return to Run History. Confirm each expected action appears independently and reaches Succeeded. A successful validation does not prove that a later cloud-storage action succeeded, so review every row in the workflow.