Restore the Lucent CM system

Restore the Lucent CM system
		GO

Purpose

This topic describes the steps to restore the Lucent CM system from backup file. The restore operation is performed using a script.

Script name and directory

Script directory	Script name
/opt/lps/current/bin/	restore_lcm_system.sh

Restore errors and warnings

Before restoring the system from a backup file, the restore script verifies if requirements are met and provides errors and warnings. If the restore script detects an error, the restore can not continue and the errors must be corrected.

The restore scripts validates the following on the current system and in the backup file:

Software version numbers are the same.

VIP host names are the same.

Internal and external host names are the same.

All database segments in the backup file are present on the existing system.

The script verifies if both nodes are available and reachable when you restore a two-node Lucent CM system.

Besides errors, the restore script also can produces warnings. The warning can be ignored if needed.

The script provides warnings for the following situations:

System names differ.

A node exists in the backup file that does not exist in the current system.

A nodes exists in the current system that does not exist in the backup file.

The current system contains a database segment that does not exist in the backup file.

The information is contained in the system.properties file that is part of the backup file.

Restore call server data

When you restore the Lucent CM system, data must also be restored at the Lucent FS 3000 and FS 5000 call servers. This prevent mismatches between data at the Lucent CM system and data at the call server.

For more information about restore procedures:

For the Lucent FS 5000, refer to the Lucent Control Platform Compact Model, Lucent SM and Lucent FS 5000 Operations, Administration, Maintenance and Provisioning..

For the Lucent FS 3000, refer to the Broadworks Maintenance Guide.

Important! To successfully restore a two-node Lucent CM system, both nodes must be available and reachable. Server status must be “up”

Restore the Lucent CM system

Perform the following steps to restore the Lucent CM system from a backup file:

Change directory to /opt/lps/current/bin/.

Start the restore script. Enter:

restore_lcm_system.sh [-f <backup file>][-o][-w <workspace dir>]

Option	Option descriptions
`-f`	Fully qualified path to the backup file.
`-o`	Overwrite existing work directory without prompting.
`-w`	Temporary directory to use as workspace. Default workspace directory is /tmp/restore/

If you did not enter the -o option, the script prompts you if the existing workspace directory must be deleted.

Select y to delete the existing backup file or n to add the new backup file next to the old backup file.

Result: The restore script starts.

The restore script validates that the following prerequisites are met

If ...

Then ...

the scripts generates errors,

Correct the errors

Restart the script.

the scripts generates warnings,

Verify if the warnings can be ignored

Correct the warnings or continue.

CAUTION

Service outage

A restore results in a complete outage of the Lucent CM system.

If possible, perform restore operations in low traffic hours.

Enter Yes to confirm the start of the restore operation.

When prompted, the root passwords for Lucent CM nodes in the system must be entered.

Result: The restore program starts and performs the following tasks:

Stop all Lucent CM processes.

Start a single database server for each database segment.

Restore the data for each database segment.

Update the system configuration files to match the new data.

Restart the Lucent CM system processes.

End of steps

		GO
© Lucent Technologies