Deployment Architecture

What is the retention period and volume limit on reserved copies in multisite indexer clustering

keerthana_k
Communicator

Hi,

Splunk documentation mentions that in case of site failure in a multisite indexer clustering deployment, the master maintains reserved copies of data to be assigned to peers of the non-functional site once it starts functioning again. Is there is any restriction on the time period upto which the reserved copy is kept alive waiting for the site to be up again? Similarly, is there any volume restriction for the same?

Thanks,
Keerthana

0 Karma

Masa
Splunk Employee
Splunk Employee
  1. Site1 and Site2 exisit, at this point all copied buckets of site2 are available in site1
  2. CM identify all CPs on Site2 become Down
  3. at this point all copied buckets of site2 are still available in site1 => The copied buckets are available until retention policy (size or time) is hit

For more information about retention policy, I recommend to read doc starting from here.
http://docs.splunk.com/Documentation/Splunk/6.5.0/Indexer/Configureindexstorage

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...