ContentsPrint

Backup and restore policy

It is essential to implement a considered, robust and secure backup policy before any failure or other restore requirements. It is not possible to define a single approach that would meet all possible customer needs; each installation should be assessed before a policy is implemented. Consider the following aspects as a part of such a policy:
  • Ignition settings. These should be printed or saved for each Linux Server after initial ignition.

  • IPOSS/SSLVPN onboarding.xml file: One for each on-boarded system should be saved.

  • License key data: All ADI license key files should be saved.

  • Manual configuration backup for each IP Office after initial installation and major configuration change.

  • Manual configuration backup for Voicemail Pro after initial installation and major configuration change.

  • Manual configuration backup for one-X Portal after initial installation and major configuration change.

  • Periodic configuration backup for every IP Office.

  • Periodic configuration backup for one X Portal – Primary and Application Server only

  • Periodic configuration backup for Voicemail Pro – Primary only

  • Periodic voice mailbox and recording data backup – Primary only

  • The timing of backup operation: This should be done when little or no traffic is present on the target system, but the backup process itself is not service-affecting.

  • The timing of restore operation: This should be done when no traffic is present on the restored system. The restore process is service affecting – any restored component will automatically restart immediately the restore is complete.

  • Security, integrity, location and capacity of backup data storage.
    noteNote

    backup of an Avaya Linux server does not include any local backup data.

  • Security of backup data communication

  • Backup prior to any software upgrade

  • Retention of backup data for older software versions should a downgrade need to be considered.

The period and number of unique instances selected should reflect the frequency of change, the consequence due to data loss, and the storage capacity of the backup data server. Periodic backups using Web Manager have up to 14 instances and a single manual backup instance, after which thesystem overwrites the oldest set. These instances are for each backup server and regardless of the backup data set; for example two weekly separate backup tasks of all IP Office configurations and Voicemail configuration overwrite the first set after 7 weeks.