# Endpoint 7.13 migration to 7.13.1 Lesson learned with Fleet “On-Prim” -Bad

**URL:** https://discuss.elastic.co/t/endpoint-7-13-migration-to-7-13-1-lesson-learned-with-fleet-on-prim-bad/275343
**Category:** Elastic Security
**Tags:** fleet
**Created:** [June 8, 2021, 7:31pm UTC](https://discuss.elastic.co/t/endpoint-7-13-migration-to-7-13-1-lesson-learned-with-fleet-on-prim-bad/275343 "2021-06-08T19:31:55Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![ferullo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ferullo/32/74240_2.png) [@ferullo](https://discuss.elastic.co/u/ferullo)
#### Post date: [June 23, 2021, 3:23pm UTC](https://discuss.elastic.co/t/endpoint-7-13-migration-to-7-13-1-lesson-learned-with-fleet-on-prim-bad/275343/16 "2021-06-23T15:23:13Z")

</div>

I tried both. When looking into this other, similar issue ([Elastic Agent filling up disk space with logs, disaster](https://discuss.elastic.co/t/elastic-agent-filling-up-disk-space-with-logs-disaster/276668)) I stumbled upon an issue that _could_ have been what caused the disk size issue you saw, we'll put in a mitigation for that.

---

_[View the full topic](https://discuss.elastic.co/t/endpoint-7-13-migration-to-7-13-1-lesson-learned-with-fleet-on-prim-bad/275343)._