How To Backup The InfoRouter Warehouse
The infoRouter warehouse contains all the documents uploaded or imported into infoRouter. The
infoRouter warehouse resides on the file system.
The infoRouter warehouse houses the following information for each document:
- Latest version of the document
- All previous versions of the document
- Meta information about the document such as description, keywords etc.
The infoRouter warehouse needs to be backed up regularly if infoRouter is being used in a production
environment.
To backup the infoRouter warehouse, perform the following:
- STOP IIS on the infoRouter application server to ensure no one is actively using infoRouter.
- Backup all warehouse components using your preferred backup solution.
- You do not need to backup the index server catalog. The catalog can be re-created automatically.
- If you are running infoRouter in Distributed mode and you have separated your warehouse across multiple physical drives or servers, make sure to backup all warehouse components at the same time.
- Preferably use the same tapes (or other media) to backup infoRouter so that this information would be much easier to access in case you need to restore infoRouter to an earlier instance.
Tip :
The “Compact” feature allows you to get rid of unnecessary versions of documents. Please use the “Compact”
function regularly to re-claim valuable disk space and to cut down on backup time.
How to Backup the infoRouter Database
infoRouter uses a database solution to keep vital meta information about the documents in infoRouter.
Information kept in the inforouter database:
- infoRouter Users
- infoRouter User Groups
- infoRouter Folders
- infoRouter Libraries
- Document and Folder Security
- Custom Property Definitions
- Custom Property Data
- Workflows
- Tasks
- and much more
Information kept in the infoRouter database stays in a perfectly synchronized way. There is an entry in the infoRouter database for each document. There are numerous other database tables and objects to help perform the operations supported by infoRouter.
The infoRouter database needs to be regularly backed up in production environments and this backup must be kept in synch with the warehouse and application directory backup.
To backup the infoRouter database, perform the following:
- Stop IIS to make sure that no one is actively using infoRouter.
- Using your preferred backup solution, backup the entire application directory nightly.
- Store the contents of the backup on the same media you used to backup the infoRouter warehouse and database backup
- In cases where the database files are in the application path, please make sure to stop the database services. This will ensure a good backup without interference.
How To Backup The Application Directory
It is very important to include the infoRouter application directory in your backup plan. The application
directory must be backed up regularly in production environments.
The infoRouter application directory houses the following:
- Portals Directory
- Config Directory
- Logs Directory
- Custom Search Page Directory
- Email Templates Directory
- Config Directory
- Various Logs
- and much more>
Each of the directories listed above contain vital information generated during the course of infoRouter
operations. New or updated portals are kept in the portal directory, custom search pages created by Search
and Category Administrators are kept in the search pages directory and so on.
This information needs to be backed up regularly in production environments.
To backup the infoRouter application directory, please perform the following:
- Stop IIS to make sure that no one is actively using infoRouter.
- Using your preferred backup solution, backup the entire application directory nightly.
- Store the contents of the backup on the same media you used to backup the infoRouter warehouse
and database backup.
- In cases where the database files are in the application path, please make sure to stop the database
services. This will ensure a good backup without interference.
How To Restore InfoRouter
In the event that you need to restore to an earlier backup of infoRouter, you must remember to restore all
the components of infoRouter from the same backup media for the given date.
To Restore InfoRouter To an Earlier Backup, Please Perform The Following:
- Stop IIS.
- Restore the infoRouter database
- Restore the infoRouter warehouse
- Restore the infoRouter application directory
- Re-build the full text index by forcing a rescan on MS Index Server for the warehouse directory
What To Do In Case Of a Server Crash
In case you experience a server crash and there is nothing to do but to start all over again with a new server,
remain calm and follow these instruction in the order in which they are described. Please feel free to call or
email us (support@inforouter.com) so we can help you get through these tasks
To Recover From a Server Crash, Perform The Following:
- Gather the most recent backup tapes (or other media)
- Allocate a new server to install infoRouter. Please make sure that the new server conforms to the
specifications and minimum requirements outlined in the Minimum Server Requirements document.
- Important Note: Make sure that the new server is setup in identical fashion. Same drive letters etc.
- Load the OS on to the new server. Make sure to install all the correct OS components outlined in
the Minimum Server Requirements document.
- Install the database solution of your choice (if you are in single server mode) on to the new server.
- Create a RECOVERY directory to restore all infoRouter components from tape.
- Restore the infoRouter database from the backup media into the Recovery directory
- Restore the infoRouter application directory from the backup media into the Recovery directory
- Restore the infoRouter warehouse directory from the backup media into the Recovery directory
- Install infoRouter onto this new server as if you are starting from scratch. Make sure to follow the
instructions in the infoRouter Implementation Guide. Install the new instance of infoRouter exactly as
you had it on the original server (Same drive letters, same paths etc.).
- Now that you have an empty infoRouter instance, we will begin the restore process.
- Stop IIS.
- Restore the database overwriting the empty infoRouter database
- Restore the Application directory overwriting the newly created application directory.
- Restore the warehouse overwriting the newly create empty warehouse directory.
- Start IIS