Add chapters for session 946320769 (Haiku)

chapters/946320769.json

@@ -0,0 +1,12 @@
+[
+  {"timestamp": "2:44", "title": "Red Hat 8 to Red Hat 9 Migration Strategy", "summary": "Three options for migrating enterprise cluster with edges from RHEL8 to RHEL9: (1) Add new servers to cluster (problematic due to Doctor replication ID mismatch); (2) Build a second Doctor system disconnected from current production; (3) Fresh build with import/export, losing audit logs and tracking tables. Doctor approach recommended to preserve historical data and test safely."},
+  {"timestamp": "9:34", "title": "Zero Downtime Upgrade vs OS Migration", "summary": "ZGU keeps same database with replicated schemas and maintains service during ST version updates. OS upgrade requires separate databases via Doctor model and requires disruption. Future ZGU may enable OS upgrades but not currently supported."},
+  {"timestamp": "14:23", "title": "Infrastructure Checklist for Server Migration", "summary": "Critical non-database items often missed: storage mounts must match exactly, DNS resolution must work identically, LDAP/SSO whitelists need new server IPs, firewall rules must allow new servers, folder monitors need mounted paths on all nodes. Test environment rehearsal strongly recommended before production cutover."},
+  {"timestamp": "24:43", "title": "SMB Connector and Protocol Limitations", "summary": "SMB connector enables cloud-to-ground file transfers via dynamic mount/dismount per file. Not suitable for high-volume transfers (>100 files/hour); resource-intensive protocol. For large files or high throughput, CFT (Secure Transport's smaller sibling) recommended as hop server for guaranteed delivery and better performance."},
+  {"timestamp": "31:42", "title": "SFTP Authentication Timeout Troubleshooting", "summary": "Five-minute SSH authentication timeout suggests firewall/load balancer idle timeout, not ST issue. ST uses Maverick SSH libraries (RFC-compliant, stricter than OpenSSH). Recommendations: test edge-to-server manually from correct IP, verify target server type, contact partner about SSH implementation compliance."},
+  {"timestamp": "36:55", "title": "Maverick vs OpenSSH Implementation Differences", "summary": "ST's Maverick libraries strictly follow RFCs, while OpenSSH is more flexible with noncompliant implementations. RSA SHA-512 signature validation delays possible if partner server noncompliant. If SSH test via edge succeeds but SFTP fails, likely partner server issue."},
+  {"timestamp": "40:02", "title": "Transfer Site Routing to Multiple Destinations", "summary": "When routing to SSH and Windows UNC path simultaneously, UNC path 'not found' errors suggest credentials or path resolution issue from Linux ST server accessing Windows share — not a desktop-to-Windows communication issue."},
+  {"timestamp": "42:16", "title": "Linux ST Server Accessing Windows Network Paths", "summary": "ST is a Linux application reaching Windows shares, not Windows-to-Windows SMB. Troubleshooting: manually test from ST server OS level, verify typos and capitalization (Linux case-sensitive), test with FQDN or IP if short hostname fails, confirm port access on Windows server."},
+  {"timestamp": "46:58", "title": "Account Maintenance Application Configuration", "summary": "Only one Account Maintenance application per system; cannot run multiple with different thresholds. Workaround: single app with multiple day values (e.g., 30,55,60) in same field for multiple warnings. Use high values (9000+) to prevent unintended triggering. If server down on scheduled day, notifications skip until next occurrence."},
+  {"timestamp": "51:18", "title": "Certificate Management in Clustered Environments", "summary": "In clusters behind load balancers, certificate hostname is typically the load balancer, not individual servers. Subject alternative names include server hostnames. Certificates migrate cleanly without renewal during server replacement when DNS name remains unchanged."}
+]