Editing Category:DESHWAL (section)

==Training on Deshwal Project Part 2. Dated 02 JULY 2025 - Tetra Support Staff - TUSHAR==

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

'''Video summary:''' "Deshwal Project Training Part 2" -- continues directly from Part 1, this time covering the operational deployment/release process rather than initial setup. Walks through the staging deployment procedure: VPN into the private staging server IP, run a pre-existing sync script to keep required files intact, then use Jenkins (a free-style project pulling from a specific Git branch/repo via stored credentials, deploying into the document root) to trigger a build -- explicitly warning never to click "Build Now" or "Delete Now" except when specifically instructed, since it deploys whatever code state currently exists, clean or not -- and finally verify the deployed site loads correctly via its URL/credentials. Production deployment mirrors staging but with different server IPs, plus an extra step: SSH to the F1 production server to run a script that syncs a specific set of files from staging into production, since some config isn't carried automatically. Covers a one-time full config backup already taken to Tetra's own S3 bucket (with the exact command used and date logged) as a safety net, and a separate, ongoing CommVault-driven backup regime run by the client's own backup team: proxy servers get a one-time backup only (rarely change), app servers get a weekly snapshot (Sunday 1am, 30-day retention, 4 copies always available), and the DB servers get both incremental backups (daily Monday-Saturday, 7-day rolling retention) and full weekly backups (Sunday 1am, 14-day retention, 2 copies), including filesystem and database data in both. Lists CommVault-side contacts to reach for backup mode changes or restores, and the client-side point of contact for general project queries. Also covers setting up VPN access via a provided client installer, and briefly introduces the Nagios-based monitoring setup on Tetra's monitoring server, which pulls metrics from each server via a proxy-server relay using custom host/service/command config files (also backed up to S3 for reuse in future deployments).