How To Fix SMMSS_ALERTS007 - This alert shows if the last good backup is too old

SMMSS_ALERTS007 - Overview

• Message type: E = Error

• Message class: SMMSS_ALERTS - Message class for MSSQL rz20 messages

• Message number: 007

• Message text: This alert shows if the last good backup is too old

What causes this issue?

The definition of a backup being too old is dependent on the type of
system involved. A production system has threshholds of Green to Yellow
of 3 days and of Yellow to Red of 7 days. A system which is described
with any of the following; DEV, DVL, TEST, QUAL, or SAND, has the
threshholds set at 30 and 60 days respectively.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If your backup is old, take a full database backup. If the threshholds
are not correct, right click and go to properties and set the values to
an appropriate level.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SMMSS_ALERTS007 - This alert shows if the last good backup is too old ?

  The SAP error message SMMSS_ALERTS007 indicates that the last successful backup of the system is considered too old. This alert is part of the SAP Solution Manager's monitoring capabilities, specifically related to the management of system backups. 
  
  Cause:
  The primary cause of this alert is that the backup retention policy has not been adhered to, meaning that the last successful backup was performed a long time ago, which could pose a risk to data integrity and recovery in case of a failure. This situation can arise due to various reasons, including:
  
  Backup Job Failures: Scheduled backup jobs may have failed due to various issues (e.g., storage issues, network problems, or configuration errors).
  Manual Intervention: Backups may not have been performed due to manual oversight or changes in the backup schedule.
  
  Configuration Issues: The backup configuration may not be set up correctly, leading to missed backups.
  Resource Constraints: Lack of resources (disk space, memory, etc.) may