This chapter describes the tasks that you perform to back up and restore your Oracle Communications Billing and Revenue Management (BRM) system.
To prevent any data loss and minimize the impact of software or hardware failure, back up your system immediately after installing or updating the system.
Create a backup of the BRM configuration files and BRM installation area (the BRM installation directory and its content: BRM_home). You can perform this backup as soon as you install and configure BRM. In particular, make sure you back up all customized files, including source code, policy, start_all, pin.conf, pin_ctl.conf, pin_setup.values, and Infranet.properties files.
Repeat the backup process whenever you customize or update the BRM configuration files. For instructions on backing up the standard configuration, see "Backing Up BRM Configuration".
Important:
Store this backup in a safe location. The data in these files are necessary if you encounter any operational or system issues.After you complete the backup, you can use the backup configuration directory and installation area to restore your system when needed. For instructions on restoring the standard configuration, see "Restoring BRM Configuration".
If you do not back up your BRM system regularly, you need to reinstall and reconfigure the system if it is corrupted due to operational or system errors. Reinstalling and reconfiguring eliminates any chance of recovering and reprocessing data processed by the BRM system at the time of the error.
If you require BRM technical support, email a copy of your backup configuration directory to your Oracle Global Support representative. If you want to send a copy of your configuration directory, use the tar command to create an archived version of that directory.
If you want to make a complete offline backup of your BRM or Pipeline Manager database, use the appropriate backup tools for your database version and ensure that the backup is completely valid and usable. The backup must contain both the database definition and all the database contents. For more information, see the discussion about performing full database backups in your database software documentation.
To create a backup of the BRM configuration, see the following:
To back up BRM configuration:
Important:
In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.On the machine on which you installed BRM, copy the vpd.properties file by running the following command:
cp vpd.properties vpd.properties_75
Go to the BRM_home directory.
Copy the content of the BRM_home directory to a new directory by running the following command:
cp -R BRM_home NewName
where NewName is the name for the new directory.
Note:
You can remove the BRM log files from the backup directory.Create an archive of the entire directory and the vpd.properties file by running the following command:
tar cvf NewName.tar.gz NewName tar cvf vpd.properties_75.tar.gz vpd.properties_75
Store the backup copies in a location outside of the BRM system by running the following command:
mv NewName.tar.gz New_Directory mv vpd.properties_75.tar.gz New_Directory
where New_Directory is the new location that is outside of the BRM system.
A compressed TAR file, of all copied files, is created with the extension tar in the new location specified (for example, brm_backup/brm_home.tar.gz).
If you are using Pipeline Manager for usage charging, back up the Pipeline Manager files.
Important:
In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.To back up Pipeline Manager files:
On the machine on which you installed Pipeline Manager, copy the vpd.properties file by running the following command:
cp vpd.properties vpd.properties_75
Copy the content of the Pipeline_home/ifw directory to a new directory by running the following command, where Pipeline_home is the directory in which Pipeline Manager is installed:
mv Pipeline_home/ifw Pipeline_home/ifw_75
Note:
You can remove the log files from the backup directory.Create an archive of the entire directory and the vpd.properties file by running the following command:
tar cvf ifw_75.tar.gz ifw_75 tar cvf vpd.properties_75.tar.gz vpd.properties_75
Store the backup copies in a location outside of the BRM system by running the following command:
mv Pipeline_home/ifw_75.tar.gz New_Directory mv vpd.properties_75.tar.gz New_Directory
A compressed TAR file, of all copied files, is created with the extension tar in the new location specified (for example, pipeline_backup/ifw_75.tar.gz).
By default, Rated Event (RE) Loader skips redo generation when loading files into the BRM database. This optimizes loading performance, but it can cause you to lose data if your system shuts down abnormally.
To prevent data loss when your system shuts down, archive all the successfully loaded files.
To back up the RE Loader files:
Create an archive of the entire directory in which the RE Loader files are stored by running the following command:
tar cvf RE_Loader_Dir.tar.gz NewName
Store the backup copy in a location outside of the BRM system by running the following command:
mv NewName.tar.gz New_Directory
A compressed TAR file, of all copied files, is created with the extension tar in the new location specified (for example, RE_Loader_backup.tar.gz).
To restore the BRM configuration:
Ensure that no users are logged in.
Users include customers, client applications, customer service representatives (CSRs), and so on.
Stop all BRM processes.
Only the database instances should be running during the patch installation.
For instructions, see "Starting and Stopping the BRM System".
Delete or rename the damaged BRM_home directory:
To delete, run the following command:
rm -R BRM_home
To rename, run the following command:
mv BRM_home New_Name
Retrieve the backup tar file of the BRM_home directory.
Extract from the TAR file the backup copy of the directory by running the following command:
tar xvf BRM_home.tar.gz
The command recreates the copy of the BRM_home directory.
Repeat steps 3 to 5 with Pipeline_home to restore the Pipeline Manager configuration.
Repeat steps 3 to 5 with vpd.properties_75 to restore the vpd.properties file for BRM and Pipeline Manager.
Note:
If you have BRM and Pipeline Manager installed on separate machines, perform this step on both the machines.Repeat steps 3 to 5 with RE_Loader_Dir to restore the RE Loader files.
Start BRM processes and Pipeline Manager.
For instructions, see "Starting and Stopping the BRM System".
All updates, which had been temporarily disrupted due to the shutdown, are processed upon restart.