# Can't upload backup - run out of disk space

**URL:** https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017
**Category:** Development
**Created:** [Abril 4, 2016, 5:12pm UTC](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017 "2016-04-04T17:12:00Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![precessor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/precessor/32/120664_2.png) [@precessor](https://meta.discourse.org/u/precessor)
#### Post date: [Abril 4, 2016, 5:12pm UTC](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017/1 "2016-04-04T17:12:00Z")

</div>

I’ve followed the instructions ([this](https://github.com/discourse/discourse/blob/master/docs/VAGRANT.md) and [this](http://blog.discourse.org/2013/04/discourse-as-your-first-rails-app/)) to get a local developer Discourse running. It seems to have worked, and I am browsing at `http://localhost:4000/` as admin. I would now like to upload the backup of my working cloud Discourse (a new install on DigitalOcean, the backup file is only about 4MB). The plan is to hack away on the local version.

My backup upload fails with

**“There has been an error while uploading ‘my-discourse-2016-04-04-131830.tar.gz’: There is not enough space on disk to upload this backup.”**

Back to the local developer Discourse, here is an image of the output from the ssh to the VirtualBox VM when I try to upload the backup (I am not sure if it will help):

 ![](https://global.discourse-cdn.com/meta/original/3X/7/6/764256c600c9fa734905ede809de512244b7a66d.png)

I am not sure how to proceed - any ideas?

---

<div class="post-metadata">

### Author: ![precessor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/precessor/32/120664_2.png) [@precessor](https://meta.discourse.org/u/precessor)
#### Post date: [Abril 5, 2016, 11:32am UTC](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017/2 "2016-04-05T11:32:18Z")

</div>

This issue remains **not solved** , but here’s my workaround for getting the Discourse backup into the VM.

1. [Get your VM up: Start Github, open Git shell, `vagrant up`, `vagrant ssh`]
2. Start Filezilla on your host.
3. Connect to 127.0.0.1:2222 via SFTP with username: _vagrant_ and password: _vagrant_
4. Copy the Discourse backup to `/vagrant/public/backups/default`
5. Back in the Git shell, start the rails instance `bundle exec rails s -b 0.0.0.0`
6. In browser `http://localhost:4000/admin/backups` see your backup listed.
7. Click restore (assuming in Discourse Settings, “allow restore” is checked)

After successfully uploading and restoring my backup, here’s a `df -Pk`

 ![](https://global.discourse-cdn.com/meta/original/3X/8/5/85fed3cc146fd4ada1b232f699df6d6fb54dafa6.png)

---

<div class="post-metadata">

### Author: ![skozz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/skozz/32/119704_2.png) [@skozz](https://meta.discourse.org/u/skozz)
#### Post date: [Janeiro 13, 2017, 3:51pm UTC](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017/3 "2017-01-13T15:51:48Z")

</div>

Works for me, in my case installing Discourse on my OS X so `/public/backups/default` 👍