<p>We have isolated the issue to a crone job connected with the Remote Backup Plugin for Craft.</p>
<p>Commenting out the following stops the daily backup.</p>
<pre><code># /home/forge/www.example.com/craft remote-backup/volume/create
# /home/forge/www.example.com/craft remote-backup/volume/prune
</code></pre>
<p>I think there is an issue with trying to connect to the remote storage location.</p>

CC BY-SA 4.0
2021-03-31T07:18:27.737Z
2021-03-31T07:18:27.737Z
Dan Lee
<p>Since updating Craft CMS to the latest version I noticed that our uploaded files get backed-up daily to temporary storage. Uploaded files live on DigitalOcean Spaces so we have no need to back up these files to the same server Craft CMS resides on.</p>
<ul>
<li>Files are stored on the following path: <code>storage/runtime/temp/tfxrsolmuf/images</code></li>
<li>This caused us to go over our allotted disk space and cause the server to go down</li>
<li>The backup is happening daily</li>
<li>Using Craft 3.6.10</li>
<li>We use the DigitalOcean spaces volume plugin</li>
</ul>
<p><a href="https://i.sstatic.net/zbtoo.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zbtoo.png" alt="enter image description here" /></a></p>
<p><a href="https://i.sstatic.net/rTFhZ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/rTFhZ.png" alt="enter image description here" /></a></p>

CC BY-SA 4.0
2021-03-30T21:57:11.493Z
What types of files exist inside of those 10 random character folder names? Images? The only place I can see in Craft that writes a random folder to the `storage/runtime/temp` folder is when restoring a database backup.
Brad Bell
CC BY-SA 4.0
2021-03-31T07:13:58.743Z
Hi @BradBell - that is correct inside each folder is our assets. Images and file uploads etc...
Dan Lee
CC BY-SA 4.0
2021-03-31T17:27:39.303Z
@DanLee as an aside, I'd recommend running some sort of [daily cron script](https://www.linuxjournal.com/content/tech-tip-send-email-alert-when-your-disk-space-gets-low) which alerts you if disk is getting low... say 80% full so your server doesn't accidentally go down again.
RitterKnight
<craft3><assets><digitalocean>
Craft CMS - 3.6.11.1 - Why are Assets Backed Up to Temporary Storage?
# Craft CMS - 3.6.11.1 - Why are Assets Backed Up to Temporary Storage?

(Asked by: username_0 on 2021-03-29)

Since updating Craft CMS to the latest version I noticed that our uploaded files get backed-up daily to temporary storage. Uploaded files live on DigitalOcean Spaces so we have no need to back up these files to the same server Craft CMS resides on.

* Files are stored on the following path: `storage/runtime/temp/tfxrsolmuf/images`
* This caused us to go over our allotted disk space and cause the server to go down
* The backup is happening daily
* Using Craft 3.6.10
* We use the DigitalOcean spaces volume plugin

[![enter image description here](https://i.sstatic.net/zbtoo.png)](https://i.sstatic.net/zbtoo.png)

[![enter image description here](https://i.sstatic.net/rTFhZ.png)](https://i.sstatic.net/rTFhZ.png)

**Tags:** craft3, assets, digitalocean

> **Comments:**
> **username_1**: What types of files exist inside of those 10 random character folder names? Images? The only place I can see in Craft that writes a random folder to the `storage/runtime/temp` folder is when restoring a database backup.  
> **username_0**: Hi @BradBell - that is correct inside each folder is our assets. Images and file uploads etc...  
> **username_2**: @DanLee as an aside, I'd recommend running some sort of [daily cron script](https://www.linuxjournal.com/content/tech-tip-send-email-alert-when-your-disk-space-gets-low) which alerts you if disk is getting low... say 80% full so your server doesn't accidentally go down again.  

---

## 1 answers

### Answer by username_0 on 2021-03-31. Score: 1

We have isolated the issue to a crone job connected with the Remote Backup Plugin for Craft.
Commenting out the following stops the daily backup.
# /home/forge/www.example.com/craft remote-backup/volume/create
# /home/forge/www.example.com/craft remote-backup/volume/prune

I think there is an issue with trying to connect to the remote storage location.


---

