System recovery
After a hard-crash, you must restore your LN Software Environment (BSE) from a back-up file stored on another system. Therefore, before you use your BSE in an operational environment, you must plan a back-up strategy for your BSE.
Back-up strategy
Before you can use LN, you must decide how you plan to protect your BSE against potential disk crashes and other system failures. If you do not plan and implement a correct back-up procedure, you cannot recover your BSE after a system crash.
You must thoroughly test your back-up and recovery procedure before and after you move to a run-time environment. You must perform test recoveries on a regular basis to ensure that your archiving and backup procedures work.
To ensure a successful recovery scheme, frequent backups are essential. You must base the back-up frequency on the frequency of changes in your BSE’s data. For example, if data changes at a high rate, the backup frequency must be proportionally high.
The amount of time you must keep the back-up files depends on the back-up frequency of your recovery scheme.
For additional safety, maintain two or more of your previous backup files, in case part of the current backup file is lost or damaged.
System recovery procedure
-
Procedure aim
To identify the steps that are required in a hard-crash procedure if you cannot reboot your operating system and restart your BSE.
-
Procedure result
This procedure results in a new BSE that functions the same as the initial installation.
-
Prerequisites
You must have on another system an undamaged backup version of the files that have crashed in your BSE environment.
Procedure summary
To recover LN:
- Restore the back-up files.
- Start and, if required, configure the Infor Solution License Manager (SLM).
-
Start the printer daemon and the shared memory:
- On a UNIX platform, run the
rc.start
shell script - On a Windows platform use the Infor ES Service Manager
- On a UNIX platform, run the
- Start the BSE environment.
In addition, you might also be required to recover your operating system and database. See your operating system and database manuals for the appropriate procedures.