Dear Clients,
Update 8th of March 2019:
At the request of the manufacturer of the solution that is at the heart of the Voyced Hosted solutions, we have had to decide to postpone the V6.0 Upgrade Weekend.
Although both PortaOne and we have allocated extra personnel and efforts to make sure the upgrade would go through smoothly, they have come across some potential issues which they feel they need to tackle first.
We will, therefore, reschedule the V6.0 Upgrade Weekend to be in a few weeks.
The weekend of the 22nd through to the 24th of March seems to be most likely at this time.
We want to get this upgrade correct and completed as soon as possible as this will also influence the planning of the follow-up upgrades that are already planned in the next month(s) or so.
Our apologies for any inconvenience this may cause and for this late announcement but we feel that reliability, quality and maximum presence are most important.
As soon as the planning has been completed and set we will create new announcements of this so that you will be notified again.
We thank you for your patience and understanding and apologise for the inconvenience that this essential maintenance work may cause.
If there are any questions or concerns, please contact our technical support team.
Kind Regards
the Voyced Technical team
Previous announcement:
We are going to upgrade the Voyced Hosted IPPBX platform to the next stable version, V6.0, over the weekend of March 8th - 10st 2019.
Service Affected:
As always, any upgrade will be tested very extensively in our testing environment before actual implementation so that the upgrade on the live systems should go through quickly and without a flaw.
The upgrade itself is separated into two parts spread over two overnight maintenance windows and we'll create separate announcements for these steps as pre-tests have passed correctly, we get nearer the time and plannings are set.
Impact: Minor Impact. Anticipated total downtime; 10-20 minutes
Start Date: Saturday, 9th of March 2019, 02:00 AM (UTC) / 03:00 AM (CET)
End Date: Saturday, 9th of March 2019, 05:00 AM (UTC) / 06:00 AM (CET)
Status Report: Service Status
Description
Test reboots of the related servers (on all geographic locations and all servers clusters) into the preinstalled V6.0 partition.
This ensures there are no issues when booting from the new root partition.
Servers will then be booted back into v5.5.
The process can take between 1 and 2 hours, with no set times for restarts.
This stage requires the minimum of downtime and will allow us to check that the update to the new release is successfully performed and to determine if there are any network issues.
Reboots can cause up to 10 minutes of downtime.
We thank you for your patience and understanding and apologise for the inconvenience that this essential maintenance work may cause.
If there are any questions or concerns, please contact our technical support team.
Kind Regards
the Voyced Technical team
Update:
Following the above announcement, here is the confirmed timescale of events for the 9th of March, Step 1 update to v6.0.
To be as clear as possible we feel the need to separate stage 2 into two distinct parts, as detailed below, so that everyone knows what to expect.
If you have not adjusted your device's settings to the Geographic redundant version yet, you will perceive downtime during Part 2 so please adjust your settings now!
If you have set your device's settings to use the Geographic redundant settings you should not have any downtime as the various Geographic locations will take over once a service goes down on the other site9s).
More information about these settings are available here: Basic Setup Instructions
Part 1 (Geographically Redundant Sites)
Start Date: Friday, 8th of March 2019, 11:00 PM (UTC) / 00:00 AM (CET)
End Date: Saturday, 9th of March 2019, 02:00 AM (UTC) / 03:00 AM (CET)
Service Affected: Anticipated total downtime; 10-20 minutes
Part 2 (Main Site)
Start Date: Saturday, 9th of March 2019, 02:00 AM (UTC) / 03:00 AM (CET)
End Date: Saturday, 9th of March 2019, 07:00 AM (UTC) / 08:00 AM (CET)
Service Affected: The process can take between 1 and 2 hours per site with no set times for restarts.
Thursday, February 14, 2019
