I have a server running on the cloud that's doing great, and I want to duplicate it so another developer can work on the system without mucking with my server.
I created a fresh VM from the LAMP appliance, ran the tklbam-init function with my api key, and ran the tklbam-restore (id) command... and now I'm waiting.
The backup itself is 1.2gb compressed, about 3.4gb uncompressed. The Local Virtual Machine I made was provisioned with 1gb of ram and 8gb of HDD space.
The restore process appears hung, it's still working (I think) and the last line says: "IOError: [Errno 28] No space left on device.
I'm curious why 8gb of storage isn't enough to restore my 1.2/3.4gb backup server? The Appliance running on the cloud is the same one I created my VirtualBox image from (LAMP). Is this an error message I can ignore, or is the restore process effectively "hung" at this point?
I can't leave my computer on overnight, so I have to wait till tomorrow to try to run the command again. I saw another thread on here about tklbam-restore commands taking a while, they suggested a binding for the /tmp/mnt directory... but it's unclear to me whether or not these commands will help me trying to restore the Cloud image to my local VM.