infoRouter Warehouse Backup | Steps and Best Practices

How to back up the infoRouter document Warehouse, including distributed mode considerations and tips for reducing backup size with the Compact feature.

By Orhan Yorukoglu

The infoRouter Warehouse is the file system location where all documents uploaded or imported into infoRouter are physically stored. It contains the latest version of every document, all previous versions, and associated metadata files (descriptions, keywords, and other properties). Losing the Warehouse means losing the documents themselves.

Regular Warehouse backups are required in any production environment.

Key Takeaways

  • The infoRouter Warehouse backup preserves all physical document files, every version, and associated metadata files stored in the file system.
  • In distributed mode, all Warehouse backup components across multiple drives or servers must be backed up simultaneously.
  • The Compact feature reduces Warehouse backup size by removing unnecessary interim document versions.
  • The Warehouse, database, and application directory must be backed up together from the same point in time to ensure a consistent restore.

Backup Procedure

  1. Stop IIS on the infoRouter application server to ensure no active sessions are running. See the technical overview for server architecture details.
  2. Back up all Warehouse components using your preferred backup solution (Windows Server Backup, third-party backup software, or scripted file copy).
  3. You do not need to back up the index server catalog. The catalog can be rebuilt automatically after a restore.

Distributed Mode

If infoRouter is running in distributed mode with the Warehouse spread across multiple physical drives or servers, back up all Warehouse components at the same time. Use the same backup media for all components so they are easy to locate together during a restore.

Reducing Backup Size

Two infoRouter features help keep Warehouse size manageable:

  • Compact: Removes unnecessary interim document versions. Run the Compact function periodically on folders with high document churn to reclaim disk space and reduce backup time.
  • System Recycle Bin: The infoRouter Control Panel includes General Application Settings with a System Recycle Bin section. Configure it to move user recycle bin items to the system recycle bin and purge periodically. This prevents deleted documents from continuing to consume Warehouse space.

Critical: Keep All Three Components in Sync

The infoRouter Warehouse, the database, 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.

See also:

Frequently Asked Questions

Do I need to back up the index server catalog along with the Warehouse?
No. The index server catalog can be rebuilt automatically after a restore. You only need to back up the Warehouse files themselves.
What is distributed mode and how does it affect backups?
In distributed mode, the Warehouse is spread across multiple physical drives or servers. All Warehouse components must be backed up simultaneously and stored on the same media so they can be located together during a restore.
How can I reduce the size of my Warehouse backups?
Use the Compact feature to remove unnecessary interim document versions from folders with high document churn. Also configure the System Recycle Bin to purge deleted documents periodically so they stop consuming Warehouse space.
What backup tools can I use for the Warehouse?
Any file-level backup solution works, including Windows Server Backup, third-party backup software, or scripted file copies. The critical requirement is that the Warehouse, database, and application directory are all backed up at the same time.