Oracle Communications Policy Management
 
Oracle Communications Policy Management
 

PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
 

this is an overview of the backup of the PCRF systems that can be configured from platcfg user of the Policy Management systems.   for step by step instructions check the versions specific Platform Configuration Users Guide.

In this Document

Goal

Solution

Created from <SR 3-12712839461>

Applies to:

Goal

Overview of backup options for the Policy Management System
 

Solution

The PCRF product has its own backup tools integrated into the platcfg menu system

  The backup settings information for the PCRF products is in the 'Platform Configuration Users Guide'  chapter 7 for your software version. The below information is intended as an overview

  Overview
our systems can perform 2 kinds of backups:
  server backup is a backup of the linux configuration of the machine. it is unique for each blade. this kind of backup can be run on any and all PCRF servers (CMP, MRA,, MPE)
  system backup is a backup of the application configuration database from the CMP, this type of backup can only be run on CMPs, and will only execute on the primary active CMP.
because of these differences the platcfg menu will be different between the CMP and the other servers in the policy network.

The backup tools are made to maintain both a local_archive ( in /var/camiant/backup/local_archive ): a limited, configurable number of backup files will be stored and maintained here.
There is a remote_archive directory also ( in /var/camiant/backup/local_archive ):.    This will contain a copy of backup files that the system has been unable to rsync to the configured remote server.
Configuration of the remote server is in the platcfg menus here too.

# su - platcfg
  select "Policy Configuration" from the top level menu
  select "Backup and Restore" from this menu
  the menu of choices here include; run a backup now, or schedule a backup to occur at regular intervals. and configuration of a remote archive server for backups.

  Hints based on experience.
    Most system do not often make changes to the linux configuration of a policy server. For that reason you probably do not have to scheduled server backups to occur very often.   But they should be taken before and after an upgrade;  otherwise, probably twice a month is adequate. (these backups would be used when replacing server hardware, but server backup from one version cannot be used in the replacement of a different version. ( i.e. a 10.5.x backup cannot be used during the replacement on an 11.5 server).   A server backup should be maintained for each server of the network, whether it was manually generated and copied out of the server, or schedule and rsynced out.

  Application configuration changes from the GUI are much more frequent, these are the content of the 'system backup'.   The system backup should be taken much more frequently than the server backup ( you should also be using policy checkpoints for any policy changes.) the need for a system backup is generally a very extreme case: ( If you have geo-redundant CMPs, as long as one of four of those can run and has the current configuration on it, the rest of your CMP configuration can be built without a system backup: but you should still have that backup, and an up to date one at that ).    It is suggested that your CMPs run system backup often, and rsync the backup out to a remote server.


  Please see chapter 7 of the platform configuration guide for usage and configuration specifics.
 

This solution has no attachment