Backup and Restore Across Versions
search cancel

Backup and Restore Across Versions

book

Article ID: 444755

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

Symantec Messaging Gateway backups are only restorable to the same version and build they were created on. For example, a backup generated from version 10.8.1 cannot be restored directly to a 10.9.2 installation.

  • Database Schema Changes: Each major and minor release typically includes database schema updates. Restoring an older backup to a newer version would lead to data corruption or service failure because the new software expects a different database structure than what is contained in the old backup.
  • Role Restrictions: Starting with version 10.8.1, restoration is further restricted by the host's role. A backup from a Central Control Center can only be restored to another host configured as a Central Control Center.

Resolution

Recommended Migration and Upgrade Path

To migrate data from an older installation to a newer version, you must follow a staged approach:

  1. Version Matching: Install a new appliance using the exact ISO version of the source system (e.g., install 10.8.1 to match your 10.8.1 backup).
  2. Restore: Perform the restoration of the backup onto this matching version.
  3. Sequential Upgrade: Once the restoration is successful and the system is stable, perform the sequential upgrade steps (e.g., 10.8.1 → 10.9.0 → 10.9.1 → 10.9.2) using the command line interface (CLI).

What is (and is not) Restored

When performing a restore, it is important to note which settings are handled by the backup file:

 
 
Data TypeStatus during Restore
Policies & ConfigurationOverwritten by backup data.
Network SettingsPreserved: Hostname, IP address, Gateway, and DNS are not overwritten.
License FilesNot included: The new appliance must be licensed separately before or after the restore.
Message Audit LogsNot included: These are stored per-scanner and require a separate manual utility for backup.

Summary of Best Practices

  • Always keep the original version ISO available in case a rollback is required.
  • Verify that both the version number and the build number match exactly between the backup source and the restore target.
  • For the specific commands and procedures, refer to Backup and Restore the Messaging Gateway.