New destination – AODocs Nava Certus supports migrations from all sources to AODocs. During the migration NC preserves the source folder hierarchy and user permission at the destination.
New destination – Sharepoint Nava Certus allows migrations from all of the sources including Sharepoint to Sharepoint destination. During migration, source folder hierarchy will be preserved at the destination. Note that source items permissions will not be preserved at the destination.
New destination – OneDrive Nava Certus supports migration from all of the sources to OneDrive destination. Source folder hierarchy will be preserved at the destination. Note that source items permissions will not be preserved at the destination.
Option to exclude large files from migration. NC introduces a new option which enables the users to filter out the large files from the migration (size defined by the user).
AODocs/Google Drive Authorization Users now have two methods to authorize Google drive source/destination, AODocs and GCS destination. They can either choose Web Authorization or Service Account Authorization based on preference and/or use-case.
New integrated tools are available to help with the migration process. The “Permission Cleaner” tool enables the user to remove any set of the permissions he desires from an existing Google drive file hierarchy. The “Google Synchronizer” tool removes any extraneous files that were placed in the Google Drive migration path after or during migration.
The “Permission Analyzer” tool is now able to output the results as a CSV file.
Permission conversion from all of the sources to all of the destinations is improved.
Fixed Issues
Amazon source – sometimes the folder structure was not replicated at the destination. This was happening only when the user did not have “Owner” permission on some bucket folders. NC now creates the item path if it does not exist.
Locked database issue is fixed.
Google drive to Google drive task type: “Copy permission” option will copy all of the source permissions to the destination.
Rate-limit license is enabled again for 1.5.0 release.
Expired authentication data prevented Nava Certus service to start. This issue is now fixed by not loading problematic migration jobs.
Logs have the same as migration jobs.
Logs were not printed immediately after the job was started. This issue is now fixed.
It was not possible to create the log file on a network drive. This issue is fixed now.
Total items size was printed zero in logs for some sources.
Not all of the task configuration as printed in the logs. All task configurations are now printed at the beginning of the log regardless of the log level.
Google drive API is updated to 1.8 version.
File size limit when migrating to Google Cloud Storage.
Before, AWS API was used to interact with GCS. In the current release we are using GCS API to migrate to the GCS destination.
OutOfMemory exception when migrating from one cloud platform to the other. Note: this fix does not include Google drive source or Google drive destination. Large files can be transferred from cloud sources (except Google drive source) to all destinations (except Google drive destination).
Sometimes after restarting Nava Certus windows service, status of some tasks was changing to Failed. It was because those tasks were failed at some point during their life time. This issue is now fixed.
Sometimes when user was migrating specific SharePoint sites, items were not placed in the destination root folder. This issue is now fixed.
If SharePoint source had a lot items, migration task would not start because application was exceeding list view threshold. This is now fixed.
Known Issues
Sometimes the “Convert to Google Doc” feature might not be able to convert the file to Google Docs format. This is due to instability in the conversion APIs that Nava Certus relies upon.
Sometimes InnerFaultException may occur when reports are generated. This error can be ignored.
Migration of large files (2GB +) may fail when destination is Google Drive. This is due to a limitation with the GData API, which Google is investigating.
Nava Certus will freeze if you have selected Web Authorization, have opened the Google authorization web page and close the Google authorization web page.
Overwrite option is not supported anymore after changing to GCS 1.8 API.
It is not possible to convert or run jobs created in the older versions of Nava Certus.
If the source contains large items, stopping the task might take few minutes. This behavior is cause because the last item should be processed and have its status updated in the database.
Permissions are not set for SharePoint Groups.
Google Backend Error [503] Sometimes this error occurred when trying to start the task. The status of the task will not change. The user has to start it one more time.
“Google Form” documents will fail to be migrated since this feature is not supported by Google yet.
In the Distributed migration type, empty folders are not migrated to their owners. Items will not be migrated and will remain unprocessed if a user group is assigned as owner of a file/folder while performing a Distributed migration type. Note that the rest of the files will be migrated to their respective owners.
A workaround is to replace the group Email address in the mapping CSV file with one of a user and restart the task. After restarting the task the mentioned files will be migrated to the specified Email address (i.e. user).
Google drive, Dropbox, OneDrive require GUI authorization to be performed. It is not possible to start a task from the CLI for the first time. Once the job is authorized, you can start or stop if from the CLI anytime you wish.
Sometimes all of the permissions are returned as they are and sometimes they are being altered by the system. In the NC database the information returned by the system is printed.
0 Comments