Output Manager stores critical information about the documents it processes in several key places. Any disaster recovery plan should ensure that the following components are backed up.
- The Database used for Output Manager
- Contents of the File store
- Configuration data for quesues and shares
- MFF transform profiles that possibly contain customizations
Disaster Recovery Plan
All disaster recovery plans should be tailored to the customer specific environment. Below is an example plan. This is only meant to illustrate the essential steps needed to back up a production system.
- Backup Output Manager Database
- This can be performed via SQL Server Management Studio (SSMS), or through power shell.
- The Output Manager Diagnostics tool also provides a quick way to create a database backup.
- Backups should be made on a regular basis depending on your organization's need
- The resulting backup file should be archived on tape or on other secure media.
- Backup Contents of the Document File Store
- Ensure that the files are backup regularly or are located on a media type that allows for sufficient disaster recovery (i.e. SAN with RAID)
- Configuration data needed to recreate the share(s) should also be stored. This should include share names and permission settings.
- Backup files that contain customizations
- It is import to make sure all files in the OM directory that have customizations are included in the regular backup
- Transform files and possibly configuration files are examples
- Save configuration data for windows print queues
- Save information required for recreating all windows print queues including settings, share names and driver information
- Configuration details should be handy in the event of a disaster
- Ensure License information is available
- Make sure that the serial number and key are available to reapply.
- This will be important when bringing the new system online.
- Review backup procedure for associated applications
- Output manager is often used with other Nuance products
- Ensure there are appropriate disaster recovery measures for those programs
- Example: DRS and Autostore
- Examine other backup methodologies
- It is also important to examine the customer's existing environment as it may radically change the backup plan.
- Use of virtualization could replace most of the back steps.
- Use of a distributed Output Manager configuration could be very useful in disaster recovery.
Test Disaster recovery
- The plan should be tested to ensure that it will be effective when a real disaster occurs.
- The frequency and scope of testing should be dictate by the customer's specific policies.