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.
The PDS files must not be modified, as reading of the files using conventional tools and interpretation of the content is not possible without specialist knowledge.  
In the event of an error, the PDS files can be made available to the responsible Service Support contact for diagnostic purposes. The *.trc and *.dmp files stored in the diag subdirectory of the installation directory should also be supplied.  

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  

 Step  
 Activity  
Manual customer data backup on the MMC  
 1.  
Manager T: Start system administration  
 2.  
Menu 28 -> Edit CDB  
 3.  
Menu 28-2 -> Back up CDB data  
 4.  
Menu 28-2-1 -> CDB on MMC  
Loading the saved customer data from the MMC into the system  
 1.  
Manager T: Start system administration  
 2.  
Menu 28 -> Edit CDB  
 3.  
Menu 28-2 -> Back up CDB data  
 4.  
Menu 28-2-2 -> CDB from MMC  
Caution: When performing this action, the system performs a hard restart.  

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 
A new license file is always required if a central control board that requires a license has to be replaced. As a result of the replacement, the MAC address changes and the license becomes invalid.  
For information on this procedure, please see Section 8.3.7 "Replacing License-sensitive Hardware (Changing the MAC Address)".  
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
   
 Step  
 Activity  
 1.  
Copy the current CDB and save it on the MMC.  
 2.  
Disconnect the system from the power supply.  
 3.  
Remove the MMC.  
 4.  
Replace the central control board.  
 5.  
Insert the MMC.  
 6.  
Restart the system by plugging in the power plug.  
 7.  
The CDB previously stored on the MMC is loaded to the system RAM. The customer system is now configured:  
 •   The CMI mobile telephones are logged on.
 •   The V.24 baud rate is set up.
 •   The ACD login port is configured.
 •   All telephone options, such as volume and display, are determined per station.
 •   Procedure: After replacing the board, load the "old" CDB from the customer disk to the system
   
 Step  
 Activity  
 1.  
Back up current CDB with HiPath 3000/5000 Manager E.  
 2.  
Disconnect the system from the power supply.  
 3.  
Remove the MMC.  
 4.  
Replace the central control board.  
 5.  
Insert the MMC.  
 6.  
Restart the system by plugging in the power plug.  
 7.  
Reload.  
 8.  
If an "older" CDB update is imported, reload the CDB into the system without the Delta mode. The "hardware and CDR switch" remain inactive.  
 9.  
Reset. The customer system is now configured. All you have to do now is  
 •   log on the CMI mobile telephones again,
 •   reset the V.24 baud rate,
 •   re-configure the ACD login port,
 •   redefine all telephone configurations, such as volume and display, per station.