Archiving or backing up the database

The database archive is necessary for optimal performance of the system and a large transaction log file reduces database performance and slows the data recovery process. Backing up the database frequently is recommended to help manage the increasing size of the transaction log.

Perform the following procedures to change the location of the archive file and to back up the transaction log.

To change the location for the archive file

By default, a CRON job backs up and stores the archive file in the installationDirectory/pw/dbarchive directory at 5:30 A.M. every Sunday. The recommendation is to store data on a different disk by changing the directory in the cron job to a directory that you specify. 

The pw database archive allows an argument for the location of the archive file. Add the argument to change the location.For example, the pw database archive /tmp/archive command saves the archive in /tmp/archive.

To back up the transaction log file

Use the pw database archive command to back up the database and truncate the transaction log files. You can also delete and re-create the transaction log file.

BMC recommends that you back up the transaction log file at least once a week. At least 11 MB of free disk space is needed to archive the database.

1. Run the pw database archive command.

2. Ensure that the /datadisk/EUGEN file has sufficient space to archive the database.

3. Respond to the following query:

   Do you want to specify another location to archive data? 
   Entering 'y' here produces the following:
   Checking filesystems to archive Infrastructure Management ...
   Following filesystems have disk space greater than 11MB.
   Filesystem Available Disk Space/ 38MB
   /datadisk 7697MB
   /export/home 6379MB

4. Enter the archive directory for Infrastructure Management. The default is datadisk.