# 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:** [4월 4, 2016, 5:12오후 UTC](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017 "2016-04-04T17:12:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [4월 5, 2016, 11:32오전 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)

---

_[View the full topic](https://meta.discourse.org/t/cant-upload-backup-run-out-of-disk-space/42017)._