A Disaster Recovery deployment of Avaya Oceana® involves two deployments at two geographically separated data centers, Data Center 1 (DC1) and Data Center 2 (DC2). On each data center, you install Avaya Oceana® and Avaya Analytics™ components with replication of data between a number of elements from DC1 to DC2.
During migration of a Disaster Recovery solution to the latest release, you must consider the hours of operation of the contact center when choosing the appropriate software migration strategy. Each Avaya Oceana® deployment allows downtime during migration. All Avaya Oceana® software migrations require downtime when the system is out of service. Alternate fallback options are available as standard for PSTN voice channels. However, no alternate fallback mechanism is available for digital and WebRTC channels within Avaya Oceana®.
The following table summarizes the supported software migration strategies for migration of Avaya Oceana® from earlier releases to Release 3.10.0.2:
Option |
Migration strategy |
Maintenance window |
Description |
Impact to contact center operations |
Option A |
Simultaneous migration of primary and Disaster Recovery sites |
Maintenance window 1 |
Migrate primary and Disaster Recovery sites in a single maintenance window. |
Avaya Oceana® contact center is unavailable during the maintenance window. |
Option B |
Two-step migration of primary and Disaster Recovery sites |
Maintenance window 1 |
Migrate primary Avaya Oceana® and Avaya Analytics™, and backup Avaya Analytics™ in a single maintenance window 1, place the upgraded primary site back in production, and then proceed to migrate the Disaster Recovery site. |
Avaya Oceana® contact center is unavailable during the maintenance windows. |
Maintenance window 2 |
Migrate Avaya Oceana® including Omnichannel Database in the Disaster Recovery site. Re-enable Disaster Recovery capabilities in the maintenance window 2. |
The maintenance window in Option B is shorter than the single maintenance window of Option A, because it is a two-step software migration process.
The migration steps in Option A and Option B are same for each application in the solution that requires the software update. For software migration, you can choose Option A or Option B but not both.
Before the Avaya Oceana® and Avaya Analytics™ disaster recovery migration, do the following in a separate maintenance window:
