This process boots the virtual machine from the copied vmdk upgrade file. The boot process backs up the server and then upgrades its components to R11.1.3 before restoring the server data.
warning
Do not use any other method to shut down the server. Doing so will cause the loss of data and settings. This method creates files used by the upgrade process.
Before you begin
You must upgrade the server to IP Office R11.0.4.8.
After upgrading to IP Office R11.0.4.8, back up all the servers and services before upgrading to R11.1.3. See Creating an IP Office backup.
Procedure
Shut down the server using the following method:
Connect to the server's platform view/web control menus using port 7071.
On the System tab, click Show optional services.
If the Media Manager service is running, deselect the service's auto-start checkbox and then stop the service.
Click Shutdown and click Yes. Wait approximately 90 seconds, after which you will see the services shutting down.
Check that the server has completed its shutdown:
In EC2, select Instances and select the instance.
Select Actions > Instance State > Stop and confirm the action.
The Description > Block devices section shows links for the instance's virtual disks; the IP Office drive (/dev/sda1) and a Media Manager drive (/dev/sdb).
Click on the /dev/sda1 link and then the EBS ID link:
Note the Volume ID. Click the Name field and give the volume a distinctive name if not already done.
Click and then select Actions > Detach.
If also present, click on the /dev/sdb link. Note the Volume ID and then select Actions > Detach.
Attach the upgrade volume as the drive from which the instance boots:
Select Elastic Block Storage > Volumes.
Select Actions > Attach Volume.
In the Instance field, select the matching instance.
For the Device, enter /dev/sda1.
Repeat the process to reattach the original IP Office volume but the Device now set to /dev/sdb. You do not need to reattach the Media Manager volume at this stage.
Restart the instance:
Select Instances and select the instance.
Select Actions > Instance State > Start and confirm the action.
The instance boots from the upgrade volume and starts the upgrade process. When the upgrade has finished, the instance automatically switches off. Wait until the instance status shows switched off:
Select Instances.
Locate the instance and verify the Status Checks column shows "Stopped".
Detach all the current volumes again (the upgrade volume and the original IP Office volumes).
Reattach the original IP Office volume as /dev/sda1 and, if present, the Media Manager volume as /dev/sdb.
When the server has restarted:
Check that the version shown is R11.1.3. If not, see Failure to upgrade.
Following the upgrade, test and verify the operation of all services:
Connect to the server's platform view/web control menus using port 7071.
On the System tab, click Show optional services.
For the Local Media Manager service, select the service's auto-start checkbox and then start the service. This starts the Media Manager database encryption process:
You must let Media Manager complete this one-time encryption process. The time required depends on the number of recordings and the server resources and can take several hours.
Interrupting the encryption process, for example restarting the Media Manager service or the IP Office server, can cause issues.
When completed, you can check recordings using the Media Manager menus.
If the server is part of a network, continue with the next server.
When satisfied with the operation of the upgraded instance(s), you can delete the upgrade volume.
