infoRouter Application Backup | What to Include and How

How to back up the infoRouter application directory, including what it contains and why it must stay synchronized with your database and Warehouse backups.

By Orhan Yorukoglu

The infoRouter application directory contains configuration files, portal definitions, custom search pages, email templates, and logs generated during normal operations. These files are created and modified as administrators and users customize infoRouter. Losing them means recreating portals, search pages, and configuration settings from scratch.

Include the application directory in every backup cycle.


Key Takeaways

  • The infoRouter application backup must include portals, configuration files, custom search pages, email templates, and logs that cannot be reconstructed from the database alone.
  • Stop IIS before running an infoRouter application backup to ensure no active sessions interfere with the file copy process.
  • The application directory, database, and Warehouse must be backed up at the same time for a consistent infoRouter application backup.
  • Automate the infoRouter application backup alongside the database and Warehouse backups using a single scheduled script to prevent missed components.

What the Application Directory Contains

DirectoryContents
PortalsCustom portal definitions created by Portal Administrators
ConfigApplication configuration files
LogsSystem and operation logs
Custom Search PagesSearch page layouts created by Search and Category Administrators
Email TemplatesNotification and workflow email templates

Each of these directories contains information generated during the course of infoRouter operations. They cannot be reconstructed from the database or Warehouse alone.

Backup Procedure

  1. Stop IIS on the infoRouter application server to ensure no active sessions are running.
  2. Back up the entire application directory using your preferred backup solution. Run this nightly.
  3. Store the backup on the same media used for the Warehouse and database backups.
  4. If database files reside within the application path (common in some MySQL configurations), stop the database service before starting the backup.

Automate the Process

Ask your network administrator to create a backup script that covers the application directory, the database, and the Warehouse together. Automating the process ensures no component is missed and eliminates reliance on manual execution.

Critical: Keep All Three Components in Sync

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

See also:


Frequently Asked Questions

What happens if I back up the application directory but not the database or Warehouse?
The restore will fail or produce inconsistencies. The application directory, database, and Warehouse are interdependent and must be backed up and restored together from the same point in time.
Do I really need to stop IIS before backing up the application directory?
Yes. Active sessions can lock files or write partial data during the backup, resulting in corrupted or incomplete copies. Stopping IIS ensures a clean backup.
How often should I back up the infoRouter application directory?
Run the backup nightly, alongside the database and Warehouse backups. This ensures all three components stay in sync.
Can I use any backup tool for the application directory?
Yes. Any file-level backup solution works, including Windows Server Backup, third-party tools, or scripted file copies. The key requirement is that it captures the entire application directory.