You are viewing limited content. For full access, please sign in.

Question

Question

How to Migrate audit database 8.3 to 9.2

Audit Trail
Updated January 23, 2015
asked on January 14, 2015

I am planning on doing a Laserfiche upgrade for a customer from version 8.3 to 9.2 in production. It is not an in place upgrade. I understand all the Laserfiche steps but what should I be doing for the Audit Trail? I tried the migration on the dev environment & when I did the audit trail configuration it created a new audit trail db for 9.2. For production we would like it the 8.3 data to be available.

Please let me know how?

0 0

Answer

APPROVED ANSWER
replied on January 14, 2015

The actual audit data from Laserfiche are stored in binary log files. What Audit Trail does is that it will read in the data from these binary log files and populate a database with it. The data that's read in depends on the date range you have configured from the Audit Trail Configuration page. As for the database itself that's used for the Audit Trail reporting, it should get upgraded automatically (with schema changes, etc.) if that's the database you choose to use during the database configuration of Audit Trail. Otherwise, there isn't really a reason for needing to retain the Audit Trail database as it can be recreated easily. The only real factor is the time it takes to repopulate the database.

0 0

Replies

replied on January 14, 2015

Thank you for your response Alex. In the Audit Trail config page it asked me for the DB server name but not for the instance name & it automatically created a new db for 9.2. How do I make sure the 8.3 db is upgraded to 9.2 for audit? I went through the manual config on the audit trail web page.

0 0
View 5 previous replies
replied on January 14, 2015

If you go back into the Audit Trail Configuration site and view the Database page, you can click the drop down to change the database you want to use. Then just click the "Update" button.

0 0
replied on January 15, 2015

I did select the old 8.3 db and click update. I do not get any results when I try to run queries on the old db. I do get results on the new 9.2 db, so I am thinking that this step dint work.

0 0
replied on January 15, 2015

Is there a reason why they can't just use the new Audit Trail database that was created in 9.2 and just re-specify the date range so it loads the proper data they want to report on?

0 0
replied on January 19, 2015

The audit info from 8.3 is lost. How do we do a seamless upgrade for audit trail if it is not an in place upgrade. For production they would lose all the old audit data before the upgrade.

Right now I am trying to run queries & no results come up against the 8.3 db but against the new db i get results.

I am trying direct sql queries from sql management studio, teh customer prefers that.

0 0
replied on January 19, 2015 • Show version history

The audit data is stored in binary audit log files that the Laserfiche Server writes to. Audit Trail just reads in the data from those binary files and loads it into the audit database. The data that gets loaded depends on the date range that's configured in the Audit Trail Configuration page.

I'm not clear on what you mean by the audit data being lost. That would only occur if they lost their binary audit log files and it wasn't being backed up.

To summarize, you can think of the Audit Trail database containing volatile data. Based on the date range specified, that's the data that is loaded into the database for which users can report from. It ultimately shouldn't matter if the actual audit database is lost as it can be rebuilt by reading in the information from the LF Server's binary audit logs and loading that information (based on the date range) back into the audit database.

0 0
replied on January 22, 2015

I went back & specified the date range for Age=365. The reporting tool brings back the results for everything after I did the upgrade. How do I get the audit data from before the upgrade as this is not an in place upgrade. In production the customer would like to get the audit data before & after so if the AUDIT files are on the old server I will not be able to generate the report.

0 0
replied on January 22, 2015

So to clarify, the customer was running LF 8.3 on one server and you upgraded them to LF 9.2 on a new server, correct? That's my assumption as you've stated that this won't be an in place upgrade.

Can you clarify then how you transferred the repository data from the old server to the new server?

For example, on the old server, say that the repository was just stored in a path like C:\My Repository. By default, there should be a folder, C:\My Repository\AUDIT that contains the binary audit log files written by the LF 8.3 Server. In actuality, their repository and audit data may be somewhere else. Regardless, when you installed LF 9.2 on the new server, did you just copy the repository data from the old server to the new server and then register the repository in the LF 9.2 Administration Console? Also, was there any modification of the SQL database during this upgrade? Did they switch SQL instances or was the database untouched?

The reason for the questions is that all of the audit data should still be present if you properly copied over the repository and AUDIT folder to the new server and registered the repository. It's also required to be using the same repository database from before. Then when you configure a date range in Audit Trail, it will just load the data from the binary audit logs into the audit data base. Upgrading the Laserfiche Server and changing hardware should not have impacted this.

If you suspect that there may have been an issue with your upgrade process that is now causing the inability to view audit data from prior to the upgrade, then it may be best to open a support case so further investigation can be done to determine what exactly happened during the upgrade and what could be causing the issue you're reporting.
 

0 0
replied on January 23, 2015

I have not copied over the AUDIT files from the old server to the new server. Our upgrade does not seem to have any issues. I will copy over the files & giving it a try.

I followed the steps of unregistering & re-register the repository on teh new server which upgraded the db. The volumes were on the network so there was no need to copy them over to the new server & the search catalog was rebuilt. But I missed the AUDIT files.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...