PCC SME Community – IP Office June 2024

IP Office

Server Edition Server Backup and Restore

Craig O’Gorman
Principal Technical Support Engineer
ogorman@avaya.com

1
IP Office Server Edition Server Backup
and Restore
• Backup and Restore
• Backup and restore policy
• Backup and restore protocols
• Disk space required for backups
• Checking the backup server’s backup quota
• Backup data sets
• Creating a remote server connection
• Backing up a server/servers
• Restoring from the backup server
• Restoring a failed server
• SOLN377106 – Virtual VMWare Restore Process

2
Backup and Restore
• If the IP Office server hard disk has sufficient capacity, you can use it to receive backups from
other IP Office servers. However, this is not a suitable solution for its own backups. Therefore,
the recommendation is to backup to another IP Office server.
• Within a primary/secondary server pair, you can configure reciprocal backups.
• The preferred option is a separate backup server. This can be done by installing an IP Office
Application server with a sufficiently large hard disk (see Disk space required for backups) and
no services (Voicemail Pro and Avaya one-X Portal) enabled.
• WARNING:
• Backup/restore is not supported between different server software release levels. Any
exceptions are specifically documented in software release notes and migration documents.
• You cannot restore data to a server unless either the IP Address or the system id (LAN1 MAC
address) match the server from which it was backed up.
• Backup and restore action must only be performed using servers inside a secure, trusted
network.

3
Backup and Restore Policy
• It is essential to implement a comprehensive, robust and secure backup policy as part of a Business
Continuity plan before any failure or other data restoration requirement. It is not possible to define a
single approach that would meet all possible customer needs. Each installation should be assessed
and a backup policy implemented.
• Backup Key Information:
• The backup process supported by web manager only includes specific data, see Backup data sets.
There is key information which, though included in the backup data, should also be recorded
separately in case it is necessary to rebuild a failed sever:
• The ignition settings for each server should be recorded. For example, IP address and host name
settings, server role, etc. These details may be required if a full reinstallation of the server becomes
necessary before any data restoration operation.
• In addition, the following are not included in the web manager backup processes and so must be
backed up using other manual processes.
• Copies of any PLDS license key files used by the system.
• If using web manager to load custom voicemail prompts, copies of those prompt files.
• Copies of any custom phone settings files plus phone screen saver and background images.
• Third Party Certificates

4
Backup and Restore Policy
• Backup Schedule
• In addition to performing backups before major system changes such as a software upgrade,
you must consider having a regular backup schedule.
• Periodic configuration backup for every IP Office.
• Periodic configuration backup for one X Portal
• Periodic configuration backup for Voicemail Pro – Server Edition Primary server only
• Periodic voice mailbox and recording data backup – Server Edition Primary server only
• 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. It
should also be noted that the backup server used will only retain up to 14 backups, after which
any further backup will cause the automatic deletion of the oldest previous backup.
• The timing of backup operation: This should be done when little or no traffic is present on the
target system(s), but the backup process itself is not service-affecting.

5
Backup and Restore Policy
• Additional Backup Options
• This documentation only looks at the backup/restore process provided through the server’s
own web manager menus. The IP Office Manager and Voicemail Pro client application also
provide methods for backing up the current IP Office service configuration and the voicemail
configuration/mailbox contents respectively.
• Therefore, also consider:
• Manual backup of the IP Office service configurations before major configuration changes.
• Manual backup of the Voicemail Pro before major configuration changes.

6
Backup and Restore Protocols
• Backup and restore is only supported using another IP Office server as the backup server. If
necessary, an IP Office Application Server can be installed without enabling the Voicemail Pro
and one-X Portal for IP Office services on that server.
• warning
• • Backup and restore action must only be performed using servers inside a secure, trusted
network.
• The server being backed up requires a remote server connection to the backup server. That
connection is configured with the settings below (see Creating a remote server connection).
For a set of networked servers, the connection from the primary server is used for all the
servers.

7
Backup and Restore Protocols

8
Enabling HTTP Backup Support
• By default, HTTP support for backup/restore is disabled. You can enable it using the following
process on the backup server.
• Security: Backup and restore action must only be performed using servers inside a secure,
trusted network.
• Enabling HTTP Backup Support on the Backup Server
• 1. Login to the web manager menus of the backup server.
• 2. Select the servers Platform View option.
• 3. Within the platform view menus, select Settings > System > HTTP Server.
• 4. Select the Enable HTTP file store for backup/restore option and click Save.

9
Disk Space Required for Backups
• The space required for a backup is highly variable. It depends on the number of servers
includes in the backup and the data sets selected. However, the largest and most significant
backup is that required for voicemail.
• The following tables show the potential space required for a worst case full backup. That is, one
that assumes all the users have used their voicemail mailbox and other facilities to their
maximum capacity.
• The minimum disk size column indicates the disk hard disk size required to have a sufficiently
large backup quota (see above) for at least one maximum full backup.

10
Disk Space Required for Backups
• Backup for a Sever Edition Network

11
Disk Space Required for Backups
• Backup for an IP Office Application Server

12
Checking the Backup Server’s Backup
Quota
• Backup is supported to a server with a hard disk of 160GB or larger. The actual portion of that space, the backup
quota, available for backup usage can be checked using the process below. On servers with a smaller hard disk,
no backup quota is supported.
• Estimating the Backup Quota
• The approximate space that will be allocated for the backup quota can be calculated as follows:
• Backup Quota = (0.8 x Hard Disk Capacity) – 92GB if the Hard Disk Capacity is greater than 160GB, otherwise
zero.
• The capacities are all approximate. The quoted disk capacity from a disk manufacturer or a virtual server platform
will differ from the capacity reported by the operating system.
• • For example: For a 500GB hard disk, the backup quota is approximately 308GB.
• Checking the Backup Server’s Backup Quota
• Once a server is installed, the actual space allocated for backups can be checked as follows:
• 1. Login to the backup server's web manager menus.
• 2. Click and select Platform View.
• 3. On the System tab, note the Quota available for backup data value. Note this is the total space usable
• for backups, it does not account for the space already used by any existing backups.
• 4. Click Solution to exit the platform view.

13
Backup Data Sets
• Each backup can include multiple selected servers. Within that backup a number of different
data sets can be selected for inclusion in the backup.
• The table summarizes the data included in the different backup data sets. Some data sets are
greyed out if the related service is not running on one of the servers included in the backup.
• When performing a restore it is also possible to select which servers and which data sets are
included in the restore operation.

14
15
Backup Data Sets

16
Creating Remote Server Connection
• Once the backup server has been configured, a remote server connection is required on the
server to be backed up. In a network of servers, the remote connection s defined on the
primary server.
• 1. In the Web Manager menu bar, click Solution.
• 2. Click Solution Settings and select Remote Server.
• 3. Click Add Remote Server.
• 4. Enter a name that identifies the connections use.
• 5. Set the Protocol to HTTPS, HTTP or SFTP as required.
• • These are the only protocols supported for backup/restore operations.
• • HTTP is only supported if the backup server has had HTTP enabled. See Enabling HTTP
backup support.

17
Creating Remote Server Connection
• 6. Set the Port to match the selected protocol. The default ports are not necessarily correct.
• • For HTTPS, set the port to 5443.
• • For HTTP, set the port to 8000.
• • For SFTP, set the port to 22.
• 7. Set the Remote Path to /avaya/backup.
• 8. For HTTP/HTTPS, no User Name or Password details are required. For SFTP, use the
details of a Web Manager administrator account.
• 9. Click Save.
• 10. The new remote server connection is now shown in the list of remote servers. It can now be
selected for backup and restore actions.

18
Backing Up a Server
• The system backs up the configuration of the server, application and user data in a single file
set. You can use this backup file to restore the server or a failed server upgrade. The system
backs up the configuration of the application to a local drive, in a predefined directory. You can
take a backup of the primary server on a remote file server, which can optionally be the
secondary server.
• Before you begin
• • Create a remote server connection for the backup server. See Creating a remote server
connection.
• You can take a back up of the primary server on a remote file server using Web Manager.

19
Backing Up a Server
• 1. In the Web Manager menu bar, click Solution.
• 2. In the Solution page, select the servers that you want to backup.
• 3. Click Actions and select Backup.
• 4. Select which data sets you want to include in the backup. See Backup data sets for details of the different sets
contents.
• 5. In the Backup Label field, type a label for the backup – Example PrimaryFULL.
• 6. In Select Remote Server drop down list, select the remote server that you have set.
• 7. To back up at a scheduled time:
• a. In Select Remote Server drop down list, select the remote server that you have set.
• b. Under Schedule Options, enable Use Schedule.
• c. In the Select Schedule list, select the schedule option that you created
• d. Set a Start Date and a Start Time.
• e. To configure a recurring backup, set Recurring Schedule to Yes and then set the Frequency and Day
• of Week.
• 8. Click OK.
• 9. The progress of the backup process is shown on the Solution menu.

20
Restoring From a Backup Server
• The following process is used to restore previously backed up data.
• warning
• Backup/restore is not supported between different server software release levels. Any
exceptions are specifically documented in software release notes and migration documents.
• You cannot restore data to a server unless either the IP Address or the system id (LAN1 MAC
address) match the server from which it was backed up.
• Close any Voicemail Pro client before attempting a restore. The restore process requires the
voicemail service to restart. That will not occur if the Voicemail Pro client is connected to the
service and will lead to incorrect restoration of data.
• During the restore process, the services being restored are restarted. This will end any calls
using those services.

21
Restoring From a Backup Server
• 1. In the Web Manager menu bar, click Solution.
• 2. Select the servers onto which you want to restore data sets.
• 3. Click Actions and select Restore.
• 4. Select the Remote Server connection that points to the backup server.
• 5. Click Get Restore Points.
• 6. The system displays the backup data sets that it has for the selected servers.
• 7. Highlight the data sets that you want to restore.
• 8. Click OK.
• 9. The progress of the backup process is shown on the Solution menu.

22
Restoring a Failed Server
• The backup data can be used to attempt to restore a server that has failed.
• Procedure
• 1. Reinstall the original server software, ensuring that the same original IP address and host
name settings are used.
• 2. Reignite the server back to its original role. If the server includes an additional hard drive
containing call recordings for Media Manager, ensure that the option to reformat the additional
drive is not selected during the server ignition.
• 3. Login to the server and complete its initial configuration.
• 4. If the server was part of a network, use the options within Manager to add it back into the
network and ensure that the connections between the primary, secondary and expansions are
all present.
• 5. At this stage, use the restore process (see Restoring from a backup server) to reload the
original data.

23
SOLN377106 – Virtual VMWare Restore
Process
• Introduction
• This document serves as a "guide" for restoring a virtualized IP Office Server Edition installed
on an ESXI System (VMWARE).
• Recovery is only possible to a system with the same software version (components IP-Office,
oneX-Portal, VMPro, WebRTC, Media Manager must have the same software version as the
source system) and you must have the UUID of the Source-VM (stored in dem vmx-file of the
VM).
• The file names and IP addresses shown in this document are only intended as examples
and must be adjusted in the respective system.
• Source VM and Destination VM should never see each other or other IP Office systems
with the same IP address on the connected networks.
• Be sure to avoid IP address conflicts as this results in IP Office interfaces being
switched off and the fingerprint changing. Therefore, it is strongly recommended to use
a separate VLAN to set up the target VM when the source VM is still running.

24
SOLN377106 – Virtual VMWare Restore
Process
• Pre-requisite IP-Office source VM
• In order to be able to restore an IP Office system, the following points must be fulfilled
beforehand. ** You can also match the screenshots in this guide when gathering info ***
• 1. There must be a full backup of the system. This full backup can be created / stored on the
same server as the IP Office system (note the hard disk size), or it can be stored on an external
server.
• 2. The UUID of the IP-Office Server Edition to be restored, which is installed in a VM-Ware
environment, must be recorded in advance. This UUID shall be noted.
• 3. The so-called "fingerprint" must be known. It is generated by the IP-Office Server Edition
itself and is required for recovery.
• 4. It is necessary to pay attention to the licensing system. If PLDS licensing is set up, a new
license file maybe must be created. If a subscription license procedure is active, this licensing
model must be activated before restoring the backup.

25
SOLN377106 – Virtual VMWare Restore
Process
• Data IP-Office source VM
• The following data must be known from the IP-Office source system (source VM):
• a. LAN1 IP address and SUBNET mask (from server eth0 192.168.42.15)
• b. LAN2 IP address and SUBNET mask (from server eth1 192.168.43.1)
• c. Default Gateway (if set up)

26
SOLN377106 – Virtual VMWare Restore
Process
• d. Gateway address (see e.g. IPO configuration / IP routes, here e.g.
default route 0.0.0.0)

• Web Manager Backup (this backup data can be stored on the same server. Please check if the
hard disk has a volume of about 200GB and the HTTP server settings must be configured (see
WebControl Port 7071 Settings / System)).
• A full backup can also be created on another medium/server.

27
SOLN377106 – Virtual VMWare Restore
Process
• After creating the Web Manager Backup on the IP Office server itself, the files must be
downloaded to a PC (download with WinSCP) from folder “/var/www/html/avaya/backup”.
• f. IPO-Hostname (WebControl 7071 / Settings / System Network/Host Name (example:
r111fp2eap.belabor4215.net)

28
SOLN377106 – Virtual VMWare Restore
Process
• g. Make a note of the APN key (IP Office security settings)

• h. The IP Office System Name (WebManager 7070 / System Settings / System System /
Name (R1113SrvPri)

29
SOLN377106 – Virtual VMWare Restore
Process
• i. Timezone of the Server Edition (WebControl 7071) (example: Europe/Berlin)

30
SOLN377106 – Virtual VMWare Restore
Process
• j. Check / obtain the license file (for PLDS licensing), write down the Subscription System ID,
Customer ID and License Server Address for IP-Office (WebManagement 7070 / System
Settings / Subscription System ID + Customer ID + License Server Address).

31
SOLN377106 – Virtual VMWare Restore
Process
• k. Readout/Recording of the IP Office self generated fingerprint (e.g. read it with putty and save
it as a txt file)
• The following commands must be entered by root access:
• (a) ipoffice get_fingerparms 2>&1 | grep "^FP_"
• (b) ipoffice get_fingerprint

• After entering the command, the following output is obtained:

32
SOLN377106 – Virtual VMWare Restore
Process

33
SOLN377106 – Virtual VMWare Restore
Process
• l. The set up remote server must be recorded.

34
SOLN377106 – Virtual VMWare Restore
Process
• m. Files of a full backup. (Screenshot shows: Files of a full backup which was created via ftp on
an external PC)

35
SOLN377106 – Virtual VMWare Restore
Process – Collect Data of Source VM
• Write down the following data of the VMWare environment.
• a. CPU (value of cores)

• b. RAM

36
SOLN377106 – Virtual VMWare Restore
Process – Collect Data of Source VM
• c. Disk partitions (partition size and partitioning type)

37
SOLN377106 – Virtual VMWare Restore
Process – Collect Data of Source VM
• d. The VLAN from LAN1 and LAN2 interface

• e. existing snapshots of the source VM must be deleted (if any) before the source VM have to
be deleted.
• f. Name of the virtual machine in VMWARE-Host

38
SOLN377106 – Virtual VMWare Restore
Process – Collect Data of Source VM
• g. VMWARE Data Repository

39
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Pre-requisite: Target VM - To restore a defective system, a new system must be deployed.
The new system must have the exact same software release as the defective one - this effects
all components of IP-Office Serveredition that has to be restored (e.g. oneX-Portal, VMPro,
WebRTC, MediaManager).
• Data IP-Office Target VM
• Deploy a target VM by OVA-File. The process must be carried out according to the
specifications of the virtualization system.
• For more information, see the document IP Office Virtual Servers (avaya.com)
• ( https://documentation.avaya.com/bundle/IPOfficeVirtualServer/page/Introduction.html ).
• !!! DO NOT POWER ON the VM after the deployment !!!

40
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Adaptation of IP-Office target VM
• a. CPU resources
• b. Random access memory (RAM)
• c. Set disk 1 to 200GB if local http-server should be used for restore process.
• d. Check Network Adapters 1 and 2 ( VLAN )
• e. Note the path to the vmx file of this VM from vSphere:

41
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Adaptation of IP-Office target VM continued:
• f. Copy the VM configuration file (.vmx file) to the local PC and edit this file by Notepad.
• Overwrite the uuid.bios value with the values of the source system.
• Example: Source System

42
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• The previously noted fingerprint values show the needed FP_UUID. It must be adjusted
according to the same format as in the vmx file.
• For this, change first FP_UUID format from
• XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX to
• XX XX XX XX XX XX XX XX-XX XX XX XX XX XX XX XX (lower string with 16 groups of 2,
separated by whitespace and “-“ after 8 groups…)
• Target System Before change:

43
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Adjusted

• g. After adapting the vmx file, upload it to the target VM (e.g. ESXi) (confirm overwriting of the
existing vmx file).
• h. VM can now be booted for the first time.
• After the VM has been started the boot process can be observed in the web console. This lasts
up to 5 minutes.
•

44
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Use the vSphere-webconsole to login as follows:
• Enter the “login”-command and type for:
• User: root
• Password: Administrator (default password)
• Enter the following commands:
• 1. systemctl start NetworkManager (Case-sensitive, US-Keyboard is used).
• 2. nmtui
• After entering, the following graphical interface appears:
• Use the arrow keys to switch to "Activate a connection"
• and confirm with Enter-key, the following interface is
• displayed:

45
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM

Point System eth0 is selected and switch to Activate with the enter key (before System the
asterisk (see System eth1) must be gone).
Press the TAB key to go to the Back item and confirm with enter.

The previous graphical display is displayed again. Now go to “Quit” with the arrow key and
confirm with Enter.

46
SOLN377106 – Virtual VMWare Restore
Process – Pre-Requisite: Target VM
• Next step is to restart the network driver service by entering the following command:
• systemctl restart network

• LAN1 interface is now active and has got the IP address 192.168.42.1 (default IP address).

47
SOLN377106 – Virtual VMWare Restore
Process – Ignition Process
• Attention: In this step, make sure that the correct values from the source VM are entered
here, otherwise the server edition will have a different fingerprint than the source VM and the
restore will be not possible later on!! (note: LAN1, LAN2, hostname, time zone)
• To start ignition process connect to the IPO via browser: https://192.168.42.1:7071/login
• Login via IPO standard password: ( root/Administrator ) and go through the ignition process:

• a. Accept Eula
• b. Set the needed Server version (Primary, Secondary, Expansion or Application-Server)
• c. New Hardware: Accept HardDrive settings unchanged
• d. Configure Network: Transfer network data from the source VM, e.g.
• i. IP address (LAN1 and LAN2)
• ii. Subnet-Mask
• iii. Gateway
• iv. Hostname

48
SOLN377106 – Virtual VMWare Restore
Process – Ignition Process
• e. Time & Companding
• i. Time zone
• ii. Companding
• f. Change Password: assign three new different passwords (these passwords are only temporarily until the restore
by webmanager), e.g.
• i. Root und security e.g. AvAyA123$4U
• ii. Administrator e.g. Avaya-Services
• iii. System e.g. System service
• g. Security
• i. CA Certificate Generate new (only temporarily)
• ii. EASG Settings: Enable
• iii. Accept pop-up alerts
• h. Summary Settings (if applicable). Maybe take a screenshot.
• The server edition reboots – waiting time at least 10 minutes (recommendation: then log in again via web control
(7071) and wait until all IPO services are green for at least 5 minutes)

49
SOLN377106 – Virtual VMWare Restore
Process – ICU Process
• Login via Webmanager (7070) with Administrator / Admin Service
• Accept Eula
• Confirm warning with "Yes"

50
SOLN377106 – Virtual VMWare Restore
Process – ICU Process
• 1. "System" menu: Control / configure LAN 1 / 2 configuration and gateway.
• !!! Make sure that the correct values from the source VM are entered here, otherwise the server
edition will have a different fingerprint and therefore no restore will be possible later!! (LAN1,
LAN2) Note: The system name is not the hostname, but what the IP Office is called (e.g.
IPOxxxxx, in the screenshot R111SrvPri).

51
SOLN377106 – Virtual VMWare Restore
Process – ICU Process

• 2. VoIP menu: Apply without changes

• 3. Voicemail menu: Apply without changes
• 4. Menu License: if necessary. change "Remote Server" to License Source "Local" and apply via the "Update" button
• 5. Menu Users: Click on the menu once and click the "back" button to return to the menu
• 6. Menu Groups: Click on the menu once and click the "back" button to return to the menu
• 7. Menu Lines: Click on the menu once and click the "back" button to return to the menu
• 8. Menu Incoming Call Routes: Click on the menu once and click the "back" button to return to the menu
• 9. Finally, select "Save to IP Office" at the top of the web manager. Select restore time "Immediately" and send.
• The system services will now restart. Waiting time approx. 10 min.

52
SOLN377106 – Virtual VMWare Restore
Process – Fingerprint Comparison
• Comparison fingerprint Target-VM / Source-VM
• Login via putty (SSH shell) to the IP address of the server edition (target VM) as <administrator/password> and switch to
root (see point 3.3 for passwords):
• The following commands must be entered by root access:
• (a) ipoffice get_fingerparms 2>&1 | grep "^FP_"
• (b) ipoffice get_fingerprint

• Outcome:
• [root@ffm ~]# ipoffice get_fingerparms 2>&1 | grep "^FP_"
• FP_Platform = Virtual (OVA)
• FP_Time Zone = Europe/Berlin
• FP_LAN1 = 192.168.42.15
• FP_LAN2 = 192.168.43.15
• FP_Hostname = <HOSTNAME> (CCFM)
• FP_UUID = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx
• FP_Length = 98

53
SOLN377106 – Virtual VMWare Restore
Process – Fingerprint Comparison
• Comparison fingerprint Target-VM / Source-VM
• [root@ffm ~]# ipoffice get_fingerprint
• init_linux_longclock: 6
• OpenTime=1719796
• Running in information mode.
• Initializing Hardware Features.
• Logfile: IPOffice on Linux PC platform
• failed to disable path mtu discovery: Protocol not available
• <IPOffice Manager Version 0.2>
• Thu 14/9/2023 16:44:49, Hello>Permanent MAC : 00:50:56:99:87:5f
• FINGERPRINT=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• [root@ffm ~] #

54
SOLN377106 – Virtual VMWare Restore
Process – Fingerprint Comparison
• IMPORTANT:
• !!! The fingerprint displayed here must match to the source VM (point 2.1 k). If this is not the
case, a step was previously done wrong, i.e. the created VM is useless and the designated
backup cannot be restore. In this case delete the created VM and start from scratch.

55
SOLN377106 – Virtual VMWare Restore
Process – Customize the Target VM
• Depending on how the full backup was created on the old (defective) Virtual Machine, the new
Virtual Machine must now be adjusted. If the old full backup has been created on the same
Virtual Machine, the hard disk of the new Virtual Machine must be expanded to 200GB and the
http server must be set up.
• 1. Above Webcontrol 7071 to enlarge the partition (including an automatic reboot), this step
lasts at least 15-20 min.).
• 2. Afterwards login to Webcontrol 7071 again and enable HTTP server for backup/restore.

56
SOLN377106 – Virtual VMWare Restore
Process – Customize the Target VM

57
SOLN377106 – Virtual VMWare Restore
Process – Customize the Target VM
• 3. Login to WebManager port 7070
• a) Add a remote server via "Solution Settings" and "Remote Server"
• „Add Remote Server“:

58
SOLN377106 – Virtual VMWare Restore
Process – Customize the Target VM
• Example for local server:
• a) Server Name: e.g. "SE local"
• b) Protocol: http
• c) Remote Server Address: < IP address LAN1>
• d) Port: 8000
• e) Remote Path: /avaya/backup (lower case)
• Press <SAVE>
• b) HTTP - Create backup
• Create a backup of all services via "Solution" and "Actions" (this step is useful, but only
necessary if you are unsure which new MAC address the target VM has (see point 4 below))

59
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup
• Optional Switch to Subscription mode
• If an IP-Office subscription system has to be restored, the IP-Office must be converted to
subscription mode before the data backup can be imported. This can be done with the IP-Office
Manager as well as with the WebManager.
• Conversion with the WebManager:

60
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup
• Depending on how a full backup was created on the source system, set up the remote server
now. The setup should be identical to the old system
• Rename Backup-Files and Upload to Target VM
• Since the MAC address of LAN1 in the target VM has changed, the file names of the web
manager backup of the source VM need to be changed. The easiest way is to create a backup
of the target VM via the web manager, in which the naming including the new MAC address is
output.
• Example:
• Marked in yellow Backup 00 of the target VM with MAC 00505699EAB0
• Marked in red Backing up the source VM with MAC 005056992994
• these files need to be renamed
• In the backup files, replace the MAC address of the source VM (02_xxxxx) with the MAC
address of the target VM (00_xxxxx) (these are the digits 04-15 of the file name of each backup
file):

61
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup

62
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup
• Follow this procedure:
• 1. Rename the files on the PC to the new MAC address of the target VM (see above)
• 2. Login by root via Putty to target VM and the create a folder “backup” in the /tmp folder
by command: mkdir /tmp/backup
• 3. Use WinSCP to transfer the renamed backup files of the source VM to the target VM in
created folder /tmp/backup
• 4. Modify all backup files via Putty in the /tmp/backup folder:
• a) chown -R apache:apache 02* .* Change File Owner
• b) chmod -R 777 02 * .* Changing file permissions
• c) cp 02*.* /var/www/html/avaya/backup Copy files to the Webmanager backup folder of
the server edition (directory path is case sensitive!)

63
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup
• Restore
• Login to Webmanager (7070) to perform restore:
• • Select your Remote Server
• • "Click on "Get Restore Points"
• • Select the all lines of the restore point (e.g. "02_xxxxxxx”)
• • Click on the "Restore" button - A warning message for server reboot appears (needs to be
confirmed).
• Restore is in progress:

64
SOLN377106 – Virtual VMWare Restore
Process – Restore Backup
• The system will now reboot. After the reboot all services should be in green state (check by
webcontrol 7071). If not maybe a manual reboot of the server edition may be necessary.
• Attention: After the reboot, the former passwords (and settings) of the source VM apply again,
including certificates.

65
SOLN377106 – Virtual VMWare Restore
Process – License
• After the system has been created, import a new license file (if the MAC address is changed).
• For PLDS licensing: Dial-in via IP Office Manager and import XML file, or
• For WebLM licensing: Dial-in to WebLM and import license file (for WebLM licensing):
• Then check the license status via system status: check the license alarms (the synchronization
of the IP Office service with the WebLM service only takes place every 9 minutes)
• If the PLDS host ID has changed, it may be necessary to register the PLDS host ID. a license
SWAP can be requested.
• Subscription systems:
• After recovery, the system ID must be read out (via the IP Office Manager application (system /
subscription) or via web manager (system settings / subscription)) and compared with the
stored system ID on the COM server and, if necessary, changed.

66
Questions?

• Can you take a IPO 10.0 500V2 and restore to a IPO 12.0 release?
• Restore to same 10.0 version and then follow upgrade process to go to 12.0
• Upgrade 1 version at a time is best practice
• Can you Export a .csv and import config in IPO Manager?
• Yes, you can use the .csv to import into same version of IPO. However, I have seen that this also works
for newer versions of IPO for non complicated configs.
• If you have a Primary Server down, you can extract just the Primary Server config from a saved
configuration solution where you have a list of configs and the ConfigInfo.cfi and send ipo config from
Manager to a Primary Server. You just need to open up each config from the list of configs in the
solution to find the one for the Primary Server and use just this config to send to the Primary Server
using IPO Manager
• It is good practice to backup 3rd Party Certificates and IPO Certificates separately.
• When upgrading please upgrade secondary first then primary then expansions. If you upgrade the
Secondary first then you can determine that your upgrade file is good with a successful upgrade of the
Secondary without effecting the solution in production.

67
68
PCC SME Community – IP Office June 2024

IP Office

IPOSS Support Questions

How to Report Bugs to get case to Development Quickly

Craig O’Gorman
Principal Technical Support Engineer
ogorman@avaya.com

69
IPOSS Support
• How to Report a Bug to get case to Development Quickly?
• When creating a case we must have the Configuration of the Solution,
Server Logs, System Monitor Trace, System status Snapshot, Details of the
captured issue – Date Time, Numbers, extensions, what has been tested to
narrow down the issue so far.
• At this point we can check for any known issues on current release
experiencing the issue… However, in order to escalate to Development we
need all the above information at the latest GA Release of the latest 2 IPO
Versions. So, right now it would be version 12.0 or at 11.1.3.1.
• If not all scenarios have been tested to narrow down the issue to a specific
detail then Tier III needs to eliminate all possible configuration changes to
rule out a config issue and sometimes also needs to do this to get more
specific details of the bug to escalate with.
• If your case is not being worked as quickly as it should you can request
SME engagement to help the process. You can also click on Management
Escalation for your case if there’s progress.

70
Questions?

71
72