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

Question

Question

Backup Methods

asked on May 16, 2018

Hello,

We are a City who is trying to figure out what our backup method should be. We were quoted on a backup software from an outside company, but I'm wondering if there is any secure way to do this in house? I just want to make sure all of the files AND the metadata can be retrievable. We are currently just storing the files themselves on Amazon Drive.

Thank you,

Kiersten

0 0

Replies

replied on May 16, 2018

The bare minimum that you must get backed up are the Repository location, Volume locations, and LF DB(s).  You may also want to back up your Laserfiche license files so that you have them if you need to deactivate/reactivate.  I normally do not bother backing up the search Catalog, but that is another set of files you may wish to backup.

2 0
replied on May 16, 2018

This resource may help.

1 0
replied on May 16, 2018 Show version history

Something to keep in mind is that backing up the files on disk and the database are two separate processes. This means that it's possible that your metadata and filesystem could get out of sync. It's not an insurmountable issue, but it's one to be aware of. The worse that can happen is that you have pages for which there are not documents, and vice versa. The closer you can keep the backups in sync, the better.

Our database is backed up every hour, and we take diffs of the file system every hour. In a recovery scenario, we'll take the newest set that enables us to restore the file system and apply transaction logs to match. If the database has a more recent backup, we'll check to see which documents have no pages, and use that information to know what we possibly lost. We don't mind documents with no pages, but we'd like to avoid pages sitting out there with no matching documents.

0 0
replied on February 11

Hi, I'm kinda new to LF and was wondering if you can elaborate on the differences between pages and documents.  i understand that the metadata information is kept in the db and the actual info/data is kept in local files.  Are these what you are referring to?

0 0
replied on February 11

Correct.

Documents are basically a metadata construct that wraps a collection of pages or, as in the cases of electronic documents, points to a file attachment.

Th stuff that exists on disk in the repository are the electronic documents, page images, and OCR'd text. There are some other miscellaneous files that aren't directly exposed to the user.

0 0
replied on February 11

A document consists of metadata and (optionally) content in any of the following forms:

  • Laserfiche-generated image pages (in TIFF format) 
  • Pages containing text content
  • An electronic document, e.g. a PDF or .docx file.

 

Both pages and electronic documents are stored in the volumes. The metadata is stored in the database.

 

When Devin said documents with no pages, they meant that the document has metadata but no pages.

0 0
replied on February 11

Specifically, in the context of backups, we'd rather have the metadata, but lose the pages, if we couldn't perfectly sync up our filesystem and database backups.

In that case, we'd know that a document existed, we'd have all of the metadata, but the pages would be lost. It's likely that the difference is a couple of hours at most, and all of that data could easily be re-imported/scanned. However, YMMV.

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

Sign in to reply to this post.