I don't think there is one answer for you MJ1, but here are some points to consider:
- Are you low on free space? If you have plenty of available space then why bother with reclaiming?
- Reclaim uses resources on the array. Do you always have the back-end resources freely available or is the back-end busy with production load some times. This is a scheduling related consideration and you are looking at when in the week will be best to avoid any performance impact.
- Reclaim takes time. You should be aware of the how much time you can expect a reclaim operation to take if you are going to want to run it regularly, so consider setting aside some quite time where you can run a reclaim and assess its elapsed time and its effect on the utilization of your array resources. Once you have a handle on this information, it can help inform you how to go about effectively scheduling reclaim activities should the need arise.
PedalHarder
3 Apprentice
•
465 Posts
0
March 20th, 2018 15:00
I don't think there is one answer for you MJ1, but here are some points to consider:
- Are you low on free space? If you have plenty of available space then why bother with reclaiming?
- Reclaim uses resources on the array. Do you always have the back-end resources freely available or is the back-end busy with production load some times. This is a scheduling related consideration and you are looking at when in the week will be best to avoid any performance impact.
- Reclaim takes time. You should be aware of the how much time you can expect a reclaim operation to take if you are going to want to run it regularly, so consider setting aside some quite time where you can run a reclaim and assess its elapsed time and its effect on the utilization of your array resources. Once you have a handle on this information, it can help inform you how to go about effectively scheduling reclaim activities should the need arise.