RDR UM A00 4 en

Remote Data Replicator (RDR)
User Manual
Version 4
417006-2705-0H3-A00
Remote Data Replicator (RDR) User Manual V4 Catalog No: X36472 August 2007 1 Edition
st
Copyright by ECI Telecom, 2005-2007. All rights reserved worldwide. This is a legal agreement between you, the end-user, and ECI Telecom Ltd. (ECI Telecom). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM. The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent, and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or disk may be published, reproduced, or disclosed to third parties, in whole or in part, without the express prior written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden. ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which may be affected in any way by the use and/or dissemination thereof. Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for informational purposes only and are not warranties of product performance or otherwise, either express or implied. ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty offered by ECI Telecom. The documentation and/or disk is provided AS IS and may contain flaws, omissions, or typesetting errors. No warranty is granted nor liability assumed in relation thereto, unless specifically undertaken in ECI Telecom's sales contract or order confirmation. Information contained in the documentation and in the disk is periodically updated, and changes will be incorporated in subsequent editions. If you have encountered an error, please notify ECI Telecom. All specifications are subject to change without prior notice. The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by all relevant copyright, patent, and other applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any other copyrighted material (for example, a book or musical recording). Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM. All trademarks mentioned herein are the property of their respective holders. ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in connection with this documentation and/or disk, the information contained therein, its use, or otherwise. Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage which may arise in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if advised of the possibility of such damages.
RDR User Manual
Contents
Contents
About This Manual .................................................................... ix
Overview .............................................................................................................ix Intended Audience ..............................................................................................ix Document Organization........................................................................................x Document Conventions .......................................................................................xi Related Documentation.......................................................................................xi Obtaining Technical Documentation .................................................................. xii Technical Assistance.......................................................................................... xii
Introduction.............................................................................. 1-1
Overview .......................................................................................................... 1-1 What is RDR?................................................................................................... 1-2 Functional Description...................................................................................... 1-2 Components ............................................................................................... 1-2 Instances .................................................................................................... 1-4 Replicas ...................................................................................................... 1-5 LightSoft Instance Backup Levels............................................................... 1-6 Differences and New Features......................................................................... 1-8 Typical RDR Configurations ............................................................................. 1-9 Backup Deployment.................................................................................... 1-9 Primary and Mirror Configurations ............................................................ 1-10 EMS-SYNCOM or EMS-XDM Configurations........................................... 1-14 LightSoft Instance Configurations ............................................................. 1-14 Activation Overview........................................................................................ 1-15 Backup Session ........................................................................................ 1-15 Recovery from Backup to Mirror ............................................................... 1-16 Reverse Update to the Primary Site ......................................................... 1-17 Alarms Notification.................................................................................... 1-17 RDR Activity Monitor................................................................................. 1-18
Preliminary Requirements ...................................................... 2-1

Overview .......................................................................................................... 2-1 Application Requirements ................................................................................ 2-1 Preliminary Requirements .......................................................................... 2-2 Preconfigured Values ................................................................................. 2-2 Minimum Backup Server Disk Capacity...................................................... 2-3
432006-2425-013-A00
ECI Telecom Ltd. Proprietary
Contents
RDR User Manual
RDR Menus .............................................................................. 3-1

Overview .......................................................................................................... 3-1 RDR Instances List........................................................................................... 3-2 RDR Common Actions Menu ........................................................................... 3-3 RDR Instance Actions Menu ............................................................................ 3-4 RDR Instance Configuration Options Menu ..................................................... 3-5 Advance RDR Configuration Options Menu..................................................... 3-7
RDR Configuration .................................................................. 4-1

Overview .......................................................................................................... 4-1 Configuration Workflow .................................................................................... 4-1 Starting the RDR .............................................................................................. 4-2 Selecting the Command Center Mode........................................................ 4-3 Instance Discovery ........................................................................................... 4-3 Performing Instance Discovery ................................................................... 4-4 Instance Configuration ..................................................................................... 4-7 Configuring Instances ................................................................................. 4-7 Configuring LightSoft Levels for NMS Instances ........................................ 4-9 Configuring Directories for EMS or ENM Instances.................................. 4-11 Viewing Instance Details........................................................................... 4-14 Modifying Instance Configuration ............................................................. 4-15 Removing the Configuration of an Instance.............................................. 4-16 Removing all Instances Associated with a Primary Component............... 4-17 Resetting Primary Host SSH Keys ........................................................... 4-19 Alarms Configuration...................................................................................... 4-20 RDR Command Center Diag Mode................................................................ 4-23
Creating and Scheduling Backups ........................................ 5-1

Overview .......................................................................................................... 5-1 Activating an Unscheduled Backup.................................................................. 5-1 Activating an Unscheduled Archive Backup..................................................... 5-3 Assigning and Removing a Shadow Backup Server ........................................ 5-4 Scheduling Backups......................................................................................... 5-6 Backup Schedules ...................................................................................... 5-9 Viewing Crontab Entries................................................................................. 5-13 Log Files......................................................................................................... 5-13
Recovering to a Mirror Component ....................................... 6-1

Overview .......................................................................................................... 6-1 Restoring to the Mirror Component .................................................................. 6-2 Setting the Mirror Component .......................................................................... 6-6 Defining Application Autostart ........................................................................ 6-10
ii
432006-2425-013-A00
RDR User Manual
Contents
Restarting the Primary Instance after Recovery (Reverse Update) ..................................................................... 7-1
Overview .......................................................................................................... 7-1 Performing Reverse Update............................................................................. 7-2 Recognizing the Primary Component............................................................... 7-3
Suspending or Resuming RDR Operation ........................... A-1 Defining an Alternate Cache Location.................................. B-1 RDR Commands ..................................................................... C-1 Error Messages....................................................................... D-1 Glossary ...................................................................................E-1 Index .......................................................................................... I-1
432006-2425-013-A00
iii
Contents
RDR User Manual
iv
432006-2425-013-A00
RDR User Manual
Contents
List of Figures
Figure 1-1: Sequence of LightSoft instance backups over time .................................... 1-6 Figure 1-2: Simple configuration example 1:1 .......................................................... 1-11 Figure 1-3: Simple configuration example 2:2 .......................................................... 1-12 Figure 1-4: RDR complex configuration N:2 with independent backup server ......... 1-13 Figure 1-5: General replication scheme....................................................................... 1-16 Figure 1-6: RDR Monitor example ............................................................................... 1-18 Figure 1-7 - Activity Monitor Activation ........................................................................ 1-19 Figure 3-1: RDR Instances List ...................................................................................... 3-2 Figure 3-2: RDR Common Actions Menu ...................................................................... 3-3 Figure 3-3: RDR Instance Actions Menu ....................................................................... 3-4 Figure 3-4: RDR Instance Configuration Options .......................................................... 3-6 Figure 3-5: Advance RDR Configuration Options for ENM/EMS Instance .................... 3-7 Figure 3-6: Advance RDR Configuration Options for NMS Instance ............................. 3-7 Figure 4-1: RDR welcome window................................................................................. 4-2 Figure 4-2: RDR Instances............................................................................................. 4-4 Figure 4-3: Possible RDR modes of Activity .................................................................. 4-4 Figure 4-4: RDR Discovery Menu .................................................................................. 4-5 Figure 4-5: Automatic Instance Discovery ..................................................................... 4-5 Figure 4-6: Manual Instance Discovery ......................................................................... 4-6 Figure 4-7 Confirming Instance Configuration ............................................................... 4-7 Figure 4-8: Defining Backup Directory during Instance Configuration........................... 4-8 Figure 4-9: Defining Backup Directory during Instance Configuration........................... 4-8 Figure 4-10: Basic Instance Configuration Completed .................................................. 4-9 Figure 4-11: RDR Instance Actions Menu ................................................................... 4-10 Figure 4-12: RDR Instance Configuration Options Menu ............................................ 4-10 Figure 4-13: Advanced RDR Configuration Options Menu.......................................... 4-10 Figure 4-14: Assign NMS Level Parameters................................................................ 4-11 Figure 4-15: Pattern File Configuration Menu.............................................................. 4-12 Figure 4-16: Restore Pattern File to Default ................................................................ 4-12 Figure 4-17: Add to Pattern File ................................................................................... 4-13 Figure 4-18: View Status of an Instance ...................................................................... 4-14 Figure 4-19: RDR Instance Configuration Options ...................................................... 4-15 Figure 4-20: Instance Configuration............................................................................. 4-15 Figure 4-21: RDR Instance Configuration Options ...................................................... 4-16 Figure 4-22: Remove configuration of an instance ...................................................... 4-16
432006-2425-013-A00
Contents
RDR User Manual
Figure 4-23: RDR Common Actions Menu .................................................................. 4-17 Figure 4-24: RDR Backup Server Special Configuration Options ............................... 4-17 Figure 4-25: Lists of Primary Hosts.............................................................................. 4-18 Figure 4-26: Warning about Removing Configuration of an Instance.......................... 4-18 Figure 4-27: RDR Common Actions Menu .................................................................. 4-19 Figure 4-28: RDR Backup Server Special Configuration Options Menu ..................... 4-19 Figure 4-29: Warning about resetting SSH .................................................................. 4-20 Figure 4-30: RDR Instance Configuration Options Menu ............................................ 4-21 Figure 4-31: RDR Alarm Notification Editor ................................................................. 4-21 Figure 4-32: Configure a host to receive alarms.......................................................... 4-22 Figure 4-33: Stop a host from receiving alarms ........................................................... 4-22 Figure 4-34: Remove all configured entries in the alarm list........................................ 4-23 Figure 4-35: RDR Common Actions Menu .................................................................. 4-23 Figure 4-36: Diag Mode On.......................................................................................... 4-24 Figure 5-1: Start Backup Session .................................................................................. 5-2 Figure 5-2: Start Archive Backup ................................................................................... 5-3 Figure 5-3: Assign Shadow Backup............................................................................... 5-5 Figure 5-4: RDR Interactive Scheduler utility................................................................. 5-6 Figure 5-5: RDR Scheduler Menu.................................................................................. 5-7 Figure 5-6: Crontab Entries Listed ................................................................................. 5-7 Figure 5-7: Adding an entry to Crontab.......................................................................... 5-8 Figure 5-8: RDR Scheduler menu.................................................................................. 5-9 Figure 5-9: Scheduling a regular backup at constant interval...................................... 5-10 Figure 5-10: Scheduling a regular backup at a specific time ....................................... 5-11 Figure 5-11: Scheduling an archive backup at constant interval ................................. 5-11 Figure 5-12: Scheduling an archive backup at a specific time..................................... 5-12 Figure 5-13: Viewing the Crontab entries .................................................................... 5-13
vi
432006-2425-013-A00
RDR User Manual
Contents
List of Tables
Table 3-1: Common Actions Menu options.................................................................... 3-3 Table 3-2: RDR Instance Actions Menu options ............................................................ 3-5 Table 3-3: RDR Instance Configuration Options Menu options..................................... 3-6 Table 3-4: Advance RDR Configuration Options Menu details...................................... 3-8 Table 5-1: RDR scheduler menu.................................................................................... 5-9
417006-2705-0H3-A00
vii
Contents
RDR User Manual
viii
432006-2425-013-A00
About This Manual

Overview
The Remote Data Replicator (RDR) application provides redundancy features for the network management applications of ECI Telecom's Transport Networking Division EMS-XDM, EMS-SYNCOM, and LightSoft. This manual describes the requirements for successful RDR installation, and detailed procedures for configuration and activation. This manual is intended for use with RDR V4.
Intended Audience
This manual is intended for telecommunications network personnel backing up management system databases, and implementing effective recovery from those backups as required.
432006-2425-013-A00
ix
About this Manual
RDR User Manual
Document Organization
The manual includes the following chapters:
Chapter 1, Introduction, provides a general and functional description of the RDR, its topological elements, new features, and typical configurations. Chapter 2, Preliminary Requirements, describes the preconditions for successful installation. Chapter 3, RDR Menus, describes some principal menus in configuration and activation procedures. Chapter 4, RDR Configuration, provides an overview of the component configuration workflow, and how to configure the components to use RDR for replicating and sending alarm messages. Chapter 5, Creating and Scheduling Backups, describes how to create regular backups or static archives, schedule automatic backups, and view the scheduled (Crontab) entries. Chapter 6, Recovering to a Mirror Component, describes how to start a mirror station from any backed-up replica in the event of a primary station failure. Chapter 7, Restarting the Primary Instance After Recovery (Reverse Update), describes how to return the primary component to normal operation. Appendix A, Suspending or Resuming RDR Operation, describes how to suspend and resume RDR activities when needed, such as for maintenance operations or a software upgrade. Appendix B, Defining An Alternate Cache Location, describes how to create and define a new cache directory and share the new directory with the zone. Appendix C, RDR Commands, describes the UNIX scripts for specialized RDR operations. For expert reference use only. Appendix D, Error Messages. Appendix E, Glossary. Index.

432006-2425-013-A00
RDR User Manual
About this Manual
Document Conventions
The following conventions are used in this manual:
Convention Indicates Example
Bold
Names of windows, dialog In the Alarms menu boxes, menus, buttons and most other GUI elements; commands; user-typed information Command line text, programming code A selection from a menu or leading to another command Notes, cautions, warnings Enter RDR. Select Update > View Objects. See examples below
Courier Menu > Option Boxes around text
NOTE: Text set off in this manner presents clarifying information, specific instructions, commentary, sidelights, or interesting points of information.
CAUTION: Text set off in this manner indicates that failure to

follow directions could result in damage to equipment or loss of information.
WARNING: Text set off in this manner indicates that failure to follow directions could result in bodily harm or loss of life.
Related Documentation
The following documents may be of assistance in RDR installation, configuration, and activation processes:

EMS-XDM User Manual EMS-SYNCOM User Manual eNM LightSoft and LightSoft User Manuals
432006-2425-013-A00
xi
About this Manual
RDR User Manual
Obtaining Technical Documentation

To obtain technical documentation related to RDR or any other ECI Telecom product, please contact: ECI Telecom Ltd. Transport Networking Division Documentation Department 30 Hasivim St. Petach Tikva 49130 Israel Fax: 972-3-9268022 email: on.documentation@ecitele.com
Technical Assistance
The configuration and operation of RDR are highly specialized processes. If you have questions or concerns about your network design or operation, the services of ECI Telecoms design engineers and highly trained field service personnel are available to you at any time. If you are interested in obtaining design assistance or a network installation plan from ECI Telecom Customer Support team, contact your ECI Telecom sales representative. With any support related issues, technical or logistic, please contact the ECI Telecom Customer Support center at your location. If you are not familiar with that location, you can contact our central customer support center action line at:
Telephone Telefax Email + 972-3-9266000 + 972-3-9266370 on.support@ecitele.com
ECI's XDM and BroadGate product lines are certified to comply with MEF9 and MEF14 standards.
xii
432006-2425-013-A00
1
Introduction
Overview
This chapter provides a general description of the RDR and functional descriptions of its topological elements. It also includes typical configurations and an overview of the RDR V4 new features. NOTE: ems, enm, and nms are used to identify RDR instances,
while EMS-XDM, EMS-SYNCOM, and LightSoft are used to identify the corresponding applications. For more information, see Instances, page 1-4. A configuration of an instance on a specific component is referred to as a component instance.
432006-2425-013-A00
1-1
Introduction
RDR User Manual
What is RDR?
RDR is a tool that provides redundancy features for ECI Telecom Transport Networking Divisions management applications, including EMS-SYNCOM, EMS-XDM, and LightSoft server station databases, on the same or different stations. RDR is flexible and can be configured in a wide variety of topologies. It provides optimal protection consistent with geographic infrastructure distribution, security needs, and available budget for standby mirror hardware. RDR can be used as a solution for:

Data protection only (no redundancy, regular backup) Disk protection (no redundant hosts but spare disks are used) Host protection (primary and mirror sites are connected via LAN) Site protection (primary and mirror sites are connected via a long distance link)
Functional Description
RDR performs remote data backup (replication) between primary stations (stations currently managing the network) and the backup server (the station storing backup data). The backup data can subsequently be restored (synchronized) on a mirror station (remote redundant station replacing failed or deactivated primary components).
Components
RDR components provide the infrastructure for RDR backup and synchronization functionality on servers. There are three types of components:
Primary: Contains one or more of the management applications that the RDR backs up. Backup: Administers the storage of backups (replicas) on backup stations. Mirror: Restores application databases from the backup station to a mirror station, enabling the network to be managed from the mirror station in the event of a primary station failure.

RDR components are referred to as belonging to sites primary components to a primary site, mirror components to a mirror site, and the backup component (when not sharing a mirror component's station) to a backup site.
1-2 ECI Telecom Ltd. Proprietary 432006-2425-013-A00
RDR User Manual
Introduction
Primary components
The primary site can contain a number of primary components, each residing on a station and each maintaining any combination of instances (see Instances, page 1-4). Each primary component may be in a Single-Zone (Legacy) or Multi-Zone configuration. RDR manages an independent backup session for every primary component instance according to its own preset configuration. Each instance can be replicated on a different backup server. The number of supported primary components and instances is limited only by the overall backup server storage capacity - see Minimum Backup Server Disk Capacity, page 2-3. A primary site contains one or more of the following management applications:

EMS-SYNCOM EMS-XDM Single LightSoft server LightSoft server main component (part of a cluster configuration)
Backup components
The backup component resides either on a dedicated station or shares a station with one of the mirror components. The backup server performs the following actions:

Initiates and manages regular and archive backup sessions Stores RDR instances backup data sets (replicas) Manages shadow backups
RDR also supports multiple backup components, allowing each instance to be configured to use different RDR backup servers. Each regular backup transfers files to a replica on the backup server. The backup server stores a set number of last successful replicas. The number of stored replicas per instance is configurable (see Replicas, page 1-5), and only limited by available disk capacity (see Minimum Backup Server Disk Capacity, page 2-3). The Backup Server usually invokes backup sessions according to a predefined schedule using the UNIX Cron utility.
432006-2425-013-A00
1-3
Introduction
RDR User Manual
Mirror components
Mirror components are sets of redundant hosts used to restore and run instances in the event of primary component failure. Mirror components are generally assigned their own servers. (Depending on user requirements, the backup component may share a server with a mirror component.) Mirror components are normally in standby mode, meaning instances installed on the component are not active but ready for a command to launch the recovery process. The operator can start a mirror station from any backed-up replica. The system topology may include one or several mirror components, according to the required redundancy. When primary stations are geographically separated with negligible chance of simultaneous failure, multiple primary components may be safely and economically serviced by a single mirror component (N:1 configuration). In more sensitive environments, multiple mirror components can provide additional assurance. For example, each primary server can be paired with its own mirror component (1:1 configuration). For more information, see Primary and Mirror Configurations, page 1-10.
Instances
An RDR instance is an occurrence of a supported application that is running on the primary component (such as EMS-SYNCOM, EMS-XDM, and/or LightSoft, in any combination). RDR instances are not the actual applications, but the data relating to the applications that need to be backed up (for example, the database and configuration). Each instance is identified by its own unique name. The instance name has the following structure:
tag@hostname[:zone_prefix]
tag: Identifies the application:

enm: EMS-SYNCOM application ems: EMS-XDM application nms: LightSoft Server application
1-4
432006-2425-013-A00
RDR User Manual
Introduction
hostname: The host name (primary or mirror components) where the instance is located. zone_prefix: The zone identifier. This is only used for Multi-Zone configuration. It is the first part of the standard zone name in ECI installations (zn). In the case of a Single-Zone (Legacy) configuration, the zone_prefix is omitted.
EXAMPLE: The RDR instance name for EMS-XDM on host foo in zone z3-foo is: ems@foo:z3. The RDR modular structure provides separate backup/recovery mechanisms for each supported instance. Each instance on each component can be configured according to user requirements, for example, to have different backup schedules or a different number of backups per cycle. NOTE: When the LightSoft server involves a cluster configuration (main server and one or more plain servers), only the main server that contains the database is installed with RDR and is relevant for backup purposes.
Replicas
RDR replicas are backup data sets of primary component instances (databases). The replicas are stored in a special folder on the backup server for each primary component instance in a user-configurable path. Two to five full regular replicas can be configured for each primary component instance (ems, enm, or nms), with the newest backup overwriting the currently oldest backup on a cyclical basis. An archive replica, which is not automatically overwritten, can also be created for each primary component instance. An archive replica is a static backup from a specific time used to freeze the system state on the backup server. Recovery can be performed based on either any cyclical replica or the archive replica. The number of replicas that can be stored is only limited by the available disk capacity (see Minimum Backup Server Disk Capacity, page 2-3). For each primary component instance, backups can be scheduled to be performed automatically at constant intervals (set time span between backups) or non-constant intervals (specific time on selected days of the week or month).
432006-2425-013-A00
1-5
Introduction
RDR User Manual
Replicas at constant intervals can be set to occur at very short intervals, as frequently as every 10 minutes, according to user requirements. (The selected interval cannot be shorter than the time it takes to create a backup. Since most nms instance backups are based on incremental changes, this provides great flexibility see LightSoft Instance Backup Levels, page 1-6.) To simplify recovery, it is recommended to schedule all primary component instances with the same backup intervals. Offsets can be used to stagger individual starting times (setting them a number of minutes apart), to balance the load and avoid network congestion.
LightSoft Instance Backup Levels

Backups of LightSoft instances (nms) can be configured at much shorter intervals. This is because most nms backups are based on incremental changes rather than full backups, so requiring far less processing time per backup and less delay before each next backup can start. The nms replication scheme defines three nested backup levels:
Level 0 (L0) full regular replicas (up to five can be defined), similar to ems or enm regular replicas Level 1 (L1) incremental backups (up to three can be defined), recording changes since the immediately preceding L0 full backup was performed Level 2 (L2) incremental backups (up to five can be defined), recording changes since the immediately preceding L1 backup was performed
Like ems or enm recovery, nms recovery is based on a choice of up to five full cyclical backups (L0 backups). But the L0 backup is also continuously updated with latest associated L1 and L2 incremental changes. The levels are configured for each instance during the instance configuration procedure (see Configuring LightSoft Levels for NMS, page 4-9). The following diagram shows an example of a sequence of backups performed over time for a NMS instance.
L0 1 L0 11
L1 2
L1 5
L1 8
L2 3
L2 4
L2 6
L2 7
L2 9
L2 10
Figure 1-1: Sequence of LightSoft instance backups over time
1-6
432006-2425-013-A00
RDR User Manual
Introduction
Levels configuration for this example is set to L1 = 3 and L2 = 2. The subscripts beside the entries denote a backup's point in time. For example, the top leftmost L0 backup was performed at Time1. The backups are spaced according to user-specified intervals.
At Time1 a full backup is created (L01). Reconstituting the database between Time1 and Time2 requires restoring from the full backup L01. At Time2 an intermediate backup of differences between Time1 and Time2 is created (L12). Reconstituting the database between Time2 and Time3 requires restoring the L01 full backup, supplemented by the L12 difference. At Time3, an intermediate backup of differences between Time2 and Time3 is created (L23). Reconstituting the database between Time3 and Time4 requires restoring the L01 full backup, supplemented by both the L12 difference plus the L23 difference. At Time4, an intermediate backup of differences between Time2 and Time4 is created (L24). (Notice that this spans two intervals.) Reconstituting the database between Time3 and Time4 requires restoring the L01 full backup, supplemented by the L12 difference plus the L24 difference. (The previous L23 difference is no longer relevant.) At Time5, an intermediate backup of differences between Time1 and Time5 is created (L15). (Notice that this spans four intervals.) Reconstituting the database between Time4 and Time5 requires restoring the L01 full backup, supplemented by only the L15 difference. (The previous L24 difference is no longer relevant.) At Time6 through Time10, similar incremental backups are performed, with recovery requiring a combination of the L0 full backup and relevant intermediate L1 and L2 backups. At Time11, a new full backup is created (L011), starting a new cycle.
Any combination of L1 and L2 intermediate backups may be defined. The greater their number (maximum L1 = 3 and L2 = 5), and the shorter the selected interval (as short as 10 minutes between backups depending on database size), the more up to date the latest backup will be.
432006-2425-013-A00
1-7
Introduction
RDR User Manual
Differences and New Features

New features introduced in RDR V4 include:

Full transparent support for Solaris 10 Multi-Zone environment. All backup activities are initiated and scheduled by the backup server instead of the primary components. Primary Instances Discovery. Native RDM database backup method is used for EMS-XDM V6.2 and later, as well as old (legacy) backup method for previous versions. For legacy EMS-XDM backups, the database consistency check is applied to avoid corrupted database backups replication. Failed replications are repeated to reduce the influence of network problems. SSH-based authentication and transport for remote operation. Application source and target versions are compared in restore operations. Block restore operations when applications are still running. Monthly backup scheduling option. Improved backup activity logging. On-line Help. Shadow (cascade) backups integrated support. Backup activity monitor.

Discontinued features are as follows:

Local backups are no longer supported. RSH-based authentication and transport for remote operation. Solaris 8 based instances. No option to send alarm notifications to Go-Global or Exceed sessions.
1-8
432006-2425-013-A00
RDR User Manual
Introduction
Typical RDR Configurations

The following sections describe a few of the possible RDR configurations. RDR flexibly enables a wide variety of topologies according to the required protection level, geographic distribution of infrastructure, and equipment budget.
Backup Deployment
Any number of backup components may be deployed, either on their own dedicated servers or sharing servers with mirror components. The backup component can be installed in the following ways:
On the same server station as a mirror component. The shared station is installed with the operating system and infrastructure of a regular network management station, as well as the RDR application. OR
On a dedicated backup server. The server is configured with only two partitions one of 2 GB for the operating system and RDR, and the remaining large partition available for backup data. Management application databases are not installed on this server.
In a 1:N implementation, the mirror site hardware must be at least as large as the largest primary site.
Shadow backup server

A shadow backup maintains a copy of the replicas contained in the RDR backup server. Its purpose is to grant a higher redundancy to the RDR backup system. One shadow backup server can support multiple backup servers. Alternatively, one backup server can save different instances on different shadow servers. When the shadow backup is configured for the instance, immediately upon the successful end of the backup session the backup server performs an additional replication of the instance replica to the assigned shadow server.
432006-2425-013-A00
1-9
Introduction
RDR User Manual
A shadow backup is configured per RDR instance; therefore you can assign a separate shadow server for each instance. NOTE: The replica of the instance on the shadow server is
automatically located in the same location as on the backup server. This allows the recovery session to also restore the instance from the shadow server.
Primary and Mirror Configurations

Primary and mirror components can be matched according to the required protection level and equipment budget. The mirror site can provide redundancy for any number or combination of primary components. The notation N:N denotes the number of primary components to mirror components. For example, 1:1 denotes one primary component serviced by one mirror component, and N:1 denotes multiple primary components serviced by one mirror component. Regardless of the primary to mirror configuration, any number of backup components may be deployed, either on their own servers or sharing a server with a mirror component. In all cases, links must be provided from the backup/mirror components to all other integrated components.
1-10
432006-2425-013-A00
RDR User Manual
Introduction
1:1 configuration
The following shows a 1:1 configuration with a dedicated mirror host for each primary host.
Figure 1-2: Simple configuration example 1:1
In this example, the backup and mirror components share a common host.
432006-2425-013-A00
1-11
Introduction
RDR User Manual
2:2 configuration
The following shows a 2:2 configuration where two primary components are serviced by two mirror components. For example, primary host 1 may run LightSoft, while primary host 2 may run EMS-XDM as a slave manager.
Figure 1-3: Simple configuration example 2:2
NOTE: If required, the primary component 2 application can be recovered on the mirror component 1, thereby merging the two applications on mirror component 1. In this example, the backup component and one mirror component share a common host, while the second mirror component resides on its own host.
1-12
432006-2425-013-A00
RDR User Manual
Introduction
N:2 configuration
The following figure shows an N:2 configuration where N primary components are serviced by two mirror components, saving on mirror hardware. The mirror site can provide redundancy for any number or combination of primary components. An individual mirror component can restore multiple primary component instances, only limited by its power, memory, and disk capacity.
Figure 1-4: RDR complex configuration N:2 with independent backup server
In this example, the backup server is deployed on a dedicated host. It should have adequate disk space for the large number of replicas from all the primary components.
432006-2425-013-A00
1-13
Introduction
RDR User Manual
EMS-SYNCOM or EMS-XDM Configurations

The primary and backup/mirror EMS sites will usually each have their own set of gateway NEs (which may be shared by both sites), although this is not required. X-terminals may be connected to both the primary and backup/mirror sites so that users can switch from one to the other, enabling seamless network management.
LightSoft Instance Configurations

When a LightSoft server is installed in one workstation, a simple 1:1 backup configuration is supported for the main server only. For larger networks, where the LightSoft server is distributed amongst several workstations, the following two schemes are supported:
1:N at the workstation level a single additional workstation may be deployed to act as backup for any server station. This approach is hardware efficient but cannot support full site redundancy. 1:1 at the LightSoft server level full hardware duplication is required. For example, for four server machines, four additional machines are required.
Some networks may have several LightSoft installations. In that case, a 1:N LightSoft backup scheme may be suitable. The backup site should include as many workstations (LightSoft server + EMSs) as the largest LightSoft site being backed up. LightSoft client users may switch from one LightSoft server site to another, enabling seamless network management.
1-14
432006-2425-013-A00
RDR User Manual
Introduction
Activation Overview
Backup Session
The RDR backup session is performed in several steps: 1. The backup server checks connectivity with the primary component. 2. The backup server initiates backup of the primary instance to the local cache on the primary component. 3. The primary component performs a data integrity check in the local cache. 4. The backup server replicates the data from the local cache to the backup folder on the backup server. NOTE: A local cache is used to eliminate a communication
link bottleneck. The local cache location is configurable for every instance on the primary component, so that the RDR can use available disk space in the most efficient way.
The RDR can be set to automatically invoke backup sessions at prescheduled times. These regular replicas are stored cyclically on the backup component with the oldest replica deleted first. The amount of replicas saved on the backup component is configured during instance configuration. Archive backups, which are replicas that are not overwritten, can also be configured for each instance.
432006-2425-013-A00
1-15
Introduction
RDR User Manual
The general replication scheme is shown in the following figure.
Figure 1-5: General replication scheme
Recovery from Backup to Mirror

When a primary site fails, its mirror site is manually activated and instructed from which replica on the backup component to recover. After completing database synchronization, work carries on as usual. The recovery process involves the following steps: 1. Define the backup server from which to restore. 2. Check backup server connectivity. 3. Set the mirror instance from which to restore. 4. Choose the primary instance to restore. 5. Choose the primary instance replica to restore. 6. Perform the mirror instance restore action from the replica chosen. 7. Set the mirror component with required parameters from the primary component, and set other servers to recognize and communicate with the mirror component in place of the failed primary component. 8. Start the application on the mirror component. For further information, see Restoring to the Mirror Component, page 5-1.
RDR User Manual
Introduction
Reverse Update to the Primary Site

Once the primary site is back in working condition, the user can return to the normal working configuration. (This should be done as soon as possible in order to have the mirror component available to handle any other potential failure.) NOTE: During reverse update, the applications on both the
primary and mirror components must be shut down.
This process involves the following main steps: 1. Perform the reverse update procedure to load the primary component with all changes made to the system during the mirror component activation period while the primary component was down. 2. Set other servers to recognize and communicate with the primary component that has been returned to duty in place of the mirror component, and allow work to resume as usual. 3. Set the mirror site to standby mode.
Alarms Notification
All backup failures generate an error message that is sent by an xmessage utility to the predefined hosts. By default, these messages appear on the primary component console and the RDR Backup Server console. You can also create a list of hosts that also receive these messages. These hosts must run X Server to be able to display the messages. There are two types of configurations:
Private list: A list of hosts to receive the error messages for a specific RDR instance. The list is located in the file: /opt/RDR/config/backup/RDR.displays.<instance_name>
Common list: A list of hosts to receive the messages for all RDR instances. The list is located in the file: /opt/RDR/config/backup/RDR.displays
For more information about how to configure the host lists, see Alarms Configuration, page 4-20.
432006-2425-013-A00
1-17
Introduction
RDR User Manual
RDR Activity Monitor

The RDR Activity Monitor allows you to monitor the RDR backup activity. An example of an RDR Monitor window is shown in the following figure.
Figure 1-6: RDR Monitor example
The Activity Monitor window displays the following information:

Instance name Instance backup status idle (green) or backup (red) Resources consumption (Memory and CPU in %) NOTE: The Activity Monitor is only displayed on the
backup server.
1-18
432006-2425-013-A00
RDR User Manual
Introduction
To access the Activity Monitor window:

From the root menu (Figure 1-7), select RDR RDR (global) Monitor RDR Backup. The Activity Monitor window appears.
Figure 1-7 - Activity Monitor Activation
432006-2425-013-A00
1-19
Introduction
RDR User Manual
1-20
432006-2425-013-A00
2
Preliminary Requirements
Overview
This chapter describes the preconditions for successful installation. It also provides an overview of the workflow for component configuration detailed in subsequent chapters. The RDR package is installed on your system components by ECI personnel. RDR must be installed on every station of the system primary, backup, and mirror. When backup and mirror components are combined on one station, a single RDR installation is required for that station.
Application Requirements
The following products, versions, and configurations are supported:

EMS-SYNCOM V1 EMS-XDM V6.1, V6.2, and V7.1 LightSoft Server V2, V3, and V4
Products without SSH are not supported. NOTE: RDR can also be used in networks based on other EMSs such as BroadGate and LAN. In these cases, the EMSs are not backed up by RDR but rather deployed in parallel in both the primary and backup sites.
432006-2425-013-A00
2-1
RDR User Manual
RDR V4 has the following requirements:
Backup Server:

OS Solaris 10 Min. RAM 512 MB Min. disk capacity 36 GB (min. required disk size derived from the backup as calculated in the formula in Minimum Backup Server Disk Capacity, on page 2-3).
Communications and Bandwidth:s

Appropriate network communication configurations on all components (primary, backup server, and mirror), enabling valid network routing between sites. It is important to calculate the time it will take to transfer a large database over the provided network bandwidth and/or storage device IO rate. Be sure to take into consideration possible simultaneous overlapping backups of a few instances at the same time. In extreme cases 2 Mb is not sufficient.
2 Mbps minimum link bandwidth between components (assuming replicas are scheduled on a staggered basis to avoid overlap). Min. network link bandwidth 2 Mbps.
Mirror Server:
Hardware configuration to match the requested applications and network. Management application versions to be the same as on the primary station. All required application license keys to be present on the station before the mirror component is first activated (preferably before RDR is installed on the station).
Preconfigured Values
Max. number of replicas per instance is five (can be changed according to customer requirements). Number of retries on transfer failure is three (can be changed according to customer requirements). Min. synchronization interval is 10 min.
2-2
432006-2425-013-A00
RDR User Manual
Minimum Backup Server Disk Capacity

The number of replicas that are stored is configurable (see Replicas, page 1-5) and only limited by available disk capacity. The following rule-of-thumb formula can assist in estimating the minimum required backup server free disk size (BDB). BDB = EPDB1 * (ENR1 +1) + EPDB2 * (ENR2 +1) + . . . + EPDBn * (ENRn +1) + .......+ NPDB * (2*NNR +1) Where:

BDB - required minimum backup-server disk capacity for backup EPDB - actual DB size of each primary EMS instance (SYNCOM/XDM) ENR - number of replicas of each primary EMS instance (add 1 for the archive) NPDB - DB size of primary NMS instance (Include all DB volumes) NNR - number of level 0 replicas of primary NMS instance (add 1 for the archive)

For EPDB and NPDB, use the actual instance database sizes or estimate the required capacity as follows:
For each XDM NE, min. capacity per replica:

Estimate 50 MB for a backup initiated from EMS-XDM. Estimate 60 MB for a backup initiated from LightSoft.
For each SYNCOM NE, min. capacity per replica:

Estimate 5 MB for a backup initiated from EMS-SYNCOM or LightSoft.
Be sure to include sufficient additional capacity for network growth. NOTE: Due to partition considerations, effective Legacy installation of Solaris 10 /sdh_home partition size is: 26 GB of a 36 GB disk, 60 GB of 73 GB, 122 GB of 160 GB, and 212 GB of 250 GB.
432006-2425-013-A00
2-3
RDR User Manual
2-4
432006-2425-013-A00
3
RDR Menus
Overview
This chapter describes some principal menus used by the configuration and activation procedures in this manual.
432006-2425-013-A00
3-1
RDR Menus
RDR User Manual
RDR Instances List

You start many RDR tasks from the RDR Instances list. The list displays all the instances, configured and unconfigured, in the system. To view a list of instances in the system:
Do one of the following:

Start the RDR application. From any menu, continue entering q to exit all the menus until the instances are displayed.
Figure 3-1: RDR Instances List
3-2
432006-2425-013-A00
RDR User Manual
RDR Menus
RDR Common Actions Menu

You perform basic RDR tasks, such as scheduling backup sessions, from the Common Actions menu. To view the Common Actions Menu: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions Menu appears. Table 3-1 describes the options in this menu.
Figure 3-2: RDR Common Actions Menu Table 3-1: Common Actions Menu options
Option Explanation Relevant section in this manual
Discover RDR Instances of Primary Components Special RDR Backup Server Configuration Actions Set Global Alarm Notification Options Schedule RDR Backup Sessions Select Command Center Mode Suspend/Resume All Backups Turn On RDR Command Center Diag Mode
Discover instances manually or automatically. Display the RDR Backup Server Special Configuration Options menu which enables you to remove all instances associated with a primary or reset primary host SSH keys. Configure alarms for all instances. Schedule a backup session. To change the mode of the action menus, to backup, primary, or mirror. Suspend/Resume all scheduled backups. Activate diag mode which creates a log file with the following information for problem diagnostics: System information, such as HostInfo, menuconf and networking. All configuration activities.
Instance Discovery Removing all Instances Associated with a Primary and Resetting Primary Host SSH Keys Alarms Configuration Scheduling Backups Selecting the Command Center Mode Suspending or Resuming RDR Operation RDR Command Center Diag Mode
432006-2425-013-A00
3-3
RDR Menus
RDR User Manual
RDR Instance Actions Menu

You perform RDR tasks for a selected instance, such as viewing its status or starting an immediate backup, from the RDR Instance Actions menu. To view the RDR Instance Actions Menu: 1. From the RDR Instances list (see RDR Instances List), select an instance with a configured status. The RDR Instance Actions Menu appears. Table 3-2 describes the options in this menu.
Figure 3-3: RDR Instance Actions Menu
3-4
432006-2425-013-A00
RDR User Manual
RDR Menus
Table 3-2: RDR Instance Actions Menu options Option Show Instance Status Explanation Display status details, including instance identity, current available backup replicas, backup scheduling, and alarms notification settings. Display configuration options, including reconfiguration and advanced settings. Start a backup session. Start a static archive backup. An archive will not be overwritten by the scheduled backups. Suspend automatic RDR functionality of this instance. Relevant section in this manual Viewing Instance Details
Instance Configuration Menu Start Regular Backup Session Start Archive Backup Session Suspend Instance Backups
RDR Instance Configuration Options Scheduling Backups Scheduling Backups
Suspending or Resuming RDR Operation
RDR Instance Configuration Options Menu

You can further configure the instances from the RDR Instance Configuration Options menu. To view the RDR Instance Configuration Options menu: 1. From the RDR Instances list (see RDR Instances List), select an instance with a configured status. The RDR Instance Actions Menu appears. 2. Select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears. Table 3-3 describes the options in this menu.
432006-2425-013-A00
3-5
RDR Menus
RDR User Manual
Figure 3-4: RDR Instance Configuration Options
Table 3-3: RDR Instance Configuration Options Menu options Menu option Re-configure Instance Advanced Configuration Options Description Modify the instance configuration. Display the advanced configuration options including assigning a shadow backup server. Configure rules for automatic scheduled backups. Remove all configuration of an instance. Relevant section in this manual Modifying Instance Configuration Advance RDR Configuration Options Menu
Schedule Instance Backups Unconfigure Instance Show Current Instance Status
Creating and Scheduling Backups Alarms Configuration Removing the Configuration of an Instance
Setup Alarms Notification Configure alarms.
Display status details, including Viewing Instance Details instance identity, current available backup replicas, backup scheduling, and alarms notification settings.
3-6
432006-2425-013-A00
RDR User Manual
RDR Menus
Advance RDR Configuration Options Menu

The advance configuration tasks differ depending on the instance type. Table 3-4 sets out the various options.
Figure 3-5: Advance RDR Configuration Options for ENM/EMS Instance
Figure 3-6: Advance RDR Configuration Options for NMS Instance
432006-2425-013-A00
3-7
RDR Menus
RDR User Manual
Table 3-4: Advance RDR Configuration Options Menu details Menu option Description Relevant section in this manual
Additional Configuration for nms Instance type Additional Configuration for enm/ems Instance type
Displayed for nms instances, it enables you to define the LightSoft Levels. Displayed for enm/ems instances, it enables you to define the pattern file configuration.
Configuring LightSoft Levels for NMS Configuring Directories for EMS or ENM Instance
Assign/Remove Assign or remove a shadow Shadow Backup Server backup server.
Assigning and Removing a Shadow Backup Server
3-8
432006-2425-013-A00
4
RDR Configuration
Overview
This chapter provides an overview of the workflow for configuration components detailed in this and subsequent chapters. It then describes the configuration process to enable replication of instances (ems, enm, and/or nms) of a primary component to a backup component. Each primary component may be in a Single-Zone (Legacy) or a Multi-Zone configuration. In addition, this chapter presents the procedures to configure messages appearing on specified displays of the system infrastructure. It is assumed that the system has already been prepared and installed in the relevant stations.
Configuration Workflow
After installing RDR on all relevant hosts, you need to perform the necessary configuration tasks as explained in the following sections. Configuration steps include: 1. Ensure that the preliminary requirements for installation are fulfilled. RDR is installed on all relevant stations by ECI Telecoms support staff. 2. Perform Instance Discovery. 3. Configure Instances. 4. Schedule the automatic backups. 5. Configure the hosts to receive the alarms.
432006-2425-013-A00
4-1
RDR Configuration
RDR User Manual
6. Perform backups to test the replication process (recommended). 7. Schedule automatic backup sessions. 8. Configure a mirror component. 9. Configure a shadow backup component if required. It is recommended that you test the backup configuration directly after performing the initial configuration. You do this by performing a manual backup, and scheduling automatic backup sessions at set intervals. The mirror component configuration may be postponed until mirror functionality is required.
Starting the RDR

After logging in as root user, you need to start the RDR tool in order to perform the backup related functionalities available. To start the RDR:
Log in as a root user and start the primary RDR component configuration session by entering RDR. The RDR welcome screen appears.
Figure 4-1: RDR welcome window
4-2
432006-2425-013-A00
RDR User Manual
RDR Configuration
Selecting the Command Center Mode

Different modes in the RDR present different action menus, as follows.

Backup Primary Mirror
To change the command center mode: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions Menu appears. 2. From the RDR Common Actions Menu, select 5 Select Command Center Mode. The Possible RDR Modes of Activity menu appears. 3. Select one of the following options:

1 RDR Backup Server Actions 2 Primary Component Actions 3 Mirror Component Actions
The Actions Menu of the selected option appears.
Instance Discovery
Instance discovery is the process of the RDR tool finding the instances (ems, enm, or nms) installed on the primary components. There are two types of discovery:

Automatic: RDR presents the instances found in the etc/hosts file. Manual: You manually enter the instances.
You should run instance discovery in the following cases:

During initial RDR configuration. After adding a new instance to a primary component.
432006-2425-013-A00
4-3
RDR Configuration
RDR User Manual
Performing Instance Discovery

This procedure enables the RDR to discover the instances on the primary components. To perform instance discovery: 1. Log in as a root user. 2. From the CDE root menu, select RDR RDR (global) RDR Command Center. The RDR tool lists the previously discovered instances.
Figure 4-2: RDR Instances
If this is the first time that you are running the RDR, the tool informs you that there are no instances that have been previously discovered. No discovered Primary Components data found on BSComp. The Possible RDR modes of Activity menu is displayed.
Figure 4-3: Possible RDR modes of Activity

RDR User Manual
RDR Configuration
3. Do one of the following:

If there are no discovered instances, enter 1. If there are instances but you want to run the discovery again, enter r and then select 1 from the RDR Common Actions menu.
The RDR Discovery Menu appears with the following options:

Manual RDR instances discovery: Manually enter the host names to be configured as primary components. Discover RDR instances by hosts DB: The RDR application automatically discovers the primary components using the /etc/hosts file.
Figure 4-4: RDR Discovery Menu
4. To automatically discover the instances from the /etc/hosts file, select 2 Discover RDR instances by hosts DB. The discovery process begins. When finished, a list of the hosts and the number of found instances appears. NOTE: Before continuing with configuration, you must quit
and re-enter the RDR application in order for the updates to take effect.
Figure 4-5: Automatic Instance Discovery

432006-2425-013-A00 ECI Telecom Ltd. Proprietary 4-5
RDR Configuration
RDR User Manual
5. To manually enter each primary component, do the following: a. Select 1 Manual RDR instances discovery. NOTE: Enter the host name, not the IP. The hosts entered
must be listed in the etc/hosts file. If you enter a host that is not listed, you receive an error.
b. Continue entering host names of other primary components until completed. c. After completing all of the host names, enter q. The RDR lists the host names to be discovered. d. Press ENTER, to begin the discovery process. The RDR starts the discovery process for the listed hosts, locating all installed instances on each. When finished, a list of the hosts and the number of found instances appears. NOTE: Before continuing with configuration, you must quit
and re-enter the RDR application in order for the updates to take effect.
Figure 4-6: Manual Instance Discovery
4-6
432006-2425-013-A00
RDR User Manual
RDR Configuration
Instance Configuration
After instance discovery, you must configure the instances. Basic configuration consists of the following:

Defining the backup directory. Defining the number of replicas.
Additional configuration includes scheduling the time of the backups and alarms.
Configuring Instances
NOTE: Non-standard configuration, such as alternate cache
location, should be done on the primary component.
To configure the instances: 1. From the RDR Instances list (see RDR Instances List), select an instance with an unconfigured status. A prompt confirming configuration of the instance appears.
Figure 4-7 Confirming Instance Configuration
432006-2425-013-A00
4-7
RDR Configuration
RDR User Manual
2. Enter y. A prompt requesting the backup directory path appears.
Figure 4-8: Defining Backup Directory during Instance Configuration
3. Press ENTER to accept the default or enter a new path and press ENTER. A prompt for the number of regular replicas appears. 4. Enter the number of replicas according to the desired reliability level and existing disk capacity. For more details, see Replicas, page 1-5. The defined instance parameters are listed.
Figure 4-9: Defining Backup Directory during Instance Configuration
5. Select y to accept the parameters. The instance is configured. If you are configuring NMS, continue with the next section, Configuring LightSoft Levels for NMS, page 04-90.
4-8
432006-2425-013-A00
RDR User Manual
RDR Configuration
Figure 4-10: Basic Instance Configuration Completed
Configuring LightSoft Levels for NMS Instances

After configuring the instances, the following setup is required for the NMS instances. For further details, see LightSoft Instance Backup Levels, page 1-6. To configure the Lightsoft levels for an NMS instance: 1. From the RDR Instances list (see RDR Instances List), select the configured NMS Server instance. The Instance Actions Menu appears. NOTE: If it is not marked as configured, perform the steps
presented in Configuring Instances.
432006-2425-013-A00
4-9
RDR Configuration
RDR User Manual
Figure 4-11: RDR Instance Actions Menu
2. Select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears.
Figure 4-12: RDR Instance Configuration Options Menu
3. Select 2 - Advanced Configuration Options. The Advanced RDR Configuration Options menu appears.
Figure 4-13: Advanced RDR Configuration Options Menu
4-10
432006-2425-013-A00
RDR User Manual
RDR Configuration
4. Enter 1 - Additional Configuration for nms Instance type. 5. Enter the number of level 1 and level 2 backups for the backup cycle. For more details about LightSoft levels, see LightSoft Instance Backup Levels, page 1-6.
Figure 4-14: Assign NMS Level Parameters
Configuring Directories for EMS or ENM Instances

In addition to the directory selected to back up in Configuring Instances, additional directories can be added for an EMS or ENM instance. These directories must be located in the home directory of the application user. For example /sdh_home/ems for user ems. NOTE: Only directories can be added to the list, not
individual files.
To define additional directories for backing up an EMS or ENM instance: 1. From the RDR Instances list (see RDR Instances List), select a configured instance and then select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears. 2. Select 2 Advanced Configuration Options. The Advanced RDR Configuration Options menu appears.
432006-2425-013-A00
4-11
RDR Configuration
RDR User Manual
3. Select 1 Additional Configuration for enm/ems Instance type. The Pattern File Configuration menu appears:
Figure 4-15: Pattern File Configuration Menu
4. To view the current pattern file, select 1-Show Current Pattern File. A list appears of the directories to be backed up. 5. To return to the default pattern file, select 3 Reset Pattern File to Default and enter y to confirm. The pattern file is reset to default.
Figure 4-16: Restore Pattern File to Default
4-12
432006-2425-013-A00
RDR User Manual
RDR Configuration
6. To add additional directories, do the following: a. Select 2 - (Re)Create Custom Pattern File. The list of additional directories available for the current instance appears. b. Select the directories, one by one, to add to the backup and enter q when finished.
Figure 4-17: Add to Pattern File
432006-2425-013-A00
4-13
RDR Configuration
RDR User Manual
Viewing Instance Details

You can easily view an instances information, such as current available backup replicas, backup scheduling, and alarms notification settings. To view an instances details:
From the RDR Instances list (see RDR Instances List), select a configured instance and then select 1-Show Instance Status. Details of the instance are displayed.
Figure 4-18: View Status of an Instance
4-14
432006-2425-013-A00
RDR User Manual
RDR Configuration
Modifying Instance Configuration

You can change the details of an instances configuration, such as modifying the number of replicas stored or changing the backup directory. To modify instance configuration: 1. From the RDR Instances list (see RDR Instances List), select a configured instance and then select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu is displayed.
2. Select 1 Re-configure Instance. You are prompted to define the configuration options as explained in Configuring Instances in 4-7.
Figure 4-20: Instance Configuration
432006-2425-013-A00
4-15
RDR Configuration
RDR User Manual
Removing the Configuration of an Instance

You can unconfigure an instance, thereby stopping its scheduled backups and alarm notifications, and deleting its backup folder. To remove the configuration details of an instance: 1. From the RDR Instances list (see RDR Instances List), select a configured instance and then select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu is displayed.
2. Select 5 Unconfigure Instance and enter y to the confirmations. All configurations are removed including the Crontab entries.
Figure 4-22: Remove configuration of an instance
4-16
432006-2425-013-A00
RDR User Manual
RDR Configuration
Removing all Instances Associated with a Primary Component

You can remove all discovery and configuration information associated with a primary component, including the data backups. CAUTION: This action cannot be reversed. All data backups
will be lost.
To remove all instances associated with a primary component: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions menu appears.
Figure 4-23: RDR Common Actions Menu
2. Select 2 Special RDR Backup Server Configuration Actions. The RDR Backup Server Special Configuration Options menu appears.
Figure 4-24: RDR Backup Server Special Configuration Options
432006-2425-013-A00
4-17
RDR Configuration
RDR User Manual
3. Select 1 Remove all Instances associated with a Primary. A list of the primary hosts appears.
Figure 4-25: Lists of Primary Hosts
4. Select the primary host to remove instances. A warning appears reminding you that this action cannot be undone. CAUTION: All information associated with the primary component will be lost.
Figure 4-26: Warning about Removing Configuration of an Instance
5. To remove the instances, enter y. To cancel, enter n.
4-18
432006-2425-013-A00
RDR User Manual
RDR Configuration
Resetting Primary Host SSH Keys

If a primary host has been changed or a new one is added, it is necessary to reset the SSH keys. CAUTION: This should only be performed in very specific
cases.
To reset primary host SSH keys: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions menu appears.
2. Select 2 Special RDR Backup Server Configuration Actions. The RDR Backup Server Special Configuration Options menu appears.
Figure 4-28: RDR Backup Server Special Configuration Options Menu
432006-2425-013-A00
4-19
RDR Configuration
RDR User Manual
3. Select 2 Reset Primary Hosts SSH keys. A warning appears.
Figure 4-29: Warning about resetting SSH
4. To continue, enter y. To cancel, enter n.
Alarms Configuration
In the event of a failure, an alarm is generated and a message is sent. By default, the messages appear on the primary component console and the RDR backup server console. You can create a list of additional hosts to receive the alarms as well. These hosts must run X Server to be able to display the messages. As explained in Alarms Notification (Alarms Notification, page 1-17), there are two ways to configure the hosts that display the messages:
Private list: A list of hosts to receive the messages from a specific RDR instance. The list is located in the file: opt/RDR/config/backup/RDR.displays.<instance_name>
Common list: A list of hosts to receive the messages from all RDR instances. The list is located in the file: /opt/RDR/config/backup/RDR.displays
To define the hosts to receive alarms from all instances: 1. From the RDR Instances list, enter r. The RDR Common Actions menu appears. 2. Select 3 Set Global Alarm Notification Options. The RDR Alarm Notification Editor menu appears. 3. Further actions are the same as defining a host to receive alarms from a specific instance. Continue with Step 3 in the following procedure.
4-20
432006-2425-013-A00
RDR User Manual
RDR Configuration
To define the hosts to receive alarms from a specific instance: 1. Select a configured instance and then select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears. 2. Select 4 Setup Alarms Notification. The RDR Alarm Notification Editor menu appears.
Figure 4-30: RDR Instance Configuration Options Menu
3. To view the list of hosts receiving alarms, Select 3 Show Current Notification List. The hosts receiving alarms for the selected instance are displayed.
Figure 4-31: RDR Alarm Notification Editor
432006-2425-013-A00
4-21
RDR Configuration
RDR User Manual
4. To add a host to receive alarms, Select 1 Add a Display to Notification List and enter the host name to be added. The host is added and will receive any alarm notifications from the selected instance.
Figure 4-32: Configure a host to receive alarms
5. To stop a host from receiving alarms, do the following, a. Select 2 Remove a Display from Notification List. The hosts currently receiving alarms are listed. b. Enter the number of the host name to be removed. c. Enter y to confirm. The host is removed and will not receive any further alarm notifications from this instance.
Figure 4-33: Stop a host from receiving alarms
4-22
432006-2425-013-A00
RDR User Manual
RDR Configuration
6. To remove all configured hosts, allowing only the default hosts to receive the alarms, select 4 Remove All Configured Entries.
Figure 4-34: Remove all configured entries in the alarm list
RDR Command Center Diag Mode

To help diagnose problems, you can activate the command center mode in order to create a log file with the following information:

System information, such as HostInfo, menuconf, and networking. All configuration activities.
To activate the command center diag mode: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions menu appears.
432006-2425-013-A00
4-23
RDR Configuration
RDR User Manual
2. Select 7 Turn ON/OFF RDR Command Center Diag Mode. The menu reappears marked with Diag Mode ON and a new option, 8 Collect Diagnostic Information, is added. 3. To view the information, select 8 Collect Diagnostic Information.
Figure 4-36: Diag Mode On
4-24
432006-2425-013-A00
5
Creating and Scheduling Backups
Overview
This chapter describes how to create and schedule regular backups or static archives, and view Crontab entries. A backup can only be performed after configuring the instance. For further details, see Instance Configuration. NOTE: Large automatic database backups are system affecting. They take time and heavily load the system. You can avoid network congestion by assigning appropriate offsets to each instances replication sessions, so that they do not run at the same time.
Activating an Unscheduled Backup

In addition to scheduled backups, you can perform a backup at any time. For example, an immediate backup is needed:
After first-time configurations. After completing first-time instance configurations, it is strongly suggested to do a full backup for each instance. Before an upgrade.
432006-2425-013-A00
5-1
RDR User Manual
To begin an unscheduled regular backup: NOTE: Full backups may take a long time.
1. From the RDR Instances list (see RDR Instances List), select a configured instance. 2. Select 3 Start Regular Backup Session. The backup session begins. NOTE: Only one backup session can run on a primary
component at a time. If you try to run a backup on a primary component that has another backup session in progress, you receive a Backup Session Overrun error.
Figure 5-1: Start Backup Session
5-2
432006-2425-013-A00
RDR User Manual
Activating an Unscheduled Archive Backup

An archive backup is a static backup of the system at a specific time. Use the archive option in order to freeze the system state at a specific time to ensure additional redundancy. NOTE: Even though archive backups ensure additional
redundancy, take into account that an archived replica uses additional disk space.
To begin an unscheduled archive backup: 1. From the RDR Instances list (see RDR Instances List), select a configured instance. The RDR Instance Actions Menu is displayed. 2. Select 4 Start Archive Backup Session. You are prompted to give a name to the archive backup. 3. Enter a name or accept the default (archive). The archive backup begins.
Figure 5-2: Start Archive Backup
432006-2425-013-A00
5-3
RDR User Manual
Assigning and Removing a Shadow Backup Server

A shadow server stores copies of the replicas from the RDR backup server in order to provide higher redundancy to the RDR backup system. When using a shadow server, the RDR tool must also be installed on the shadow server. When a shadow backup is configured for an instance immediately after a successful backup session, the backup server performs an additional replication of the instance backup folder (replica) to the assigned shadow server. A shadow backup is being configured per RDR instance. Therefore, you can assign a separate shadow server for each instance. NOTE: The replica of the instance on the shadow server must
be located on the same path as on the backup server, in order for a recovery session to be able to restore the instance from the shadow server when needed.
To assign/remove a shadow server: 1. From the RDR Instances list (see RDR Instances List), select a configured instance. The RDR Instance Actions Menu is displayed. 2. To view the details of an already configured shadow backup server, select 6 Show Current Instance Status. The RDR displays the details, including which server has been assigned as a shadow server. 3. Select 2 Advanced Configurations Options> 2 Assign Shadow Backup Server, enter the shadow server name or IP, and enter y to confirm. The server is assigned as a shadow server for the current instance. 4. To remove the shadow server, select 2 Remove Shadow Backup Server and enter y to confirm.
5-4
432006-2425-013-A00
RDR User Manual
Figure 5-3: Assign Shadow Backup
NOTES:
Configure the shadow backup server only after performing an initial manual backup of each instance to test the replication process. This provides the backup data necessary to form a shadow replica. It is recommended to postpone shadow backup configuration until all basic components (including mirror components) have been configured.
432006-2425-013-A00
5-5
RDR User Manual
Scheduling Backups
You can schedule regular or archive backups to be done automatically for each primary component instance at intervals that are constant (set time span between backups) or non-constant (specific time on one or more days of the week or month). Replicas at constant intervals can be set to occur as little as 10 minutes apart. The selected interval cannot be shorter than the backup creation time. LightSoft backups can be scheduled at very short intervals (see LightSoft Instance Backup Levels, page 1-6). To simplify recovery, it is advisable to schedule all primary component instances with the same backup intervals. Offsets can be used to stagger the individual starting times a number of minutes apart according to database size, and therefore balancing the load and avoiding network congestion. NOTE: Scheduling a backup session is a very sensitive operation and must be performed cautiously. Be careful to avoid scheduling conflicts and backup session overlaps.
To define a backup schedule: 1. From the RDR Instances list (see RDR Instances List), select a configured instance. The RDR instance Actions Menu is displayed. 2. Select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears. 3. Select 3 Schedule Instance Backups to start RDR Scheduler utility.
Figure 5-4: RDR Interactive Scheduler utility
5-6
432006-2425-013-A00
RDR User Manual
4. Select an instance. The types of available scheduling methods are listed.
Figure 5-5: RDR Scheduler Menu
5. Select a scheduling method and answer all the questions about scheduling. For more information, see Backup Sched. 6. When you are finished, enter q. The Crontab entries are listed, including the backup sessions you have just scheduled. The pending entry is displayed in regular font with the word {pending} in red. The backups that have already been added to Crontab are in a bold black font.
Figure 5-6: Crontab Entries Listed
432006-2425-013-A00
5-7
RDR User Manual
NOTE: At this point, you have only defined the scheduled

backup. It is listed as a Crontab entry with a pending status. It will not take effect until you append it to the Crontab as explained in the following step. Backup Sessions that have taken effect are applied entries and are displayed in bold.
The following options are available.

Select an entry by its number. Enter a to define another backup entry. Enter q to exit.
7. To append a pending backup session, enter its number. The RDR displays the option that you selected and presents the following options:
1 Apply the entry to the Cron Table: The scheduled backup session will take effect. 2 Remove this temporary entry: Deletes the entry. 3 Show entry details: Displays the entry details.

Figure 5-7: Adding an entry to Crontab
8. To apply the entry, select 1 Apply this entry to Cron Table. The backup is scheduled.
5-8
432006-2425-013-A00
RDR User Manual
Backup Schedules
There are 2 methods of backup session scheduling:
By constant interval: Schedule periodic backups in a constant time interval of minutes or hours. Use offset to distribute backups, preventing overlapping and overloading of different components/instances backups. At specific time of the day: Define a backup session invocation at a specific time of the day. The action can be repeated daily or on specific day(s) of the week or the month.
Table 5-1 describes the options available in the RDR Scheduler menu.
Figure 5-8: RDR Scheduler menu
Table 5-1: RDR scheduler menu Menu option Description
Regular Backup A regular backup scheduled at a constant time interval. by Constant Interval A regular backup is a standard RDR backup session overwriting the oldest existing cyclical replica. (The amount of replicas saved is according to the predefined number of replicas. For details, see Replicas, page 1-5.) (LightSoft Only) A regular backup cycle of an nms instance is automatically performed as either a full (L0) backup or an intermediate (L1 or L2) incremental backup, according to the instance configuration. For details, see LightSoft Instance Backup Levels, page 1-6. Regular Backup - at A regular backup, scheduled at a specific time of a specific Specific Time of the day. Day
432006-2425-013-A00
5-9
RDR User Manual
Menu option
Description
Archive Backup An archive backup, scheduled at a constant time interval. by Constant Interval An archive backup is a special backup session to a named separate replica (default name archive). Special backups always involve full database backup (for LightSoft corresponding to L0). Archive Backup - at An archive backup, scheduled at a specific time of a Specific Time of the specific day. Day
Use the following illustrated examples to guide you in configuring the backup schedule:
Figure 5-9: Scheduling a regular backup at constant interval
5-10
432006-2425-013-A00
RDR User Manual
Figure 5-10: Scheduling a regular backup at a specific time
Figure 5-11: Scheduling an archive backup at constant interval
432006-2425-013-A00
5-11
RDR User Manual
Figure 5-12: Scheduling an archive backup at a specific time
5-12
432006-2425-013-A00
RDR User Manual
Viewing Crontab Entries

This section describes how to view the scheduled Crontab entries of a specified instance. To view Crontab entries: 1. From the RDR Instances list (see RDR Instances List), select a configured instance. The RDR instance Actions Menu is displayed. 2. Select 2 Instance Configuration Menu. The RDR Instance Configuration Options menu appears. 3. Select 3 Schedule Instance Backups to start RDR Scheduler utility. The backups that have already been scheduled are listed.
Figure 5-13: Viewing the Crontab entries
Log Files
The RDR creates log files for each instance. Every time the RDR backs up an instance, it updates the log file with information such as if the backup was successful or failed. The RDR automatically names the log files according to the format, <instance>@<Hostname>_<zone>.log., and stores them in the folder /var/RDR/logs.
432006-2425-013-A00
5-13
RDR User Manual
5-14
432006-2425-013-A00
6
Recovering to a Mirror Component
Overview
This chapter describes how to start a mirror station from any backed-up replica in the event of a primary station failure. Mirror components are normally in standby mode, meaning the instance on the mirror component is installed but not running and ready for a command to launch the recovery process. When a primary component fails, the operator can start a mirror station from any backed-up replica. The mirror site is instructed from which database replica to recover. After database synchronization is completed, work can carry on as usual. When the primary component is ready to be returned to operation, the reverse update procedure is used to load the primary component with changes that occurred to the system when the mirror component was active. This is explained in Recovering to a Mirror Component, page 6-1. The procedure is in two main parts: 1. Restoring to the mirror component, as described on page 6-2. 2. Setting the mirror component with required parameters from the primary component. For details, see Setting the Mirror Component, page 6-6.
432006-2425-013-A00
6-1
RDR User Manual
Before you start:

Ensure that the primary instance is really down. Ensure that the appropriate application is correctly installed and not running on a mirror component. NOTE: Additional manual configuration operations may be required to provide full system functionality on the mirror site. These operations are application specific depending on the recovery case, RDR, and the managed network topology, and are beyond the scope of this manual. For information, refer to the relevant application manuals and engineering procedures.
On a system with LightSoft and EMS(s), first start the LightSoft server and then the EMS(s), so that each EMS is registered on the LightSoft server. Upon successful completion of the recovery session, start the application in the regular way. NOTE: When a mirror station is installed with components that do not have to be mirrored (for example a single mirror station supporting an nms server and ems residing on two stations), be sure to only start the relevant mirror component/s.
Restoring to the Mirror Component

This procedure restores a selected replica to the Mirror Component. After completing this procedure, you still need to configure the mirror component with the primary component parameters, and set the other components to recognize the mirror component instead of the failed primary component (see Setting the Mirror Component, page 6-6).
6-2
432006-2425-013-A00
RDR User Manual
To start a recovery session: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions Menu appears. 2. Select 5 Command Center Mode 3 Mirror Component Actions 1 Start Mirror Recovery Session. The RDR asks for the Backup Server to restore from:
--> Enter Backup Server name or IP [?,q] BSComp
3. Define the backup server to restore from. The RDR checks the connection to the backup server selected and then lists the instances available on the mirror component.
Step 1. Check Backup Server BSComp connectivity... BSComp Mirror Instances on MirrorComp: # 1 2 3 4 5 6 TAG ems enm nms ems enm nms ZONE z6-MirrorComp z6-MirrorComp z6-MirrorComp z3-MirrorComp z2-MirrorComp z3-MirrorComp VERSION 60.63 10.111 02.108 62.38 10.111 03.025 TITLE EMS EMS NMS EMS EMS NMS XDM Syncom Server XDM Syncom Server OK
Select a mirror instance to restore to... [1-8,?,q]--> 1
4. Select a mirror instance to restore to. NOTE: If the instance is running, the following warning appears and you cannot continue with the restore.
Error!!! Cannot perform recover when LightSoft Network Manager Server is running.
The RDR then lists the instances available on the backup server which match the type of mirror instance you have selected in this step.
Available RDR instances [ Backup Server "BSComp" ]: # TAG TITLE PRIMARY PriComp PriComp ZONE z2-PriComp z3-PriComp STATUS
1 ems EMS XDM [configured] 2 ems EMS XDM [configured]
Select a primary instance ( q for exit )... [1-2,?,q] --> 1
5. Select a backed-up instance to restore from. The RDR lists the replicas available of the instance selected.
432006-2425-013-A00 ECI Telecom Ltd. Proprietary 6-3
RDR User Manual
NOTE: The RDR lists both automatic and archive backup

replicas.
Replicas of instance ems@PriComp:z2: 1 Date: 2007/02/06 08:28:22 2 Date: 2007/02/05 16:28:17 3 Date: 2007/01/30 07:41:40 archive [ver. 60.63] [ver. 60.63] [ver. 60.63] Replica - 2 Replica - 1 Replica - test-
Select a replica to restore... [1-3,?,q] --> 1
The warning message below appears the first time only, denoting that the RSS is configured.
Warning: Permanently added 'BSComp,192.9.100.62' (RSA) to the list of known hosts.
6. Select a replica. The utility compares the versions of the selected instance to recover with the one existing on the mirror. If they do not match, the following warning appears.
W A R N I N G !!! Instance version to be restored (60.63) doesn't match the installed application version (60.62). The application maybe disabled after recovery!! ----> Do you want to continue the Recovery Session? [y,n,?]
6-4
432006-2425-013-A00
RDR User Manual
The RDR displays a summary of the recovery session defined in the previous steps. A confirmation appears.
02/06/07 09:07:38 Mirror Recovery Procedure on MirrorComp starting...
A T T E N T I O N !!! 1. All local databases current data will be lost !! 2. Be sure that routing and network interfaces are set properly for application being restored. 3. Be sure that you have valid licenses to run applications on Mirror Component.
Network Management Dept Transport Networking Division ECI Telecom Ltd.
Recovery Session Data [instance ems@PriComp:z2]: Primary instance: Replica to restore: Backup time: Mirror instance: ----> ems@PriComp:z2 (ver. 60.63) 2 2007/02/06 08:28:22 ems@MirrorComp:z6 (ver. 60.63)
Do you want to proceed? [y,n,?] y
7. Enter y to confirm. The recovery session begins.

02/06/07 09:07:52 Start Recovery Session (ems@MirrorComp:z6) [Backup Server: BSComp, Primary Instance: ems@PriComp:z2, Replica: 2] Recovery is underway, wait... /-\|/-\|
At the end of a successful recovery, the following message appears:

Recovery Session ended successfully.
432006-2425-013-A00
6-5
RDR User Manual
Setting the Mirror Component

This section describes how to synchronize the components to communicate with the mirror component and not the primary component, after restoring to the mirror component (Restoring to the Mirror Component, page 6-2). NOTE:
Valid mirror station configurations in the following procedures may include:

LightSoft client on a dedicated station, OR EMSs on a dedicated station, OR LightSoft server in combination with a LightSoft client and/or EMSs
A mirror station cannot only include an active LightSoft client and EMS(s). When the LightSoft client and/or EMSs must be recovered on the same mirror station as the LightSoft server, perform the LightSoft server recovery procedure first.
Before you start: 1. Restore the required instances to the mirror component (see page 6-2). 2. Enable autostart for each component that will be activated by the Mirror by running the following commands as root user:
rm /etc/.NO_NMS_AUTO_START (for LightSoft server) rm /etc/.NO_SYN_AUTO_START (for EMS-SYNCOM) rm /etc/.NO_XDM_AUTO_START (for EMS-XDM)
6-6
432006-2425-013-A00
RDR User Manual
To recover the LightSoft server to the mirror site: 1. In the mirror site, activate the nms instance on the mirror component, as follows: a. Enter rm /etc/.NO_NMS_AUTO_START to enable autostart on boot b. Enter /opt/NMS/server/sh/ConfigureNMS.sh. c. If LightSoft server is alone on the mirror station, select Configure NMS single server. OR If LightSoft server is distributed amongst multiple servers, select Configure NMS cluster (valid for LightSoft V2). (In this case, the same Primary Servers WorkStation ID(s) should be copied to the alternate mirror component.) OR If EMS-SYNCOM, EMS-XDM and/or LightSoft client share the same mirror station, select Combined Mode (LightSoft + EMS + Client). 2. In the primary site, on each LightSoft client that remains active, enter /opt/NMS/server/sh/ConfigureNMS.sh 3. In the primary site, on each EMS-SYNCOM or EMS-XDM that remains active, do the following: a. Update ems.conf or enm.conf by modifying the expression
S &env_ns_port ENBARH_NAMESERV_PARAMS Primary:3075:2
substituting the applicable mirror host name in place of Primary (the primary host name). b. Enter RegisterEMS -f Mirror:3075:2 substituting the applicable mirror host name in place of Mirror (the mirror host name).
432006-2425-013-A00
6-7
RDR User Manual
To recover a LightSoft client to the mirror site: NOTE: If the same mirror station is also used to recover the LightSoft server, perform the LightSoft server recovery procedure first.
In the mirror site, activate the required LightSoft clients on the mirror component, as follows:
If only a LightSoft client is to be activated on the mirror (the LightSoft server remains active on the primary site), enter /opt/NMS/client/sh/ConfigureNMS.sh OR
If the LightSoft server is distributed amongst multiple servers, select Configure NMS cluster (valid for LightSoft V2) OR If both the LightSoft server and a LightSoft client are to be activated on the same mirror, enter /opt/NMS/server/sh/ConfigureNMS.sh
No actions are required on either LightSoft clients or EMSs on the primary site.
6-8
432006-2425-013-A00
RDR User Manual
To recover an EMS-SYNCOM and/or EMS-XDM to the mirror site: NOTE: If the same mirror station is also used to recover the LightSoft server, perform the LightSoft server recovery procedure first.
In the mirror site, activate the required EMSs on the mirror component as follows: 1. Update ems.conf or enm.conf by modifying the expression
R &env_mtnm_ems_no EMS_INSTANCE_NUMBER ### 1 999
substituting ### with the EMS ID of the Primary EMS. 2. Update ems.conf or enm.conf by modifying the expression
S &env_ns_port ENBARH_NAMESERV_PARAMS NMSComp:3075:2
substituting NMSComp with the hostname of the station that functions as the LightSoft server, as follows:
If the LightSoft server remains active on the primary component, specify the primary component station. If the LightSoft server has been recovered on a mirror station, specify that stations name.
3. Enter RegisterEMS -f NMSComp:3075:2 In place of NMSComp, substitute the hostname of the station that functions as the LightSoft server. 4. Enter rm /etc/.NO_AUTO_SYN_START /etc/.NO_AUTO_XDM_START No actions are required on either LightSoft clients or the LightSoft server on the primary site.
432006-2425-013-A00
6-9
RDR User Manual
Defining Application Autostart

The application autostart feature, available causes the application to automatically start up when the station starts. This functionality can be disabled or re-enabled.
touch /etc/.NO_NMS_AUTO_START touch /etc/.NO_SYN_AUTO_START touch /etc/.NO_XDM_AUTO_START
To disable application auto startup:

To disable automatic startup, create matching flag file/s by entering the script line/s for the required application/s, as shown below. (Enter only the line relevant for the required application.)
touch /etc/.NO_NMS_AUTO_START touch /etc/.NO_SYN_AUTO_START touch /etc/.NO_XDM_AUTO_START
(Any NMS) (EMS-Syncom V10.100 or later) (EMS-XDM V5 or later)
To enable application auto startup:

To enable automatic startup after disabling it, remove matching flag file/s by entering the script line/s for the required application/s, as shown below. (Enter only the line relevant for the required application.)
rm /etc/.NO_NMS_AUTO_START rm /etc/.NO_SYN_AUTO_START rm /etc/.NO_XDM_AUTO_START
(Any NMS) (EMS-Syncom V10.100 or later) (EMS-XDM V5 or later)
6-10
432006-2425-013-A00
7
Restarting the Primary Instance after Recovery (Reverse Update)
Overview
This chapter describes how to perform a reverse update session to return the primary component to normal operation. The process involves loading the primary component with changes that occurred in the system since the mirror component was activated. Reverse update is performed as a cold backup session and must be implemented only when instance applications on mirror and primary components are down. The procedure includes two main steps: 1. Performing reverse update to the primary component (see Performing Reverse Update, page 7-2). 2. Setting the other components to recognize that the primary component has been returned to duty in place of the mirror component (see Recognizing the Primary Component, page 7-3). Before you start:
Ensure that the instance application to be reverse updated is shut down on the mirror and primary components. Ensure that the appropriate applications are correctly installed on the primary component.
432006-2425-013-A00
7-1
RDR User Manual
Performing Reverse Update

This section describes how to perform reverse update to the primary component. After completing this procedure, you must set the other servers to recognize that the primary component has been returned to duty in place of the mirror component (see Recognizing the Primary Component, page 7-3). To start a reverse update session: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions Menu appears. 2. Select 5 Command Center Mode 3 Mirror Component Actions 2 Start Reverse Update Session. The RDR asks from which mirror server to restore.
--> Enter Mirror Component hostname or IP address [?,q] MirrorComp
3. Define the mirror server to restore from. The RDR checks the mirror server connectivity and then displays the installed instances on the primary component.
Check connectivity with "MirrorComp"... MirrorComp OK
Step 2. Select primary instance on "PriComp"... RDR Instances on PriComp: # 1 2 3 4 5 6 7 8 TAG ems enm nms ems enm nms ems nms ZONE z2-PriComp z2-PriComp z2-PriComp z6-PriComp z6-PriComp z6-PriComp z3-PriComp z3-PriComp VERSION 60.63 10.111 02.108 60.63 10.111 02.108 62.38 03.025 TITLE EMS EMS NMS EMS EMS NMS EMS NMS XDM Syncom Server XDM Syncom Server XDM Server
Select an instance to restore to... [1-8,?,q] -->
4. Select a primary instance to restore to. The RDR lists instances on the mirror server that match the primary instance you have selected in this step. The following message appears if the instance is active.
ERROR!! Cannot continue while "XDM Element Manager" is UP on PriComp!!
7-2
432006-2425-013-A00
RDR User Manual
5. Select a backup instance to restore from.

Step 3. Select mirror instance on "MirrorComp", wait... Mirror Instances on MirrorComp 1 2 ems z6-MirrorComp 60.63 ems z3-MirrorComp 62.38
Select a mirror instance for reverse update... [1-3,?,q] --> 2
The utility compares the versions of the selected mirror and primary instances. If they do not match, a warning appears. The RDR lists the details of the reverse update with a warning that the reverse update will overwrite all current data 6. Confirm the reverse update session. The session begins.
Start Reverse Update Session to ems@PriComp:z2 [Mirror Host: MirrorComp, Mirror Instance: ems@MirrorComp:z6] Reverse Update is underway, wait... /-\|/-\|
A success message appears when finished.

Reverse Update Session ended successfully. Press Return to continue...
Recognizing the Primary Component

After reverse update to the primary component (see page 7-2), you must set other servers to recognize and communicate with the primary component that has been returned to duty in place of the mirror component. This procedure is similar to setting the mirror component after recovery, as described on page 6-6.
432006-2425-013-A00
7-3
RDR User Manual
7-4
432006-2425-013-A00
A
Suspending or Resuming RDR Operation
This appendix describes how to suspend RDR activities, for example, in order to perform maintenance operations or a software upgrade, and to resume the activities when required. To suspend or resume all RDR operation: 1. From the RDR Instances list (see RDR Instances List), enter r. The RDR Common Actions Menu appears. 2. Select 6 Suspend All Backups/6 Resume All Backups.
Figure A-1: RDR Common Actions Menu
432006-2425-013-A00
A-1
RDR User Manual
To suspend or resume the RDR operations of a specific instance: 1. From the RDR Instances list (see RDR Instances List), select an instance. The RDR Instance Actions Menu appears. 2. Select 5 Suspend Instance Backups/5 Resume Instance Backups.
Figure A-2: RDR Instance Actions Menu
A-2
432006-2425-013-A00
B
Defining an Alternate Cache Location
Relocation of alternate cache directory is required when the /var partition is too small. To configure an alternate cache location, the following two steps are required:

Create and define a new cache directory. Share the new directory with the zone(s).
To create and define a new cache directory: 1. As root, activate the RDR at the Global zone of the Primary component. 2. Select 2 Primary Component Actions > 1 Configure Special Primary Component Options > 1 Relocate Cache Folder. The RDR lists the instances. 3. Select an instance. The old cache directory is displayed and you are prompted for the new cache directory location.
432006-2425-013-A00
B-1
RDR Commands
RDR User Manual
# RDR Possible RDR modes of Activity ["PriComp"]: 1 2 3 RDR Backup Server Actions Primary Component Actions Mirror Component Actions
Select RDR mode ( q for exit ) [1-3,?,q] --> 2 RDR Primary Component "PriComp" Actions Menu: 1 2 Configure Special Primary Component Options Start Reverse Update Session
Select an action... [1-2,?,q] --> 1 Configure RDR Primary Component "PriComp" RDR Primary Configuration options 1 2 Relocate Cache Folder Clean Instance Cache
Select an option ( q to exit )... [1-2,?,q] --> 1 RDR Instances on PriComp 1 2 3 4 5 ems enm nms ems nms z2-PriComp z2-PriComp z2-PriComp z3-PriComp z3-PriComp 60.63 10.111 02.108 62.38 03.031
Select an instance... [1-8,?,q] --> 1 Current cache location for instance ems@PriComp:z2: /var/containers/share/ems
4. Enter the new cache directory. Be sure that there is enough space to hold the database backup. If the directory does not exit, it is created. 5. Enter y to confirm. NOTE: The new location can be on a different disk too.
B-2
432006-2425-013-A00
RDR User Manual
RDR Commands
--> Cache folder new location [/var/containers/share/ems]: [?,q] /sdh_home/alt_cache/ems Current cache path: /var/containers/share/ems/.RDR.CACHE_z2 New cache path: /sdh_home/alt_cache/ems/.RDR.CACHE_z2 --> Do you want to relocate? [y,n,?] y RDR Primary Configuration options 1 2 Relocate Cache Folder Clean Instance Cache
Select an option ( q to exit )... [1-2,?,q] --> q
To share the alternate cache directory with the zone(s): 1. As user root, run the ZoneAdmin tool and select the relevant zone. The Zone Actions Menu appears.
# ZoneAdmin Interactive Zone Administration Service
Current zones status on host "PriComp": Zone Name --------1 2 z2-PriComp z3-PriComp Hostname -------z2-PriComp z3-PriComp Status -----[ id - 1 ] [ id - 2 ] running running
Select a zone ["add" to add new one] [1-3,q] --> 1 Zone "z2-PriComp" Actions Menu 1 2 3 4 5 Remove Boot / Reboot (init 6) Halt (init 0) Show Status Additional Settings
2. Select 5 Additional Settings > 5 Define Global Shared Directory. A prompt appears for a directory to share. 3. Enter y to confirm. The directory is shared.
432006-2425-013-A00
B-3
RDR Commands
RDR User Manual
NOTE: To remove sharing, select 6 Remove Global Shared Directory and then reboot the zone.
Select an action (q for exit) [1-5,q] --> 5 Zone "z2-PriComp" Additional Setting Menu 1 2 3 4 5 6 Change Hostname Share / Unshare Data Connect to Console Update Existing Zone Define Global Shared Remove Global Shared
Directory Configuration Directory Directory
Select an action (q for exit) [1-6,q] --> 5 Enter an Existing Directory (full path) to Share with Zone "z2-PriComp": [?,q] /sdh_home/alt_cache/ems Directory to Share: /sdh_home/alt_cache/ems Do you want to continue ? [y,n,?] y Sharing /sdh_home/alt_cache/ems ... Done.
B-4
432006-2425-013-A00
C
RDR Commands
This appendix describes various UNIX scripts that can be used to perform specialized RDR operations. This section is for expert reference use only. Users should perform regular RDR operations using the RDR menu structure accessed with the RDR command, as described in the procedures in this manual.
SyncMaster
RDR synchronization (replication) utility. Function description: Performs direct replication between the primary component and backup server. Supports regular and archive replications. Normally invoked by cron (see SetCronRDR). Usage:SyncMaster
[-i inst_name] [-dest target] [-a] [-l] [-ll log_level] [-dd debug_level] [ -suspend | -continue ] [-help ]
Options:
-i <instance name> -dest <target> -a -dd <debug_ level> -l -ll <log_level> -suspend -continue -help Instance name. Backup to specific target (replica name). Archive backup. Set debug level [0-3, default - 0]. Enable logging. Set log level [0-3, default - 1]. Temporarily suspend activity. Resume backup activity (if suspended). Print help message.
432006-2425-013-A00
C-1
RDR Commands
RDR User Manual
ReverseUpdate
RDR Primary component restore utility. Functional description: Restore Primary Component from Mirror Usage: ReverseUpdate
[-M mirror host] [-p primary_instance] [-m mirror_instance] [-dd debug_level] [-f ] [ -help ]
Options:
M <hostname> - p <instance name> - m <instance name>D -dd <debug_level> -f -help Restore from specified mirror host. Instance on Primary Host to restore to. Instance on Mirror Host from where to restore. Set debug level [0-3], default 0. Set force (non-interactive mode). Print help message.
RestartMirror
RDR restore (recovery) utility. Functional description: Interactive utility for restoring a replica from a backup server and launching an application on a mirror component. Usage: RestartMirror
[-p inst_name] [-m inst_name] [-b hostname] [-r replica] [-f] [-dd debug_level] [-help]
Options:
--p <inst_name> --m <inst_name> -b <hostname> r <replica> dd <debug_level> -help Primary instance name. Mirror instance name. Backup Server from which to restore. Replica from which to restore. Set debug level [0-3]. Print help message.
C-2
432006-2425-013-A00
D
Error Messages
The following table lists the RDR error messages and suggestions for troubleshooting purposes.
Error Number Message Diagnosis
1 3 5 6 12 11 10 20 23 2|4|13|14| 21|22|30 99 50 51
Fatal installation/config problem Transfer cannot be completed Request cannot be completed RDR cannot connect to $PRIM_MASTER RDR cannot transfer $inst_name Transfer cannot be complete RDR cannot connect to $inst_name Transfer interrupted RDR cannot transfer $inst_name RDR cannot transfer $inst_name Backup Session Overrun RDR cannot replicate from $PRIM_MASTER RDR cannot make replica dir on $shadow_server
There is a problem with the RDR package configuration. There is a problem with the application configuration.
A handshake cannot be established. Either the disk is full or there is a problem with permissions. There is a problem with the $BACKUP_SERVER configuration. There is a problem with the rsync server $inst_name configuration. A disk or network problem. A permissions or network problem.
The previous session is still opened (pid `cat $master_lock`).
A permissions or configuration problem.

D-1
432006-2425-013-A00
RDR Commands
RDR User Manual
Error Number
Message
Diagnosis
60 70 71 0 *
RDR cannot backup DB on $PRIM_MASTER RDR cannot backup local DB on $PRIM_MASTER RDR cannot restore local DB exit 0 Unknown problem A local cache size problem or a database problem.
D-2
432006-2425-013-A00
E
Glossary
This appendix defines various terms used throughout this manual.
Application Backup Server Backup Client Primary site Mirror site Primary component Mirror component Shadow component Slave manager Synchronization Replica Archive Backup (replica) Reverse Update Mirror Restart Site Protection Host Protection Disk Protection Instance Instance tag
432006-2425-013-A00
Software to be protected by RDR RDR component to store replicas Primary host to be backed up by backup server Original set of computers running applications to be protected Redundant set of computers running applications to be protected Host belonging to the primary site Host belonging to the mirror site Host backing up the Backup Server In the case of an integrated application host running slave manager Process of copying data between components A single copy of application data stored on a backup server Special copy of application data for long-term storage Process of restoring data on a primary component from a mirror component Starting the application on a mirror site after primary failure Highest redundancy level providing recovery in the event of total site disaster Redundancy solution providing recovery in case of application host crash Redundancy solution providing recovery in the event of data disk crash Set of the RDR-supported application data associated with the RDR component Symbolic name for instance identification
ECI Telecom Ltd. Proprietary E-1
Glossary
RDR User Manual
Hot backup Cold backup Incremental backup Backup level crontab file Backup session Recovery session Automatic backup session Post-recovery action Timestamp
Method of backing up application data without shutting down the application Method of backing up application data that requires application shutdown Backup method that copies only the differences relative to the last backup In incremental backup method, a number specifying the increment value UNIX file containing instructions for launching commands at a specific time Process of instance data copying to a backup server Process of restoring backup data on a mirror component Backup session invoked by crontab Instance-dependent action for setting up data after recovery Special unique file created for every backup session containing time and identification data
E-2
432006-2425-013-A00
Index
A
About This Manual ix Activation See Component Activation Application Requirements 2-1 Archive Backups 5-6 reverse update to primary 1-17, 7-1 Components 1-2 backup 1-3 mirror 1-4 primary 1-3 Configuration Workflow 4-1 Configurations in RDR 1-9 backup deployment 1-9 EMS configuration issues 1-14 LightSoft configuration issues 1-14 primary-to-mirror ratio 1-10 Configuring messages display 4-20 mirror settings after restore 6-6 primary components 4-1 shadow backup server 5-4 Cron Entries 5-13
B
Backup Components 1-3 Backup Deployment 1-9 shadow backup server 1-9 Backup Levels for LightSoft Instances 1-6 Backup Server Disk Capacity 2-3 Backup Session 1-15 Backups creating and scheduling 5-1 creating regular or archive backups 5-6 cron entries 5-13 Bandwidth Requirements 2-2
E
EMS Configurations 1-14
C
Communications Requirements 2-2 Component Activation backup session 1-15, 5-1 recovering from backup to mirror 1-16, 6-1
432006-2425-013-A00
F
Frequencies and wavelengths A-1, B-1 Functional Description 1-2 components 1-2 instances 1-4 replicas 1-5
I-1
Index
RDR User Manual
G
Glossary of Terms E-1
R
RDR configurations 1-9 functional description 1-2 terminology 1-1 what is? 1-2 RDR Commands Restart Mirror C-2 Reverse Update C-2 SyncMaster C-1 RDR Menus 3-1 Main menu 4-2 Recovery from Backup to Mirror 1-16, 6-1 restore procedure 6-2 setting the mirror component 6-6 Replicas 1-5 Restart Mirror Command C-2 Restarting the Primary 7-1 performing reverse update 7-2 recognizing the primary component 7-3 Resuming Primary Operation A-1, A-2 Reverse Update Command C-2 Reverse Update to Primary 1-17
I
Installation Requirements See Preliminary Requirements Before Installation Instances 1-4 LightSoft backup levels 1-6
L
LightSoft Instance Configurations 1-14
M
Main Menu 4-2 Menus See RDR Menus Messages Display Configuration 4-20 Mirror Components 1-4 recovery to 6-1
N
N to 2 Configuration 1-13
P
Preliminary Requirements Before Installation 2-1 application requirements 2-1 backup server disk capacity 2-3 communications and bandwidth 2-2 Primary Components 1-3 backing up 5-1 messages display configuration 4-20 reactivating 7-1 suspending or resuming operation A-1, A-2 Primary-to-Mirror Configurations 1-10 1 to 1 1-11 2 to 2 1-12 N to 2 1-13
S
Scheduling Backups 5-1 Shadow Backup Server 1-9 configuration 5-4 Suspending Primary Operation A-1, A-2 SyncMaster Command C-1
T
Technical Assistance xii Terminology 1-1 Typographical Conventions xi
I-2
432006-2425-013-A00
RDR User Manual
Index
W
What Is RDR? 1-2 Workflow configuration 4-1
432006-2425-013-A00
I-3
Index
RDR User Manual
I-4
432006-2425-013-A00

RDR UM A00 4 en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RDR UM A00 4 en

Uploaded by

Copyright:

Available Formats

Remote Data Replicator (RDR)

RDR User Manual

Preliminary Requirements ...................................................... 2-1

ECI Telecom Ltd. Proprietary

RDR User Manual

RDR Menus .............................................................................. 3-1

RDR Configuration .................................................................. 4-1

Creating and Scheduling Backups ........................................ 5-1

Recovering to a Mirror Component ....................................... 6-1

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

About This Manual

ECI Telecom Ltd. Proprietary

About this Manual

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

About this Manual

Courier Menu > Option Boxes around text

CAUTION: Text set off in this manner indicates that failure to

ECI Telecom Ltd. Proprietary

About this Manual

RDR User Manual

Obtaining Technical Documentation

ECI Telecom Ltd. Proprietary

ECI Telecom Ltd. Proprietary

RDR User Manual

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

tag: Identifies the application:

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

LightSoft Instance Backup Levels

Figure 1-1: Sequence of LightSoft instance backups over time

ECI Telecom Ltd. Proprietary

RDR User Manual

ECI Telecom Ltd. Proprietary

RDR User Manual

Differences and New Features

Discontinued features are as follows:

ECI Telecom Ltd. Proprietary

RDR User Manual

Typical RDR Configurations

Shadow backup server

ECI Telecom Ltd. Proprietary

RDR User Manual

Primary and Mirror Configurations

ECI Telecom Ltd. Proprietary