- Knowledge Base
- Zmanda Recovery Manager (ZRM)
-
Zmanda Enterprise
-
Zmanda Recovery Manager (ZRM)
-
Backend Operations
-
Backup
-
Server Installation
-
Client Configuration
-
Account and Licenses
-
Sources
-
Storage
-
Schedules
-
Backup Sets
-
Backup Operations
-
Restore Operations
-
Monitoring and Reporting
-
Configurations
-
ZMC/UI
-
Whitepaper
-
Zmanda Cloud Storage
-
VMWare
-
Key Vault
-
Disaster Recovery
-
Zmanda Support
-
Product lifecycle
-
Zmanda Pro
BACKUP FAILED: MYSQLDUMP: GOT ERRNO 28 ON WRITE
This article is for Zmanda Recovery Manager For MySQL.
Issue Symptoms
mysqldump: Got errno 28 on write ERROR: mysqldump command did not succeed. Command used is mysqldump --opt --extended-insert --single-transaction --default-character-set=utf8 --create-options --user=root --password=***** --databases .... > "/var/lib/mysql-zrm/dailyrun2/20061101140140/backup.sql" INFO: backup-status=Backup failed INFO: Backup failed ERROR: /usr/bin/mysql-zrm did not finish successfully
Issue Description
This error means that sufficient disk space is not available to do backups.
Resolution
Please check the free space available in the filesystem used for backups (default is /var/lib/mysql-zrm directory in the machine running ZRM for MySQL).
Add additional disk space to the filesystem and re-run the ZRM for MySQL backup for the backup set.