Amanda Enterprise FAQs
- Zmanda Windows Client Reinstallation Process
- Zmanda Uninstall Information Consolidated
- Zmanda Client for Windows does not support System State restore to different hardware
- xinetd/inetd (or amandad) does not appear to respond successfully to “amanda” service requests on this AEE server (localhost)
- Windows NTFS backup object “include” property
- Windows MS-SQL failed with error code 268
- Windows Client: return error code 260
- Windows Application backup failed with error code 268
- When the Amanda server’s hostname or IP address changes
- When starting ZBA, VM gives a kernel error about requiring x86-64 CPU
- What network ports are used by Amanda Enterprise?
- What is Amanda Enterprise Backup Staging Area?
- Warning: Cannot stat: No such file or directory
- VSS Shadowstorage Space
- Volume Shadow Copy Service (VSS) Errors
- VMware ESX Backup fails with fault detail “FileFaultFault”
- VMware ESX Backup fails with “missing size line from sendbackup” and “A file was not found”
- Verifying Correct Tape Library Operation
- Verifying Backups Created by Amanda Enterprise
- Upgrading Client to Latest Version
- Updating your AWS Keys
- Unable to find DLE backup history. Can not continue.
- Troubleshooting SQL VSS Writer Issues
- To change the temporary directory and template location
- Timeout waiting for ACK
- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835.
- TAPE ERROR OCCURRED: [No acceptable volumes found]
- System State Restore Failed
- System state restoration in Windows causes Amanda service to hang
- Strange – Index Creation Failed with a Windows backup
- Split or Spanning Dumps across Multiple Tapes
- Shutting Down ZMC Completely and Cleanly
- Setup of ssh transport for amrecover restores
- Server validation Failed for Windows client
- Server Not the Same as Index or Tape Server
- selfcheck request failed: Connection refused
- SCSI tape error
- Restore to Windows Share using the Zmanda Windows Client fails
- Restore of a few small files from a large backup take a long time
- Preventing disk thrashing in Amanda Enterprise
- PostgreSQL configuration check and/or backup fails
- NOTE: skipping tape-writable test
- Not enough holding disk space
- Not allowed to use this program (crontab)
- No writable valid tape found
- NDMP Backup Configuration
- Navigating to the hostname or IP address of the backup server does not load the ZMC login page
- NAK error on client during Check Host/amcheck
- MSSQL Semi-Cluster Aware Backups With ZWC
- MSSQL Semi-Cluster Aware Backups With ZWC
- Msexchange lev 0 FAILED [Writers status is not stable]
- Monitor tab shows running backups however none in progress
- Migrating ZRM older than 3.7 and ZMC 3.1.5 to ZRM 3.8 and ZMC 3.3.9
- Linux/Solaris file system backup does not traverse file system boundaries
- ISCSI Tape Library Initiator and Target Configuration
- Invoking a Backup from the Command-line
- Installing Amanda Enterprise on Scientific Linux 6.2
- Incompatible ZMC MySQL DB version. Found v, but need v101.
- I am seeing high memory usage while restoring files using ZMC on Solaris/Opensolaris
- How to use the amrestore command to restore data from tape
- How to use the amrecover command to restore data
- How to use the amadmin command to find configuration information
- How to use Solaris 10 Service Management Facility (SMF)
- How to suppress strange lines from reports
- How to setup NetBackup PostgreSQL Agent to be Cluster aware
- How to send files to the Zmanda Support Team
- How to run a script before and/or after a backup job
- How to restore from tape using standard unix utilities
- How to restore data from a vtape using the dd command
- How to replace an archived tape with a new tape?
- How to repair the Zmanda Management Console (ZMC) database-for-AE
- How to reduce the Number of Virtual Tapes for a Backup Set
- How to reduce the backup impact on an Amanda client when performing multiple dumps on the same client
- How to recover from an Amanda archive file using system tools from command line
- How to prevent more than one full backup per Backup Cycle
- How to Perform Backups and Restores through SSH
- How to Move ZWC MySQL folder to another directory
- How to modify the backup media block size
- How to install the license file on ZBA?
- How to increase the size of backup disk on the Zmanda Backup Appliance
- How to improve ZBA performance?
- How to generate a self signed certificate in ZMC
- How to generate a self signed certificate for backup encryption with ZWC
- How to enable SSH authentication in Amanda Enterprise
- How to determine tape drive and tape changer device names in Linux
- How to configure ZMC’s Apache to listen on one IP address only
- How to configure Amanda backups through a firewall (w/iptables example)
- How to change Zmanda Management Console (ZMC) Apache ports after installation
- How to backup standby instances in Oracle
- How to backup a Linux HA cluster
- How to back up network mapped drives on Windows clients
- How to add or modify dumptype parameters?
- How to abort a running backup
- How does Amanda ZMC discover tape drives
- How does Amanda ZMC discover tape changers
- How does Amanda Enterprise backup to disk?
- How do I recover from Amazon S3 Storage without using Amanda?
- How backup scheduling works in Amanda Enterprise
- How Amanda estimates backup size when compression is enabled
- GLib: Cannot convert message: Conversion from character set ‘UTF-8’ to ‘646’ is not supported
- Getnameinfo failed: Unknown error
- Found 0 changer(s) usable by the ‘amandabackup’ user
- Fallback_splitsize of 100 MB < 0.1% of tape length
- FAILED [disk /cad, all estimate timed out] timeout waiting for REP
- FAILED [data timeout]
- ESX host check SOAP request error – possibly a protocol issue
- ERROR: Writing label: tape is write-protected
- ERROR: Unable to connect to event server. The ZMC services are not running.
- ERROR: Cannot resolve `localhost’
- ERROR: Can not open license file /etc/zmanda/zmanda_license
- Error restoring the selected files
- Error reading Amanda header: block size too small
- Error messages when using Amazon S3
- Enabling Changed Block Tracking (CBT) for VMWare Guests
- Drive not ready after 120 seconds, rewind said “/dev/nst0: Input/output error”
- Does Zmanda offer installation Quickstart help?
- Does Amanda support differential backups?
- Does Amanda support differential backups?
- Degraded Mode errors
- Creating SSL Certificate for Apache in ZMC
- Could not run mtx binary at ‘mtx’
- Could not resolve address ‘255.255.255.255’ — check resolver configuration OR file vhost.c, line 190, assertion “rv == APR_SUCCESS” failed
- Could not read license information. Please contact Zmanda Support to resolve the issue
- Configuring the amandabackup user so the password does not expire
- Configure Amanda over IPv6
- Compressed Folder Limitation in Windows Client
- Collecting Zmanda Windows Client Logs for Support
- Collecting Server Logs for Zmanda Support
- Collecting Client Logs for Zmanda Support
- Can’t switch to incremental dump
- Can’t change “No Data Sent” and “Backup Estimate” timeouts
- Can’t assign requested address
- Can not use more space (xxxx MiB) than free (xxxx MiB)
- Backup of VM on ESX server gives “Fault string: A specified parameter was not correct”
- Backup of VM on ESX host fails with “stderr: VixDiskLibVim: Not licensed to use this function.”
- Backup Failure: gtar terminated with signal 9 on Solaris
- Backing Up Your Amanda Enterprise Server
- Backing up PostgreSQL using Amanda Enterprise
- Archiving Strategies
- Applying Patches
- amrecover [request failed: timeout waiting for ACK]
- amrecover [request failed: recv error: Connection reset by peer]
- amrecover [request failed: recv error: Connection reset by peer]
- Amazon S3 : clock skew
- Amanda Enterprise Server Enhanced Security Configurations
- Amanda Enterprise / Zmanda Recovery Manager GUI Crash – Couldn’t release the accept mutex
- Amanda Enterprise / Zmanda Recover Manager PHP Memory Exhausted
- 1 tapes filled; runtapes=1 does not allow additional tapes
- [Can not execute /usr/bin/star: No such file or directory]
- “EOF on read” when using SSH authentication method
- “EOF on read” error from a client
- ‘staging’ must not be accessible to any group or user other than ‘amandabackup’