What happens if I restore the database but not the Warehouse?

The database will contain metadata pointing to documents that no longer exist in the Warehouse, resulting in broken references. All three components must be restored together from the same backup.

Can I use SQL Server Express for my infoRouter database?

Express editions have size and feature limitations that can affect backup and maintenance capabilities. Check the infoRouter system requirements and avoid using editions not intended for production use.

Does infoRouter support automated database backups?

infoRouter relies on your database platform's native backup tools. Use SQL Server Maintenance Plans or mysqldump scripts to automate backups on a nightly schedule.

Why do I need to stop IIS before running the database backup?

Stopping IIS ensures no active user sessions are writing to the database during the backup. This prevents partial transactions from creating inconsistencies in the backup file.

infoRouter Database Backup Guide | Steps and Requirements

The infoRouter database stores all metadata about documents, users, groups, folders, Libraries, security assignments, Custom Property definitions and values, workflows, and tasks. Every document in the system has a corresponding set of database entries that describe it. Losing the database means losing the organizational structure that makes your documents retrievable.

Regular database backups are required in any production environment.

Key Takeaways

The infoRouter database stores all metadata for documents, users, folders, security assignments, workflows, and audit trails, making regular database backup essential.
infoRouter supports database backup on both Microsoft SQL Server and MySQL using standard platform tools.
The infoRouter database, Warehouse, and application directory must be backed up simultaneously to avoid data inconsistencies during restore.
Restoring mismatched database backup components will result in broken references between metadata, documents, and system configuration.

Supported Database Platforms

infoRouter supports the following database platforms:

Microsoft SQL Server
MySQL

What the Database Contains

The infoRouter database stores:

Users and User Groups
Libraries and folder structures
Document and folder security assignments
Custom Property definitions and data
Workflows and tasks
All other metadata that describes documents and system configuration

This information is maintained in a synchronized state with the document Warehouse and the application directory. All three components must be backed up together.

Backup Procedure

Stop IIS on the infoRouter application server to ensure no active sessions are running. See the technical overview for server architecture details.
Run the backup using the standard backup procedures for your database platform (SQL Server Management Studio, mysqldump, or your preferred backup tool).
Store the backup on the same media used for the Warehouse and application directory backups.

Critical: Keep All Three Components in Sync

The infoRouter database, the document Warehouse, and the application directory must be backed up at the same time and stored together. If infoRouter needs to be restored, all three components must be from the same point in time. Restoring mismatched components will result in data inconsistencies.

Frequently Asked Questions

What happens if I restore the database but not the Warehouse?: The database will contain metadata pointing to documents that no longer exist in the Warehouse, resulting in broken references. All three components must be restored together from the same backup.
Can I use SQL Server Express for my infoRouter database?: Express editions have size and feature limitations that can affect backup and maintenance capabilities. Check the infoRouter system requirements and avoid using editions not intended for production use.
Does infoRouter support automated database backups?: infoRouter relies on your database platform's native backup tools. Use SQL Server Maintenance Plans or mysqldump scripts to automate backups on a nightly schedule.
Why do I need to stop IIS before running the database backup?: Stopping IIS ensures no active user sessions are writing to the database during the backup. This prevents partial transactions from creating inconsistencies in the backup file.