Introduction Monitoring 

To ensure that your server backups are always up and running properly, the Server Backup Management Service includes a monitoring feature that generates alert emails to notify you as project owner in case of any issues with your server backup.

Monitoring Alert Notification

The following steps describe all types of alert emails that you can receive, as well as possible solutions for each case.

Unable to create a backup when the backup quota is reached

Example-Mail 1: "Requested backup exceeds allowed Backup gigabytes quota. Requested 200G, quota is 1000G and 880G has been consumed."

This email is sent to all Project Owners and Project Admins when the requested backup exceeds the allowed Backup quota in gigabytes. I.e. 200Gb were requested, the quota is set to 1000Gb, but 880Gb have already been consumed.

Possible solutions:

• Try to reduce the amount of backups in your project to a necessary minimum by cleaning up existing backups, that are not required anymore.
• Reconfigure the defined backup schedules in your project to create backups at a reasonable recurrence rate.
• If you need the backup quota in your project to be increased, please feel free to contact our professional support colleagues via JIRA ticket.

Example-Mail 2: "BackupLimitExceeded: Maximum number of backups allowed (350) exceeded"

This email is sent to all Project Owners and Project Admins when the maximum number of 350 allowed backups is exceeded.

Possible solutions:

• Try to reduce the amount of backups in your project to a necessary minimum by cleaning up existing backups, that are not required anymore.
• Reconfigure the defined backup schedules in your project to create backups at a reasonable recurrence rate.
• If you need the allowed number of backups in your project to be increased, please feel free to contact our professional support colleagues via JIRA ticket.

Unable to create a backup from schedule for server with id: {{server_id}}

Example-Mail: "Unable to create backup, because there is already running process for one or more of the scheduled for backup volumes attached to server with id {{server_id}}"

This email is sent to all Project Owners, Project Admins and Project Members when there is already a process running for one or more scheduled backups for volumes attached to a server.

Possible solutions:

• Reconfigure defined backup schedules and increase the time of recurrence or delete excessive backup schedules in your project to avoid overlapping backup processes. The runtime of your backup depends on the performance class of your chosen storage type and the size and amount of volumes to be backupped.