|
|
|
|
@@ -20,11 +20,35 @@ The V8Migrate plugin can migrate data from AyaNova 7.6 patch 8 or newer ONLY.
|
|
|
|
|
|
|
|
|
|
To migrate to AyaNova 8 from versions of AyaNova older than AyaNova 7.6 patch 8 (i.e. AyaNova 1.x, 2.x, 3.x, 4.x, 5.x, 6.x, 7.x older versions) the process is to upgrade in two steps: Upgrade to AyaNova 7.6 latest release first then migrate the data to AyaNova 8.
|
|
|
|
|
|
|
|
|
|
AyaNova 7.6 can automatically upgrade any older version of AyaNova newer than AyaNova CE.
|
|
|
|
|
|
|
|
|
|
We will provide a temporary license key and instructions at no charge to enable you to migrate any older version of AyaNova to AyaNova 8.
|
|
|
|
|
|
|
|
|
|
[Contact our support department](https://contact.ayanova.com/contact) for the resources and instructions required.
|
|
|
|
|
[Contact our support department](https://contact.ayanova.com/contact) for the resources required.
|
|
|
|
|
|
|
|
|
|
AyaNova CE: it's potentially possible to upgrade to AyaNova 8 from AyaNova CE in a triple step upgrade process but we would need to do it in-house, contact AyaNova support for details.
|
|
|
|
|
**WARNING**
|
|
|
|
|
|
|
|
|
|
If you are running a version of AyaNova _older than 7.6_ in production use and are not licensed or able to upgrade it to the latest AyaNova 7.6 release, there is an extra step and precaution: you should take care to _NOT_ accidentally upgrade your current, in-production AyaNova installation database but rather a copy of it only, unless you are able to upgrade your production AyaNova to the latest release (have a active support and updates subscription) OR are ready to completely abandon using your older production use AyaNova entirely and permanently.
|
|
|
|
|
|
|
|
|
|
This is because AyaNova 7.6 will **automatically** upgrade an older AyaNova database when it is opened and break access to it from the older pre-7.6 AyaNova installations on other computers if they are sharing that database.
|
|
|
|
|
|
|
|
|
|
If you were to use a _temporary_ AyaNova 7.6 key issued to you for migration purposes it would expire and prevent access to AyaNova 7.6 so if you were to upgrade your production in-use 7.0.3 for all users it would stop working when the temporary 7.6 key expires.
|
|
|
|
|
|
|
|
|
|
This may or may not be an issue for you if you have already thoroughly tested out 8.x and are confident you are ready to completely switch over to it but if you aren't then the upgrade should be done on a computer or virtual machine isolated from the in-production AyaNova you are currently using.
|
|
|
|
|
|
|
|
|
|
Assuming you want to take the safest route and not break existing access to the old in-production AyaNova for the time being then:
|
|
|
|
|
|
|
|
|
|
The process would be to start with a completely separate computer with access to the AyaNova 8 server but not running your current production AyaNova.
|
|
|
|
|
|
|
|
|
|
- Download and install the latest AyaNova 7.6 trial version fresh from our website here (https://ayanova.com/download.htm)[https://ayanova.com/download.htm]
|
|
|
|
|
- set it up to use a freshly backed up and restored _copy_ of your in production older AyaNova data
|
|
|
|
|
- Once you have configured the latest AyaNova 7.6 to connect to the local _copy_ of your older AyaNova data it will see there isn't a valid license and prompt you for one
|
|
|
|
|
- Install the _temporary_ AyaNova 7.6 key [requested from support](https://contact.ayanova.com/contact) earlier using the fetch address and fetch code provided by Support
|
|
|
|
|
- Once you have an isolated AyaNova 7.6 running with your data you can continue to follow the migration steps below
|
|
|
|
|
|
|
|
|
|
#### Migrating from AyaNova CE
|
|
|
|
|
|
|
|
|
|
It's potentially possible to upgrade to AyaNova 8 from AyaNova CE in a triple step upgrade process but we would need to do it in-house, contact AyaNova support for details.
|
|
|
|
|
|
|
|
|
|
### How to get the fastest possible migration
|
|
|
|
|
|
|
|
|
|
@@ -34,6 +58,16 @@ Ideally all on the same computer if possible.
|
|
|
|
|
|
|
|
|
|
Speed issues are most noticeable in cases where there are a large number of > 1mb sized Assigned docs or Wiki files that need to be transported across the internet or slow LAN connections.
|
|
|
|
|
|
|
|
|
|
### Errors during migration
|
|
|
|
|
|
|
|
|
|
It is our goal for migration to happen as automatically as possible with as little human intervention as necessary.
|
|
|
|
|
|
|
|
|
|
It's possible for older AyaNova 7 data to have one or more issues that the migration utility has not come across previously and been coded to work around triggering an error and stopping migration.
|
|
|
|
|
|
|
|
|
|
If this happens please copy and paste the **entire** migration log (not just the error) using the "Copy log to clipboard" button in the v8-migrate utility and send it to AyaNova support.
|
|
|
|
|
|
|
|
|
|
They will advise if it's something that can be easily corrected at your end by making a small change in AyaNova 7 or they will forward the log to our Development department to add a work around in the v8-migrate code to enable migration to complete without intervention.
|
|
|
|
|
|
|
|
|
|
### Plan for one or more test migrations
|
|
|
|
|
|
|
|
|
|
AyaNova 8 is [different from prior versions](ay-start-changes-from-v7.md) and we recommend doing one or more test migrations before scheduling with your staff to do the final switch-over.
|
|
|
|
|
@@ -66,9 +100,11 @@ In other words you cannot continue to work in both AyaNova 7 and AyaNova 8 at th
|
|
|
|
|
|
|
|
|
|
### Migrating Assigned docs and Wiki files
|
|
|
|
|
|
|
|
|
|
In AyaNova 7 there were two ways to link to files from within objects: As Wiki files which are stored inside the database and Assigned docs which are file URL links to file system locations visible to all users of AyaNova 7.
|
|
|
|
|
Migrating files can have implications that need to be taken into account depending on the size of individual files and all files together as a whole.
|
|
|
|
|
|
|
|
|
|
In AyaNova 8 all files are stored as "Attachments" in a special file system location controlled by the AyaNova 8 server.
|
|
|
|
|
In AyaNova 7 there were two ways to link to files from within objects: As Wiki files which are stored inside the database and Assigned docs which are file URL links to file system locations visible to all users of AyaNova 7 on your network.
|
|
|
|
|
|
|
|
|
|
In AyaNova 8 it's much simpler: all files are stored as "Attachments" in a special file system location controlled by the AyaNova 8 server.
|
|
|
|
|
|
|
|
|
|
During migration you have the option of migrating Assigned docs or not however Wiki files will be automatically migrated.
|
|
|
|
|
|
|
|
|
|
@@ -82,6 +118,18 @@ Timeout: there is a built in timeout of 100 seconds for any single operation dur
|
|
|
|
|
|
|
|
|
|
In the case of very large problematic files it may be necessary to have the Users split the file into smaller chunks where possible if it absolutely has to be stored in AyaNova.
|
|
|
|
|
|
|
|
|
|
#### Viewing the files in database in AyaNova 7
|
|
|
|
|
|
|
|
|
|
In AyaNova 7 you can view the files you have stored in the database ("Embedded" Wiki files) using the [Administration -> Files in database](https://ayanova.com/AyaNova7webHelp/index.html?files_in_database.htm) feature.
|
|
|
|
|
|
|
|
|
|
There is no practical way to view how many Assigned docs will be potentially migrated unless they were assigned in the first place from known locations available to all users on the network in which case you may be able to examine the total file storage in the folders used.
|
|
|
|
|
|
|
|
|
|
### Migrating to a hosted subscription server
|
|
|
|
|
|
|
|
|
|
There is a hard limit by default of 20gb total storage for a subscription service server (unless arrangements have been made for extra storage in advance). Keep this in mind when migrating your AyaNova 7 data to a hosted AyaNova 8 server if you have a large number of assigned docs or Wiki files to be migrated.
|
|
|
|
|
|
|
|
|
|
See [above](#migrating-assigned-docs-and-wiki-files) for more details.
|
|
|
|
|
|
|
|
|
|
### Avoid corrupted data
|
|
|
|
|
|
|
|
|
|
#### Other users
|
|
|
|
|
|
