Probe Redis and understand mirror versus primary

Where: Protection → Country / ASN and Redis

Steps

1. Keep Redis primary OFF until installed-service validation is complete.
2. If the host supports the required local loopback Redis runtime, enter the supported connection options privately.
3. Use the explicit saved-configuration probe and inspect temporary-key/script/expiry/cleanup results.
4. Distinguish SQL-authoritative mirroring from optional primary reservation counters.
5. Before enabling primary, test outage, eviction, restart, concurrent requests and failover on an isolated actual installation.

Check the result

Mirroring adds Redis work without reducing SQL counter writes. Primary uses durable SQL reservations in blocks of 16; failover can use conservative upper bounds and restrict earlier.

If it does not work

The probe does not certify production concurrency/performance. Missing existing-window keys are not reinitialised to grant a fresh allowance. Shared hosting without this service should retain SQL counting.