1. Knowledge Base
  2. Zmanda Enterprise

Zmanda Backup Server File Locations

A list of pertinent files and their locations on the Zmanda Backup Server

Amanda Enterprise files are installed in the following directories:
Amanda Server File(s)
Location
CLI Executables
/usr/sbin
Man pages
/usr/share/man
GUI/Web Components (including GUI log files)
/opt/zmanda/amanda, /opt/zmanda/common
License key file
/etc/zmanda/zmanda_license
Backup Set and other configuration files
/etc/amanda, /etc/cron.d, /etc/logrotate.d
Libraries
/usr/lib
Amanda-controlled executables
/usr/lib/amanda
Amanda Perl Libraries
/usr/lib/amanda/perl
Amanda Debug log files
/var/log/amanda/
Backup images (vtapes) and staging area (holding disk)
/var/lib/amanda (default location for backup to disks)
 
On Solaris servers, the Amanda Enterprise files are located at /opt/zmanda/amanda directory. For example: The configuration files under /etc/amanda in Linux server will be found under /opt/zmanda/amanda/etc/amanda on Solaris server.
Do not directly delete or change any of these files or directories unless apprised by the Zmanda Support Team. Changing any of these files directly can result in failed backups and other problems.
Zmanda provides Amanda server disaster recovery solutions to protect Amanda server. Please contact Zmanda Sales or Zmanda Support Team for more details.
You should monitor free space availability in /tmp, /etc/amanda and /opt/zmanda/amanda directories. At least 10 percent free space must be available in these file systems. Amanda stores the backup index, Zmanda Management Console database and temporary files in these locations, and thus these directories can fill up over time. The /tmp directory is also used to store backup images temporarily during the restore process, which can fail if it runs out of space. Lack of space in these directories can affect Amanda functionality and performance.
Amanda Debug log files are collected by the Zmanda support tool for troubleshooting Amanda problems. Amanda debug file for a process or command instance is kept for four days for each backup set.