https://community.splunk.com/t5/Getting-Data-In/Can-the-retention-policy-be-based-on-both-time-AND-space/m-p/23520#M3691 <P>Yes. All the configurations are evaluated, and whenever one of them is satisfied, the appropriate data is aged out.</P> Sat, 31 Jul 2010 09:12:03 GMT gkanapathy 2010-07-31T09:12:03Z https://community.splunk.com/t5/Getting-Data-In/Can-the-retention-policy-be-based-on-both-time-AND-space/m-p/23519#M3690 <P>In other words, can I set 30 days OR 700G (for instance)? The docs aren't clear on how to do that.</P> Sat, 31 Jul 2010 08:33:03 GMT https://community.splunk.com/t5/Getting-Data-In/Can-the-retention-policy-be-based-on-both-time-AND-space/m-p/23519#M3690 bfaber 2010-07-31T08:33:03Z https://community.splunk.com/t5/Getting-Data-In/Can-the-retention-policy-be-based-on-both-time-AND-space/m-p/23520#M3691 <P>Yes. All the configurations are evaluated, and whenever one of them is satisfied, the appropriate data is aged out.</P> Sat, 31 Jul 2010 09:12:03 GMT https://community.splunk.com/t5/Getting-Data-In/Can-the-retention-policy-be-based-on-both-time-AND-space/m-p/23520#M3691 gkanapathy 2010-07-31T09:12:03Z