Question

Does a migration document exist for an upgrade+migration scenario?

Laserfiche

Updated March 7, 2016

asked on March 7, 2016 • Show version history

The situation I am faced with is that we are on an older version of Laserfiche on a very old (Server 2k3) physical server. I tried to do away with it altogether since we no longer use it other than retention of documents for SARBOX. Unfortunately we need to keep that stuff around for a long time, so I have no choice but to migrate the data. I am in a tricky situation here.

I am migrating from:

1.) Physical (2k3) Server to Virtual (2k8R2) server, which has MS SQL installed already

2.) LF version 7 to 9

3.) From a legacy (soon to be decommissioned fully) network to a new network - there is no direct access between the 2 of them.

I have read the install documentation and understand the need to do the database upgrade, though from what I read this requires connection between both the new and the old DB which isn't possible in our situation.

If I understand correctly, there are the following components involved with the entire system:

1.) The LF server

2.) The LF client

3.) The actual scanned document repository

4.) The database

*I realize there are more option features to go along with this, but do not need them. All we need is the ability to maintain archive and retrieve documents in case of audit.

Anyone have any suggestions or know of any documents I can reference for this type of migration? Thanks!

0 0

Replies

replied on March 7, 2016

Can you do a backup of the database for LF7 and load it to SQL 2008? From there you can run the Migration Utility 9 to convert the database from Lf7 to LF9. Then all you need is to copy the volumes/images from the old server to the new server.

2 0

replied on March 7, 2016

Hi Mike,

You don't explicitly need to mirror them, but you'll need to tell the Laserfiche Server that the locations have moved (relative to itself). The final section of the migration wizard provides a UI for this, or you can go into the administration console post-migration and manually update the volume paths.

2 0

replied on March 7, 2016

Yes, I can do that and was already thinking this was the proper approach.

Another question - do the drive letters of the images need to be matched up on both of the servers? Meaning, on the old server, there is a separate drive, E:, for just the images themselves. Does this have to be mirrored on the new server?

If it does, is there anyway I can change the drive letter on the old server first then migrate?

0 0

replied on March 7, 2016

Awesome! Sounds simple enough! Thanks for the assistance.

0 0

You are not allowed to follow up in this post.

Question

Question

Does a migration document exist for an upgrade+migration scenario?

Replies

Sign in to reply to this post.