Running dockerctl backup on a machine with a limited amount of memory can fail, however it incorrectly reports "Backup complete". This is misleading because the backup file is probably either truncated or corrupted.
[root@fuel tmp]# dockerctl backup
DEPRECATION WARNING: file /etc/fuel/client/config.yaml is found and will be used as a source for settings. However, it deprecated and will not be used by default in the ongoing version of python-fuelclient.
Reading container data...
Committing fuel-core-6.1-nginx...
605e3bdfeec9f0d89246617b03d5500c19cc7655e69e1ddbfc393328d1b09c19
[...]
Saving fuel-core-6.0-postgres...
Archiving system folders
tar: Removing leading `/' from member names
Compressing archives...
Failed to malloc ckbuf in hash_search
Cannot allocate memory
Fatal error - exiting
Cleaning up...
Backup complete. File is available at /var/backup/fuel/backup_2015-03-05_2303/fuel_backup_2015-03-05_2303.tar.lrz
[root@fuel tmp]#
Bogdan, what's the spec of your VM you used to generate this bug? I just want to know so I can reproduce. I can add a check, but there needs to be a way to back up even if there is little memory.