Dual Visibility Configuration Available for Zero-Downtime Migration
infoTemporal Server v1.21 introduces Dual Visibility capability to enable migration from one Visibility database to another without service interruption. This is critical for upgrading Visibility infrastructure or migrating from standard to advanced Visibility.
Need to migrate Visibility store from one database to another (e.g., from standard to advanced Visibility, or between different database types) while maintaining service availability
1. Verify Temporal Server is version 1.21 or later for Dual Visibility support. 2. Plan migration strategy including target Visibility database selection. 3. Set up new Visibility store with proper schema and configuration. 4. Configure Dual Visibility in Temporal Service to write to both old and new stores. 5. Monitor both Visibility stores for consistency and performance. 6. Allow sufficient time for new store to populate with current data. 7. Validate query results match between old and new stores. 8. Switch read operations to new Visibility store. 9. Monitor for any issues with query performance or results. 10. After validation period, disable Dual Visibility and remove old store configuration.