Symptoms

When attempting to perform a manual database backup (via Main Menu -> Status & Manage -> Database screen) of the Subscriber Database Server's (SDS's) active Site Operations Administration and Maintenance (SOAM) configuration database, the task returns Result '-1,' Status 'exception,' with Result Details indicating 'Backup did not start' and 0% task progress.

Changes

Cause

The cause of this problem is the misconception that the SDS SOAM should have database backups similar to certain other Oracle Communications products that share the same user interface layout and Network/Site OAM architecture.

Solution

No active solution is required.  SDS database backups are taken at the active Network Operations Administration and Maintenance (NOAM) server only, not at the site (SOAM) level.  All configuration and provisioning is done through the NOAM, where the master database is held.

Although the SDS SOAM will allow the 'Backup' to be attempted through its GUI, it will fail by design. The logic is that if any backup file were produced at the SOAM and subsequently used for restoration, it would create data mismatches against the master database held at the NOAM.

The SDS documentation suite does not instruct the operator to attempt creating database backups at the site level, nor does the disaster recovery guide instruct use of a SOAM database for restoration or any other purpose.

This solution has no attachment