Troubleshooting

This guide is designed to help you begin to troubleshoot any issues you may run into when using Zmanda Classic. We will break down the issues into groups based on where they occur in your workflows.

General Troubleshooting Tools

Server Logs

Item/Action
Path or Command
Comments

Server Logs Location

/var/log/amanda

Server Configurations Location

/etc/amanda and /etc/zmanda

How to collect server logs and configurations

Run as root: /opt/zmanda/amanda/bin/zm-support

Outputs a .tar.gz file that you can send to our support team

How to send server logs to Zmanda Support

Client Logs

Item/Action
Path or Command
Comments

Collect Windows Client Logs

Run the ZWC Support utility

Collect Linux Client Logs

/usr/sbin/zm-support-client

Server Services

Item/Action
Path or Command
Comments

Check Zmanda Management Console (ZMC) Services

setup-zmc

Same command to check if the vault is unsealed

Check Zmanda Backup Server Services

setup-aee

Restart ZMC Services

systemctl restart run-zmanda-zmc.service

Restart Backup Server Services

systemctl restart run-zmanda-backup-server.service

Unseal the Vault

setup-zmc unseal

Client Services

Item/Action
Path or Command
Comments

Restart Windows Client Services

Type "Services" in the windows search bar and find the Zmanda Windows Client Backup Controller and ZWC-Database services. Right click and click restart.

Other Helpful Tools

Item/Action
Path or Command
Comments

Login as the amandabackup user

As root: su - amandabackup

Some tasks require you to be logged in as the amandabackup user. Do not change this user's password.

Check a backup job status in the command line

As amandabackup: amstatus <backup-set-name>

<backup-set-name> should match the name given in the UI and is case sensitive

Last updated

Was this helpful?