<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/adm_system_recovery" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">System recovery</Title>
		<Keyword ContextSensitive="No"><Level1>System recovery</Level1>
		</Keyword>
	</Header>
	<AimSection><SectionTitle>System recovery introduction</SectionTitle>
		<Paragraph class="Default">This section describes the relevant procedures and the steps required to carry out the crash recovery procedure of an ERP LN Software Environment (BSE) for UNIX platforms and Windows platforms.</Paragraph>
	</AimSection>
	<GeneralSection><SectionTitle>System recovery overview</SectionTitle>
		<Paragraph class="Default">After a system crash, you must restore your ERP 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.</Paragraph>
		<GeneralSection><SectionTitle>Back-up strategy</SectionTitle>
			<Paragraph class="Default">Before you can use ERP 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 proper back-up procedure, you might not be able to recover your BSE after a hard crash.</Paragraph>
			<Paragraph class="Default">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.</Paragraph>
			<Paragraph class="Default">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.</Paragraph>
			<Paragraph class="Default">The amount of time you must keep the back-up files depends on the back-up frequency of your recovery scheme.</Paragraph>
			<Paragraph class="Default">For additional safety, maintain two or more of your previous backup files, in case part of the current backup file is lost or damaged.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>System recovery procedure</SectionTitle>
		<GeneralSection><SectionTitle>Procedure aim</SectionTitle>
			<Paragraph class="Default">This section describes the steps required in a hard crash procedure if, after a crash, you cannot reboot your operating system and restart your BSE.</Paragraph>
		</GeneralSection>
		<GeneralSection ID="proc_result_and_prerequisites"><SectionTitle>Procedure result and prerequisites</SectionTitle>
			<GeneralSection><SectionTitle>Result</SectionTitle>
				<Paragraph class="Default">This procedure results in a new BSE that functions the same as the initial installation.</Paragraph>
			</GeneralSection>
			<GeneralSection><SectionTitle>Prerequisites</SectionTitle>
				<Paragraph class="Default">You must have on another system an undamaged backup version of the files that have crashed in your BSE environment.</Paragraph>
			</GeneralSection>
		</GeneralSection>
		<GeneralSection ID="proc_summary"><SectionTitle>Procedure summary</SectionTitle>
			<ProcedureList><ListIntro>To recover ERP LN after a hard crash, take the following steps:</ListIntro>
				<ListItem>Restore the back-up files.</ListItem>
				<ListItem>Start and, if required, configure the Infor Solution License Manager (SLM).</ListItem>
				<ListItem><List><ListIntro>Start the printer daemon and the shared memory:</ListIntro>
						<ListItem>On a UNIX platform, run the rc.start shell script</ListItem>
						<ListItem>On a Windows platform use the Infor ES Service Manager</ListItem>
					</List>
				</ListItem>
				<ListItem>Start the BSE environment.</ListItem>
			</ProcedureList>
			<Paragraph class="Default">In addition, you might also be required to recover your operating system and database. Refer to your operating system and database manuals for the appropriate procedures.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Important information, such as database parameters, login accounts, Kernel parameters, and so on, must be logged in a safe place, for example, in a system or database administrator’s log book, so that you can reuse this information during a recovery.</Paragraph>
			</Note>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
