Migrating From Version 7 To 8
Download as PPT, PDF1 like562 views
The document outlines the migration process from Laserfiche version 7 to version 8, detailing the necessary preparations, including database management, metadata structure changes, and client upgrades. It emphasizes the importance of planning, having backups, and resolving any data inconsistencies that may arise during migration. The document also includes technical steps for using the migration wizard and considerations for client and repository setup post-migration.
Migrating From Version 7 To 8
- 1. VA Laserfiche User Group seminar Migrating version 7 to 8 Rosalind Collins, City of Charlottesville, Laserfiche administrator
- 2. Overview of migration process Planning Preparing the stage Migrate SQL database Index images Register the repository Configure version 8 Backup Client migration
- 3. Laserfiche System Laserfiche Server (application server – the engine) SQL database – meta-data File server – Images, OCR text data Laserfiche Clients View/Read-only and Full (concurrent licensing) Weblink Integrations Add-on modules (Quick Fields, Workflow …)
- 4. Migration Planning Metadata structure changes Plan ahead for field merging New repository name cannot have spaces (or underscores) Resources for migration Software is free May want consulting services for migration (is not included in annual support) Internal resources Timing
- 5. Timing Opportune time to upgrade Hardware (LF or SQL server), SQL software, operating system, LF server location or SAN location or install additional Laserfiche modules Downtime Clients will need to be upgraded ** Other LF modules may need to be upgraded right away / some are backwards compatible Changes to metadata structure may require user training, changes to integrations and other changes
- 6. Preparing the stage Metadata staging Change field names (to automate or prevent merging) Data inconsistencies and other issues that arise in first test for migration will need to be resolved – build in time to do so Communicate upgrade plan Ensure full backup of data (vol files) and SQL database Take LF 7.x server offline if installing LF 8 on new machine – if on same machine, LF8 will replace LF7 – stop the LF server service prior to upgrade) Make source SQL database read-only
- 7. Migrate the SQL database Install migration utility Separate install from server Can be on server or another workstation Can be installed before or after LF Server Works only with the SQL server Install Laserfiche Server 8 can be done after wizard (below) If installing on same machine as LF 7, it will uninstall 7 before installing 8 (can’t have both on same machine at same time) Or on same network (take LF 7 machine offline first – can’t run both 7 & 8 on same network at same time) Use advanced options to turn on DCOM if want version 7 clients to be able to use it Run migration wizard Need permission to create DB on SQL server If creating new DB on same SQL server, the new (vers8) SQL database must have a different name from previous / if on different machine, can use same DB name
- 8. Migration Wizard pt1 Choose server type (SQL, Oracle) Server name, Authentication info, select database Choose destination type (SQL, Oracle) Choose dest server, Auth info, select/name DB Advanced options: Don’t migrate thumbnail data (will be recreated in 8 automatically) Template field merging Audit data Run Check Now Checks for known problems, data constraints, inconsistencies, page doesn’t exist, unmatched references, invalid data … Migration Guide on support.laserfiche.com gives technical info on any problems that might arise
- 9. Migration Wizard pt2 If OK, Continue – otherwise – Save Log file and resolve issues On continue, log will be created with all fields to be merged & any issues it thinks might arise from this Ok, Finish – “Ok to create db?” Yes It will run with a progress meter 4GB db took about an hour to migrate Completion message will show any problems it encountered (ver 8.1 also has end with error & resume in progress) Continue
- 10. Migration Wizard pt 3 Register Repository Could also Cancel here, Database is migrated Can register in Admin console If LF Server 8 is installed and running, can use this wizard to register the repository If using Migration Wizard to register repository – click Preview Will see volume paths (can save preview) Close OK Done – migration complete message Will get message to reindex files Can reindex now or later Wizard will use Quick Reindexer utility Admin Console or QR utility can be run later
- 11. Reindex and Configure Reindex documents Can do this in Wizard If not in wizard, recommended to use QRcmd.exe (Quick Reindexer, comes with migration utility) Test Client: Version 7 client can talk to LF server 8 (but have to turn on DCOM when installing server 8 – advanced options) Will have to attach new repository Check some documents Do a search using keyword (text) Any problems – laserfiche.com support site has technical information for resolving issues, common errors (like forgetting step above) Update backup procedures to include new SQL database , new repository (if changed) Set up new repository Recycle bin Windows accounts to replace LF user/group accounts
- 12. Clients Install client upgrades Client application Is msi install, so it can be “pushed” to clients Users may have to re-attach repository Snapshot upgrades along with client (32-bit) May have to reconfigure snapshot settings (if repository name changed, template changes, etc) To use 64-bit snapshot, deselect snapshot in client install and then go to “more” install options and choose 64-bit snapshot QuickFields Weblink Integrations
- 13. Special Notes (optional) Archive LF7 SQL db Object IDs are unchanged, except Recycle Bin becomes id 2, so whatever was id=2 will be changed. Otherwise, URL references will work.
Editor's Notes
- #4: Vendor recommends not having LF server app on same machine as SQL server LF 8 optimized for SQL 2005 (will run with SQL 2000 and SQL 2008) File server – recommend on SAN with RAID 5 Need to ensure the people responsible for all the parts of the system are included in communication about the upgrade and perhaps in the planning itself
- #6: Downtime – if all goes well, could only be a day or over a weekend … biggest factor is migrating the data – 4GB took an hour … so can estimate from there – factor of hardware and network Clients – if turn on DCOM during LF8 install, vers 7.x clients can use it Weblink and Web Access versions 7 will run after migration as long as included DCOM in LF 8 installation RME gets upgraded with the server Snapshot gets upgraded with client (if had to rename repository, will have to re-run snapshot configuration) Audit Trail will get upgraded with server BUT data will not migrate -> can use vers 7 admin console to export the audit log before migration QuickFields 7 will run with 8, but so many advances in QF 8 – suggest even recreating QF sessions to take advantage of new features – rethink and redesign processes (can multi-task more, for example). There is a migration utility for QF that will migrate your vers 7 sessions … but it will set things up in vers 8 just as they were in vers 7, so may not run optimally using vers 8 features. Workflow – is not backwards compatible – will have to re-do all workflows in version 8 as well (but there’s a good reason in that it does things better)
- #9: Field merging – can set to merge or never merge … if merge, it will ask about each merge it finds. Be prepared. If never merged, you can merge fields manually in Admin Console after upgrade
- #10: SQL Server default settings determine where the log goes
- #11: To move volumes (images), just move (copy recommended if possible) the VOL folders to new SAN location prior to start of this page UBS recommends moving volumes AFTER migration – so put in path for current volumes location to test that migration worked, then move volumes as last step
- #12: run QRcmd locally on LF Server machine from DOS prompt (qrcmd ? will give params)
- #14: ** can find something by its object id by sorting on that column – would be an early folder or document … In LF 8 can search by object id. In LF 7 – can do it? But need advanced search ??