# ELK 5.3 - Archive and delete indices
**URL:** https://discuss.elastic.co/t/elk-5-3-archive-and-delete-indices/91285
**Category:** Elasticsearch
**Created:** [June 29, 2017, 1:08pm UTC](https://discuss.elastic.co/t/elk-5-3-archive-and-delete-indices/91285 "2017-06-29T13:08:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Greenie](https://discuss.elastic.co/u/Greenie)
#### Post date: [June 29, 2017, 1:08pm UTC](https://discuss.elastic.co/t/elk-5-3-archive-and-delete-indices/91285/1 "2017-06-29T13:08:07Z")
I am running ELK stack on a single node Windows 2012 R2 server. It was working well until after deploying several winlogbeat clients (about 60 total) at once. The server seemed to be overloaded trying to process all of the logs, so I added RAM and it has been a couple of weeks now and never recovered. I can still search but it is slow and times out most times, but the server performance itself looks to be fine with 4 cores and 64GB of RAM. I read that archiving older indices onto an external drive would help, but I could not find anything through my research explaining how to do this. Any help would be greatly appreciated.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [June 30, 2017, 5:45am UTC](https://discuss.elastic.co/t/elk-5-3-archive-and-delete-indices/91285/2 "2017-06-30T05:45:34Z")
You can't really do what you're asking.
It'd be either you taking a snapshot of older indices and storing them on that disk, or setting up another node with that disk as it's data path.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 28, 2017, 5:45am UTC](https://discuss.elastic.co/t/elk-5-3-archive-and-delete-indices/91285/3 "2017-07-28T05:45:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.