12.1 |
Service and Maintenance Tasks |
12.1.1 |
Backing Up the Customer Database (CDB Backup) |
| A distinction is made here between |
| • | backup of customer data without HiPath Software Manager and |
| • | backup of customer data with HiPath Software Manager. |
12.1.1.1 |
Customer Data Backup Without HiPath Software Manager |
Definition |
| CDB backup refers to saving the customer database (CDB) to the multimedia card MMC (HiPath 3000) or copying the cyclic RAM data and saving it in two PDS (Permanent Data Service) files (HiPath 5000). |
| Note: The RUN LED flashes repeatedly for a short period to signal that a CDB backup, which takes about 30 seconds, is in progress on the MMC. |
12.1.1.1.1 |
Automatic Customer Data Backup |
HiPath 3000 |
| A two-stage concept guarantees automatic customer data backup. |
| A complete CDB backup version can be found on the MMC at any time. Deltas for this backup are stored in an SRAM area (with battery backup) in the central control board. If the SRAM area is full, the customer data is automatically backed up. This means that the entire CDB, including SRAM content, is copied from the SDRAM in the central control board to the MMC. The current CDB is simultaneously stored on the MMC along with the "old" CDB, which is not deleted until the current CDB is completely stored on the MMC. |
| In case of a power outage, the SDRAM content that has no battery backup is completely lost. However, by re-accessing the CDB backup on the MMC, the system's database can be restored to the state it was in prior to the power outage. |
| Regardless of the volume of changes to the database, HiPath 3000 always automatically performs a complete CDB backup at midnight, system-time. |
HiPath 5000 |
| On the communication server, RAM data is copied automatically every three minutes and stored in the file hicom.pds. This file contains the complete data description of the HiPath 5000 with emulated HG 1500 boards. This includes: |
| • | customer data |
| • | trace |
| • | error history |
| • | call charge data |
| • | status data |
| The directory in which the two PDS files are to be stored must be defined when the HiPath 5000 software is installed (setup). The two PDS files are created when the HiPath 5000 is started for the first time. |
12.1.1.1.2 |
Manual Customer Data Backup with HiPath 3000 |
| You can perform a manual CDB backup using HiPath 3000/5000 Manager E (in online mode) or Manager T. |
| However, be aware that it is not possible to deliberately abort a manual backup that is initiated using Manager T. Once the CDB backup process starts, it should be ended because the backup continues to run in the background. |
| You can also manually initiate a CDB restore, including the call detail data, from the MMC. |
Procedure: Manual CDB backup, system restore using Manager T |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
12.1.1.2 |
Customer Data Backup with HiPath Software Manager |
Definition |
| The HiPath Software Manager supports, among other things, the backup of customer databases (Backup Manager) from all HiPath 3000/5000 systems in t114he same customer network (see also Section 12.1.7 "Backing Up System Components (Backup Manager)"). |
| The CDB backups are stored in a directory which must be defined in advance. The data backup can either be started manually immediately or performed at a predefined time. A cyclic backup, which saves the customer data at a set time every day, is also possible. |
| Refer to the help provided with the HiPath Software Manager for information on backing up customer data with this tool. |
12.1.1.3 |
CDB Treatment When Replacing Central HiPath 3000 Hardware |
|
| When replacing a central control board due to a hardware defect, for example, the following options are available for handling the CDB: |
| • | Procedure: After replacing the board, load the "current" CDB to the system |
|
| • | Procedure: After replacing the board, load the "old" CDB from the customer disk to the system |
|
| HiPath 3000/5000 V8, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3580S100017620 | 2011-01-24 |