billmax documentation   BillMax Billing Solutions
  877.245.5629
  sales@billmax.com
 
Chapter 4. Backing Up to Offline Storage
Prev  Maintaining BillMax  Next

Chapter 4. Backing Up to Offline Storage

Table of Contents

BillMax database backups
The MySQL log file
The DBLOG log file
The Electronic Funds Processing log files
The Statement files
Local customizations to the BillMax system
Other Maintenance Tasks

The mechanics of how to do backups to offline storage are beyond the scope of this documentation. This documentation describes files that might be considered for backups to offline storage.

The goal of doing BillMax backups should be to recreate the billing/provisioning operations given the complete failure of the billing/provisioning operations. This documentation will describe BillMax related data that should be considered for backup to offline storage.

BillMax database backups

BillMax provides different mechanisms for implementing backups of the BillMax database. When "billmax-admin nightly" is executed (which is normally done at night using cron. The following happens with regards to backups and compressing files.

  1. If the setting for MYSQLD in /usr/local/billmax/local/billmax.conf is "YES", then BillMax will shutdown the MySQL database.

  2. /usr/local/billmax/local/backup_hook will be run if it exists and is executable. The expectation is that this is a script or program that may be written to:

    1. Copy the previous night's backup to tape, DVD, etc.

      Run specialized processing related to backups, disk usage, etc.

  3. If the setting for MYSQLD in /usr/local/billmax/local/billmax.conf is "YES" and the setting for BACKUP_DB in /usr/local/billmax/local/billmax.conf is "YES", BillMax will copy the MySQL database files in /usr/local/billmax/mysql/var/databasename to /usr/local/billmax/mysql/var/databasename.backup where databasename is the name of the database as specified in /usr/local/billmax/local/billmax.conf by the DB_DATABASE setting. All files are copied except those with "datacall" in the name. Those are only copied when "billmax-admin nightly" is executed on an Sunday.

Using either /usr/local/billmax/local/backup_hook or some other method, consider copying the files in /usr/local/billmax/mysql/var/databasename.backup to offline storage.

[Warning] Warning

If used, nightly processing will not continue until successful completion of /usr/local/billmax/local/backup_hook.

Prev  Up  Next
Chapter 3. Monitoring Diskspace  Home  The MySQL log file
Document Revision A for BillMax 2.2.0   -   Copyright © 1997-2006 The iSpark Group, Inc.

All rights reserved. No part of this documentation may be reproduced or transmitted in any fashion without written permission by The iSpark Group, Inc. This documentation is for the sole use of licensees of the BillMax billing software created by The iSpark Group, Inc. Making the documentation available to a non-licensee of BillMax without written permission of The iSpark Group, Inc. is a violation of the use of this documentation.

While precautions have been taken in the preparation of this documentation, The iSpark Group, Inc. assumes neither liability nor responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.

All terms mentioned that are known to be trademarks have been appropriately capitalized. Use of the a trademark does not affect the validity of any trademark or service mark.

Links to third-party Web sites are provided for convenience. The iSpark Group, Inc. is not responsible for any content contained in the third-party Web sites.

Comments about this documentation may be sent to doc@billmax.com