I have this retention settings like this
maxHotBuckets = 3
frozenTimePeriodInSecs = 48211200
maxTotalDataSizeMB = 1000000
I found out that the buckets were timed by the size and not the date.
I changed the maxTotalDataSizeMB and restored the old buckets to a restore directory.
I CP -rp the old buckets to the production firewall/db directory but I am not seeing the logs in the UI.
Do I need to restore to the "colddb" or "thaweddb"?
Can I just copy the buckets back into the production db?
Do I have to restart splunkd to read the data in the buckets?
In addition to that, you don't need to restart splunk when you move functional buckets to a production db, because splunk will automatically update the manifest over time. If you want the data immediately, then a restart will do that.
So the above answer is for archived data. that is archived by splunk.
In my case I do a full back of the index files every month. Thanks to support guru "Joshua Backing" I found out that if you restore live buckets from tape and the bucket ID dose not conflict with any other live bucket you can just copy the bucket back to the /indexname/db directory then stop and start splunkd and whala the data is viable.
I did notice that many of the buckets moved to the /indexname/colddb right away. Again thanks to Joshua, he said this could be for normal more than 300 warm bucket rotation. the data is still searchable and will not be rotated out of the database until the size or time policy is reached.
Thanks again Joshua Splunk Support Rules
just make sure that you increase the retention time/index size limits of the index before you copy the buckets back, otherwise the bucket will be dropped once again...