Problem
What is the ARCserve/Open database? How do I maintain the
ARCserve database? Where does it exist? Either the disk space
on the drive that stores the database is approaching or greater
than 85% used, or the percentage of space used by the ARCserve
database is large. Solution
The ARCserve database stores information about backup jobs that have been run, tapes used for backups, and remote clients that are available for backup.
This database reduces the time needed to restore files by archiving information about files, directories, filesystems and disks and clients.
The ARCserve Report Manager uses information stored in the database to create various reports.
All database operations are begun from the Database Manager window from the ARCserve icon located in System Administration folder on the X-desktop.
The four database view options available from the Database Manager are:
Summary:Informational only, displays information about disk usage and number of records in each SCO ARCserve/Open database.
Job List:Tracks information about jobs that have been processed by SCO ARCserve/open.
Tape List:Tracks information about the tapes used, including formatting, the number of times a tape has been used and number of errors ARCserve encountered with a tape.
Remote Clients:Contains information about remote Unix servers and clients that can be backed up or restored.
The database should be maintained periodically. The more backup
jobs that are run, the larger the database will become, taking up
more disk space. The "Summary" view displays database usage.SCO ARCserve provides two methods to maintain the database: pruning and purging. The method used is dependent on the SCO ARCserve administrator, tape usage, and backup frequency.
Pruning preserves all job and session records, but removes all
details about individual files that were included in the backup
sessions. If there are old job records in the database that
may someday need to be restored then "pruning" should be used
and not "purging". Restoring a "pruned" session means that the
entire session would be restored, not an individual file."Purging" completely deletes all traces of a database record, including session and file information. To restore files from a job that has been purged use SCO ARCserve/Open's Merge Tape utility to merge a tape's information back into the database.
To set and enable pruning and purging options, open the
"Database" menu item from the database manager. Choose period
to prune and/or purge and make sure that appropriate "enable"
button is chosen.Note that the pruning and purging options do not reduce the actual size of ARCserve's database files, but make room for more database records within the space already allocated to them. Therefore the pruning and purging options are not effective measures for freeing up disk space, but are only useful for capping the size of these files. Pruning and purging should be run as soon as the Total DB Size figure in the Database Manager reaches the maximum size desired.
Please note that the maximum file size can be 2GB of the ARCserve
database. Before it reaches this limit it should be copied to a
separate file or archived to tape. Otherwise, if it is simply
deleted then any files required from ARCserve backup tapes would need
to be merged back into the ARCserve database from this tape which
will be time consuming.RELOCATING THE SCO ARCSERVE/OPEN DATABASEBy default, the SCO ARC/serve/Open database is located on the
"root" filesystem. An SCO ARCserve/Open system may become so
busy that despite pruning and purging, the database will grow
to a point that the root filesystem is over 85% full.Use the following method to permanently move the database to a new filesystem.
1. It is recommended that you back up the database directory, /usr/lib/ARCserve/dbase, before moving it to a different location.
2. Run astop.3. Change to the following directory:cd /var/opt/K/SCO/arcserve/2.1.0e/usr/lib/ARCserve4. Move the database directory to a different filesystem than "/root" filesystem.
mv ./dbase /<new_filesystem>/dbase5. Make a link to the new database directory:
ln -s /<new_filesystem>/dbase ./dbaseand to check the database integrity run:
./dbcheck FTS/fts6. Run astart. See also
Visit Skunkware's "find" utilities available from:ftp://ftp2.sco.com/pub/skunkware/osr5/vols/and download the following file:findutils-4.1-VOLS.tar