Your entire database (MySQL) All of your applications All of your images All of your configuration files All of your installation files

Full text


 Your entire database (MySQL)

 All of your applications

 All of your images

 All of your configuration files

 All of your installation files


•Under most configurations this is a one stop shop for all of your configuration files, and data.

EDI Directory Structure

•This directory houses all of the installation files that you need to expand your system or get your current system back up and running.

EDI_Software Directory

•These are the actual files that are saved in your archive. While these are the most important part of your data they cannot be used without the database.


•This is the master record of all information that is stored in your eDoc system. This contains information about every record in the system as well as every user allowed to access the system and what they allowed to do.

The Database

•These serve as organizational categories in the database. They categorize tables to make it easier to navigate your system.


•Tables are storage compartments inside the database that store all the information that the system needs to function. This includes index information for all of your images,

permissions, login information for all of your users, and licensing information for all your products.


•This is what happens when the worst happens.

DR (Disaster Recovery)


2020DOC •This is your database management and scanning application. You are also able to manage your users and permissions through DOC. ProDOC •This is the front end capturing software. In most cases this handles scanning IDs, capturing receipts, capturing loan forms, and scanning other type of documents. 2020COLD Statements •This application allows you to access and import your monthly statement files. IntelliSweep •IntelliSweep runs on the server and imports all documents captured in ProDoc, into your database. In some cases this application also handles the import of your Member_List file. Auto-Renamer •This product handles the automated renaming and sorting of your daily reports. Auto-Import •This application handles the automatic importation of your monthly statement files. 2020 iDOC •This is a browser based application that allows you to view data and manage permissions.


 Your Archival System

 How to get things in, how to toss things out

 Keeping your tables down to a reasonable size

 Audit your system security

 Manage permissions

 Periodic tasks, what to do and when to do them

 Your Server

 Patching , Updates, and other Maintenance


There are three ways to get data into your eDOC system.

 Imported Manually

 For images this method is by using the “Import” function in 2020DOC. This is a great way to

handle large documents that are already electronic. The preferred format for these imports are PDF or Tiff files.

 For statements this would be a manual import into 2020COLD Statements. Our preferred format

for this is text or PDF imports. PDF imports require configuration changes and not all PDF formats are available for capture.

 For reports you would manually sort and rename your reports. Reports are supported in text

format only.

 Captured Automatically

 For images this method is used when ProDOC captures documents automatically and sends them

up to the server for import through IntelliSweep.

 For statements this utilizes your Auto-Import Services to import your statement.  For reports Auto-Renamer renames, and sorts your reports.

 Scanned Directly




Relocate the physical image location to NAS or other storage


Export and store to another storage





Export and store to another storage





Relocate report files to NAS or other storage location.



 Periodically verify your indexes.

 Log into DOC, view a table, and ensure that your users are correctly entering index information. Examples  Make sure that these indexes and table configurations are optimized for you and your users. Optimized?

 Divide your receipts by year.

 Create a new table at the end of every year and move all the receipts from the previous year into it. This helps

manage the number of records that are in each table as well as improves the ability to locate them.  Verify that every table in your database has its own “Default Location”.

 Not having separate locations will lead to an extremely messy situation if at anytime your system needs to be

recovered. It also is detrimental to the support process. How?

 Check to make sure all your documents are flowing properly.

 Periodically check your database to make sure the documents that are being captured are up to date. If you are

capturing receipts everyday make sure you can see today’s receipts.

 Verify that your previous months statements have been imported correctly.

 Ensure that your daily reports are in the system and check the exceptions directory to make sure there is nothing

awaiting processing.

 Audit your permissions and ensure users have the correct access.

 To accomplish this you can manually go through each user/group to ensure the correct permissions are set.

 We recommend utilizing the group permissions feature and adding each user to the corresponding group instead of adding permissions

to a user individually.

 If you utilize MySQL security you can obtain the SAReport tool which will export a security report explaining who


 Backup Targets For File Based Backups

 EDI Directory Structure

 This target contains all configuration files and all data for your eDOC system. This

directory structure is a dynamic target and is recommended to be backed up often.

 If you have relocated your statements, reports, or image locations to another server you must remember to include those targets in your backup.

 MySQL Data Directory

 This target contains the index and database information that allows your eDOC system

to function. This is also a dynamic target and should be backed up at the same frequency as your images.

 You can also configure a MySQL dump to extract a text backup of your databases that can be stored with, or instead of the MySQL Data Directory.

 EDI_Software Directory

 This directory contains all of your installation files that can be used to expand or

recover your system. This target does not change unless updates are made to it by you or our staff. This is not an imperative backup location but is recommended to expedite the recovery process.

 We have an excellent backup strategy called iSync that will

minimize any headache associated with backing up your server (including other servers)


Patches and Updates

 We recommend, what Microsoft recommends (stay up to date)

 If we find a compatibility issue with an update, we will let you know.

Operating System Upgrades

 Though we have not rolled out support for Windows 7 yet our

general support method is current -1.

Leverage the network and inquire about our partner


Who is responsible?

In short that would be you, but we and our partners are

here to help.

 If you are utilizing a file based backup system then restore

what you have and give us a call. There will be a charge associated with digging through the mess but we will have you up and running as quick as possible.

 If you are utilizing iSync then your system will rollover to

the virtualized eDOC server. If your disaster is larger than just a server crash your system is virtualized in multiple different locations to ensure minimal downtime.


Things to check after today’s course

Verify your indexes.

Ensure your receipts are divided by year.

Verify your tables each have their own location.

Check your tables and make sure everything is


Audit your permissions and make sure those who

need access have it.

Look into your backup strategy and make sure you


 For questions about the information in this document, procedures,

or issues you find while performing your checks please call EDI

support at 800-425-7766 Opt. 2 or email

 For inquiries about iSync or any other eDOC application please

contact Jared Christiansen at 800-425-7766 Ext. 404 or

 For inquiries on network or server maintenance please contact

Matt Sawtell with WescoNet at 800-327-3478 Opt. 8 or





Related subjects :