Editing Category:BEETEL (section)

==Training session on Beetel Project 16 Feb 2024 - Tetra Support Staff - Manish Singh==

{{#ev:youtube|RstBXABJjC8|640}}

'''Video summary:''' "Beetle KT" -- a Hindi-language infrastructure-background KT for Beetel, complementing the "Beetel Project" troubleshooting video with the physical layout and access model. Beetel runs two physical host machines (BM1 and BM2). BM1 hosts four VMs: the NF database, the "SDNet" server (the Java/JBoss website Tetra fully supports -- config, install, backup, and snapshots all owned by Tetra), PM Tools, and Partner Portal; BM2 hosts a single VM for a separate Axis Bank server. Tetra's actual support scope is narrow: only the SDNet server itself (application + database backups); the other VMs on BM1/BM2 were provisioned by Tetra as a one-time project delivery but are now the client's (or the client's own downstream client's, in the Axis Bank case) responsibility to back up and maintain. Snapshots for all VMs on BM1 are stored on BM2 (and vice versa was considered during migration planning but rejected in favor of just cross-host snapshot storage, not full replication) on a monthly schedule. Explains the access model in detail: Tetra's VPN IP is allow-listed only on the SDNet server itself, so direct SSH/PuTTY access is limited to that one box; reaching any other VM (Windows servers, etc.) requires a separate Beetel-provided VPN client that routes into a Cockpit-based web GUI, through which individual VMs can be opened/managed -- this is also how Windows-specific issues (e.g. copy-paste not working, permission fixes) get handled, since Cockpit is the only path to those machines. Repeats and adds detail to the SDNet server's backup mechanism already covered in "Beetel Project": application (JBoss) and database backups are each driven by their own cron-scheduled script under `/root/scripts`, written as `.tar` archives into local `_backup` directories (JBoss: max 4 backups retained via `mtime`-based cleanup, run monthly on the 1st; database: 7-day retention) and then rsynced out to an 11TB Windows-server directory mounted locally over the network for offsite retention.