case 4751 - manual: subscription service updates, notices, downtime and times
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -8,17 +8,17 @@ AyaNova subscription service ensures you are always running the latest version o
|
||||
|
||||
Our network operations engineers will take care of all updates required to AyaNova or the underlying server operating system hosting AyaNova.
|
||||
|
||||
### Update advance notifications
|
||||
### Update notifications
|
||||
|
||||
When an update is required to be installed we will try to give at least 24 hours advance notice however in the case of an urgent security update we may not be able to give any advance warning due to the urgency of the situation.
|
||||
|
||||
An upgrade notification will be emailed to the email address used to purchase the AyaNova subscription service. The notification will contain information about the type of upgrade required and a link to the [AyaNova change log](changelog.md) so you can see exactly what will be fixed, changed or new features added.
|
||||
When your service has been upgraded to a new version of AyaNova, a notification is emailed to the email address used to purchase the AyaNova subscription service. It contains a link to the [AyaNova change log](changelog.md) so you can see exactly what was fixed, changed or added.
|
||||
|
||||
### Downtime during an update
|
||||
|
||||
Standard upgrades to AyaNova typically require less than one minute of down time where the AyaNova server will be unresponsive. During an update there is typically no need to log out of AyaNova, there will be a brief period of non responsiveness and then AyaNova will continue to respond normally.
|
||||
Every week the operating system of the server hosting your AyaNova is updated, and the server is then restarted: AyaNova is unavailable for as much as 2 minutes.
|
||||
|
||||
In the case of an operating system upgrade the server itself hosting your AyaNova instance needs to be rebooted so there can be as much as 2 minutes down time on average. Again there is typically no need to log out of AyaNova, it is designed to allow you to continue working once it has reloaded and is ready for connections.
|
||||
When a new version of AyaNova is installed, which is less frequent than the weekly update, the server is shut down for the upgrade, so AyaNova can be unavailable for a few minutes longer, usually 5 minutes or less.
|
||||
|
||||
In either case there is no need to log out of AyaNova: it stops responding for a short time and then continues normally once it is ready for connections again.
|
||||
|
||||
### Web application update pop-up
|
||||
|
||||
@@ -28,13 +28,14 @@ If you choose to do it later you can continue to work and then select to reload
|
||||
|
||||
### What time will my service be upgraded?
|
||||
|
||||
We have chosen standard times for each data center to install standard updates that are intended to be outside of normal business hours relative to each data center to avoid any disruption to your business.
|
||||
We have chosen standard times for each data center to install updates, outside of normal business hours relative to each data center to avoid any disruption to your business.
|
||||
|
||||
Usually, if necessary, we will perform maintenance or upgrades on Thursday (our west coast north america time zone).
|
||||
Updates are installed every Thursday (Pacific time, our time zone).
|
||||
|
||||
Your service will be updated at the following data center local time:
|
||||
|
||||
- New York 7 p.m.
|
||||
- Atlanta 7 p.m.
|
||||
- San Francisco 7 p.m.
|
||||
- Amsterdam 1 a.m.
|
||||
- Singapore 1 a.m.
|
||||
@@ -44,7 +45,7 @@ Your service will be updated at the following data center local time:
|
||||
- Bangalore 5:30 a.m.
|
||||
- Sydney 4 a.m.
|
||||
|
||||
Note that in the case of an urgent or emergency security update we may be forced to install it immediately at any time of day without advance notice.
|
||||
An urgent update, such as a security fix, may be installed on any day and at any time if necessary; we always try to keep the impact on your business as small as possible.
|
||||
|
||||
## Backups
|
||||
|
||||
|
||||
Reference in New Issue
Block a user