ZRM FAQs
- “last_backup” is a reserved file name
- Amanda Enterprise / Zmanda Recovery Manager GUI Crash – Couldn’t release the accept mutex
- Backup failed: mysqldump: Got errno 28 on write
- Backup Set directory not found
- Binary logging is off
- Can not open output file for writing
- Cannot find bin log file
- Change the user that ZRM runs as
- checksum for file does not match
- Collecting Server Logs for Zmanda Support
- copy-plugin exited with error
- Could not copy bin log file
- Could not copy database
- Could not copy table
- could not delete in directory
- Could not read file
- Could not resolve address ‘255.255.255.255’ — check resolver configuration OR file vhost.c, line 190, assertion “rv == APR_SUCCESS” failed
- error opening temporary file
- Error stopping slave
- ERROR: Can not open license file /etc/zmanda/zmanda_license
- Errors found during verification
- Got packet bigger than ‘max_allowed_packet’ bytes when dumping table
- Got packet bigger than ‘max_allowed_packet’ bytes when dumping table
- Host ‘ZRMserver’ is not allowed to connect to this MySQL server
- How to Backup MySQL Triggers
- How to cancel a ZRM restore job
- How to collect logs from ZRM running on Windows platform
- How to create Sudoer configuration for snapshots
- How to generate a self signed certificate in ZMC
- How to repair a Zmanda Management Console (ZMC) database for ZRM
- How to retrieve forgotten password for ZRM
- How to send files to the Zmanda Support Team
- How to set up MySQL user privileges for backup and restore
- How to set up passwordless authentication for ZRM
- How to upgrade to the latest version of ZRM
- Info: Space requirement on the backup directory
- last backup directory is not valid
- mail command failed
- MyDumper: /usr/bin/myloader: symbol lookup error: /usr/bin/myloader: undefined symbol: gzopen64
- MyDumper: /usr/bin/myloader: symbol lookup error: /usr/bin/myloader: undefined symbol: gzopen64
- mysql-zrm appears to be already running
- Navigating to the hostname or IP address of the backup server does not load the ZMC login page
- ndb_mgm
- Replication data will not be backed up
- Restart of cluster node(s) failed
- Restoration of Amazon EBS snapshot fails
- Restoration of Amazon EBS snapshot fails
- Restoration of incremental backups fail to a remote MySQL server
- Retaining MySQL Binary Logs only as long as needed (ZRM)
- Retaining MySQL Binary Logs only as long as needed (ZRM)
- Snapshot create failed
- Sorry, you must have a tty to run sudo
- Steps to follow when doing Remote MySQL Backup
- Tar: s: unknown function modifier
- Tar: s: unknown function modifier
- The table(s) of the database will be backed up in logical mode since some of the tables use a transactional engine
- The table(s) of the database will be backed up in logical mode since some of the tables use a transactional engine
- Timeout hit while waiting for nodes(s) to restart
- umount failed
- Unable to use snapshot
- Volume Shadow Copy Service (VSS) Errors
- What should be done when MySQL server is being upgraded to newer version?
- What should be done when MySQL server is being upgraded to newer version?
- Zmanda Recovery Manager for MySQL – backup failed
- ZRM: Monitor page does not update