Question

Migration v7 to v9 testing - Best practices?

Version 9 Version 7 Administration Installation and Upgrades

Updated August 15, 2014

asked on August 8, 2014

Hello!

I'm doing more testing as we move from v7 to v9. I would like to run the migrations to temporary dbs, Register the new repositories, check them out, then delete them and run the migration for real.

This lets us get a handle of any issues and of the time the migration will take.

I have one problem, though. Our volumes are stored on another file server, and listed in the volume on V7 using the UNC path.

This means that once the repository comes up on V9, it is immediately able to access the documents.

What is the best practice in this case? I want to be able to bring up the V9 repo to test, but not with the production volumes.

Thanks in advance...

0 0

Replies

replied on August 8, 2014

You can change the volume paths in Administration Console after restoring the database.

If you don't want any period of time where the live volumes are accessible maybe block network communications to the server hosting the volumes or manually replace the volume paths in the database tables.

0 0

replied on August 8, 2014

I thought changing the paths would work too, but if you change the paths in v9 it wants to move all of the files from their existing location.

That would be bad...

At this point, I'm thinking that changing the paths in the DB tables might be my only option.

0 0

replied on August 12, 2014

When migrating from Laserfiche 7 to Laserfiche 9, migration utility only upgrades the database. When you are testing the system, you are working with a copy of the database, but the production volumes. Make a copy of the production volumes to use during testing, preserving the originals.

Keep in mind if you are working with a copy of the volumes, they must be synced with the database. If changes have been made to one or the other, but not both, you will find problems in your repository. Consider testing from a stored back-up.

This help file as well as the attached whitepaper speak specifically to migrating from Laserfiche 7 to Laserfiche 9 and should be a good reference for you.

Laserfiche_7_to_9_Migration_Quick_Reference.pdf (70.93 KB)

| Download

0 0

replied on August 12, 2014

Thanks Katherine!

I'm trying to keep the "Test" copy on LF9 from touching my production volumes.

So far, I haven't needed to have "real" documents for my testing, so after the migration but before I attached the new repo I edited the vol table and changed the paths to a nonexistant drive.

The result was a repository which is fine for testing but the pages are missing. (much like if the volume files were missing for whatever reason.) This lets me work out the procedure, test the conversion, convert to Windows accounts, create workflows, etc.

I would do this through the interface, but it seems if you change the volume location in LF9 the interface wants to move the data for you. (I think I will put in a feature request - it would be friendlier if you saw a popup at that point which asked whether you wanted to move the files or not.)

Thanks for the info!

0 0

replied on August 15, 2014

Hi Michael,

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

If you still need assistance with this matter, just update this thread. Thanks!

0 0

You are not allowed to follow up in this post.

Question

Question

Migration v7 to v9 testing - Best practices?

Replies

Sign in to reply to this post.