8.1 KiB
OVERVIEW
This is the technical guide to the migration to v8 process.
There is also a business administration focused guide to migration outlining business object changes and steps that need to be taken after the migrate process has completed.
Migration is done by the AyaNova 7 plugin "V8Migrate" which is available as an optional install from the AyaNova Download page.
The migrate process happens via network and you can migrate to any server on the same computer or visible inside or outside your network via HTTP.
MIGRATING FROM AyaNova 7.6 patch 7 OR OLDER
The V8Migrate plugin can migrate data from AyaNova 7.6 PATCH 8 or newer ONLY. For versions of AyaNova older than 7.6 patch 8 you must first upgrade them before continuing.
SPEED
It is recommended where possible that migration be done on the fastest possible network connection between the V8Migrate plugin, the AyaNova 7 database and the AyaNova 8 server. 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.
MIGRATING ASSIGNED DOCS / 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 arbitrary locations for files visible to all users of AyaNova 7.
In AyaNova 8 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.
AyaNova 8 has a hard limit of 10GiB per attachment. The migration utility will log a warning about any files found to be larger than 10GiB and will not attempt to migrate them.
Note, however that there may also be other limitations depending on how and where the AyaNova 8 server is hosted. For example if the AyaNova 8 server sits behind an nginx proxy server (for example) there is a default limit of 30mb for file uploads which may need to be adjusted. The migration plugin will keep track of any files that fail to migrate due to a 413 file size exceeded error and it will log a warning and will reset the limit down to that level and not attempt to export any files larger than the limits it "finds".
A 1 GiB file can take easily take an hour to migrate to a remotely hosted server via an average internet connection so exporting Assigned docs may need to be undertaken very carefully if the users have linked to a large number of big files in AyaNova 7 and you are migrating to a remote server across the internet.
Timeout: there is a built in timeout of 100 seconds for any single operation during migration, this can be increased in the options dialog of the migration plugin displayed after login to as much as 3600 seconds (1 hour) and if you see timeout errors during migration of large files you will need to increase this value.
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.
PLAN FOR ONE OR MORE TEST EXPORTS
AyaNova 8 is very different from prior versions and we recommend doing one or more trial migrations before scheduling with your staff to do the final switch-over. Plan on taking plenty of time to go through the migrated data in AyaNova 8, familiarize yourself and your staff with all the changes in the new version of AyaNova.
Ensure data has migrated as expected and that all staff are comfortable with working in the new AyaNova before committing to a final migrate and switch over.
A test migrate will give you an idea of how long it will take to better plan the final migrate and change over to v8.
WARNINGS
AyaNova 8 database will be erased
The V8Migrate plugin will erase all data including attached files in the AyaNova 8 database as the first step.
There is no ability to synchronize or migrate only recent changes from v7, the migrate process entirely replaces the V8 data.
Note that it's possible to run the migrate plugin more than once for testing and evaluation just be aware that you will lose anything entered into V8 each time you run the Export to V8 plugin from v7.
In other words you cannot continue to work in both AyaNova 7 and AyaNova 8 at the same time and expect to migrate and import data repeatedly to keep them in "sync".
Avoid corrupted data
Other users
If other users are working in AyaNova when the migrate plugin is run the resulting migrate data may be corrupted as there could be records changed or missing that will be required to import. Be certain no other users are working in AyaNova 7 before you migrate.
Generator
Be sure to stop the AyaNova 7 Generator before starting the migrate plugin. Failing to do so could result in a corrupted migration.
Remote access users
Ensure no users are making changes via a remote access option such as the DataPortal, WBI, MBI or RI. If you can't be certain they are out we recommend stopping your IIS server to be certain no one is remotely making changes.
Lost entries
If you have a networked installation of AyaNova 7, when you are ready to transition to the newer version of AyaNova you will need to ensure that no other users are still working in the old AyaNova 7 making entries that will never be brought over to v8 after you do the final migrate to v8.
We recommend stopping the V7 database server immediately after the final migrate if there is any chance that there are still users inside or outside of your network that may access AyaNova 7.
Before uninstalling AyaNova 7
Examine your imported data in AyaNova 8+; carefully ensure that the data you expect to see has been imported properly. You may still need to make another migrate in case of any issues that arise so it's not a good idea to immediately uninstall AyaNova 7 until you are sure the newer version of AyaNova has all your data in it and is ready for business.
We recommend keeping your AyaNova 7 installation for some time on at least one computer after switching to v8 in case an issue comes up or something needs to be checked.
Keep your last AyaNova 7 backup
We recommend you keep one or more backup copis of your AyaNova 7 database in a safe location OFF SITE for at least a year after transitioning to AyaNova 8 in case any issues arise. If possible a "permanent" copy burned to DVD may be prudent.
MIGRATION FROM AYANOVA 7.xx
-
Avoid future problems: If you haven't already, go back and read the section titled "WARNINGS" above carefully.
-
Multi-user only: If migrating from a networked multi-user AyaNova 7.xx installation, now is the time to ensure all users are out and networked Generator service is stopped. Do not proceed until this is verfied.
-
Login to AyaNova 7.xx as the Administrator / manager account
-
Select the "Export to V8" plugin in AyaNova 7 from the main window plugin menu and the login and server URL dialog will open (note: this plugin is installed by default in the latest releases of AyaNova. If you don't see it, you may need to upgrade to the latest release first.)
-
Enter the URL of your AyaNova 8 server. There is a "Test URL" button to optionally confirm if you have entered the correct address or not.
-
Enter your AyaNova 8 SuperUser account login credentials. No other account is permitted to perform this operation. The default SuperUser account login name is "superuser" and password is "l3tm3in" if it has not been changed. (you really should change it as soon as possible)
-
A form will popup and show the progress of the Export operation. There is no easy way to estimate how long this will take, it depends on the network latency and speed between the Export to V8 plugin and the AyaNova 8 server as well as the number and complexity of objects entered into AyaNova and the quantity and size of files that may need to be uploaded. Allow plenty of time for this operation.
-
When the migrate is finished you will be able to login to V8 and start setting things up