TetraWiki - User contributions [en]

Category:MPSDC (XTRANET)

2026-07-25T02:53:52Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:MPSDC (XTRANET)]]

==MPSDC (XTRANET) KT Session 13-July-2026- Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' KT session on MPSDC/XTRANET's 5-server Zimbra Network Edition infrastructure: two MTA+proxy nodes (ZP1/ZP2, active-active, fronted by the client's own external load balancer -- not something Tetra manages), two mailbox+LDAP nodes (ZM1/ZM2, active-passive in a PCS cluster), and a dedicated archive server. Covers a recent full-stack rebuild -- RHEL 7 to RHEL 9 and Zimbra 10.0 to 10.1.13, driven by accumulated vulnerabilities on the old OS -- done by standing up five fresh RHEL 9 VMs alongside the old server and migrating mail data across via imapsync, keeping the same server naming. Also covers routine issue patterns: application relay-denied errors needing the app's IP whitelisted on both proxy nodes, mail flow via dedicated Trend Micro-hosted MX records for spam filtering on both inbound and outbound, and -- the most detailed part of the session -- the full offline license activation procedure this client requires (unlike most clients' simpler online activation): disabling/permissive-mode SELinux, installing the license daemon package, generating network/license fingerprint files from the server, submitting them through Zimbra's licensing portal to get back an XML activation file, and applying it either via the admin console or the `zmlicense` CLI.

Category:FUSIONHONDA

2026-07-25T02:53:31Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:FUSIONHONDA]]

==Training session on FUSIONHONDA ZIMBRA BSP & ENERGO Project 22 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' This session covers the shared Zimbra mail server (v10.1.10, soon upgrading to 10.1.20) hosting multiple client domains including Energo Construction, Energo Products, Fusion Hyundai, HACO India, and SCS.net/Shrop Charity. Topics covered: S3 object storage configuration for the message volume, SOGo security integration for inbound/outbound mail (including the required Postfix master.cf entry for mail delivery to work), setting up delegated (domain-scoped, not global) admin accounts via zmprov, per-client mailbox and domain storage quotas, and account provisioning/deletion as the routine day-to-day support request pattern for this server.

Category:BHUTAN

2026-07-25T02:53:30Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:BHUTAN]]

==Training on Bhutan Project. Dated 16 July 2026 - Tetra Support Staff - Takshay==

{{#ev:youtube|5XgqXqA_1YY|640}}

'''Video summary:''' Comprehensive KT session on the Bhutan client's migration from a single-server Zimbra open-source install to a full multi-server Zimbra Network Edition cluster. New architecture: two LDAP nodes with multi-master (MMR) replication, two MTA+proxy nodes, a single mailbox server, a single archive server, a dedicated LDAP/license-daemon node, and two HAProxy+keepalived nodes providing a shared virtual IP as a load balancer in front of the proxy pair (so either proxy can fail without users noticing). Covers building MMR replication between the two LDAP nodes (each pointing to the other as its replication master), the archiving setup (a dedicated, mail-only Class of Service with an auto-created per-user archive account that silently BCCs a copy of every inbound/outbound mail, restored via export from the archive account and import back into the user's mailbox when needed), and the live migration itself -- moving each of the ~400-500 mailboxes one at a time via `zmmboxmove` with the sync happening in the background so users see no disruption. Cutover was done by repointing the HA virtual IP's DNS to the new setup and updating the Barracuda relay IP configuration for external in/out mail; the old single server was then decommissioned via `zmprov deleteServer` once every account was confirmed moved off it. Only client-specific customization requested afterward was their own logo on the Zimbra login/webmail interface.

Category:INFOSYS DGRAM ELK

2026-07-25T02:53:28Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:INFOSYS DGRAM ELK]]

==Training on INFOSYS DGRAM ELK KT Part 1. Dated 05 June 2026 - Tetra Support Staff - Prashant==

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

'''Video summary:''' Part 1 of the INFOSYS DGRAM ELK KT (see Part 2, 6IrkurBVESg, for the deeper data-flow explanation). Gives the fuller device-coverage picture for the 19-node observability cluster: roughly 400-900 monitored assets spanning Linux/Windows servers, network devices (Juniper routers, Aruba switches), storage arrays (NetApp done via SNMP; a Pure Storage array not yet integrated because the vendor declined to cooperate), and a range of security devices -- Fortinet sandbox, web proxy, DLP, and F5 load balancers, only partially onboarded because the client's security team hasn't enabled SNMP access on some of them yet. Explains the two integration patterns used: for devices Elastic has an official "out-of-the-box" integration for (e.g. Palo Alto next-gen firewalls), logs flow in with minimal setup once Elastic Agent is pointed at them; for devices that can't be integrated directly (older network/security gear), an intermediate collector server receives the device's SNMP/syslog output and runs Elastic Agent itself to forward that on into the cluster.

==Training on INFOSYS DGRAM ELK KT Part 2. Dated 05 June 2026 - Tetra Support Staff - Prashant==

{{#ev:youtube|6IrkurBVESg|640}}

'''Video summary:''' Part 2 of a KT session on the ELK-based observability platform built for the Infosys DGRAM project. Explains the basic data flow taught by analogy to Prometheus+Grafana: an Elastic Agent installed on each monitored server collects logs/metrics and ships them to Elasticsearch, which Kibana then queries to render dashboards (Logstash sits optionally in between as a filtering/transform pipeline, but isn't heavily used here since Elastic Agent already does most of that collection work natively). Describes the two clusters built for this client: a smaller "search cluster" (8 nodes: 3 combined master+data Elasticsearch nodes, 1 machine-learning-role node, 2 Kibana, 2 Logstash) and a much larger 19-node "observability cluster" (11 Elasticsearch nodes including warm-tier nodes plus 3 machine-learning-role nodes, 2 Kibana, 2 Fleet servers, 2 APM nodes, 2 Logstash). Also introduces Fleet, Elastic's centralized agent-management service, which lets them configure and monitor every Elastic Agent across the fleet from one place (a handful of commands to enroll a new agent) rather than configuring each server's agent by hand.

Category:DRUSHTI

2026-07-25T02:53:27Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:DRUSHTI]]

==DRUSHTI KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' KT session on Drushti, described as the very first BSP client Tetra ever onboarded. Unlike most BSP clients, Tetra's support scope here is narrow and specific: Drushti runs its own single Zimbra Business-edition server (Ubuntu 22) that Tetra does not manage day-to-day -- support is limited to the Zert license-monitoring agent and license-activation issues only, contacted through an intermediary (Nitin), since Drushti itself is downstream of another party in the resale chain. Covers Zert's install requirements (small VM, ~1GB RAM, 50-60GB storage, must have port 389 LDAP connectivity to the Zimbra server) and the standard fix when license usage stops reporting correctly after the client restores their Zimbra server from backup onto new hardware: since Zert licenses are tied to a device ID, the old (now-orphaned) device ID has to be deleted/deactivated in the Zimbra BSP portal and a fresh one created and reactivated for the rebuilt server.

Category:JVINTERNATIONAL

2026-07-25T02:53:25Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:JVINTERNATIONAL]]

==JVINTERNATIONAL KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' KT session on JV International's mail setup, which moved away from being self-hosted entirely: originally on a qmail/Postfix-based stack, then migrated (about a year and a half before this recording) to Google Workspace (G Suite) with just a single paid mailbox (their other few IDs were dropped). Covers the difference between Google Workspace's normal user login and its separate admin-console URL/login, how their storage plan (100GB) doesn't match Google's standard published tiers because it predates current pricing, and the data migration approach -- Google discontinued raw IMAP-client-based syncing for admins, so migration is now done through a built-in tool in the Workspace admin console where you supply the source mailbox server/credentials and Google handles an exact, complete sync (avoiding the duplicate/missing-mail issues that plain imapsync could produce). Cutover itself was a standard MX and SPF record update. Since going live, this client's mail has needed effectively zero support -- no complaints, described as a "set and forget" account precisely because Google Workspace doesn't have the kind of operational issues a self-hosted mail server would.

Zimbra BSP Implementation=edit

2026-07-25T02:53:24Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:Zimbra]]

==Zimbra BSP Implementation Complete Handover KT Session. Dated 13 JULY 2026 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' General handover/training session covering the overall Zimbra BSP (Business Support Plan) process end-to-end, rather than one specific client. Recaps the 4 COS editions (Business/Business Plus/Standard/Professional -- all current clients are on Business) and the standard practice of creating and assigning the correct Class of Service as each domain's default so users don't drift onto a pricier tier by accident. The bulk of the session is a walkthrough of the internal Zimbra BSP monitoring portal used to track every client's license usage against what they've purchased, including why SysNet Global and ISON BPO are tracked under a separate "organization" in that portal from the rest of the client base (a different, discounted pricing arrangement, not a technical difference) -- and a live correction of a data-entry mistake found in that day's usage numbers. Also covers the daily license-usage report spreadsheet emailed each morning and evening by the on-shift engineer, and how to pull a specific past month's usage report (e.g. end-of-June) when the sales team needs it for billing.

Category:Rahul Chaudhary

2026-07-25T02:53:23Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:RAHUL CHAUDHAY]]
[[category:Zimbra]]

==Rahul chaudhry ISP KT session. Dated 13 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' KT session on a dual-ISP failover setup built for the Rahul Chaudhry client's on-premise Zimbra mail server, which has two separate ISP links (two different public IPs) and wanted automatic failover if either link went down. Solution: a new dedicated front-end server running HAProxy, configured to load-balance all mail/web ports (443, 25, 587, 143, 993, 110, 995) roughly 50/50 across both ISP-facing IPs in normal operation, continuously health-checking the backend and shifting all traffic to the surviving link if one becomes unreachable -- verified by deliberately taking each link down in turn during testing. Also covers: Let's Encrypt SSL via certbot for the HAProxy frontend, moving DNS management for the domain over to the company's own account after recurring access problems with the client's original registrar, setting up dual MX records (different priorities, one per ISP-facing IP) so inbound mail also has a fallback path, and a note on the client-side firewall config needed for outbound failover plus keeping the SPF record in sync with whichever public IP outbound mail is actually leaving from.

Category:NEWSNATION

2026-07-25T02:53:22Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

==Newsnation_BSP_ImplementationS KT session . Dated 13 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' KT session on NewsNation's migration from Zimbra open-source to Zimbra Network Edition (Business Support Plan, Business-tier COS). Covers the standard BSP setup pattern (create the correct Class of Service and set it as domain default before license activation, so new accounts don't default to the pricier Professional tier), password migration via a zmprov batch script generated from the old server's password list, and mail data migration via multiple parallel imapsync batches for their ~645 users. The bulk of this session focuses on their specific two-node DRBD storage cluster: one node ("n1") was rebuilt on Rocky Linux 8 with only the Zimbra software packages installed (not a full Zimbra init) while the live node ("n2") stayed up, DRBD was reconfigured to keep the underlying disk in sync between both nodes so either can mount and take over as primary if the other fails, then the roles were swapped and the second node rebuilt the same way. Also covers installing Zert, Zimbra's own license-usage monitoring tool (via an LDAP connection back to the mail server), and the shared daily report spreadsheet that shift engineers use to track every BSP client's license usage against what they've actually purchased across all client organizations.

Category:STL FASTENERS

2026-07-25T02:53:21Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:STL FASTENERS]]

==STL FASTENERS Project Handover KT. Dated 25 Aug 2025 - Tetra Support Staff - Tushar==

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

'''Video summary:''' [NO TRANSCRIPT AVAILABLE] "STL FASTENERS Project Handover KT" -- no captions exist for this recording. Based on the title, this is a knowledge-transfer handover session for the STL Fasteners client's project (dated 25 Aug 2025 per the wiki page), likely covering their server/mail setup for whoever is taking over support.

Category:JIL

2026-07-25T02:53:20Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:JIL]]

==Training about JIL project. Dated 23 January 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' Architecture training on JP Associates/JIL's Zimbra Network Edition setup, which is unusual in that it's really *two* separate multi-server Zimbra clusters (one for ~1650 users, one for ~500) sharing the same external domain. Each cluster has active-active MTA pairs, multi-master LDAP replication (MMR, not the default single-master replica type), an active-passive PCS-clustered mailbox pair, plus its own archive and log server, fronted by HAProxy for high availability. Internal mail between the two clusters routes MTA-to-MTA based on domain-level split routing rules; if a user isn't found on one cluster the mail retries against the other before bouncing. External-facing access goes through a separate single-URL server running an Nginx + Python/Flask app that looks up which cluster a given user's mailbox lives on and redirects the login accordingly (mobile/IMAP/POP/ActiveSync instead go directly through per-cluster virtual IPs, since the single-URL server only handles web/443). Also covers why a dedicated OpenLDAP lookup server was built in front of the Barracuda spam gateway -- Barracuda can't hold two entries for the same domain, so this lookup server independently mirrors valid usernames from both Zimbra clusters so Barracuda can bounce mail for nonexistent users before it ever reaches the mail servers. Full configuration docs and server details for this setup are pointed to on the wiki's own "JIL" special category page.

[[File:Jalindia_cluster_installation_and_configuration.pdf]]

Category:DESHWAL

2026-07-25T02:53:19Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

==Training on Deshwal Project Part 1. Dated 01 JULY 2025 - Tetra Support Staff - TUSHAR==

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

'''Video summary:''' "DeshwalProject Training Part 1" -- a Hindi-language architecture and setup walkthrough for the Deshwal client's LAMP-stack environment (Linux/Apache/PHP/MySQL, plus Jenkins), which has separate Production and Staging environments. Architecture, top to bottom: a public IP/domain NATed to a private IP shared by two DMZ-facing reverse-proxy servers (Proxy 1 primary, Proxy 2 secondary) using keepalived for a floating/virtual IP, so both proxies can receive traffic simultaneously based on load, each configured to prefer its local app server (App1) and fail over to App2 only if App1 becomes unavailable for a defined window; two application servers (App1 primary, App2 secondary) behind the proxies, where App1's attached disk (holding `/data` and `/backup`) is shared out to App2 via NFS -- note this is a direct NFS export from App1 itself, not a separate third-party NFS appliance; and two database servers (DB1 master, DB2 slave) with one-way replication, where App1 always writes to DB1 and manual promotion of DB2 to master is required if DB1 fails. External backups are handled by a separate team using a Commvault backup agent. The session then walks through the actual proxy-server build: installing/upgrading Apache, a redirect vhost that forces all HTTP requests to HTTPS, and a separate reverse-proxy vhost implementing the App1-primary/App2-fallback routing, with the firewall restricted to ports 80/443/56 and keepalived installed only on Proxy 1 in production. On the app server side: mounting the dedicated data disk, storing actual application data under `/data` and symlinking it into the Apache document root (with root ownership, SGID, and group-based permissions so the Apache user can read/write without owning the files), editing the app's DB-connection config, installing PHP and its required packages (noting Ubuntu bundles PHP with Apache, requiring an Apache restart to apply config), and installing phpMyAdmin from a downloaded tarball into a defined path with its own vhost, read-only S3-backed file storage for downloadable assets, and appropriate permissions.

==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).

== '''Deshwal live activity from dev to staging-sify''' ==

http://172.16.20.21:8080
username - Tushar
password - Kalyan123tush@r
login
click DeshwalNew
click Build Now

== '''Deshwal live activity from staging-sify to prod-sify''' ==

app1
http://172.16.20.16:8080
username - Tushar
password - Kalyan123tush@r
login
click DeshwalNew
click Build Now

app2
http://172.16.20.17:8080
username - Tushar
password - Kalyan123tush@r
login
click DeshwalNew
click Build Now

==Training on Deshwal Live Activity Via Jenkins. Date 11 July 2025- Tetra Support Staff - TUSHAR==

{{#ev:youtube|G-XN2eiZdgQ|640}}

'''Video summary:''' "Deshwal Live Activity Via Jenkins (updated 11 July 2025) - TUSHAR" -- a focused, practical live-demo recording of the actual staging and production deployment steps introduced in Part 2, done by a different presenter (Tushar) as a refresher. Connects via a Deshwal-specific VPN profile, opens Jenkins on the staging server (port 8080), clicks the "DeshwalNew" job and "Build Now," confirms a green/successful build, and repeats the same steps against both production application servers (App1 and App2, each running its own Jenkins instance on the same default port) since the environment has two app servers requiring independent builds. After both builds succeed, verifies the deployment by logging into the staging and production site URLs directly with admin credentials to confirm no errors (e.g. database connectivity) before considering the release complete, followed by a status update to the team. Also opens up the Jenkins job's actual build configuration for a deeper explanation: it pulls from the master branch of the Deshwal Git repo using stored credentials, whichever code developers have most recently pushed; the build step is a shell script that first fixes file/folder ownership and permissions, `rsync`s the pulled code into the Apache document root while excluding an "intact" folder (config/data files that must survive each deployment and are instead separately synced back in from a preserved backup location), and runs the `rsync`/`chmod`/`chown` operations with `sudo` because the Jenkins service account needs elevated rights for those specific operations -- with a matching `sudoers` entry granting Jenkins passwordless access to exactly those three commands.

== '''Deshwal code revert activity and daily working process from developer side.''' ==

==================================================================================
ONE TIME CHANGES :
changes done on Git and Github :
git reset --soft <commit-id-previous-version>
git checkout -b production
git checkout -b staging
git reset --soft <commit-id-latest-version>
==================================================================================
REGULAR CHANGES :

Work need to do to Deepika:
==================================================================================
When code is mature on development environment and tested in development, Then need to merge code to staging branch.
git checkout staging
git merge master
NOTE : effect of this will be code will get deployed in staging server.
NOTE : NO NEED TO DO ANY WORK TO SERVICE TEAM.
=================================================================================
When code is mature on staging environment and tested in staging, Then need to merge code to production branch.
git checkout production
git merge staging

'''NOTE :''' effect of this will be code will be get deployed in production server
'''NOTE :''' NO NEED TO DO ANY WORK TO SERVICE TEAM.

==Training on Oxypc CICD Deployment KT DESHWAL. Dated 08 JULY 2026 - Tetra Support Staff - PRASHANT==

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

'''Video summary:''' "Oxypc CICD Deployment KT DESHWAL" -- an English-language KT session on the CI/CD pipeline built for OxyPC, a separate PHP (Yii2 framework) project deployed to `/var/www/html/oxypc`, hosted on GitHub and deployed via Jenkins (chosen over alternatives like GitHub Actions/GitLab CI). Walks through the Jenkins pipeline stage by stage: a checkout-from-SCM stage using stored Git credentials against the main branch (built using Jenkins' "generate pipeline syntax" helper); a code-review/validation stage that runs a PHP lint/syntax check (`php -l`-style check) -- currently commented out on the development pipeline at the developers' request, but still active on staging, demonstrated live by intentionally introducing a PHP parse error and showing the check catch it; a backup stage that snapshots the current deployed code into a dedicated backup directory under `/opt` with its own retention policy before the new code is deployed; the actual deployment stage that syncs the checked-out code to the live path; and a post-deployment stage that emails a designated group (the presenter plus two others) automatically if the build fails. Explains the GitHub webhook integration that makes deployment fully automatic: a developer push to GitHub fires a webhook that Jenkins listens for, which kicks off the entire pipeline (checkout -> validate -> backup -> deploy -> notify) without manual triggering -- noting the presenter doesn't have direct access/credentials to the GitHub webhook config itself (owned by the client's dev team) but can describe the flow. Closes by briefly showing a `sudoers` entry added for the Jenkins user to allow the specific commands the pipeline needs without a password prompt.

Category:BEETEL

2026-07-25T02:53:18Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:BEETEL]]

==Training session on Beetel Project 19 Dec 2023 - Tetra Support Staff - Manish Singh==

{{#ev:youtube|1Clvbt1Vin4|640}}

'''Video summary:''' "Beetel Project" -- a Hindi-language KT session covering support/troubleshooting for Beetel's Java-based website (running on JBoss + Apache httpd + PostgreSQL), originally hosted on a cloud provider and later migrated by Tetra to Beetel's own in-house servers (Tetra retains VPN-based access for support, though day-to-day control sits with Beetel). Establishes the standard troubleshooting sequence for a "site is down" ticket: first check whether the site's front page loads (it may still render by default even if login is broken, so logging in with the help-desk test credentials is required to confirm the app is actually healthy), then check the three core services -- httpd, JBoss, and PostgreSQL -- restarting whichever is down (Apache/Postgres restart cleanly via `systemctl`, but JBoss additionally needs a specific follow-up command/script to fully bring the application back up after a restart). Covers the backup setup in detail: a daily 2am PostgreSQL database backup and a monthly (1st-of-month, 12am) JBoss/application backup, both driven by cron-scheduled scripts stored under root, landing first in a local backup directory (retained 7 days for DB, 4 backups for JBoss, older files auto-pruned by a custom cleanup script) and then rsynced out to a mounted remote Windows backup server share for longer-term retention. Explains how to verify backups are actually landing (checking file dates/sizes under the local and mounted remote backup paths) and flags that very old files sometimes accumulate on the remote mount and may need manual cleanup since retention there isn't automatic. Also references a rough personal migration notes file (IPs, /etc/hosts entries, DB setup steps from the original migration) as background context, explicitly noting it's not needed for day-to-day support -- the three-service-check-plus-backup-monitoring routine is what actually matters for tickets.

==Training session on Beetel Snapshot Understanding - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [SPARSE TRANSCRIPT - long stretches of silence/background music with little captioned speech; summary reflects only the clearly legible portions] "Beetel Snapshot Understanding" -- an English-language walkthrough of the KVM/libvirt-based VM snapshot and recovery mechanism used for Beetel's ~5-6 VMs. Explains the core approach: each VM's disk state is defined by an XML domain file (used to recreate/register the VM automatically if its host goes down); a script triggers `virsh`-style snapshot creation, which redirects new writes to a temporary overlay disk while the original base disk stays untouched and consistent; a nightly "block commit" operation (taking roughly 35 minutes) then merges the accumulated changes from the overlay back into the base disk. For resilience, each host's VM snapshots/backups are stored on a different physical machine rather than locally -- e.g. one host's ("55") snapshot backups land in a specific data/snapshot path on another host ("54"), and vice versa -- so a host failure doesn't take out its own backups with it. Access to the environment is via a VPN client requiring a one-time password emailed on connect, plus a separate web UI for direct VM console access. Given the heavy audio gaps in this recording, finer procedural detail (exact commands, snapshot restore steps) could not be reliably captured -- this summary reflects only what came through clearly.

==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.

==Beetel Database Change Activity for Each Financial Year 01 Sep 2025 - Tetra Support Staff - Tushar Sonawane==

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

'''Video summary:''' "Beetel database change activity for each financial year" -- a short, guided screen-share walkthrough (via remote-desktop tool) of a recurring annual maintenance task for the Beetel system: updating a database "system code" record that stores the current financial year. The presenter talks a colleague through navigating the admin/database interface: searching for the "system" table/section, browsing through paginated records to locate the specific financial-year entry, editing it, and changing the year value from "2024" to "2025" (both the primary field and a "last modified" date field), then saving. Confirms the change took effect by logging into the site afterward and checking it reflects the new financial year. This is a narrow, single-purpose recurring runbook task -- there is no broader architectural or troubleshooting content in this recording beyond the step-by-step navigation to make this one annual change.

==RCA Beetel Year End DB Activity==

1) Connect NextExtender VPN

2) '''Connect DB'''

'''Url - https://192.168.12.23/phpPgAdmin/'''
'''username - postgres'''
'''password - HGVR_#dzsds3@'''

3) click on bttindia

4) click on public

5) search systemcode

6) click on systemcodes

7) click on browse

8) go on 27 number page

9) check for FINYR

10)click on edit

11) change the all value from 2024 to 2025 this done in year 2025 , change current financial year.

12) save

13) login to website and check

14) http://192.168.12.23:8080

15) username : HELPDESK

16) password : helpdesk

==Training on BEETEL ORCLE DATA BASE. Dated 20 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' "BEETEL ORCLE DATA BASE KT SESSION" -- a Hindi-language handoff KT specifically about Beetel's Oracle database server, which previously ran on an aging physical machine (circa 2003-2004 hardware). To eliminate the single-point-of-failure risk of that old hardware, the presenter P2V'd it: took a full disk image of the physical server (a QCOW2 image, visible mounted via NFS in the hypervisor's storage) and imported/ran it as a VM inside a Proxmox VE cluster (referred to as "PRX"), with the original physical server kept powered off and untouched as a fallback (since both share the same IP, only one can be online at a time -- if a rebuild is ever needed, the physical box can simply be powered back on). Walks through the actual recovery/access procedure step by step: log into the Proxmox web UI (root credentials provided), select and start the Oracle VM from the console if it isn't already running, then reach the application's web frontend on a specific port found via `netstat -antp` on the guest (in this case landing on port 9000, one of several Java service ports tried) using the client's own application login. Confirms VM specs (2 vCPU, 8GB RAM) via the Proxmox hardware/summary tabs. This is a narrow, single-purpose recording -- its only content is how to locate, start, and reach this one P2V'd Oracle database VM in an emergency, not general Beetel infrastructure (which is covered in the separate "Beetel Project" and "Beetle KT" videos).

Category:Technology Eng-Onboarding

2026-07-25T02:53:17Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Technology Eng-Onboarding]]

==Technology-Presentation-BB-for Eng-Onboading. Dated 27 Dec 2024 - Biswajit Banerjee==

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

'''Video summary:''' New-engineer onboarding presentation given by Biswajit Banerjee covering Tetra's company history and full technology breadth (not a client-specific support session like most others). History: founded 1995 by four co-founders (the name "Tetra" = four), spun out of a company called PCL, started in hardware sales and Novell Netware deployments in the pre-internet era, moved into Linux around 1997-98, built early internet/mail/proxy/Samba solutions for client offices, weathered the Y2K migration, and evolved its mail-hosting stack over the years from sendmail to qmail to Postfix/Zimbra (Zimbra since ~2006-07). Second half covers the company's current scope: hybrid Zimbra + Microsoft 365 deployments, ELK and Prometheus/Grafana monitoring, their own in-house CloudStack private-cloud platform (a major current growth focus), Kubernetes/microservices/DevOps work, their OTRS-based "iHelpDesk" ticketing product, document management via Nextcloud/Alfresco, and custom LAMP-based government/enterprise software projects (notably an "online building plan" application used at scale in West Bengal, Punjab, and Haryana, integrating with third-party scrutiny software and pitched internationally). Closes with a client-name overview spanning large enterprises (Adani, ICICI Bank, NTPC) and SIs (Infosys, HP), framed as context for why new engineers need to stay comfortable picking up new technology rather than specializing narrowly.

Category:MPPOLICE

2026-07-25T02:53:15Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:MPPOLICE]]

==Training session on MP Police Zimba and OS upgradation and integration 15 Dec 2023 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' Detailed 32-minute walkthrough of the MP Police Zimbra project: a combined OS + mail server upgrade (CentOS 6.10 to 7.9, Zimbra 8.0.5 to 8.8.1, via intermediate hops) plus a set of new integrations delivered as part of the tender -- ActiveSync (mobile mail sync), RocketChat (client-requested open-source chat, replacing paid alternatives like Zoom/Webex for that need), an archival server (every inbound/outbound mail archived and retrievable, unlike Zimbra's own 4-day log retention), a Jitsi video-conferencing server (open-source alternative per tender requirements), NextCloud for file storage/sharing, an ELK server for centralized mail-server log monitoring/retention, a DR setup in a separate environment kept in sync via lsyncd, and a Barracuda spam filter in front of Zimbra. Also covers the scale (~96,000 users, ~140TB of data across incremental/full backups on dedicated large disks) and the recurring support pattern for this account -- routine Zimbra tickets plus periodic questions about accessing the archive, chat, or video-conferencing tools, all backed by documentation the presenter had written and was uploading to the wiki.

Category:NFC

2026-07-25T02:53:14Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:NFC]]

==Training on NFC Project KT PART 1. Dated 13 Nov 2024 - Tetra Support Staff - Narendra Chall==

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

'''Video summary:''' "Narendra NFC KT 1" -- an English-language KT session covering the NFC (National Fertilizers Corp-type client) Zimbra mail environment, deployed at three locations: Hyderabad, Kota, and JTC, migrated from Rediffmail to Zimbra Network Edition 10.0.0.2. Incoming mail flow is: KSMG (a secure mail gateway that applies spam/allow-block rules and can bounce mail) -> IMSVA (Trend Micro InterScan Messaging Security Virtual Appliance, doing further per-IP/domain/account filtering) -> a Postfix daemon pair -> the MTA -> the destination mailbox; every user also has a separate archive (AR) account that a linked archive server populates for all in/outbound mail. Hyderabad runs four physical servers -- two paired mailbox/MTA/proxy servers (PCS cluster + fencing, so the standby takes over automatically if the active one fails), a shared pair of NAS storage boxes (primary/secondary) behind them, a dedicated AR server, and an internal mail gateway serving ~18-20 internal domains (with manual internet-relay as a fallback if that gateway fails). Kota and JTC mirror this setup but use DRBD replication instead of PCS/NAS, which the presenter flags as the single most important thing to monitor: DRBD sync must be checked daily, since if the primary fails while sync is only partially complete (e.g. 60%), the un-synced portion of data is permanently lost on failover. All outbound internet mail from Kota/JTC users must route through the Hyderabad MTA hub -- intra-site mail doesn't need this. Mailbox sizing (Class of Service) is tied to employee designation/grade (e.g. 2GB/7GB/12GB/18GB tiers), and user creation is scripted to auto-provision the matching archive account and notify designated stakeholders. Common support scenarios covered: 90-day mandatory password rotation and reset requests, a 30MB outbound attachment size cap, password-protected PDFs being blocked/bounced on delivery (unprotected PDFs pass), mailbox quota checks for "can't send mail" tickets, and a protected "public circular" dynamic distribution-list folder that only one admin account can modify.

==Training on NFC Project KT PART 2. Dated 16 Nov 2024 - Tetra Support Staff - Raviraj==

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

'''Video summary:''' "RAVIRAJ NFC KT 2" -- continues the NFC KT series with a support/operations-focused walkthrough. Covers the two Zimbra webmail clients NFC users may be on (Classic and Modern) and why it matters to ask which one a caller is using before troubleshooting; per-site public-circular distribution lists (Hyderabad, Kota, JTC); a two-tier attachment policy enforced via mail transport groups -- "Group One Transport" permits attachments, "Group Two Transport" (assigned by officer designation) does not -- plus separate sender restrictions that limit some users to internal-only mail. Describes the KVM-virtualized server layout per site (each physical/base machine hosts a paired mailbox/MTA/LDAP/proxy set) and the failover model: connectivity or load issues trigger automatic cluster failover to the secondary node, but a mailbox-specific problem requires a manual cluster shift; console access via the KVM host's URL is the fallback when SSH/PuTTY access fails, and if even the console doesn't respond the VM must be power-cycled. Notes an important operating constraint: NFC (a central government client) does not permit any remote login access to their environment -- support is done by walking NFC staff through fixes verbally on calls rather than connecting directly. Covers day-to-day troubleshooting patterns: slow mail delivery caused by a full mailbox quota; users' archive mount getting incorrectly pointed at another site's archive server (checked/fixed via `zmmailbox` commands to unmount and remount correctly); the full outside-to-inside mail path (KSMG -> IMSVA -> Postfix -> MTA -> mailbox) and where to check first when external mail isn't arriving, including manually releasing genuine mail that IMSVA quarantines as unscanned/spam (safe to release, and released mail doesn't get re-quarantined); and daily DRBD replication-status checks required only at Kota and JTC (which use active-passive DRBD replication), since Hyderabad's mailbox setup is active-active and doesn't need this check.

==Training on NFC Project KT PART 3. Dated 16 Nov 2024 - Tetra Support Staff - Raviraj==

{{#ev:youtube|5dYgl9Sf-D0|640}}

'''Video summary:''' "RAVIRAJ NFC KT 3" -- a detailed, mostly Hindi Q&A-style KT session covering several distinct NFC operational topics. Confirms that NFC-to-NFC mail (e.g. Kota to JTC) stays entirely on the internal gateway and never touches the internet path. Walks through the two ways new mailboxes get created: an automated bash script that interactively prompts for username, mail ID, display name, storage quota tier (2/6/12/18/32 GB), and site (Hyderabad/Kota/JTC), then auto-creates and mounts the matching archive (AR) account for Kota/JTC users -- versus manual creation through the Zimbra admin console (referred to as "GI"), which requires the AR account to be created and mounted by hand afterward. Goes deep on the DRBD replication risk at Kota/JTC: it's active-passive, so if the primary disk fails while the secondary is only partially synced (e.g. 50%), only that synced portion survives -- recovering from a "StandAlone" (out-of-sync) state requires manually disconnecting and reconnecting DRBD to force a resync, with no automatic reverse-sync. By contrast Hyderabad's mailbox cluster is active-active, storing identical data on both nodes in parallel, so this failure mode doesn't apply there. Also covers: checking HAProxy status per site (`systemctl status proxy`) as a first troubleshooting step; SSL certificate deployment on the proxy servers, where three separate cert files are combined into a single `bundle.pem`, the previous bundle is backed up (renamed `.old`) before the new one is deployed, Hyderabad's proxy is the single point where certs are uploaded/renewed (Let's Encrypt for one flow, a purchased commercial cert handed off by the vendor for another) and then synced out to Kota/JTC's proxies, and that RocketChat on this environment uses the same certificate; that antivirus/patch management for the gateway is handled entirely by the vendor, out of Tetra's support scope; domain-based mail routing through the internal gateway versus the internet path, including updating Postfix's `postmap` after adding/renaming a routed domain; and how to rename a user's mailbox/alias (demonstrated with a promoted senior officer's account) so mail to both the old and new address keeps reaching them via an alias pointed at the renamed account. Closes with configuring the three per-site public-circular distribution lists (Hyderabad/Kota/JTC) in the admin console -- setting which specific accounts are permitted to send to each circular list versus the full list of members who receive it.

==Training on NFC Project KT Final. Dated 06 Dec 2024 - Tetra Support Staff - Raviraj==

{{#ev:youtube|jH61YI-0PM0|640}}

'''Video summary:''' "RAVIRAJ NFC KT FINAL" -- the wrap-up session of the NFC KT series, re-walking the full mail architecture (KSMG -> IMSVA -> Postfix -> MTA -> mailbox for inbound; the reverse for outbound) and the KVM base-machine layout at each site (JTC and Kota each run 3 base machines -- two paired MTA/LDAP/mailbox/proxy nodes plus a dedicated archive/AR machine; Hyderabad separates internet-facing servers, KSMG/IMSVA/Postfix, from intranet servers including a RocketChat VM), before going deeper into day-to-day maintenance procedures than the earlier KT videos. Explains the manual PCS cluster failover procedure step by step: check cluster status to see which node (mailbox1/mailbox2) is currently live and confirm both nodes are online, then standby the active node and un-standby the other to force a controlled switch -- only done in response to a real connectivity/overload issue, not routinely. Covers the DA-domain bypass procedure: if NFC's local email gateway can't reach a particular DA (government) domain, editing Postfix's transport config to comment out that domain's local-gateway routing so mail for it goes via the internet path (IMSVA) instead. Reiterates the with-attachment/without-attachment/internal-only sender group model and the DRBD up-to-date-disk check that only applies at JTC/Kota (not Hyderabad, which is active-active NAS replication). Adds new maintenance detail: daily ClamAV signature updates (main.cvd, bytecode.cvd, daily.cvd) pushed via script to the MTA antivirus scanning layer across all three sites, and confirms SSL certificates and RocketChat are both maintained without downtime as part of routine operations. Functions as a consolidated review/summary of the architecture and procedures already covered piecemeal in the earlier NFC KT videos, rather than introducing an unrelated topic.

MPonline

2026-07-25T02:53:13Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:MPONLINE]]

==Training about MPonline project. Dated 10 March 2022 - Tetra Support Staff - Pappu==

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

'''Video summary:''' General training session (not client-support-call style like most others) walking a newer team member through the standard end-to-end process of standing up and migrating a Zimbra Network Edition mail server, using the MPonline project as the working example. Covers: pre-checks (disk space, setting a proper static hostname via hostnamectl/hosts file/DNS entries), disabling SELinux and firewall rules that would block Zimbra, removing conflicting pre-installed services like Postfix (since Zimbra ships its own MTA), downloading the correct Zimbra tarball version via wget, running the installer and setting the admin password, backing up and restoring Zimbra's mailbox index/store data between an old and new server (via rsync, followed by fixing ownership to the zimbra user and reindexing), migrating user passwords across via zmprov, activating the Zimbra license (zmlicense), and general tips: using `screen` to keep long-running migration commands alive across a dropped SSH/RDP session, and referencing separate recorded sessions (by other team members) that cover the DNS/BIND configuration and live-cutover/downtime process in more depth.

Category:CRPF

2026-07-25T02:53:12Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:CRPF]]

==Training on CRPF Session 1. Dated 02 NOV 2024 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' KT session (Part 1) on CRPF's mail environment, migrated from Lotus Notes to Zimbra and split across two parallel deployments: a Network Edition environment (~5000 users) and an Open Source environment (~10000 users), each with its own pair of MTA, LDAP, and mailbox servers plus an HA pair in front. To hide this split from end users, a single-URL login server (Python/Flask, itself HA'd via a shared virtual IP between two identical instances) looks up which environment a given user belongs to via a text file that's regenerated from both environments' user lists every 5 minutes by cron -- meaning a newly-created account needs up to a 5-minute wait before it can log in through the unified URL. Also covers CRPF's specific requirement around their 429 physical offices: accounts are provisioned with an office-suffixed internal domain and restricted so a user can only mail within their own office's user group, while an email alias masks that internal office-specific address so the outside-facing address a correspondent sees never reveals which office the user belongs to.

==Training on CRPF KT Session Part 1. Dated 16 July 2026 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' Another CRPF KT session covering the same dual Network Edition / Open Source Zimbra split described in "CRPF Session 1" (VuCx41rFxds) on this page, with additional detail. Clarifies the split is rank-based: senior/high-rank staff (~5000 of ~14000-15000 total users) sit on the Network Edition side, regular staff on Open Source. Covers OS installation basics for these servers (minimal RHEL-family install, local-only root credentials, no external access), and explains cross-environment mail delivery via split-domain routing: since the same domain exists on both sides, a mail from an Open Source user to a Network Edition user (or vice versa) is routed by checking whether the recipient exists locally; if not found on either side after being relayed back and forth up to three times, it bounces back to the sender. Also notes structural differences from the other session's description: mailbox servers here are standalone (no HA clustering) and each environment has its own log server rather than a shared archive server. Full installation documentation was noted as being covered in a following session.

==Training on CRPF KT Session Part 2. Dated 16 July 2026 - Tetra Support Staff - TAKSHAY==

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

'''Video summary:''' A third, more complete CRPF KT session covering the same dual Network Edition / Open Source Zimbra architecture as the other two videos on this page (VuCx41rFxds, IqYu4dBUpNU) -- same 429-domain, rank-based split, single-URL Flask/nginx login router (here specified as active-passive via a shared virtual IP, not active-active) -- but adds several details not covered elsewhere: LDAP uses true MMR (multi-master) replication between the two LDAP nodes so either can go down without impact; "archiving" here isn't Zimbra's built-in archive feature but a simpler BCC-style mechanism -- each user has a paired hidden "username_in"/"username_out" mailbox that silently receives a copy of every inbound/outbound mail; authentication is handled entirely through the client's own Windows Active Directory server rather than Zimbra's native LDAP auth, with a self-service password change/reset page (OTP sent to the user's registered number) integrated against that AD server; and a NextCloud server is deployed separately for document/file management. Confirms overall scale: ~5000 licensed users (Network Edition) plus additional Open Source users, across 429 total domains, as two separate multi-server Zimbra instances.

Category:CSC

2026-07-25T02:53:11Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:CSC]]

==Training on CSC PROJECT PART 1. Dated 24 OCT 2024 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' Overview of the CSC client's Apache CloudStack private-cloud environment, demoed first on an Ubuntu test setup then walked through against the real production environment (two locations, Noida and Pune). Covers the CloudStack dashboard/architecture: the management node (controls everything via API/UI, backed by a MariaDB database), Compute hosts (physical hypervisors, each running multiple KVM guest VMs that can be live-migrated between hosts, rebooted, or put into maintenance mode from the UI), and primary vs. secondary storage (primary for live VM/management data, secondary -- originally NFS, since migrated to Ceph for resilience -- for ISOs and templates used to build new VMs). The main project work: upgrading the CloudStack version itself, upgrading each management node's underlying OS off end-of-life CentOS onto Rocky Linux, and setting up a Galera cluster so the two management nodes replicate their database and can fail over to each other -- validated first in the Ubuntu test environment, already live in Pune, still pending client downtime approval in Noida. Also covers the general host-replacement pattern used across the client's compute fleet: migrate all VMs off a host, reformat it onto Rocky Linux, and re-add it to the cluster.

Category:XTRANET

2026-07-25T02:53:10Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:XTRANET]]

==Training on Xtranet Project KT. Dated 17 May 2024 - Tetra Support Staff - Alok Singh==

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

'''Video summary:''' Another architecture session for the same MPSDC/XTRANET Zimbra deployment covered elsewhere on the wiki (see the "MPSDC (XTRANET)" page), this one focused on mail flow and network segmentation rather than the OS/version upgrade. Inbound mail lands first on Trend Micro IMSVA (email security/AV scanning) before reaching the two active-active MTA nodes, then the mailbox pair (active-passive cluster, shared storage) and archive server. A load balancer sits in front of the MTA pair for webmail access so a single MTA failure is transparent to users. User authentication is via Active Directory (AD account required for every Zimbra login, integrated directly rather than Zimbra's own local auth). The distinct content here is the network design: servers are split across an Internet-facing zone, a DMZ zone (MTA + Trend Micro, firewalled), and a protected "MZ" zone (mailbox, archive), with a full list of ports that had to be explicitly requested from the client's separate network team to open between zones (389 for LDAP auth, 22, 53/DNS, 514/syslog, plus the standard Zimbra service ports). Also covers connecting to the client's data center via Array Networks' "Motion Pro" VPN client.

==Training on Service-tea-training-1-xtranet-compliances. Dated 30 May 2024 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' Interactive team training session ("Service Team Training 1: Xtranet compliances") led for junior engineers (Kasim, Takshay, Manish, Alok), using the Xtranet/MPSDC government tender as a worked example of how compliance documentation works on government projects. Explains that government tenders list specific technical compliance requirements (e.g. "must have mail," "must have archiving") that have to be proven point-by-point with a compliance sheet, supporting documentation, and screenshots/URLs as evidence -- illustrated using Xtranet's own compliance spreadsheet and mail-flow architecture diagram (Trend Micro AV gateway -> two MTAs -> clustered mailbox -> archive server, AD-authenticated, load-balanced). The bulk of the session then turns into general teaching about multi-server Zimbra deployments -- the difference between a single-server all-in-one Zimbra install versus splitting LDAP, MTA, proxy, and mailbox onto separate servers, why certain components (like the antispam/antivirus engine) must live specifically on the MTA and not the mailbox server, and quizzing trainees on what an MTA and a proxy component actually do -- referencing other real deployments (Infosys, NFC) as further multi-server examples.

Category:YOUSECURE

2026-07-25T02:53:09Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:YOUSECURE]]

==Training on YOUSECURE Project KT PART 1. Dated 19 April 2024 - Tetra Support Staff - Alok Singh==

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

'''Video summary:''' "YOUSECURE Project KT PART 1" -- a Hindi-language architecture walkthrough of the YouSecure hosting environment, drawn on a whiteboard/diagram live during the call. YouSecure runs two parallel environments -- "eSign Production" and "Traditional Production" -- both LAMP-based (Linux/Apache/PHP) with separate MySQL database servers, and every server is deployed as an HA pair (e.g. a primary and an "A" duplicate with adjacent IPs, each with its own paired database). The network is split into a DMZ zone (a 192.168.1.x segment, holding the WAF and external HAProxy) and an MZ/internal zone (a 192.168.2.x segment, holding the internal HAProxy, the four LAMP web servers -- each serving a different client domain in the Traditional environment -- and the database servers), with NAT rules on the firewall exposing the private DMZ IPs to the internet. Request flow: internet -> WAF -> external HAProxy -> internal HAProxy -> the correct backend LAMP server per the HAProxy config's per-domain routing rules -> its paired database. HAProxy is configured for priority/failover order rather than even round-robin -- it sends all traffic to the primary backend and only fails over to the secondary if the primary goes down -- and the two MySQL databases behind each pair stay in sync via master-to-master replication so no data is lost on failover. A separate problem is also covered: because uploaded files (PDFs etc.) land only on whichever LAMP server actually handled the request, and the paired servers aren't otherwise replicated, a failover could leave the secondary server missing files the primary had received. This was solved with a shared NFS server -- both paired LAMP servers mount the same NFS-backed directory (e.g. the upload folder), so either server can read files regardless of which one originally wrote them. The eSign environment mirrors this exact design but with a smaller footprint (essentially one web server instead of four).

==Training on YOUSECURE Project KT PART 2. Dated 25 April 2024 - Tetra Support Staff - Alok Singh==

{{#ev:youtube|3HBxyGg2uBQ|640}}

'''Video summary:''' "YOUSECURE PART 2a" -- a short, focused Hindi-language KT session walking through the actual HAProxy configuration file referenced in Part 1 (`/etc/haproxy/haproxy.cfg`), shared live on-screen. Explains the frontend/backend structure: the external HAProxy frontend listens on ports 80 and 443 and defines an ACL per website (using short truncated names like "ekyc1" for readability) that matches on the incoming domain and routes to a correspondingly-named backend, with separate 80 (`mode http`) and 443 (`mode tcp`) definitions per site; each of the four Traditional-environment sites (KYC, Video, Sign, and a fourth) has its own backend block listing both paired servers' IPs with `balance first`, so requests always go to server 1 until it's marked down, at which point HAProxy fails over to server 2 -- confirming the priority/failover behavior described in Part 1 rather than even load distribution. Also briefly covers the internal HAProxy's MySQL-facing config, which binds to the HAProxy server's own IP and load-balances (same `balance first` pattern) between the two paired database servers, and notes that NTP is configured on every server for clock synchronization across the environment.

==Training on YOUSECURE Project KT PART 3. Dated 25 April 2024 - Tetra Support Staff - Alok Singh==

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

'''Video summary:''' "YOUSECURE PART 2b" -- a continuation of the HAProxy walkthrough, this time live-tailing logs and troubleshooting on the actual servers. Demonstrates using `tail` on the HAProxy log (under `/var/log`) to watch real incoming requests in real time and read the log lines to identify which named backend and which specific server (`srv1`/`srv2`) each request was routed to, confirming the `balance first` failover behavior live -- including what the log looks like when the primary is down and traffic is on the secondary. Moves on to NTP troubleshooting: the internal HAProxy servers (two IPs, one per environment -- Traditional and eSign) double as the NTP servers for their environment's VMs, and a support ticket was caused by some VMs having "NTP connection refused" because the NTP client service wasn't running -- the fix is checking the service status per-VM and starting it, with NTP pool servers pulled from a regional (India) pool defined in the client config. Also revisits the NFS setup in more detail: a `/data` partition with per-service subdirectories (video, KYC, etc.) is exported from the NFS server and mounted onto the equivalent local content directory (e.g. mounting over `/home`) on both paired LAMP servers per site, so uploaded content is visible to whichever server is active. Closes with a tour of the oVirt/RHV-based virtualization platform hosting the whole environment (~38 VMs across separate Traditional and eSign manager consoles), a mention of a master-to-master MySQL replication reference doc, brief pointers to related but out-of-scope docs (Amanda backup software, LVM issues), and a note that email relay (a two-hop relay setup) is also part of the environment. The presenter notes the full YouSecure setup took roughly 4-5 months to build.

==Training on YOUSECURE (Signxca) DR related training. Dated 13 June 2024 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|1UqTmeOmGTs|640}}

'''Video summary:''' "Signxca DR related training to service team" -- a long (~45+ minute), mixed Hindi/English hands-on training session on the SignXCA disaster-recovery setup, aimed at the service/support team. Opens with the conceptual architecture: the primary datacenter (DC) runs both the eSign and Traditional environments across four oVirt/RHV hosts backed by a shared, partitioned storage array, while the DR site is a smaller, half-capacity mirror (fewer hosts, its own storage) connected to the DC via one-way storage-to-storage replication that gets reversed once a DR drill or real failover ends. A key design point is an L2 network extension between DC and DR, meaning VMs can come up at the DR site with the exact same IPs they had at the DC -- during a real DR event, the DC side is shut down, replication is paused, and the full environment (normally ~200-300 VMs, though DR is provisioned at reduced capacity) is expected to boot at DR unchanged. The session then moves into hands-on DR-drill execution: navigating the oVirt "Disaster Recovery" role, generating the DR configuration file (`dr.conf`) from a template using the manager's API credentials, hostnames, and CA certificate copied from the currently-active site, correcting auto-generated/commented-out fields for the secondary (DR) site, verifying host DNS/hosts-file entries and reachability between manager and target hosts, and applying the resulting Ansible playbook-driven failover. Also covers checking storage/data-domain visibility from the DR-side manager UI and using the `admin@internal` oVirt account for command-line/API operations. The recording includes real troubleshooting back-and-forth (access/OTP issues, a mid-session interruption) rather than a clean scripted demo, consistent with an authentic live training call.

==Training on YOUSECURE (Signxca)-Ovirt-Partial-DR-DRIL related training. Dated 18 Nov 2024 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|eQa7v-7yPEA|640}}

'''Video summary:''' [LONG RECORDING - ~1hr40min live execution; summary reflects the opening planning/kickoff segment, which sets the pattern for the rest of the call] "SignxCa Ovirt Partial DR DRIL" -- a real-time, unscripted recording of the team actually executing a partial disaster-recovery drill for SignXCA (the live counterpart to the separate DR training/walkthrough video). The team coordinates the drill live over call: take backups first, then shut down all VMs across both the Traditional and eSign production environments, and only then update DNS to point at the DR site -- deliberately keeping replication running until each VM is powered off so the final in-flight data is captured before cutover (explicitly distinguishing this from a snapshot, which only captures data up to the moment it's taken). One VM (the hosted engine, running a CRL service) is intentionally kept online longer than the rest. Roles are split between people physically at the DC and at the DR site, with instructions to screenshot each VM's shutdown status for an audit trail of what was on/off and when. The recording captures real coordination overhead (confirming who has DR access, chasing down team members, an aside about a previous long-running migration where staff pulled an all-nighter) rather than a clean procedural walkthrough -- consistent with genuine operational drill footage rather than a rehearsed demo.

Category:MGRM

2026-07-25T02:53:08Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:MGRM]]

==Training on MGRM Project. Dated 21 Feb 2024 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' Overview of the support setup for client MGRM: a single-server Zimbra Network Edition mail architecture (recently upgraded from an older Zimbra version after a spam-scanning engine was causing unreadable/corrupted mail formatting for end users) plus a separate LAMP-based "Doc server" that's integrated with Zimbra purely for opening file attachments (Office docs, PDFs, etc.) in the webmail interface, and Zimbra's own mail archiving (both sent and received mail retained beyond Zimbra's normal short-term logs). Also covers their OTRS ticketing tool deployment (same install pattern as another client, SafExpress, referenced earlier in this training series) -- access is via a FortiClient VPN that the client has since revoked, so troubleshooting now goes through AnyDesk; covers the standard OTRS health checks (mail queue, the httpd/postfix/cron/daemon services, and file permissions when a developer needs access to a specific script) and where the OTRS application user/paths live on that server.

Category:WBOBPASS

2026-07-25T02:53:07Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:WBOBPASS]]

==Training on WBOBPASS Project. Dated 23 Feb 2024 - Tetra Support Staff - Manish Singh==

{{#ev:youtube|4Gsk4BL3MP0|640}}

'''Video summary:''' Architecture walkthrough of the West Bengal "OBPASS" (online building-plan approval) government application. Staging is a simple single proxy/single app/single DB server chain. Production is more redundant: two proxy servers behind a load balancer, two application servers (one handling the bulk of traffic, the second more of a standby that can't fully absorb the load alone if the first goes down), and two database servers in a manual master/slave setup (failover to the slave is not automatic -- has to be brought up by hand). A separate Windows "scrutiny" server, connected to both staging and production, receives files pushed from the application during the citizen-facing form-submission flow. Shared document/PDF storage is an NFS mount, synced from the primary to secondary app server by a script whenever a developer changes data. Covers a recent migration of the whole 7-server production estate onto the state government's own "SCI platform" data center (new floating IPs for every server), with the NFS disk's actual mount-point cutover still pending (scheduled for a maintenance window later that night) and a related planned hardware upgrade (RAM/disk) once the state data center processes the request. Briefly mentions NKDA as a related project on the same platform, with its staging server ready but production not yet built.

==Training on UDMA-ARCH.. Dated 02 nov 2024 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' Architecture overview of UDMA (Urban Development & Municipal Affairs), another West Bengal state government application on the same general platform family as OBPASS/NKDA/the upcoming Panchayat project -- all hosted and infrastructure-provisioned by the state's own data center (SDC), with Tetra handling installation and infra-level support only (application-level PHP bugs are a separate PHP team's responsibility). Production architecture: a hardware load balancer in front of two active-active reverse proxy servers sitting in a DMZ zone (deliberately holding no data, so a compromise there can't leak anything), forwarding to two active-active application servers and a master/slave database pair (again, manual failover only) in a protected "MZ" zone -- plus two Windows servers handling form-scrutiny checks and an unused ticketing server built at initial setup but never adopted. Application and database servers share a common NFS-mounted disk for uploaded PDFs/documents. Staging is a simpler single proxy/app/DB LAMP stack. Access to all of it is via the state data center's own VPN (OTP-based, provisioned by a named Tetra contact who liaises with the SDC). Also notes a recent platform migration for these servers from a previous hosting provider onto the current one.

Category:Alstom

2026-07-25T02:53:05Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

=='''Alstom ELK Training session'''==

==Training on Alstom ELK Training session. Dated 17 Feb 2024 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|R6xAaw4J0-o|640}}

'''Video summary:''' Detailed 1-hour session on the ELK (Elasticsearch/Logstash/Kibana) security log monitoring platform built for Alstom, a French rail-solutions company, as part of a Central Security Program (CSP) requiring centralized log capture and alerting across their Windows and Linux estate. Architecture: an rsyslog relay server receives logs from all devices on ports 514 (TCP) and 8514 (UDP) and forwards them to a 2-node Elasticsearch cluster (both nodes configured as master, for redundancy) via Logstash, with a custom Logstash filter/pipeline tagging entries by hostname and program name. Covers building alert rules from specific Windows Event IDs (account disabled/enabled/deleted, privilege/security-group escalation, failed logins, password resets, audit log clears) and equivalent Linux alerts (sudo escalation, failed su attempts, anti-brute-force config changes), plus McAfee (ePO) event alerts and ELK's own internal health alerts (cluster health, disk/CPU usage, shard/thread-pool sizing). Also walks through building Kibana dashboards for authentication-failure trends, and the snapshot/backup mechanism -- an LVM volume shared across both nodes via NFS, snapshotted via Elasticsearch's Curator/snapshot API, which the presenter had already used once to recover from an accidental data deletion during setup.

ALSTOM

2026-07-25T02:53:04Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:ALSTOM]]

==Training on ELK Alstom. Dated 17 Feb 2024 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|R6xAaw4J0-o|640}}

'''Video summary:''' Detailed 1-hour session on the ELK (Elasticsearch/Logstash/Kibana) security log monitoring platform built for Alstom, a French rail-solutions company, as part of a Central Security Program (CSP) requiring centralized log capture and alerting across their Windows and Linux estate. Architecture: an rsyslog relay server receives logs from all devices on ports 514 (TCP) and 8514 (UDP) and forwards them to a 2-node Elasticsearch cluster (both nodes configured as master, for redundancy) via Logstash, with a custom Logstash filter/pipeline tagging entries by hostname and program name. Covers building alert rules from specific Windows Event IDs (account disabled/enabled/deleted, privilege/security-group escalation, failed logins, password resets, audit log clears) and equivalent Linux alerts (sudo escalation, failed su attempts, anti-brute-force config changes), plus McAfee (ePO) event alerts and ELK's own internal health alerts (cluster health, disk/CPU usage, shard/thread-pool sizing). Also walks through building Kibana dashboards for authentication-failure trends, and the snapshot/backup mechanism -- an LVM volume shared across both nodes via NFS, snapshotted via Elasticsearch's Curator/snapshot API, which the presenter had already used once to recover from an accidental data deletion during setup.

Nagios Upgrade Process with PCS cluster

2026-07-25T02:53:03Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Spectranet]]

https://youtu.be/lWkX0EPfvho

==Nagios Upgrade Process with PCS cluster Dated 7th May 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [SPARSE TRANSCRIPT - long screen-share session with minimal narration] "Spectra nagios upgrade on PCS cluster platform" -- a ~1.5 hour hands-on walkthrough upgrading the Spectranet Nagios monitoring server running on a PCS/DRBD cluster. The recovered narration fragments are consistent with the title: stopping the PCS cluster ("pcs cluster stop"), stopping DRBD replication, reconfiguring the virtual IP, rsyncing roughly 177GB of monitoring data across, then restarting and validating the cluster came back up successfully with the upgrade complete. Ends with a reminder to the team to confirm the next scheduled backup runs. Given how sparse the transcript is, treat this summary as a rough guide rather than a precise record -- the actual command sequence would need to be checked against the recording.

Category:ISONBPO

2026-07-25T02:53:02Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]

==Training on ISONBPO & SYSNET GLOBAL BSP KT Session. Dated 20 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' Detailed 37-minute KT session covering the combined Zimbra Business Edition setup for two separate clients, ISON BPO and SysNet Global, consolidated onto shared infrastructure fronted by a single HAProxy server. Topics: migrating both from Zimbra open-source to Network/Business Edition (critically, always creating and assigning the Class of Service *before* activating licenses or creating users, to avoid accounts defaulting to the far more expensive Professional tier); password migration from the old servers via a generated zmprov batch of "SetPassword" commands; data migration via imapsync run with multiple parallel threads and a persistent local cache directory (avoiding a full re-sync if the process is interrupted/restarted); and the HAProxy configuration itself -- a single shared URL/IP with custom, non-standard ports (1000 for ISON, 2000 for SysNet) used specifically to let a subset of users without smartphones or the technical ability to set up an authenticator app bypass the otherwise-mandatory two-factor login. Also covers the custom Flask-based single-sign-on-style login landing page (backend on port 5000, proxied through HAProxy on 443) that fronts both clients' mailboxes, an LDAP-driven script that keeps that login page's user list in sync automatically, and Let's Encrypt SSL certificate generation/renewal for the setup.

Newsnation Distribution List management and issue

2026-07-25T02:53:01Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:NEWSNATION]]
[[category:Zimbra]]

==Newsnation Distribution List management and issue. Dated 18 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|34svaUPohK8|640}}

'''Video summary:''' [SPARSE TRANSCRIPT - long silent/screen-share gaps] Troubleshooting session for a NewsNation issue where a user couldn't send mail to a distribution list (a 69-member group). Investigation centered on the distribution list's sender-permission property (restricted to specific senders vs. open to anyone), checked via the Zimbra admin console's contact/group settings. The eventual fix required a service restart, which the recovered narration indicates had to be scheduled for a maintenance window (a Saturday) rather than applied immediately. Transcript quality is too poor to reconstruct the exact root cause/setting that was changed.

==Newsnation Distribution List management and issue part 2. Dated 22 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [DUPLICATE CONTENT] Titled "Newsnation Distribution List management and issue part 2," but the transcript is byte-for-byte identical to the "part 1" video (34svaUPohK8) on the same wiki page -- same distribution-list sender-permission troubleshooting content, same timestamps. This looks like either the same recording uploaded twice under different titles, or a linking mistake on the wiki page. Worth flagging for the page owner to check whether this is genuinely a distinct "part 2" recording that simply has mismatched captions, or a duplicate video ID that should be corrected/removed.

TR69 Nagios Custom API Deployment For Spectra

2026-07-25T02:53:00Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Nagios]]
[[category:Spectranet]]

==TR69 Device addition NagiosXi Spectra 2022 02 14 11 16 00. Dated 14 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|dYXGu-5k35c|640}}

'''Video summary:''' [NO TRANSCRIPT AVAILABLE] Video titled "TR69 Device addition NagiosXi Spectra 2022 02 14 11 16 00" -- no captions/transcript exist for this recording, so no content-based summary could be generated. Based on the title alone, this appears to be a walkthrough of adding TR-69 managed devices into Nagios XI monitoring for the Spectranet account, recorded 14 Feb 2022.

Zimbra to Zimbra Migration

2026-07-25T02:52:59Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:MPOnline]]

==Training Zimbra to Zimbra Migration Part 1. Dated 12 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|00Ms3pMwh5Y|640}}

'''Video summary:''' [PARTIAL TRANSCRIPT - long stretches are silence/background music with no captioned speech] "Zimbra to Zimbra Migration Part 1" -- the opening installment of this migration series (continued in Parts 2 and 3), introducing the exercise as a large, potentially multi-day live deployment/migration for a client referred to as "Cisnet Global" and telling the team to keep other members available since it may run past a single session. Covers: connecting to VPN and checking the target server, discovering the current OS is too old for the intended Zimbra 8.8.15 package and that a matching newer VM needs to be created instead; attempting to provision a new VM of similar capacity in a different region (India) via the hosting provider's console, hitting a provisioning restriction, and having to raise a support ticket to get it resolved. The presenter frames the exercise explicitly as a teaching moment -- stressing that everyone on the team should understand how to build a Zimbra server end-to-end and the different available migration methods, since this knowledge underlies most support and migration work. As with Parts 2 and 3, this is real-time unscripted operational footage rather than a scripted walkthrough, with the actual hands-on Zimbra install/config work continuing in Part 2.

==Training Zimbra to Zimbra Migration Part 2. Dated 12 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|9Htpow4hBNc|640}}

'''Video summary:''' [PARTIAL TRANSCRIPT - long stretches are silence/background music with no captioned speech] "Zimbra to Zimbra Migration Part 2" -- a hands-on screen-recorded walkthrough of standing up a fresh Zimbra Open Source install on a newly provisioned server as the target of a mail migration. Covers: setting the new server's hostname, adding local DNS/resolver entries and confirming MX resolution before continuing (deliberately deferring firewall configuration until after the software downloads to avoid blocking outbound access); initially downloading the wrong Zimbra 8.8.15 build (a CentOS 6 package) and re-downloading the correct one; installing GNU `screen` so the lengthy Zimbra install can run as a detached background process; working through the interactive Zimbra installer's component selection (LDAP, logger, MTA, DNS cache disabled since only one DNS role is needed, SNMP, store, spell, proxy, etc.), an "unknown platform" override prompt caused by running on an OS release newer than the installer explicitly recognizes, and a missing-package dependency error that required checking the install log directly; and finally configuring the domain name and MX record during the installer's final steps, troubleshooting a DNS resolution error that came up at that point, before the install completes. Consistent with a real-time, unscripted troubleshooting session rather than a clean walkthrough -- multiple false starts and error recovery are part of the recorded content.

==Training Zimbra to Zimbra Migration Part 3. Dated 13 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, appears to mistake background audio/music for song lyrics throughout] "Zimbra to Zimbra Migration Part 3" -- continuing the same migration series as Part 2. The few legible fragments indicate this installment covers the data-import phase on the new server (started August 24 per one clear fragment), IMAP-based mail import for desktop clients, subscribing/selecting folders during import, configuring backup, and a step referencing the official Zimbra documentation about the LDAP admin password during setup (the fragment suggests being told NOT to reset it). Given the pattern is consistent with the other affected videos in this collection, this looks like a genuine audio-quality issue with the source recording rather than an isolated transcription failure -- worth flagging to whoever owns these recordings if an accurate summary is needed.

==Training Zimbra to Zimbra Migration Part Final4. Dated 13 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, appears to mistake background audio/music for song lyrics throughout] "Zimbra to Zimbra Migration Part 3" -- continuing the same migration series as Part 2. The few legible fragments indicate this installment covers the data-import phase on the new server (started August 24 per one clear fragment), IMAP-based mail import for desktop clients, subscribing/selecting folders during import, configuring backup, and a step referencing the official Zimbra documentation about the LDAP admin password during setup (the fragment suggests being told NOT to reset it). Given the pattern is consistent with the other affected videos in this collection, this looks like a genuine audio-quality issue with the source recording rather than an isolated transcription failure -- worth flagging to whoever owns these recordings if an accurate summary is needed.

ISON BPO Deployment Videos

2026-07-25T02:52:58Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:ISONBPO]]

==Training on Nagios Check nwc health plugin. Dated 12 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|9ujR_0B_eEc|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output] Titled "Training on Nagios Check nwc health plugin" for ISON BPO. The auto-generated transcript is badly garbled (heavy noise/unrelated fragments throughout), but the few coherent pieces are consistent with the title: downloading and installing the `check_nwc_health` Nagios plugin (a well-known open-source plugin for monitoring network device health -- switches, routers, etc.), then defining a custom Nagios check command around it (referencing `$HOSTNAME$` and community-string style arguments, suggesting SNMP-based device checks). Not enough reliable content survived transcription to describe the exact configuration steps taken -- would need a manual review of the recording for real detail.

==Training on Nagios Gearman testing ISONBPO. Dated 12 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output] Titled "Training on Nagios Gearman testing ISONBPO." Like the other video on this page, the transcript is dominated by nonsensical repeated filler ("jhaal", "ajay ko") that appears to be an ASR mis-transcription of background noise/music rather than speech. The handful of legible fragments reference Mod Gearman worker configuration, restarting the worker service via systemctl, checking service status, and creating/renaming a Nagios host group -- consistent with testing a Mod Gearman distributed-monitoring setup for ISON BPO (the same Mod Gearman feature described in the Spectranet SOC video on a different page). Not reliable enough to reconstruct the actual steps taken.

==Training on ISONBPO Nagiosxi Deployment on Probe part 2. Dated 12 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|gSUgwUO-N1M|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output] "ISONBPO Nagiosxi Deployment on Probe part 2." Same recurring transcription failure as the other videos on this page (dominated by nonsensical repeated filler). Legible fragments reference NagiosXI probe/host-group configuration -- copying/duplicating a host template, changing an icon/image setting, configuring a disk-usage check, and entering a device's IP address -- consistent with the title's topic of deploying NagiosXI monitoring via a probe/satellite server for ISON BPO. Not reliable enough to document the actual configuration steps.

ISONBPO Nagiosxi Deployment on Probe Windows

==Training on ISONBPO Nagiosxi Deployment on Probe Windows. Dated 14 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|4pvRjrCvvvM|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output] "ISONBPO Nagiosxi Deployment on Probe Windows" -- the Windows-agent counterpart to the other NagiosXI probe videos on this page, and affected by the same transcription failure. Legible fragments reference an NSClient-style Windows monitoring agent config file (an .ini file), needing to arrange machine access through a colleague named Pawan for a specific IP, and checking a Windows service's status -- consistent with configuring Windows host monitoring on the NagiosXI probe/satellite server for ISON BPO. Given this and the other three ISONBPO videos on this page all share the same severe transcript quality problem, it's likely a genuine audio/recording issue with the source videos rather than an isolated case -- worth flagging to whoever owns these recordings.

ISGEC Issue of user not able to login

2026-07-25T02:52:57Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:ISGEC]]
[[category:Zimbra]]

==ISGEC issue of user not able to login in Zimbra . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|P42mTIX-QuE|640}}

'''Video summary:''' [SPARSE TRANSCRIPT - largely screen-share with little narration] Troubleshooting session on an ISGEC Zimbra login issue: users being prompted for their password repeatedly because the password wasn't being accepted, despite being correct. The available transcript is mostly silent/screen-only segments, but the recovered narration is consistent with the title -- diagnosing and resetting whatever account/LDAP object was causing the authentication failure, ending with a working fix ("so they should be working with this object now").

Newsnation Saturday Zimbra Backup Process

2026-07-25T02:52:56Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:NEWSNATION]]
[[category:Zimbra]]

==NewsNation Every Saturday Mail Backup Process As Discussed With Alok . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [LOW CONFIDENCE - poor audio/transcript quality] Session titled "NewsNation Every Saturday Mail Backup Process As Discussed With Alok." The auto-generated transcript for this one is heavily garbled (likely poor recording audio), so this summary is based mostly on the title plus the few coherent fragments recovered: it appears to walk through setting up an automated, cron-scheduled weekly mail backup job (references to scheduling at specific times, starting/killing/restarting the job, and copying data out, possibly to S3/cloud storage) for NewsNation, with a troubleshooting/support-call callback process if the scheduled job doesn't run cleanly. Recommend a manual re-check of this one against the actual recording if precise technical detail is needed -- the transcript isn't reliable enough to summarize further.

Training 2022 Linux team/

2026-07-25T02:52:54Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[Category:Training_2022]]

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-1 . Dated 01 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Sending,Recieveing Bouncing part1" -- a clear, well-structured English-language training session on the methodology for diagnosing mail sending/receiving/bouncing issues, using SysNet Global as a running example. The central teaching point: a support engineer should NOT jump straight to logging into the server -- first understand exactly what the customer is reporting (not receiving mail vs. sending bounces vs. sent-but-not-received-and-not-bounced are three different problems needing different investigation paths) and understand how mail is supposed to flow for that specific domain, since 40-60% of issues can be diagnosed or at least narrowed down without ever logging in. Walks through the actual discovery process: use `host`/`nslookup` (both Linux and Windows CMD demonstrated) or a tool like MXToolbox to find a domain's MX record and confirm where mail is actually supposed to land; check whether port 25 (SMTP) on that mail server is even reachable via telnet, since a dead SMTP port typically means the whole world can't reach that server (a different problem shape than one-off delivery failures); and cross-check by asking the customer to test sending to an external address like Gmail to isolate whether the problem is inbound-only, outbound-only, or both. Only once external factors (DNS/MX/port reachability) are ruled out does the engineer log into the server itself -- at which point the priority is knowing what platform is running (Zimbra/Postfix account for the large majority of environments, with a small remainder split between Kloxo -- a free cPanel-like panel for small/shared customers -- and a handful of consulting-only environments) and reading the relevant logs. Ends mid-session (to be continued in a Part 2) citing time constraints, having covered the discovery/triage methodology but not yet reached the actual server-side log-reading portion.

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-2 . Dated 02 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Sending,Recieveing Bouncing part2" -- continues directly from Part 1's SysNet Global example, moving from external discovery into actual server-side log reading. Recaps the principle: only log into the server once external checks (MX record, port reachability) confirm the problem is internal. Once logged in, first identify the mail platform running (checking running processes for Postfix vs. Zimbra vs. qmail -- Zimbra always runs on top of Postfix) before touching logs, since Zimbra's Postfix-derived mail log (`/var/log/zimbra.log`, referred to as "mail log") is the key artifact, rotated daily with roughly 4 days retained by default (older logs must be pulled from dated/rotated files if the issue is older). Demonstrates actually searching the log with `grep`/`cat` for a sender domain to confirm mail was received, then explains Zimbra's internal mail-tracing pattern in detail: Postfix accepts an inbound message and assigns it an internal queue/message ID; that message is handed to Amavis (running on the Postfix-Amavis integration, itself wrapping ClamAV for antivirus and SpamAssassin for spam scoring) for antivirus/anti-spam scanning; once Amavis clears the message ("passed clean"), Postfix picks it back up under a *new* message ID (since it now moves to an internal delivery queue) -- so tracing a single email end-to-end in the logs requires following the ID chain from the original SMTP-accepted ID through to this second internal ID; final local delivery happens over Postfix's LMTP protocol on port 7025 into the user's actual mailbox, and once that final "sent via LMTP" line appears for a given message ID, delivery is confirmed successful with nothing further to look for. Notes this Amavis-based two-ID tracing pattern is specific to Zimbra environments; plain Postfix (without Zimbra) doesn't generate this secondary internal queue ID, making its logs comparatively simpler to trace. Explicitly calls this pattern "very critical" and pauses to check the trainees understood it before moving on.

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-3 . Dated 03 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Sending,Recieveing Bouncing Part3" -- continues the series, shifting from receiving-mail diagnosis to sending-mail diagnosis, which the presenter notes is harder because outbound problems can't be fully diagnosed from outside. Covers checking domain expiry as a first, quick external check for both directions (using `whois` locally or via web tools -- domain expiry is rare but cheap to rule out) and confirming the mail server itself is reachable (ping/traceroute/login) as a sign of whether the issue is DNS/domain-level or server-level. The core topic of this part is Tetra's outbound mail-relay architecture and why it's necessary: many cloud/hosting ISPs (Google Cloud, DigitalOcean, and others) block direct outbound SMTP (ports 25/587/465) to prevent spam abuse, while a few (Linode, AWS) allow it. For platforms that block outbound mail, Tetra runs its own relay servers (built on plain Postfix, not Zimbra) hosted on an ISP that does allow outbound SMTP, and binds them to non-standard, harder-to-block custom ports (e.g. 588, 589) that the client's mail server relays through instead of sending directly -- illustrated with a live diagram of a Zimbra server on GCP (where outbound 25 is blocked) relaying mail out through one of these dedicated relay servers. Notes this relay setup is standard for most of Tetra's hosted mail environments but not universal -- it depends on the specific customer/hosting arrangement, and briefly mentions there are three relay servers in total (consistent with the "server-relay1/2/3" setup described in other Zimbra-architecture videos on this wiki).

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-4 . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|2k6IQMwCyjw|640}}

'''Video summary:''' "Training Sending,Recieveing Bouncing part4" -- continues the series, focused on discovering how outbound mail is actually routed for a given customer and diagnosing outbound-specific delivery problems. Demonstrates checking a live Postfix config to see whether a relay host is defined (its presence/absence in the config tells you immediately whether mail leaves the box directly or via one of Tetra's relay servers), using Pahwa as a live example of a client currently routing through Trend Micro's cloud gateway with a known ongoing issue affecting Microsoft-destined mail specifically. Reiterates the ~4-5 day log retention limit on Zimbra's rotated mail logs as a hard constraint on how far back an issue can be traced. Introduces "CBPolicyd" (Postfix's policy daemon) as the mechanism controlling sending restrictions on the relay servers -- covering things like greylisting and per-domain/per-user sending quotas or rate limits -- and explains that a customer hitting an undocumented sending restriction (e.g. exceeding an outbound quota) is a real, if less obvious, cause of "my mail isn't going out" tickets; points to internal wiki documentation covering the relay servers' CBPolicyd deployment for anyone who needs to go deeper on that topic (called out as a separate, more involved topic not covered fully in this session). Session ends with the presenter noting time is up and to continue in the next part, having covered outbound relay discovery and policy-based blocking as the two main outbound-specific diagnostic angles beyond what was already covered in Parts 1-3.

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-5 . Dated 07 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Sending,Recieveing Bouncing part5" -- shifts to diagnosing actual bounce cases, live, on one of Tetra's real relay servers (`server-relay1.tetrain.com`, confirming there are three relay servers total as mentioned in Part 4). Opens with the retry logic behind Postfix queuing: a failed outbound message isn't simply dropped -- it retries on a roughly logarithmic backoff (e.g. ~6 minutes, then ~30 minutes, then hours, then up to a day later), and the specific error encountered determines how long the next retry waits (a temporarily unavailable server retries soon; a nonexistent domain waits much longer). Demonstrates searching the relay's Postfix mail log for "bounce" and walks through several real bounce cases found live: one where a message triggers a bounce/delivery notification for unclear reasons requiring deeper log tracing by message ID; one where a specific recipient address is explicitly rejected by the receiving mail server (meaning the sender's own admin needs to contact the receiving domain's admin, since the sending side has no control over another domain's rejection policy); and one caused by a missing/incomplete SPF record on the sender's domain -- diagnosed by pulling the domain's TXT/SPF record via MXToolbox and confirming the sending relay server's IP isn't authorized in it, which is why the receiving Gmail-side server rejected the mail as likely spam. Notes bounce causes are numerous and case-specific, and that this topic continues into the next session. Ends mid-topic due to time (session capped at ~30 minutes as usual for this series).

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-6 . Dated 08 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Sending,Recieveing Bouncing part6" -- continues the bounce-diagnosis series with more live examples (interrupted partway by an unrelated live infrastructure task the presenter was simultaneously monitoring -- a data-sync operation being tracked in parallel). Covers reverse-DNS (PTR) records as another critical factor in deliverability -- checking that a relay server's IP resolves back to the expected hostname, since receiving mail servers commonly reject mail from IPs with missing/mismatched reverse DNS. Walks through an SMTP 554/571 "sender address rejected" bounce for a SysNet Global user, and makes an important diagnostic point: seeing "sender address rejected" from Tetra's own relay server (not the destination server) doesn't just mean that one recipient domain is blocked -- if the sending mail server is configured to route ALL outbound mail through a dedicated relay, then a sender-address rejection at the relay level blocks that user's mail to everywhere, not just the one destination they were testing with, which matters for correctly scoping the ticket. Explains the two-file Postfix relay configuration structure used across Tetra's relay servers: a "network" file whitelisting which IPs are allowed to relay mail through the server, and a sender-restriction file where specific sender addresses can be explicitly listed with `reject` to block them from using the relay (found to be the actual cause of the case being debugged -- the user's address had been deliberately blocked at some earlier point). Also covers reading Postfix's log symbols for identifying bounce/mailer-daemon messages (a message with no outbound queue ID reaching a "mail delivery subsystem"-style sender is characteristically a bounce), an oversized-attachment bounce example, and closes by answering a trainee's question distinguishing CBPolicyd (the milter/policy daemon Tetra primarily uses for quota-style sending limits) from milters more generally, noting CBPolicyd or other milters can also be configured to reject based on content, not just volume, depending on setup.

==Training Genral Discussion for Mail Bounce. Dated 09 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training Genral Discussion for Mail Bounce" -- a wrap-up/general-discussion session for the bounce-diagnosis series, working through several real support-ticket examples pulled live from the presenter's mailbox. Opens with a client-specific policy note: a client called "GoodLife" is the sole exception permitted to use IMAP (allowed because they carry very large mailboxes, up to ~70GB) while every other customer ("MotorCorp" and others) must be configured on POP3 with a 15-day server-side retention limit -- a useful concrete policy to know before troubleshooting a client's mail-client configuration complaints. Walks through several real bounce/undelivered-mail tickets and how to reason about each: a "triple bounce" case traced to a customer's own script/PHP code failing to send correctly (requiring back-and-forth log correlation between the customer's app logs and Tetra's server logs, since the fault could be on either side); a case where the *receiving* server explicitly denies mail by policy (meaning the customer needs to be told to contact the recipient's admin, since Tetra's side has no control over another organization's denial policy); a case where Outlook itself reports the sending error, meaning the diagnostic path is straight to Zimbra's own logs to find the real underlying cause (possibly a Zimbra/Postfix-level CBPolicyd restriction misconfigured for that domain); and a broader "mail bouncing from all domains" case root-caused to the customer changing their router/outgoing IP without notifying Tetra, so the new IP wasn't allow-listed on Tetra's relay servers -- fixed live by adding the new IP to the relay's Postfix "networks" allow-list file and re-running `postmap`, with the presenter stressing that customers changing their outbound IP without notice is a recurring, easily preventable cause of sudden full-domain bounce issues.

==Training SSLCertificate Training Part 1. Dated 10 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, filled with recurring nonsense "subscribe" filler phrases] "SSLCertificate Training Part 1" -- an SSL certificate fundamentals training session. Legible fragments cover self-signed vs. commercial certificates, browser-enforced maximum certificate validity periods (mentioning a 3-year cap), and a News Nation certificate-application example. Given the severity of the transcription failure, no reliable detailed summary of the actual deployment steps can be produced.

==Training SSLCertificate Training Part 2. Dated 11 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "SSLCertificate Training Part 2" -- a clear English-language session on commercial SSL certificate generation and deployment, contrasted with the Let's Encrypt process covered in an earlier (unrecorded or untranscribed) session. Explains that every certificate is one of three types: domain-specific, wildcard (e.g. `*.tetrain.com`, valid for any subdomain), or the much rarer IP-based certificate, and that mismatched domains/certs produce browser "not certified" warnings. Walks through the commercial issuance flow using real client examples (CareIndia, News Nation): generate a CSR (Certificate Signing Request) either via a vendor's web portal or with OpenSSL locally, submitting identifying details (common name = the domain, organization, country, state, city); a CSR always generates a paired private key that must be preserved exactly -- regenerating the CSR changes the key and invalidates any certificate already tied to it, which is why the presenter deliberately avoids re-generating one mid-demo. Covers domain-ownership verification methods vendors use before issuing (hosting a verification file/key on the site, or emailing the domain's registered admin contact for click-to-approve), and that a completed order returns multiple files -- the actual domain certificate, plus intermediate and root certificates that must be chained together correctly on deployment (matching the `chain.crt` + main cert pattern used in the team's Let's Encrypt process). Distinguishes Zimbra's admin-console CSR generator (used only to *generate/request* a certificate, since Zimbra's UI doesn't understand automated ACME renewal the way an Apache/Nginx site can) from `certbot`, which Tetra uses only in "get cert" (not full install) mode against Zimbra since Zimbra isn't a web server Certbot recognizes -- versus a plain Apache/Nginx-backed site (demoed on Beetel's server), where Certbot can both obtain and fully deploy the certificate automatically. Ends by assigning homework: come prepared for the next session to deploy a commercial certificate manually on Apache (matching cert, key, and intermediate cert), with the presenter stressing self-directed exploration as essential for Linux administration skill-building.

==Training On Engineers queries. Dated 14 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as several other recordings in this training archive] "Training On Engineers queries" -- a Q&A-style session answering engineer questions, per the title. Legible fragments touch on WHOIS domain lookups (checking domain registration/ownership info), cron jobs, and a specific mail-delivery ticket discussion. Given the severity of the transcription failure, no reliable detailed summary of the questions/answers can be produced.

==Training On Letsencrypt SSL Certificate renewal for Apache Server for Beetelcsd in. Dated 15 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [SPARSE TRANSCRIPT - long stretches of silence/background music] "Letsencrypt SSL Certificate renewal for Apache Server for Beetelcsd in" -- a hands-on Let's Encrypt/Certbot certificate renewal walkthrough for Beetel's CSD Apache-based site, following up on the SSL Certificate Training series. The legible portion shows the renewal running into an issue where nothing could reach the server on port 443, traced to the server's own iptables firewall blocking traffic -- the presenter checks the INPUT/OUTPUT chain policies to diagnose whether inbound HTTPS or outbound validation traffic (or both) was being blocked, consistent with the earlier training's point that Certbot's automated flow can fail for reasons unrelated to the certificate itself (like a firewall) and needs manual troubleshooting when it does. Given the sparse transcript, the specific fix applied could not be reliably captured.

==Training On Commercial SSL Certificate Deployment for zimbra for Customer Jacob Ballas. Dated 15 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [MIXED/PARTIAL TRANSCRIPT QUALITY - first ~5 minutes is unusable gibberish filler, remainder is legible] "Commercial SSL Certificate Deployment for zimbra for Customer Jacob Ballas" -- a hands-on commercial certificate deployment for client Jacob Ballas's Zimbra server. The legible portion shows the deployment being complicated by discovering the server is running a very old, end-of-life Zimbra version (8.6, several major versions behind the 8.7/9.0 series current at the time), which the presenter flags as a real security concern -- an outdated web-facing portal being a plausible attack vector -- and states that a version upgrade is a prerequisite before the certificate work can safely proceed, since the current version is past its supported line. The recording then shows Zimbra services being restarted/brought back up after applying changes. Given the transcript quality, the exact upgrade or certificate-application commands used could not be reliably captured.

==Training Zimbra Mail Backup. Dated 15 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as several other recordings in this archive] "Training Zimbra Mail Backup" -- per the title, a training session on Zimbra's built-in backup mechanisms (mentioning NetBackup integration for Zimbra Network Edition/professional tiers). Legible fragments touch on basic Linux commands for backup operations, rsync-style copy behavior for incremental/changed files, and general backup fundamentals. Given the severity of the transcription failure, no reliable detailed summary of the actual backup configuration steps can be produced.

==Training CapitalBank VA fix and Jakson Archive Piler. Dated 17 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as several other recordings in this archive] "CapitalBank VA fix and Jakson Archive Piler" -- per the title, a session covering a vulnerability-assessment (VA) remediation for Capital Bank and Jakson's Piler mail-archiving setup. Legible fragments reference checking system/package versions and RPM-based updates (Capital Bank appears to be on an RPM-based OS), and general system checks. Given the severity of the transcription failure, no reliable detailed summary of the specific fixes applied can be produced.

==Training Zimbra Cli part 1. Dated 17 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Zimbra Cli Training part1" -- opens by triaging a list of previously-requested training topics against what's already been covered (undelivered mail, backup, certificate renewal all done in earlier sessions), pointing to the internal wiki for a couple of smaller documented topics (adding a new archive account/ID -- explained inline: create the archive user on the archive server, then map it to the corresponding main-server user in the "archivelist" file and run `postmap` so mail starts flowing to the archive automatically) and flagging "server not working" and "new domain configuration" as too generic/out-of-scope to teach as a single topic. Then begins the actual CLI training: explains that while most Zimbra administration can be done via the GUI, CLI is essential for engineers actually managing environments, and introduces `zmprov` as the single most powerful and heavily-used Zimbra CLI command -- capable of managing accounts, calendars, global config, class-of-service, domains, blocked senders, mailbox-level settings, and especially server-level configuration (demonstrated with `zmprov help server`, showing create/delete/modify-server options and inspecting a server's `zimbraMyNetworks` -- the whitelisted IP ranges, by default including `127.0.0.1`/localhost and the server's own IP). Also distinguishes `*ctl` commands (e.g. `zmamavisctl status`, `zmmailboxdctl status`) as service-level start/stop/status controls, one per Zimbra service (MTA, mailbox, Amavis, MySQL running behind the mailbox service, etc.), from `zmprov`'s broader configuration-management role. Session is cut short by a live infrastructure interruption (an SDWAN probe connectivity issue the presenter had to step away to handle) and closes with a plan to continue the `zmprov` deep-dive in the next session.

==Training Zimbra Cli part 2. Dated 19 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Zimbra Cli Training part2" -- continues the `zmprov` deep-dive live against a real SysNet Global Zimbra server. Establishes the core naming convention that unlocks the whole command family: the first letter(s) tell you the operation -- `g` = get/query (safe, read-only), `c` = create, `m` = modify, `d` = delete, `sp` = set password -- so `ga` = get all accounts, `ca` = create account, `ga <account>` = get one account's full attribute dump, `am` = modify account, `gs`/`ms` = get/modify server (per-host settings, requires specifying the hostname), `gcf`/`mcf` = get/modify the global config (environment-wide settings, no hostname needed). Demonstrates: listing all accounts (`zmprov ga | wc -l` to count ~4000 accounts) and grepping the output for a specific surname to find matching accounts; reading and then safely (without actually applying) walking through changing a server's MTA relay-host (`zimbraMTArelayhost`) setting via `gs`/`ms`; and inspecting `zimbraMtaMyNetworks`, explaining its security significance -- any IP listed there is fully trusted to relay mail through the server without authentication, so it should only ever contain localhost and the server's own IP, plus rare, deliberate additions for specific non-authenticating applications (each addition requires copying the full existing value, appending the new IP, and re-running the modify command since it's a single space-delimited attribute, not an appendable list). Also shows the equivalent lookup for global SMTP settings via `gcf`/`zimbraSmtpHostname`. Closes by encouraging trainees to build their own personal Zimbra server to practice `zmprov` hands-on, take a live Q&A question about the practical risk of an unauthenticated relay IP (confirming any user, not just a specific account, could send mail from a trusted IP without credentials), and ends with an unrelated live production interruption (the presenter noticing and fixing an unexpected configuration value change on a real server before closing the session).

==Training Zimbra Cli part 3. Dated 22 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as several other recordings in this archive] "Zimbra Cli Training part3" -- continuation of the zmprov CLI training series. Legible fragments reference the local server config file (holding credentials like the LDAP/root/admin passwords), multiple mailboxes in a multi-server architecture, and a mention of Ordnance Factory Board as an example client. Given the severity of the transcription failure, no reliable detailed summary of the specific commands taught can be produced (see the clearer Parts 1 and 2 of this same series for the bulk of the reliably-captured CLI content).

==Training session Tetra team on Isgec samba Nextcloud understanding. Dated 27 Oct 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|84Qs_uRYbfc|640}}

'''Video summary:''' "Training session Tetra team on Isgec samba Nextcloud understanding" -- an architecture-and-handoff training session covering the ISGEC client's multi-platform environment (four platforms total including Zimbra, Samba, and Nextcloud, accessed via a dedicated customer-care VPN), explaining the rationale for the multi-server split as reducing the blast radius of spam/compromise incidents across services. Covers Samba fundamentals: it's a single-box, no-real-"architecture" service used to share files/drives between roughly 100 Windows client machines over a common authenticated share (accessed via a UNC path/IP in Windows Explorer, where each user can only browse into directories they have credentials for -- demonstrated with two named users unable to see each other's private folders); all user/permission/share configuration lives in `smb.conf`; because command-line user management wasn't practical for ISGEC's own staff to operate, Tetra additionally deployed a GUI tool for them to add/remove users themselves. Briefly notes name-service/NIS configuration is notoriously syntax-heavy and error-prone, and that Zimbra installs typically take 2-3 days end-to-end (not the "couple of hours" some expect). Moves into a live walkthrough of ISGEC's single-server Nextcloud instance (a relatively recent migration): demonstrates its Collabora-based real-time online document editing (Excel- and Word-equivalent collaborative documents, no local software install needed) and mobile/desktop client support with automatic user sync from the customer/lab-users directory. Flags a concrete, actionable item live in the session -- the SSL certificate on this Nextcloud instance is set to expire around October 12 and needs renewal, framed explicitly as a process/follow-up issue rather than a technical one ("this isn't about who's technically capable, it's about making sure it gets followed up and done"). Also recaps a previously-resolved real support issue: users of a specific lab application (with ~1.2TB of data) were unable to copy large datasets through Nextcloud, which was diagnosed and fixed by the presenter, with a reference to the original deployment documentation for the lab app's PHP/module prerequisites.

==Training With mithlesh GSTN explian. Dated 28 Oct 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [SPARSE TRANSCRIPT - a ~30+ minute recording with very little captioned speech, long stretches of silence/background noise] "With mithlesh GSTN explian" -- an architecture explanation session for the GSTN (government) client's environment, presented to/by Mithlesh. Legible fragments reference roughly 25 services, standard documentation, Windows services, share creation and permissions, logical volume creation, user/AD (Active Directory) management, and CRM status -- consistent with GSTN's Samba-as-AD-replacement architecture described in other training sessions on this wiki (e.g. "Training Session 2021 march 1"). Given how sparse the captioned audio is, no reliable detailed summary of the specific architecture walkthrough can be produced.

==Training session Tetra team on Sysnetglobal understanding. Dated 31 Oct 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|-Oi7OkupzWA|640}}

'''Video summary:''' [NO ACCESS - VIDEO REMOVED] This video has been removed by YouTube entirely for violating YouTube's policy on harassment and bullying. This is distinct from the "private video" cases found elsewhere on this wiki (McFiFCgjdAM and others) -- a removed video cannot be restored by the uploader and the content is permanently gone. No content, transcript, or even a title is retrievable. Whoever owns this wiki page should be aware the embed is not just broken but pointing at content that no longer exists anywhere on YouTube -- worth investigating why a training recording would have triggered this kind of policy removal, and the embed/link should likely be removed from the page rather than repaired.

==Training session Tetra team on CDIL understanding. Dated 05 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [MIXED/PARTIAL TRANSCRIPT QUALITY - patchy throughout with long silent gaps] "Training session Tetra team on CDIL understanding" -- an architecture discovery/handoff session for client CDIL, similar in format to the ISGEC session on this same page. The presenter explains that unlike other clients, CDIL's environment wasn't handed over with documentation -- the team had to independently discover what existed (mail, "Diamond" application, backup setup) rather than being briefed on it, describing this as a first-time situation requiring active reverse-engineering of the architecture rather than a walkthrough of known documentation. Covers a Chandigarh/Shimla dual-location setup (two servers with fixed IPs that can't be changed, one acting as a base/primary server), TetraControl as the monitoring/chat platform used to track this and other environments, and an application running on Tomcat as its backend (traffic hits an Nginx/proxy layer in front, which forwards to Tomcat, rather than users hitting the app server directly). Also touches on a disk-space risk -- a log or data directory at risk of filling up, where clearing it would resolve the space issue but at the cost of taking the affected service down, so it's treated as a last-resort fix rather than routine maintenance. Given how patchy the transcript is throughout, this summary reflects only the clearly identifiable topics, not a complete architecture walkthrough.

==Training Spectra Handover with Alok. Dated 05 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|PGg9Iv7H-Ag|640}}

'''Video summary:''' "Spectra Handover with Alok" -- a hands-on infrastructure handover for the Spectra client's environment. Opens covering the hosting/instance access basics (credentials, control panel), then a load-balancer troubleshooting scenario: internal access to a service resolves and works correctly (verified by taking web nodes 2 and 3 down in turn and confirming the site still loads, proving the load balancer is actively distributing traffic), but external packets aren't landing -- traced to a DNS mapping issue on the global/public DNS side rather than the internal network, which the presenter walks through live without fully resolving on-camera. The bulk of the session is a detailed PCS (Pacemaker/Corosync) cluster walkthrough with DRBD-backed storage: checking `pcs status` to see which of two nodes is active/online, manually taking a node offline/standby with `pcs node standby` (and back online with `unstandby`, watching DRBD resync progress and timing, ~49 seconds observed for a small dataset), and checking DRBD sync state directly via `/proc/drbd` (states include "Connected" vs "StandAlone," and node roles "Primary"/"Secondary" -- data is only current on the Secondary if it shows fully synced with the Primary). Explains why certain cluster resources are configured with "failure ignore" -- because Pacemaker's default behavior is to fail over the service to the other node on any restart or config-triggered reload, which is undesirable for a brief, expected restart, so failure-ignore prevents an unnecessary cluster shift for these specific resources. Also covers the day-to-day support pattern the client should follow: temporarily disabling/re-enabling a specific cluster resource (`pcs resource disable/enable`) when a service appears stuck, rather than restarting the whole cluster (which can trigger a full failover); a monitoring dashboard the client was given to self-check service/sync status, with a known recurring gap where the client isn't receiving the latest alerts and needs to check manually. Closes by clarifying that the client's monitoring/NMS access needs to be verified with them directly, and to escalate immediately if the client can't see something that should be visible.

==Training session Tetra team on TATAELECTRONICS ZIMBRA DLP understanding. Dated 07 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|9RTHkBx6EXc|640}}

'''Video summary:''' [PARTIAL TRANSCRIPT - substantial silent/music gaps throughout] "Training session Tetra team on TATAELECTRONICS ZIMBRA DLP understanding" -- an architecture and scope-boundary session for Tata Electronics' Zimbra environment, with a strong emphasis on clarifying what is and isn't Tetra's responsibility. The presenter is explicit that writing or modifying DLP (Data Loss Prevention) policy content itself is out of scope for the team -- that's owned by Amit's team -- and pushes back on the idea of guessing at policy configuration via "Google search," stressing the team should understand and support the environment, not experiment on it. Describes Tata Electronics' architecture: a single Zimbra instance hosted as a VM (likely on VMware), not exposed to the internet and reachable only over a client-controlled secure internal network limited to factory staff -- noted as having diminishing relevance since most day-to-day work is handled through other channels. Covers the DLP solution running on top as a 4-point (or similarly-tiered) Boldon/BB-type add-on, and briefly reviews what a DLP policy conceptually is at a high level. Later in the session, introduces an "FSM" (Affiliate/Field Service Management-type) server and a secondary/primary routing concept relevant to escalation paths. A trainee's live question about whether DRBD-style replication could be reused for a different context ("YouSecure") prompts the presenter to caution that DRBD is a genuinely complex technology that shouldn't be reached for by default, and that NFS, while simpler, is meaningfully slower than proper SAN-based storage -- a reminder that infrastructure choices should match the actual requirement rather than defaulting to what's familiar. Session closes with an unresolved escalation waiting on confirmation from another team member (Yogesh) before the topic can be closed out.

==Training session Tetra team on Reachingcriticalwill some kloxo understanding. Dated 09 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|HK-WXK5CCeo|640}}

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - patchy in places but core content legible] "Training session Tetra team on reachingcriticalwill some kloxo understanding" -- an architecture walkthrough for the "Reaching Critical Will" client, a LAMP-stack website. Explains that the site isn't directly exposed to the internet -- the actual Apache/LAMP service runs on a local, non-public-facing address and is reached only through a proxy layer, demonstrated by contrasting opening the site via its normal domain versus attempting to hit its underlying IP directly. Walks through the Kloxo (free cPanel-alternative) control panel used to manage this and similar small-website hosting accounts, showing how to define/locate a website's configuration in the panel and find its actual backing IP address. Shares root credentials live via chat for the demo environment, and shows checking Apache's actual running configuration directly from the config files as the reliable way to confirm what's serving a given site rather than assuming, since panel entries and reality can drift. Given some transcript gaps, finer procedural detail beyond this overview could not be reliably captured.

==Training session Tetra team on Infosys DOP Amanda understanding. Dated 10 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - some gaps but core content legible] "Training session Tetra team on Infosys DOP Amanda understanding" -- an architecture and handover session for Tetra's long-running relationship with Infosys, specifically the Department of Posts (DOP) project using Amanda backup software. Sets context first: Infosys is a very large, structured organization, so remote access typically isn't available for Infosys-owned environments the way it is with smaller clients -- Tetra has delivered many projects with Infosys over roughly 11-12 years, some now finished and some still ongoing, and for this particular DOP engagement the implementation itself required physical, on-site work in Delhi (near Rajokri Road) because of the department's requirements, even though ongoing support is remote after that. Notes the Income Tax Department is a related/relevant reference program with its own data center presence in Delhi (GK-2 area) -- likely mentioned as an architecturally similar or connected engagement. On Amanda itself: it's the backup solution deployed for DOP, backing up multiple machines from a single data-center (DC) server, with a second environment configured as DR (disaster recovery) alongside the primary DC. The presenter pauses mid-session to check whether formal documentation exists for this deployment before continuing, suggesting institutional documentation for this particular engagement may be incomplete or hard to locate. Given the transcript gaps, deeper Amanda-specific configuration detail beyond this overview could not be reliably captured.

==Training session Tetra team on Infosys ITD zimbra understanding. Dated 11 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - patchy but core content legible] "Training session Tetra team on Infosys ITD zimbra understanding" -- continues directly from the DOP/Amanda session, now covering the Income Tax Department (ITD) side of the Infosys engagement, which runs Zimbra rather than Amanda. Recaps the two Infosys sub-projects side by side (DOP on Amanda backup; ITD on Zimbra) before walking the ITD Zimbra architecture: a DC (data center) with Zimbra 8.8.15 components and a separate DR (disaster recovery) environment that is currently NOT properly replicating -- root-caused to someone having disabled DR-DC replication entirely by mistake, so it isn't functioning until re-enabled/fixed. Notes the architecture as documented is missing a piece around HA/clustering that needs to be reconciled with what's actually deployed, and references comparable documented architectures (e.g. GSTN) as a pattern to check against. Reviews some account details shared with the team (admin/mailbox counts, credentials) and works through an architecture diagram live. Closes with the presenter redirecting a trainee's tangential question about Docker/microservices back on topic, reiterating this session is specifically about understanding this customer's existing multi-server architecture, not a general technology discussion.

==Training session Tetra team on some kloxosites Adani understanding. Dated 15 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - patchy but core content legible] "Training session Tetra team on some kloxosites Adani understanding" -- covers two related small-hosting topics. First, a quick tour of several small websites hosted on Kloxo (mentioning a client like "Rajeev Associates," where both mail and website are hosted together), checking that mail is actually functioning by looking it up externally (e.g. confirming DNS/MX resolves correctly via a Google search-style check) and cross-referencing against a conceptual documentation diagram that notably wasn't part of the original migration paperwork. The larger portion of the session covers Adani's secure access setup: logging into `myadani.com` requires both an email address and a registered mobile number, and critically, actions like accessing a "Security" section trigger a second-factor approval step delivered to a companion mobile app (an RSA-style authenticator) that the user must approve on their phone before the access is granted -- explained as Adani's standard "secure ID" two-factor access model applied to their admin/portal login flow. Given some transcript gaps, finer detail beyond this overview could not be reliably captured.

==Training Zimbra Admin Console Training for Apsecuritas. Dated 18 Nov 2022 - Tetra Support Staff - Pappu==

{{#ev:youtube|4Ew8Qo-McV4|640}}

'''Video summary:''' "Zimbra Admin Console Training for Apsecuritas" -- a client-facing (Apsecuritas) walkthrough of the Zimbra admin console, aimed at teaching the client's own staff which day-to-day tasks they can safely self-serve versus what must go through Tetra. Opens by showing the server console (port 7071) and confirming running Zimbra services from both the OS level and the admin console's own service status view. Covers admin console basics: viewing the Zimbra version, total account and domain counts on the server dashboard, creating a new account (name + password, domain auto-selected), and viewing/managing an existing account's mail directly from the admin console (view mail, reset password). Explicitly draws the boundary for the client: day-to-day account creation/password resets are fine for them to do themselves, but domain-level configuration changes should always be discussed with Tetra first, since self-service misconfiguration at that level has caused difficult mail-recovery incidents before. Walks through the "Manage" section listing all accounts, aliases, and distribution lists on the server, and briefly tours per-server config (Advanced tab, message/index data storage volumes) as read-only informational context rather than something the client should change. Also addresses a few live client questions: acknowledges a slow support-response complaint and commits to the standard 30-minute reply SLA going forward; explains that a case of a domain's own mail getting caught in that same domain's junk filter isn't something fixable from the admin console -- it requires server-level (MTA/filter) investigation, not just whitelisting; and defers questions about installing Zimbra on mobile or configuring third-party mail clients to a follow-up with a colleague (Mukul), promising an email with the procedure.

==Training session Tetra team on Infosys ITD ELK understanding. Dated 24 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training session Tetra team on Infosys ITD ELK understanding" -- a detailed architecture walkthrough of the Income Tax Department (ITD)'s ELK-based logging platform, part of the same Infosys engagement covered in other sessions on this wiki. Opens with the underlying business rationale: the Income Tax environment generates enormous volumes of application logs across many machines, and reading raw text logs server-by-server has no practical value -- what's needed is a visual, aggregated view of connection counts, server/application performance, data throughput, and error rates across the whole environment, which is exactly what ELK (Elasticsearch/Logstash/Kibana) is for. Explains the cluster's real scale: 2 master nodes plus a large number of additional Elasticsearch/Kibana/Logstash nodes, totaling roughly ~99 machines across three parallel environments -- PDC (a testing/staging predecessor, referred to loosely as "Non-Prod"), a UAT-like environment, and BCP (Business Continuity Planning, i.e. the actual primary/DR production data center pairing) -- with security protocols and single sign-on experimented on first in the pre-prod environments before being promoted to production. Contrasts self-built open-source ELK (where every component -- Filebeat/Logstash shipping, Elasticsearch nodes, Kibana -- must be assembled and wired together manually) against fully-managed cloud logging platforms (e.g. AWS/GCP's built-in equivalents) that ship as a ready-made UI with nothing to build. Walks through ITD's actual deployment documentation live: PDC has 3 master nodes plus dedicated Elasticsearch data machines and a separate log-test machine; installation followed a standard pattern of setting each node's data directory, getting nodes talking to each other, then layering on Kibana with reverse-proxy access in front of the application servers; explains Logstash's per-pipeline configuration (input source, filter, output -- e.g. targeting all three master nodes as Elasticsearch output, indexing rules, multiple parallel pipelines for different log types) and how filters can be written from scratch, found pre-built, or auto-detected via plugins to parse/tag incoming log fields for later visualization. Uses the practical framing that even in a well-organized log stream, an engineer should be able to eyeball raw records and get an intuitive sense of pattern/category (e.g. "which kind of log entries are these, and what do they mean") before formalizing that into filter rules -- and that when in doubt, the right move is to just ask the person who built the original pipeline rather than guess.

==Training session Tetra team on Infosys ITD Nagios understanding. Dated 26 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training session Tetra team on Infosys ITD Nagios understanding" -- a detailed handover of the ITD monitoring platform built on NagiosXI, covering roughly 1200 devices. Demonstrates the live monitoring web dashboard/console and reviews original architecture documentation. Explains SNMP as the core monitoring protocol -- pulling metrics like traffic, memory, and port status from network devices and storage without needing local agents -- and that "NRPE proxying" (routing monitoring traffic through an intermediary) is only needed for devices not directly network-reachable or on a segmented network, which wasn't required here since ITD's devices were all directly reachable. Covers WMI (Windows Management Interface) as the equivalent mechanism used for Windows hosts. Walks through the range of what's actually monitored: network switches/devices (fan speed, dual power-supply failover status, temperature, per-interface bit/error rates); physical server health via IPMI/BMC-style out-of-band management ports (remote OS install, hardware status, disk/memory failures) on IBM AIX and other platforms; virtualization platforms (VM failure detection, storage consumption, snapshot/backup counts); and Hitachi enterprise storage (capacity, per-volume utilization, disk failure) queried via a dedicated query package rather than plain SNMP. Notes the full onboarding of this many unique device types took roughly 5-6 months of iterative work, and that AIX support specifically required NRPE-based agents rather than SNMP given the platform's specifics (RPM package copied and installed per-client machine, with documented troubleshooting steps for common install errors). Explains the team's standard troubleshooting handoff pattern for network-device monitoring gaps: check the target device output first using a documented reference command/expected-output pair; if no output comes back, escalate to the relevant network team (separate teams typically own switches/routers, firewalls, and other device classes respectively) since a missing SNMP response at that layer isn't something the monitoring team can fix themselves. Closes noting that despite the platform's scale, day-to-day support tickets are rare because the client's own on-site team (named contacts including Sudhanshu and Ashish) handles ground-level operations, with Tetra mainly stepping in for upgrades or platform-level issues.

==Training session Tetra team on Safeexpress OBPASS Punjab Noida understanding. Dated 28 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Training session Tetra team on Safeexpress OBPASS Punjab Noida understanding" -- covers two separate, unrelated projects. First, SafeExpress: a ticket-management LAMP application with a frontend where users log in and generate/view support tickets, and a backend built on a UPI-style internal API for the ticket workflow -- support ownership sits mainly with a colleague (Rakesh) who has the deepest platform knowledge and direct customer contact, so calls on this platform are infrequent and get routed to him. A real past incident is recalled: outbound notification email hit Microsoft 365's default outbound-sending cap (1000 messages/day per account), causing many customer notification emails ("your ticket has been generated") to fail to send during high volume -- resolved by working with the client to raise that limit and tuning based on what the mail logs showed. Second and larger: the OBPASS (Online Building Permission/Approval System) platforms for Punjab and Noida/West Bengal -- a government building-permit approval workflow where an application (e.g. for a house/building in Patiala) routes automatically through the relevant approving authority (e.g. fire department) for review/approval, with multiple government bodies plugged into the same automated routing system. Explains the vendor split: Tetra built the integration/architecture and the overall system routing, while a separate company, Vinjas, built the actual "scrutiny engine" (the core rules/validation logic that checks submitted applications) which plugs into Tetra's architecture. Clarifies scope explicitly: Tetra does NOT manage the underlying infrastructure for this platform (Windows-based) -- support is reactive only, triggered by escalations that come in via a WhatsApp group shared with the client and a partner company (Medha) that also has visibility into both the Punjab and Noida deployments. The application layer is PHP/LAMP-based, built by Tetra's PHP team, with per-client PHP version and module customization handled case-by-case depending on what the original application build required (e.g. serving PHP 7.2 to match what a given deployment was built against, since installing modules independently for a mismatched PHP version won't work). Closes with an open Q&A, noting light attendance (only two trainees present) and encouraging questions be raised immediately rather than saved for later.

==Training session Tetra team on PHDCCI RADICO understanding. Dated 29 Nov 2022 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [NO ACCESS - VIDEO REMOVED] This video has been removed by YouTube entirely for violating YouTube's policy on harassment and bullying -- same situation as -Oi7OkupzWA elsewhere on this page. No content, transcript, or title is retrievable, and this cannot be fixed by the uploader since the video is permanently gone. The embed/link on the wiki page should likely be removed rather than repaired. Two removals for the same reason on the same "Training_2022_Linux_team" page is worth flagging as a pattern to whoever manages the uploading account.

==Training Session OTRS, Wiki & Nagios Monitoring. Dated 03 Dec 2022 - Tetra Support Staff - Alok==

{{#ev:youtube|7w3LGmsKgzI|640}}

'''Video summary:''' "Training Session OTRS, Wiki & Nagios Monitoring" -- a practical onboarding session covering three internal tools new team members need to use daily. OTRS (the ticketing tool): explains that client issues arrive via a dedicated support email address and generate tickets automatically; tickets show up in the "Status View" with a ticket number, title, timestamp, and an assigned owner (assignment is done by Pradeep, and each engineer's queue reflects the specific clients they're responsible for -- e.g. HP and Spectra tickets go to whoever owns those accounts); covers the ticket state model in detail -- "New" (just arrived, no work started), "Open" (actively being worked), and "Pending Reminder" (used when work is done on Tetra's side but the ticket is waiting on the client, e.g. for confirmation), stressing that engineers are responsible for moving tickets through these states correctly rather than leaving them stale. Nagios monitoring (the bulk of the session): demonstrates the live dashboard showing ~758 monitored hosts across many clients/servers/cloud locations, with per-host status codes (e.g. "0" meaning no active issue) and per-server service checks (CPU load, disk partition usage, Apache status, SSL certificate expiry, current logged-in users, and service-specific checks like MySQL for database servers or SMTP/IMSVA-Trend-Micro anti-spam status for mail gateways). Explains that these checks are implemented via NRPE plugins -- separate plugins exist per check type (disk, load, database, NTP/ping, swap, etc.), each with configurable warning/critical thresholds (e.g. a "check_users" plugin warning at 5 logged-in users and critical at 10; disk space warning at 20% free, critical at 10%) -- and that adding a new server to monitoring means installing/configuring NRPE on the target host (config typically lives under `/etc` or `/usr/local`), then registering that host as an object on the Nagios server itself with its IP and the correct client "host group" (functioning like a WhatsApp group -- all servers belonging to one client sit together under that client's group). Frames this as foundational knowledge -- new engineers are expected to study what NRPE/NCPA/NSClient plugins exist so they know which one to reach for when asked to monitor a new service type. The Wiki portion of the session's title is not covered in the transcribed content reviewed here (likely addressed in a portion with poor or missing captions).

==Training L0 And L1 calls training session Part 01. Dated 15 Dec 2022 - Tetra Support Staff - Varad==

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

'''Video summary:''' "L0 And L1 calls training session Part 01" -- a hands-on training session for the most common L0/L1 support call types, walked through live in a Zimbra-style admin panel using Motocorp (Hero MotoCorp) as an example client. Covers: verifying a user's identity/contact details before making changes (checking postal code and other stored contact info against what the caller provides, matching the client's on-file address in Raipur); resetting a user's password when a client has already created one but it needs to be reset -- entering the new password twice and confirming, then separately verifying the reset actually worked by copying a verification link into a pre-built notepad template, pasting in the user's email and password, and confirming login succeeds (troubleshooting a case live where the password initially appeared not to take effect); blocking a mail ID on client request (toggling account status from Active) and creating a new mail ID for a client (entering the ID, pressing Insert/Escape at the right points in the panel flow). Also touches on a related backend step -- after certain account changes, restarting the relevant Zimbra service (Amavis is mentioned specifically) using the appropriate restart command so the change takes effect. Summarizes the four core L0/L1 ticket types covered: create ticket, delete mail ID, block mail ID, and create mail ID (demonstrated for Hero MotoCorp). Ends by telling trainees they'll need to rejoin for a continuation session since this one is wrapping up.

==Training L0 And L1 calls training session Part 02. Dated 15 Dec 2022 - Tetra Support Staff - Varad==

{{#ev:youtube|8f8JJ6t3tEU|640}}

'''Video summary:''' "L0 and L1 training session Part 02" -- continues the L0/L1 call-handling series, working through real ticket examples end to end. Covers CLI-based user management via `zmprov`-style commands: a lookup command to view a client's full account info before making changes, a create-account command (demonstrated creating a marketing address), and setting/resetting a password. Walks through a CareIndia IP-whitelisting ticket: editing a specific two-line section of a config file (never anything below it) to swap out the old whitelisted IP for the new one provided in the ticket, with a strict "always edit exactly the first two lines, proper spacing" convention. Covers postfix relay-domain onboarding for CareIndia: adding a new mail domain/extension into the relay config with correct spacing, then running `postmap` to apply it -- flagged as one of three recurring CareIndia ticket types (alongside the other two just covered) that come in roughly every 8-15 days. Moves into Nagios-adjacent mail-queue management for Hero MotoCorp: checking mail queue status (`postqueue`-style commands) to see counts of active/deferred mail, checking how many messages are stuck pending, and flushing/clearing the queue with the appropriate flush command when messages are stuck -- repeated for a second server ("Relevant") with a much larger queue backlog (37 messages) using the same two-command pattern. Closes with an Arihant Electricals new-mailbox-creation ticket: stresses that when a client's ticket specifies both the mail ID and the desired password, that exact password must be used rather than generating a new one; walks through logging into that client's specific webmail admin URL, creating the account with the client-specified first/last name and password, and verifying the account works by logging in and changing the password via the admin panel as a final confirmation step.

==Training session Tetra team on Reachingcriticalwill some kloxo understanding. Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [DUPLICATE CONTENT] This video is byte-for-byte the same recording as HK-WXK5CCeo elsewhere on this wiki -- identical title ("Training session Tetra team on reachingcriticalwill some kloxo understanding") and identical transcript from the opening seconds onward. See the summary for HK-WXK5CCeo for the actual content (Reaching Critical Will client's LAMP website behind a Kloxo-managed proxy). Worth flagging to the page owner as a likely duplicate upload/embed rather than two distinct recordings -- one of the two embeds on this page is probably redundant.

==Nagios training session Dated 29 Dec 2022 - Tetra Support Staff - Varad==

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

'''Video summary:''' "Nagios training session 29 12 2022" -- a dedicated dashboard-navigation training for the Nagios monitoring platform (complementing the shorter Nagios segment in "Training Session OTRS, Wiki & Nagios Monitoring"). Tours the main views: Hosts (every monitored client/server, with up/down status -- demonstrated live with an actually-down server, "IMSS Tribune"), Host Groups and Hostgroup Grid (per-client server groupings with rolled-up OK/warning/critical/pending counts), and the technical overview dashboard showing totals (~758 services monitored, at the time 1 service in a problem state). Explains what specific alerts mean and how each gets resolved: SSL certificate expiry alerts (checked by domain expiry date, e.g. flagging a domain expiring in ~66 days as not yet urgent versus one expiring next month, escalated to L2 engineers, with a reminder to update the client and remove the domain from the watch list once renewed); root-partition/disk-usage warnings (won't clear until the underlying disk space is actually freed, unlike CPU-load or memory-utilization alerts which are typically transient and self-clear); and the difference between alerts requiring action versus those that just need a 15-minute wait-and-refresh cycle to auto-clear (e.g. temporary load spikes). Demonstrates the mail-queue-clearing workflow live for two named servers -- a relay server ("Relay 2") and Hero MotoCorp's mail server -- explaining that persistent mail-queue-count alerts require logging into that specific server and running a queue-flush command (distinct commands per server/context), unlike other alert types. Also covers reading the graph view for a host (total/down/warning counts visualized over time) and reiterates the standing team norm: any alert encountered should be posted/updated in the team's alert-tracking group as part of the response, not just resolved silently.

==Training session on Nagios Alert 07 Feb 2023 - Tetra Support Staff - Alok==

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

'''Video summary:''' "Training session on Nagios Alert Tetra Support Staff Alok" -- a focused session on the judgment call behind mail-queue-growth alerts specifically: when a queue-size warning fires but the support engineer on shift doesn't have credentials to log into that particular mail server, the correct move is NOT to guess whether it's normal or a problem -- it's to call the engineer who does have access and ask them to check the actual mail contents. Uses Hero MotoCorp as the running example: it has 3000+ dealer/account recipients, so any single outbound campaign naturally spikes the queue as it fans out to all of them, making a growing queue completely normal there and not something to escalate reflexively. Teaches the actual verification method for engineers who do have access: log into the server and read the queue contents directly to confirm whether messages are genuine business mail or spam, and if genuine, no action is needed even though the count keeps climbing -- but recommends watching the trend for at least 20-30 minutes before concluding it's benign, since a queue that keeps climbing without leveling off is the actual red flag. References a real recent incident as a contrast case: spam sent through one relay mail ID caused a relay server's queue to spike to ~2000+ messages overnight, which was NOT normal and required immediate escalation -- explicitly reasoning that queue growth can't just be assumed harmless, because if it actually is spam, the sending IP risks getting blocklisted by receiving mail providers, which is the real business risk driving the urgency to verify rather than wait.

==Training session on Basic qmail training 24 March 2023 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Basic qmail training" -- a clear English-language session explicitly scoped as diagnosis/troubleshooting knowledge, not qmail installation (Tetra doesn't build new qmail environments, but still supports the few legacy ones that exist, plus Kloxo's internal use of qmail). Demonstrates identifying a running qmail environment via `netstat -ntplu` (spotting MySQL, ClamAV, a separate spam-scanning engine, POP3, and port 25/SMTP via `tcpserver` -- notably no IMAP on this particular primitive setup) and `qmailctl stat` to confirm all qmail sub-services are up. Covers the SMTP relay/control-file configuration for outbound mail: a client (HACO India) is shown routing all outbound mail through `server-relay.tetrain.com` via qmail's `smtproutes` control file, where a blank/no-domain entry acts as a catch-all default relay; explains how to safely change which relay server a domain uses (first confirm the new relay server's IP is allow-listed on the target relay, then update the control file) and explicitly warns against changing it reflexively on a single complaint -- if mail were truly going to spam/junk for everyone using that relay, many customers would be reporting it, so an isolated complaint usually means something specific to that one customer, not the shared relay. Walks through qmail's multi-log tracing pattern in detail, paralleling the Zimbra/Postfix tracing training elsewhere on this wiki: SMTP-level connections land in `/var/log/qmail/qmail-smtpd/current` (piped through `tai64nlocal` to get human-readable timestamps); antivirus/spam scanning results appear in the mail log (ClamAV plus the separate spam engine, tagged with spam-score info); and actual delivery status is tracked separately in `qmail-send`'s log, where entries are tagged "local" (delivered to a local/virtual-domain mailbox) or "remote" (relayed onward, typically via the configured relay server's IP) with numeric delivery/message IDs and explicit "delivered"/"bounced" (symbol-marked) outcomes -- e.g. a bounce caused by "no such mailbox." Clarifies virtual-domain handling: a domain not present locally as a virtual domain gets routed remotely rather than delivered locally. Ends with a brief live Q&A confirming the local/remote distinction, before the session is interrupted by an unrelated incoming maintenance-window request for a database downtime window.

==Training session on Zimbra8 6 OS centos6 to zimbra8 8 15 RHEL8 migration session1 30 March 2023 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Zimbra8 6 OS centos6 to zimbra8 8 15 RHEL8 migration session1" -- a detailed walkthrough of migrating a Zimbra 8.6 Open Source instance on CentOS 6 to Zimbra Network Edition 8.8.15 on RHEL 8, following Zimbra's official migration documentation closely (explicitly flagged as important since rsync binaries are OS-version-specific -- reusing binaries built for the wrong OS release will break things). Covers the documented flow: confirm backups exist first; on the old server, take an LDAP dump (`slapcat`-equivalent), back up mail/message data, and export it; provision a brand-new target server (rather than in-place upgrading) and run the appropriate Zimbra install/restore process there. Walks through setting the new server's admin/LDAP/MySQL passwords to match the old server's -- pulled directly from the old server's `localconfig.xml`, since matching credentials are required for the LDAP data restore to work. Details the LDAP import itself: stop Zimbra on the new server, back up the existing empty LDAP directory, then import only the actual database content (explicitly skipping config and access-log databases as unnecessary for this migration, unlike a master/master replication setup which would need them) using the previously-exported LDAP dump file, followed by an `ldap-config`/reindex-equivalent structural rebuild step that must exactly match between old and new (any mismatch causes problems) -- this rebuild step being the most time-consuming part of the whole process. Covers the actual mail-data transfer approach: rsync the full mailstore/index directories from old to new server, timing a couple of incremental rsync passes first to estimate how long a final sync will take (recommending doubling the observed time as a safety margin when scheduling the actual cutover window, since some additional work is always needed beyond the raw sync). Also covers practical field-support realities: confirming with the trainee whether remote access to the target site is available before the actual cutover, since at least one deployment location has no internet connectivity requiring physical presence. Session closes previewing the next topics -- building a Zimbra cluster and the incremental upgrade path (8.6 to 8.7 first, not straight to 8.8, since intermediate hops are required) -- promising the recording will be shared afterward as a reference alongside hands-on practice.

==Training session on Hero forwarding delegated admin 07 April 2023 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [NO ACCESS - VIDEO REMOVED] This video has been removed by YouTube entirely for violating YouTube's policy on harassment and bullying -- the third such removal found on this "Training_2022_Linux_team" page (alongside -Oi7OkupzWA and jvQ3KWMbCTU). No content, transcript, or title is retrievable, and this cannot be fixed by re-uploading under the same account necessarily fixing anything -- three strikes on one page for the same policy is a pattern worth investigating with whoever manages the uploading account, since it may put the account itself at risk. The embed/link on the wiki page should be removed rather than repaired.

==Training session on SORBS Security admin 05 June 2023 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' "Sorb Security Google Chrome 2023 06 01 16 08 58" -- a business/product overview session on why commercial-grade mail security is necessary, explicitly separate from a technical deep-dive (framed as covering the commercial/administrative angle). Opens with a candid admission: Tetra has lost customers in the past due to not having a strong enough security solution, citing real recurring support calls -- clients like Arihant and HCF calling to get senders blacklisted -- as evidence that basic spam filtering alone isn't enough anymore; modern threats require ATP (Advanced Threat Protection covering phishing and content filtering) on top of traditional antivirus/antispam. Describes Trend Micro's evolution as a case study: their older IMSVA (InterScan Messaging Security Virtual Appliance) product required a dedicated on-prem machine routing mail traffic through it, whereas their newer offering is fully cloud-based -- customers simply point their MX record at Trend's cloud security layer. Covers rough cost comparison to frame the business case: a basic Zimbra-based add-on security layer runs roughly ₹100/mailbox/year at scale (3-4000 users), while dedicated enterprise-grade security gateway solutions (naming "Sorb Security" among ~12 comparable vendors in this space) start around a ₹2000/mailbox minimum, historically positioning them as enterprise-only -- but the presenter notes newer entrants are bringing that cost down significantly as they push into the Indian market. Explains the underlying technology at a high level: these solutions route mail through a sandboxed cloud environment where AI-driven rules analyze the full message context (not just static signature matching) before delivery, with sandboxing specifically defeating novel/zero-day spam techniques that wouldn't be caught by traditional pattern matching.

==Training session on Radico Client Training Video - Tetra Support Staff - Alok Singh==

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

'''Video summary:''' "Radico Client Training Video" -- a hands-on MySQL master-slave replication architecture walkthrough for the Radico client, run over remote desktop rather than VPN since this client doesn't provide VPN access. Radico's application is a LAMP-style setup (a separate Apache server) with dedicated database servers split across two physical locations, Sitapur and Rampur -- each location runs one MySQL master and one MySQL slave (4 database servers total, 2 pairs). The presenter built the Sitapur pair personally (Rampur's was inherited/pre-existing but functionally identical) and documented the setup on the internal wiki. Explains the replication mechanics: MySQL Community Edition installed on both nodes; the master grants a dedicated replication user/password to the slave; key config values on the master include `server-id` and `gtid_mode`, and GTID (Global Transaction ID) is the mechanism used to verify replication is actually in sync -- checked via `SHOW SLAVE STATUS` on the slave and comparing its GTID reference against the master's `SHOW MASTER STATUS` / executed-GTID-set output, which must match. Config changes (e.g. raising `max_connections` from a default like 500) go in `my.cnf` under the `[mysqld]` section, requiring a MySQL restart to take effect. Explains the operational significance of master-slave (as opposed to master-master, contrasted with the YouSecure architecture covered elsewhere on this wiki): failover here is NOT automatic -- the application server only ever points at the master's IP, so if the master goes down, promoting the slave requires manually and completely shutting down the dead master first, then reassigning its IP to the slave, since the application has no built-in awareness of the slave's existence; this must never be done to a live/running master, only after confirming it's fully down, since two servers simultaneously claiming the master IP would cause serious problems. Contrasts this with a master-master setup (like YouSecure) where both nodes replicate bidirectionally and either can serve as primary behind a load balancer, with automatic failover. Closes confirming Radico's total footprint is 4 database servers (2 master-slave pairs, one per location), with a light aside about the recording being on.

==Training session on Carbonio Internal Presentation - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|4gH5VuNIPjo|640}}

'''Video summary:''' "Carbonio Internal Presentation" -- a strategic internal presentation introducing Carbonio as Tetra's planned successor to Zimbra Open Source. Sets the business context up front: Zimbra Open Source is effectively end-of-life -- no further binary updates/upgrades are expected from Zimbra, and even where upgrades were technically possible they're no longer straightforward the way they used to be -- so an alternative open-source mail platform is needed. Explains why Carbonio specifically over other open-source alternatives (Group-Office, iRedMail-type platforms mentioned as considered but passed over): Carbonio is built by Zextras, a company that has long built commercial add-ons and enhancements for Zimbra itself (mobile sync, backup tooling, etc. for the open-source edition), so its architecture, CLI (a `zextras`-equivalent to `zmprov`), and overall feel are intentionally very close to Zimbra, minimizing the relearning curve. Notes Carbonio's community edition (CE) comes with a 5-year open-source commitment from Zextras, distinguishing it from a purely commercial-only product, and that after evaluation the platform is judged stable enough to start onboarding real customers, with a concrete plan to migrate Tetra's own Zimbra mail onto Carbonio within about two weeks as an internal pilot, working with the service team through that migration for hands-on familiarity. The bulk of the session is a live demo comparing feature-by-feature against Zimbra: the admin console runs on a different port (6071) with a default `zextras`-named admin account rather than Zimbra's `admin`, but otherwise closely mirrors Zimbra's admin structure -- account creation, domains, Class of Service, global address books, LDAP-based authentication (with the same external LDAP/AD integration options used on real client environments like GSTN), per-user/group mailbox quotas, and a genuinely new capability: a built-in disclaimer/footer editor in the admin UI itself, versus Zimbra where this required CLI work. Covers resource booking (shared meeting rooms/projectors), multi-server architecture support (relevant since most of Tetra's open-source Zimbra deployments are single-server, unlike commercial multi-server setups such as ISGEC's separate MTA/mailbox/LDAP split), storage/data-volume management, and an MTA-monitoring panel (queues, spam/antivirus status, TLS config) that in Zimbra required CLI access. On the user-facing side: near-identical mail composition/attachment flow (including attaching from a server-side drive, not just local files) but with several features built in that Zimbra needed bolted on separately -- integrated chat (vs. Zimbra requiring a separate chat add-on), built-in video/screen-sharing meetings with presence indicators (positioned as a possible internal Zoom alternative), a Zimbra-Drive-equivalent file-sharing feature with mobile support, and native ActiveSync plus first-party mobile and desktop apps (versus Zimbra needing a separately-built ActiveSync server for Outlook-based clients). Session includes some live technical hiccups (screen-share/Zoom glitches) consistent with an unpolished, in-progress internal evaluation rather than a rehearsed product pitch.

==Training session on Aadani Pariyojna Traning Video - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' "Adani Project Training Video" -- an architecture and support-process handover for Adani's LAMP application. Two identical LAMP servers run in active-passive HA (same credentials on both, automatic failover if one goes down), plus a separate UAT server used for pre-production testing. Explains the primary recurring type of ticket: vulnerability-assessment remediation, where Adani provides a spreadsheet of specific vulnerabilities to close, applied identically to both production servers since they're kept in sync -- gives concrete past examples (disabling TRACE method via config changes, tracking exactly which of several possible methods was used for later reference; renewing an expired SSL certificate on both production servers, keeping notes on the config file paths touched at the time for future reference). Covers login access: reached via a client-provided VPN link and URL, with login requiring approval from a specific person (Rakesh) as an access-control step -- new team members needing access must go through him. Explains the collaboration model for fixes that aren't purely infrastructure-level: some vulnerability findings are developer-side (PHP/application-level) rather than server-level, requiring coordination with the client's own dev team or their assessment vendor's team via a walkthrough meeting to fully understand and properly close an issue rather than guessing. Covers service-restart etiquette: when implementing config changes that require restarting Apache or MySQL, the client should always be told the expected downtime up front (e.g. "Apache restart is roughly 30-40 seconds" or a few minutes for other changes) so they can choose a low-impact time to schedule it, rather than restarting unannounced. Clarifies database ownership: Tetra's own team (naming a colleague, Deepika, who handles the PHP/application side) manages the database directly; database credentials aren't kept readily on hand and need to be requested from her via chat when actually needed for a login.

==Training session on Nagios Training Service team part2 03 March 2024 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - frequent dropped words/audio glitches throughout, likely a mic/connection issue on the presenter's end; summary reflects the identifiable topic flow] "Nagios Training Service team part2" -- continues directly from a prior Nagios session (recapping NRPE, NSClient, NCPA, and SNMP as the device-onboarding mechanisms already covered). Goes deeper into application-level and platform-level monitoring: using Nagios's built-in Oracle and MySQL database plugins directly rather than building custom checks; monitoring VMware at both the host and guest VM level. Introduces SNMP traps as a concept distinct from the polling-based checks used so far -- a trap is the monitored device proactively pushing an alert (e.g. "I've crossed 80% utilization") to Nagios rather than Nagios polling for it -- but explicitly recommends against using traps in most environments in favor of standard polling, flagging it mainly as something worth understanding conceptually since it may come up in questions. Walks through Nagios's config file structure directly on the server under `/usr/local`: `commands.cfg` for check-command definitions, and separate host/service definition files, with an explicit warning not to hand-edit certain auto-generated config files. Mentions a config/CRM-style ID system used to identify/relate hosts to specific customers. Given the significant transcript quality issues throughout this recording, finer procedural detail beyond this topic outline could not be reliably captured.

==Zimbra-Daffodil-Webinar-session 12 Dec 2024 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' "Zimbra Daffodil Webinar 12 12 2024" -- a ~2-hour public marketing/partner webinar (not an internal training session, unlike most other videos on this page), jointly hosted by Zimbra, Sorb Security, and Tetra Information Services, aimed at prospective customers. Structure: Tetra's Mukul Mahajan opens with company background (established for years, open-source-focused, 24x7 support, partnerships with Red Hat, Elastic, Sorb Security, and a ~10-year Zimbra service partnership) and introduces the panelists -- Biswajit Banerji (Tetra's Technical Director, 30+ years experience, 15+ years in Zimbra specifically), Push Mathur (Zimbra's senior sales engineer for the APAC/India region), Mr. Ban (CEO of Sorb Security, email-security specialist), and Mukul himself. Push Mathur presents Zimbra's product pitch: positioned as a full open-core collaboration suite (mail, calendar, contacts, chat, video conferencing in one interface, not just email), with hundreds of millions of mailboxes deployed across government/education/enterprise/banking customers; a key differentiator is deployment flexibility (on-prem, colocated data center, private/public cloud, or hosted) versus competitors that lock customers into cloud-only; positions Zimbra as lowest total-cost-of-ownership, horizontally scalable without service disruption, and strongly data-sovereign since Zimbra itself never touches or stores customer mail data when self-hosted; covers mobile/MDM support (ActiveSync, remote wipe, corporate-approved-device enforcement) and open APIs enabling third-party integrations. Mr. Ban then presents Sorb Security's email-security product (the same product covered in more technical depth in the separate "Sorb Security" video on this wiki) -- highlighting an anti-phishing approach based on containerized/sandboxed link browsing (so a user can safely click a suspicious link inside an isolated container without actually being able to submit credentials, framed as 100% prevention rather than probabilistic detection) and a "MySpace" self-service portal for end users to release quarantined mail, maintain business continuity if the mail server is down, manage personal allow/block lists, and use AI-assisted features like automatic translation of foreign-language email content -- pitched as enterprise-grade capability at a more accessible price point than established competitors. Biswajit Banerji then covers Tetra's value proposition as the implementation/support partner: extensive migration experience from Google Workspace, Microsoft 365, and other open-source mail platforms onto Zimbra, claiming near-zero-downtime migrations even at multi-million-mailbox, hundreds-of-servers scale, using in-house-built migration tooling. Includes live audience quiz/poll segments and a Q&A collected via chat for a later session. Given the marketing/webinar format and its length, this summary reflects the overall pitch structure and key claims rather than a full transcript of all two hours.

==Technology Presentation BB for Eng Onboarding 27 Dec 2024 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' New-engineer onboarding presentation given by Biswajit Banerjee covering Tetra's company history and full technology breadth (not a client-specific support session like most others). History: founded 1995 by four co-founders (the name "Tetra" = four), spun out of a company called PCL, started in hardware sales and Novell Netware deployments in the pre-internet era, moved into Linux around 1997-98, built early internet/mail/proxy/Samba solutions for client offices, weathered the Y2K migration, and evolved its mail-hosting stack over the years from sendmail to qmail to Postfix/Zimbra (Zimbra since ~2006-07). Second half covers the company's current scope: hybrid Zimbra + Microsoft 365 deployments, ELK and Prometheus/Grafana monitoring, their own in-house CloudStack private-cloud platform (a major current growth focus), Kubernetes/microservices/DevOps work, their OTRS-based "iHelpDesk" ticketing product, document management via Nextcloud/Alfresco, and custom LAMP-based government/enterprise software projects (notably an "online building plan" application used at scale in West Bengal, Punjab, and Haryana, integrating with third-party scrutiny software and pitched internationally). Closes with a client-name overview spanning large enterprises (Adani, ICICI Bank, NTPC) and SIs (Infosys, HP), framed as context for why new engineers need to stay comfortable picking up new technology rather than specializing narrowly.

==Take backup on Simple storage (S3) 23 Aug 2025 - Tetra Support Staff - Tushar==

{{#ev:youtube|8wLxa2OKINE|640}}

'''Video summary:''' "Take backup on Simple storage (S3)" -- a hands-on walkthrough of backing up server data (specifically database dumps) to S3-compatible object storage using rclone. Covers the AWS-side prerequisites: creating a dedicated IAM user in AWS IAM with full S3 access, selecting the "third-party tool access" user type (rather than AWS Management Console access) when creating it, and generating that user's access key ID and secret access key for use by rclone. Walks through installing rclone via a curl-downloaded install script, then configuring a named "remote" (visible later via `rclone config show`) pointing at the S3-compatible endpoint -- demonstrated using DigitalOcean-style object storage as one example endpoint, but explicitly generalized: rclone/most S3 clients (including the S3 Browser GUI tool also demoed) support any S3-compatible provider, not just AWS S3 itself, selectable via an account-type dropdown ("Amazon S3" vs "S3 Compatible Storage"), with the connection URL/endpoint and region needing to match the chosen provider. Explains the actual backup command structure: `rclone sync` (not `copy` -- sync mirrors changes to the destination rather than accumulating duplicate copies each run) with the source being a local database dump file/variable and the destination written as `remotename:bucketname/folderpath`; notes the target bucket and folder are auto-created on first run if the third-party access permissions are set correctly, and that bucket names must be globally unique across all of S3 (not just within the account) -- if the sync command doesn't auto-create the bucket, that's a signal the chosen name is already taken elsewhere and needs to change. Covers two important tuning flags used in Tetra's actual backup scripts: retention logic that deletes all but the 7 most recent incremental backups as new ones land (rolling 7-copy retention), and `--tpslimit 5` to rate-limit the client's own outbound API requests (GET/HEAD checks against the bucket) so as not to exceed the storage provider's request-rate limits, which otherwise produces rate-limit errors during sync -- particularly relevant since `sync` (versus plain `copy`) does more existence-checking against the destination and is more prone to hitting this limit. Also briefly demonstrates the equivalent GUI workflow in S3 Browser for managing multiple S3-compatible accounts/credentials side by side.

==NIC-CODE update recording session 04 OCT 2025 - Tetra Support Staff - Vinod==

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

'''Video summary:''' [NO ACCESS - VIDEO REMOVED] This video has been removed by YouTube for violating YouTube's Terms of Service (a general ToS violation, distinct from the three harassment/bullying removals found elsewhere on this "Training_2022_Linux_team" page -- -Oi7OkupzWA, jvQ3KWMbCTU, and KwKpsjt2x5k). No content, transcript, or title is retrievable. This is the fourth video removal found on this single page, which strongly suggests a systemic problem with the uploading account rather than four unrelated incidents -- worth raising directly with whoever manages that YouTube account, since repeated ToS strikes can put the account itself at risk of suspension, which would take down every other (currently working) video on this and other wiki pages hosted under the same account.

Zimbar NE Demo Video made for Tender

2026-07-25T02:52:53Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Zimbra]]
== Zimbra NE Demo ==

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

'''Video summary:''' [NO ACCESS] This video has been deleted from YouTube ("This video isn't available anymore") and can no longer be viewed, transcribed, or recovered. The embed on this wiki page will need to either be removed or replaced with a note that the recording is gone.

Help:Editing

2026-07-25T02:52:52Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:NKDA]]

==Training on NKDA-Architecture. Dated 13 NOV 2024 - Tetra Support Staff - NARENDRA==

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

'''Video summary:''' Detailed architecture walkthrough (video titled "NKDA-Architecture") of a multi-site Zimbra Network Edition 10.0 mail deployment across three locations (Hyderabad, Kota, Jetsi), migrated from an earlier RainLoop/Rainmail setup. Each site runs redundant physical mail servers (MTA + LB + mailbox pairs in a PCS/DRBD HA cluster, shared NAS storage, automatic failover) plus a dedicated archive server that every user's mail is copied to. Inbound mail flow: KSMG gateway (spam/rule filtering) -> IMSVA (inbound/outbound scanning and per-domain/account rules) -> Postfix daemon -> MTA -> mailbox. Only the Hyderabad servers have direct internet mail access; Kota and Jetsi route all outbound mail through Hyderabad's MTA. Covers an "ANet" gateway used only for a set of internal-only domains (with a documented bypass procedure -- commenting those domains out of the MTA's transport file -- if that gateway goes down), quota tiers assigned by job grade/designation, scripted user creation that auto-provisions the matching archive account, a 90-day password rotation policy, blocking password-protected PDF attachments from being delivered, and the daily check needed on DRBD-based sites (Kota/Jetsi) to confirm primary/secondary storage sync hasn't fallen behind, since a failover during incomplete sync causes real data loss.

Technical Training Serssions 2021 Linux Team

2026-07-25T02:52:51Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Training‏‎]]

==Session for Client Introduction with Technologies (Part1) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, mixing gibberish Hindi filler words with scattered English fragments] "service training 16Jan part1" -- a service/support training session recording. The few legible fragments reference "News Nation environment," "architecture," and "customer service," suggesting this covers the News Nation client's environment architecture (consistent with the News Nation Zimbra distribution-list content covered elsewhere on this wiki) as part of a support-team training session. Given the severity of the transcription failure, no reliable detailed summary of the actual training content can be produced from this recording.

==Session for Client Introduction with Technologies (Part2) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

{{#ev:youtube|7VX1kXFQWEs|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as Part 1] "service training 16Jan part2" -- continuation of the same service training session. Legible fragments reference mailbox/email topics: downloading mail via a mobile mail app, a shared mailbox scenario where multiple people need access to the same mailbox, and antivirus. Given the severity of the transcription failure (consistent with Part 1 and the wider pattern seen elsewhere on this wiki, e.g. the ISON_BPO_Deployment_Videos page), no reliable detailed summary of the actual training content can be produced.

==Session for Client Introduction with Technologies - capital bank . Dated 18th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

{{#ev:youtube|9rHaInJVD84|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other service training recordings] "Service training jan 18th" -- another service training session in the same series as the 16 Jan recordings, with the same severe transcription failure. No reliable content summary can be produced from the legible fragments alone.

==Session for Client Introduction with Technologies - JBOSS/POSTGRESQL Brijraj/Beetel . Dated 19th Jan 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other service training recordings] "Service training Jan19" -- continuation of the same service training series (16/18/19 Jan), same severe transcription failure. No reliable content summary can be produced.

==Session for Client Introduction with Technologies - LAMP . Dated 20th Jan 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the "service training" recordings on this page] "Training session Jan20 php mysql" -- a training session on PHP/MySQL web application architecture (per the title and a few legible fragments referencing application requirements, a PHP-based application model, and configuration/software requirements), but the transcription failure is too severe to reliably summarize the actual content taught.

==Session for Introduction with Technologies - Generic . Dated 24th Mar 2021 ==

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

'''Video summary:''' "Training Session 2021 march 1" -- a clear, well-recorded English-language company-wide technology overview and onboarding session (unlike most of the other videos on this page, this one has good transcript quality throughout). A senior team member walks newer staff (Sanju, Chandrakant, and others) through the breadth of technologies Tetra supports across its client base, and points them to Tetra's internal wiki (the same wiki this cleanup project is auditing) as the canonical source of implementation, fine-tuning, release, integration, and deployment-issue documentation -- explicitly framing it as an asset built up by the whole team over years that new hires must be given access to and contribute back into. Covers, in order: Zimbra (open source and enterprise, from small to very large/enterprise deployments); cloud platforms used (AWS, Google Cloud, Linode, DigitalOcean); DRBD clustering as a "poor man's cluster" used when a customer won't provide dedicated SAN/LUN storage (cited customers: RDM, News Nation); full open-source Linux-based data center builds for customers like RDM (firewalls, mail, AD, virtualization all on Linux); backup tooling (Bacula for Capital Bank; Amanda/Zamanda for Infosys DOP's DR/DC services); Postfix as a critical, deeply-understood component underlying Zimbra; PHP/LAMP applications requiring deep Apache/PHP/MySQL tuning at scale, including a hospital-management LAMP application; JBoss + PostgreSQL deployments (Beetel's Java application, built in-house, requiring JBoss/JDK performance tuning); Samba as a Linux-based AD replacement for large customers like GSTN, alongside a note that for very large/sensitive clients Tetra often works L3/L4 alongside an on-site L1/L2 team; Trend Micro IMSS (Internet Messaging Security Suite) for mail security, deployed for a customer called Pahwa; a potted history of Tetra's mail-server technology evolution (sendmail in 1997-98, qmail from 1998 through ~2010-2011, then migration to Zimbra), with qmail still living on inside the Kloxo control panel (a free, open-source cPanel-alternative demoed live, used for small customers needing basic mail/DNS/PHP/MySQL hosting); Tetra's own mail-relay infrastructure (three relay servers, Postfix-based, needed because major cloud platforms block direct outbound mail, requiring correct DKIM/SPF/domain setup); Oracle OVM as a virtualization platform (used by Capital Bank); RHEV and its free/open-source equivalent oVirt as enterprise virtualization platforms (RHEV deployed for GSTN); Red Hat Satellite for patch/system management; and the ELK stack (and its packaged form, Graylog) for centralized log management and dashboarding at scale, with large deployments at Infosys and as part of the GSTN portal's monitoring stack.

==Session Harsh for Team about Infosys-ITD zimbra Deployment . Dated 25th Mar 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other Harsh/service-training recordings on this page] "Harsh Training to Engineers" -- an internal engineer training session walking through client architecture documentation. Legible fragments reference the Income Tax Department of India as the example client, a multi-service setup for roughly 500 users with paired MTA/proxy servers, mailbox storage, and DC/DR (data center/disaster recovery) redundancy -- consistent with a Zimbra multi-server HA architecture walkthrough similar to other client-architecture training sessions on this wiki. Given the severity of the transcription failure, a reliable detailed summary beyond this high-level topic identification cannot be produced.

==Session for Introduction with Mail Concept . Dated 25th Mar 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "training session 25th" -- a fundamentals training session on mail protocols. Legible fragments cover the difference between POP3 and IMAP (POP downloads mail locally and can remove it from the server, leaving no server-side copy accessible from other clients, versus IMAP which keeps mail on the server and syncs across clients/offline mode), configuring these in Outlook/Thunderbird-type clients, and general mail server security concepts. Given the severity of the transcription failure, a reliable detailed summary beyond this topic identification cannot be produced.

==Session Harsh for Team about Infosys-ITD ELK Deployment . Dated 26th Mar 2021 ==

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

'''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - heavily garbled Hindi ASR with technical terms frequently mis-transcribed; summary reflects only confidently identifiable content] "ELK Training By Harsh" -- an internal training session on the ELK (Elasticsearch, Logstash, Kibana) stack plus Kafka, using the Income Tax Department of India as a real client example of the architecture. Explains the general log-pipeline pattern: Filebeat-type lightweight shipper agents run on each source device/server to pick up and forward logs; Kafka sits in between as a message broker/buffer so many source devices' logs can be collected without overwhelming the pipeline; Logstash parses and transforms the incoming log data; and Elasticsearch indexes and stores it for fast search. Kibana then provides the graphical dashboard/visualization and search layer on top, including building different reports/visualizations per log type when there are many source servers to monitor. Frames the use cases in relatable terms: comparing it to how large platforms (Facebook, Google) use similar log/event-analytics platforms to detect and moderate problematic content at scale, and describing security/infrastructure use cases like traffic monitoring, alerting, and correlating activity across many devices in an organization's environment. Given the heavy transcription noise throughout, exact configuration steps and commands could not be reliably captured -- this summary reflects only the architecture and concepts that came through clearly.

==Session for Mail Concept (Contd). Dated 26th Mar 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "training mail concept contd" -- continuation of a mail-fundamentals training session, this time on mail security/anti-spam concepts. Legible fragments reference comparing mail security gateway vendors (Trend Micro vs Barracuda), IP block lists and how mail gets released from them, spam-filtering approaches, and a passing mention of Axis Bank in a list-related context. Given the severity of the transcription failure, a reliable detailed summary beyond this topic identification cannot be produced.

==Session Harsh for Team about Samba and Desktop Central Deployment at Triburg. Dated 27th Mar 2021 ==

{{#ev:youtube|6CHqu7iuY68|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other Harsh-led recordings on this page] "Training - SAMBA and Desktop Central for Triburg - Harsh" -- an internal training session on the Samba + ManageEngine Desktop Central setup built for client Triburg. Legible fragments indicate Samba was deployed as a Linux-based domain controller (replacing a Windows AD license), taking roughly 3-4 months to build out, paired with a ManageEngine Desktop Central agent/panel for managing endpoint devices -- printer sharing, device/mobile settings, and patch/software deployment across machines joined to the domain -- without needing per-machine Windows Server licensing. Given the severity of the transcription failure, a reliable detailed summary beyond this topic identification cannot be produced.

==Session Harsh for Team about NextCloud deployment at Triburg. Dated 1st April 2021 ==

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

'''Video summary:''' [NO TRANSCRIPT AVAILABLE] "Nextcloud training harsh" -- a 1hr26min unlisted internal training recording with no auto-generated captions/transcript available on YouTube at all (unlike most other videos on this page, which have garbled but present captions). Based on the title alone, this is an internal training session on Nextcloud (self-hosted file sync/sharing, likely covering a deployment Tetra has built for a client, consistent with the ISGEC Nextcloud/Piler/Samba deployment referenced elsewhere in this engagement's history) presented by the same "Harsh" who leads several other training sessions on this page. No content details can be honestly reported without a transcript.

==Session Harsh for Team about Various Clients deployments. Dated 2nd April 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other Harsh-led recordings on this page] "Training by Harsh multiple client part 1" -- an internal training session covering setups across several different clients (per the title). Legible fragments reference Samba file/folder shares and quotas, migrating data between old and new servers, and Samba service configuration/recommendations. Given the severity of the transcription failure, a reliable detailed summary beyond this topic identification cannot be produced.

==Session for Zimbra Mail Concept (Contd).Part2 Dated 2nd April 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "zimbra mail concept of services firewall and structure" -- per the title, a fundamentals training session on Zimbra's internal services, firewall requirements, and overall server structure. Legible fragments reference Zimbra version 8.x, comparing open-source and commercial editions, and general security topics, but the transcription failure is too severe to reliably reconstruct the actual technical content taught.

==Session for Zimbra Mail Log Analysis Approach Dated 5th April 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "training zimbra log analysis approach" -- per the title and a few legible fragments, a training session on reading Zimbra's log structure (mailbox/mta logs) to trace mail flow -- specifically framed around answering "who sent this mail and where did it go after being sent." Also touches on identifying critical services vs. normal log noise. The transcription failure is too severe to reliably reconstruct the specific commands or log-reading techniques taught.

==Session for Zimbra Mail Log Analysis Approach (part2) Dated 6th April 2021 ==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "training zimbra logs understanding part2" -- continuation of the Zimbra log-analysis training. No reliable content summary can be produced from the legible fragments alone.

==Session for Essel and Spectra (part2) Dated 2nd October 2021 ==

{{#ev:youtube|sN3e-nhIp2U|640}}

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "Essel or Spectra" -- a training/architecture session covering one of these two clients' environments (title suggests it may cover either/both). Legible fragments reference multiple geographic server locations (Delhi-Mumbai and Bengaluru-Chennai corridors), a video server, a monitoring/worker service distributing load between servers, and general "customer problem" troubleshooting framing. Given the severity of the transcription failure, no reliable detailed summary of the actual architecture or content can be produced.

==Session for Client Introduction with Technologies (Part1). Dated 2nd November 2021 - Tetra Support Staff - Chandra Kant Shakya==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "BLS,Pahwa,Brijraj,Beetel,Techfour,Interarch." -- a multi-client overview/handoff session per the title, covering BLS, Pahwa, Brijraj, Beetel, Techfour, and Interarch. Legible fragments reference Beetel International's main mail server, checking Zimbra logs, and Zimbra's attractor/calendar sync configuration. Given the severity of the transcription failure, no reliable per-client summary can be produced beyond this list of clients covered.

==Session for Client Introduction with Technologies (Part2). Dated 3rd November 2021 - Tetra Support Staff - Chandra Kant Shakya==

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

'''Video summary:''' [VERY POOR TRANSCRIPT QUALITY - largely unusable ASR output, same gibberish pattern as the other recordings on this page] "Energo,Kloxo,Triburg,Careindia,mobilepedia,WB,proxmox" -- a multi-client overview/handoff session per the title, covering Energo, Kloxo (control panel), Triburg, Careindia, Mobilepedia, WB (West Bengal), and Proxmox. Legible fragments describe adding a mail ID/archive account to a config file via a copy-paste-and-edit-then-postmap process, and mentions two Zimbra servers ("Trai Bharti"-sounding client) working together, plus Energo running multiple domains (Energo Products, Chanel India). Given the severity of the transcription failure, no reliable per-client summary can be produced beyond this list.

Category:Spectranet

2026-07-25T02:52:50Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
==Spectra PCS cluster failover process. - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' Live demo of the PCS cluster failover process for Spectranet's Nagios monitoring server. Before failing over, checks that DRBD (application data) and MySQL master-slave replication are fully synced between the two nodes. Failover itself is done by putting the currently-active node into standby (`pcs node standby`), which cleanly stops its services in order (Apache, cron, NPCD, Nagios) while the other node starts the same services and takes over the virtual IP -- verified both from the Nagios admin panel and from the backend PCS/fencing status. Demonstrates the failover in both directions (node 2 to node 1, then back), including running a manual `resource cleanup` when one stop step reported a failure. Confirms the web interface stays reachable throughout via the shared virtual IP.

==Spectranet Training. Date:- 31- January- 2026 - Tetra Support Staff - Manish Singh==

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

'''Video summary:''' KT session on Spectranet's SOC (Security Operations Center) Nagios XI environment, recently upgraded (OS and Nagios version both bumped). Architecture: a primary Nagios XI node in an HA pair (MySQL master-master replication + DRBD disk sync between the two nodes, PCS/fencing managing which node is live). Covers a recent architecture change: the old "Probe" satellite-server setup (used to offload monitoring load for remote/high-volume devices, feeding passive checks back to the main server) was replaced with Nagios XI's newer built-in Mod Gearman distributed-worker feature, which fixed a recurring problem where passive checks weren't triggering alerts in a timely way -- the probe machine is now just a Gearman worker, not a separate monitoring instance. Flags an important operational caution: at the time of recording, MySQL replication to the secondary HA node is broken/paused (not yet fixed), so the team must not attempt to shift the cluster over to that node. Also walks through the credentials sheet for VPN/server/web-console access, and references separate documentation already uploaded to the wiki covering the DRBD/Pacemaker cluster setup and the OS/version upgrade process used (built a fresh VM on the new OS, migrated the existing app version across, then upgraded in place).

Tetra Training Videos on Hangouts

2026-07-25T02:52:49Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Training‏‎]]

==Session for Mail Server concept . Dated 15th may 2014 - Tetra Support Staff - Biswajit Banerjee==

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

'''Video summary:''' [NO ACCESS] This video is set to "Private" on YouTube -- YouTube shows "This is a private video. Please sign in to verify that you may see it." No transcript or content is retrievable without an account that has been explicitly granted access. Whoever owns the wiki page should check whether this video was made private intentionally (in which case the embed and any surrounding link should probably be removed) or by accident (in which case it may just need to be set back to unlisted/public).

== Mail Server Qmail Demo and Training Part1 ==

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

'''Video summary:''' [NO ACCESS] This video is set to "Private" on YouTube -- same situation as McFiFCgjdAM on this same page. No transcript or content is retrievable. Given multiple videos on this "Tetra_Training_Videos_on_Hangouts" page are private, this may be a systemic visibility issue affecting the whole batch of Hangouts recordings rather than isolated one-off cases -- worth checking the uploading account's video visibility settings for this whole page rather than fixing videos one at a time.

== Qmail Training Session conducted in 2015 part2 ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as McFiFCgjdAM and InmQPjal5fs on this page. Three consecutive videos on "Tetra_Training_Videos_on_Hangouts" are now private, reinforcing that this is very likely a systemic visibility setting on the whole batch rather than isolated cases.

== Qmail Training Session conducted in 2015 part3 ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts". This video ID appears twice in that page's video list (two separate embed slots pointing at the same video), and both are equally inaccessible.

== Mail Server Training Session conducted in 2015 part4 ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts". This video ID appears twice in that page's video list (two separate embed slots pointing at the same video), and both are equally inaccessible.

==Cluster Technologies Training in 2015 ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Present Client information ( as of Nov 2016 ) ''' ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Nagios Client configuration ''' ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Mail Server Training ''' ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Training DNS with respect to Mail ''' ==

{{#ev:youtube|LsqqS-7FOco|640}}

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Qmail Training Conducted by Kamal Kishore ''' ==

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

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts".

== '''Zimbra Basics Training Nov 30 2016 ''' ==

{{#ev:youtube|x-7n-t0Lv1I|640}}

'''Video summary:''' [NO ACCESS] Private video -- same pattern as the other private videos on "Tetra_Training_Videos_on_Hangouts". This was the last of the page's 12 embedded videos checked, and all 12 (11 unique IDs, one repeated) are private -- almost certainly a single account-level visibility change on the uploading YouTube account rather than 11 independent mistakes, so it's worth checking with whoever owns that account whether this was intentional before re-embedding anything on this page.

Ubuntu 12.10 Usage Presentation for Cryobanks

2026-07-25T02:52:48Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Cryobanks]]

== Presentation for Cryobanks ==

{{#ev:youtube|1Q3xgh4NhCM|640}}

'''Video summary:''' [NO ACCESS] This video is set to Private on YouTube and could not be viewed or transcribed. It would need the wiki page's original uploader (or someone with access to that YouTube account) to either make it Unlisted/public or share it directly before an accurate description can be written.

Category:PHDCCI

2026-07-25T02:52:46Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]

==Training on PHDCCI Migration. Dated 29 Feb 2024 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|8jGZrw0Ybwg|640}}

'''Video summary:''' Walkthrough of the PHDCCI mailbox migration from Google Workspace to Microsoft 365 (~300 users, ~1TB of data), done as a user-to-user IMAP migration rather than admin-to-admin because the client's existing Google Workspace vendor would only provide a restricted admin account, not full rights. Covers: purchasing M365 licenses first, creating an IMAP migration endpoint against Google's IMAP server, building the CSV batch file (Microsoft username / Google Workspace username / Google Workspace password) via the Exchange admin panel's migration wizard, temporarily disabling each account's 2FA "login challenge" (a 10-minute window) so the sync can authenticate, adding the domain and letting Microsoft auto-configure MX/SPF DNS records, and troubleshooting failed batch entries (almost always a changed password) by deleting and re-running just that user. Also covers enabling IMAP access on the Google Workspace side (it wasn't originally enabled, since the client used the Gmail web UI directly) and disabling MFA org-wide post-migration at the client's request.

Category:ISGEC

2026-07-25T02:52:45Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]
[[category:Zimbra]]

==Training on ISGEC BSP Project. Dated 20 July 2026 - Tetra Support Staff - Takshay==

{{#ev:youtube|ivJ-tq--y6E|640}}

'''Video summary:''' KT session on the ISGEC Zimbra deployment (Business/Network Edition, migrated in-place from the open-source edition without a full remigration -- the Class of Service was created and applied before the license upgrade so existing user quotas stayed correct). Architecture is a two-server split: LDAP+mailbox on one node, MTA+proxy on the other, with all client inbound traffic hitting the LDAP+mailbox node. Covers creating/assigning a Business Edition COS at both user and domain level, and the standard practice for client-facing admin accounts: a delegated (domain-scoped, not global) admin created via "zimbraIsDelegatedAdmin TRUE" rather than handing out the real super-admin, with actual admin credentials kept in-house and rotated/locked whenever a server sits at a client's own location. Also covers the underlying KVM virtualization platform hosting the mail and Samba services.

Category:Energo Group

2026-07-25T02:52:44Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]

==Training session on FUSIONHONDA ZIMBRA BSP & ENERGO Project 22 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' This session covers the shared Zimbra mail server (v10.1.10, soon upgrading to 10.1.20) hosting multiple client domains including Energo Construction, Energo Products, Fusion Hyundai, HACO India, and SCS.net/Shrop Charity. Topics covered: S3 object storage configuration for the message volume, SOGo security integration for inbound/outbound mail (including the required Postfix master.cf entry for mail delivery to work), setting up delegated (domain-scoped, not global) admin accounts via zmprov, per-client mailbox and domain storage quotas, and account provisioning/deletion as the routine day-to-day support request pattern for this server.

Category:Pahwa Group

2026-07-25T02:52:43Z

Admin: Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo)

[[category:Tetra Clients]]

==Training on PAHWA (BRYAIR) BSP Mail Server Magiration. Dated 20 July 2026 - Tetra Support Staff - Takshay==

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

'''Video summary:''' "PAHWA (BRYAIR) BSP Mail Server Migration KT session" -- a Hindi-language internal KT recording walking through a Zimbra migration for client Pahwa (Bry-Air). Covers: the four Zimbra BSP subscription tiers (Business, Business Plus, Standard, Professional) and confirming the client is on Business; provisioning a new Ubuntu 22.04 server with local DNS via dnsmasq and verifying it with host/nslookup; a single-server Zimbra install (10.1.19 at the time) following the official install guide; post-install license activation -- creating a "Business" Class of Service, setting it as the domain default, and manually re-assigning the pre-existing admin account to that COS since new users inherit the domain default but the original admin doesn't; activating the license via the admin UI or the `zmlicense -a` backend command; creating ~900 mailboxes with `zmprov ca`, batched into scripts of 100 users each; migrating user passwords by exporting them from the old server with `zmprov gap` and replaying the output on the new server so credentials transfer unchanged; migrating mailbox data via imapsync (installed either side, run from the destination in this case) using admin-to-admin authentication; going live and installing Zert to monitor per-client license/feature usage against what's actually been purchased (e.g., catching a client using Professional-tier features while paying for Business); and finally describing Pahwa's secondary DR server, which runs the same Zimbra version under a DR license with weekly (not live) imapsync replication, plus the standard Zimbra Network Edition default backup schedule (incremental Monday-Friday, full backup Saturday night, three cron-driven backup scripts, 30-day retention).

Technical Training Serssions 2021 Linux Team

2021-04-06T18:58:47Z

Admin:

[[category:Training‏‎]]

==Session for Client Introduction with Technologies (Part1) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Okd_MQE2oqw</HTML5video>

==Session for Client Introduction with Technologies (Part2) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">7VX1kXFQWEs</HTML5video>

==Session for Client Introduction with Technologies - capital bank . Dated 18th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">9rHaInJVD84</HTML5video>

==Session for Client Introduction with Technologies - JBOSS/POSTGRESQL Brijraj/Beetel . Dated 19th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">MZZKR0Lt8FQ</HTML5video>

==Session for Client Introduction with Technologies - LAMP . Dated 20th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Jw5dVkNqy5w</HTML5video>

==Session for Introduction with Technologies - Generic . Dated 24th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">PGeTUt9vj50</HTML5video>

==Session Harsh for Team about Infosys-ITD zimbra Deployment . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">ar1q3ufH2jk</HTML5video>

==Session for Introduction with Mail Concept . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">uN8iTDPr9bQ</HTML5video>

==Session Harsh for Team about Infosys-ITD ELK Deployment . Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">e7AfaibdCVM</HTML5video>

==Session for Mail Concept (Contd). Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">k4wIxQVnf7I</HTML5video>

==Session Harsh for Team about Samba and Desktop Central Deployment at Triburg. Dated 27th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">6CHqu7iuY68</HTML5video>

==Session Harsh for Team about NextCloud deployment at Triburg. Dated 1st April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">RFTOkS71vRM</HTML5video>

==Session Harsh for Team about Various Clients deployments. Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">jdxJAKkfUTs</HTML5video>

==Session for Zimbra Mail Concept (Contd).Part2 Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">QIvBgsFTEiA</HTML5video>

==Session for Zimbra Mail Log Analysis Approach Dated 5th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">CcngpTUNZZE</HTML5video>

==Session for Zimbra Mail Log Analysis Approach (part2) Dated 6th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">nSb4il5IlvE</HTML5video>

Technical Training Serssions 2021 Linux Team

2021-04-05T18:28:45Z

Admin:

Resolution for 1032 Replication error on mysql with GTID

2021-04-05T13:24:23Z

Admin:

[[category:Radico-Khaitan‏‎]]

RCA

fix 1032 error of replication
Referance: https://lalitvc.wordpress.com/2018/03/01/replication-handler-error-ha_err_key_not_found-and-memory-tables-in-replication/

Set global slave_exec_mode = IDEMPOTENT;
stop slave;
start slave;
show slave status\G
Should be fine now
check if the seconds behind master is 0 , then
Set global slave_exec_mode = STRICT;

Observe the replication for some time .

Resolution for 1032 Replication error on mysql with GTID

2021-04-05T13:23:24Z

Admin: Created page with "category:Radico RCA fix 1032 error of replication Referance: https://lalitvc.wordpress.com/2018/03/01/replication-handler-error-ha_err_key_not_found-and-memory-tables-i..."

[[category:Radico]]

RCA

fix 1032 error of replication
Referance: https://lalitvc.wordpress.com/2018/03/01/replication-handler-error-ha_err_key_not_found-and-memory-tables-in-replication/

Set global slave_exec_mode = IDEMPOTENT;
stop slave;
start slave;
show slave status\G
Should be fine now
check if the seconds behind master is 0 , then
Set global slave_exec_mode = STRICT;

Observe the replication for some time .

Technical Training Serssions 2021 Linux Team

2021-04-02T14:45:26Z

Admin:

Technical Training Serssions 2021 Linux Team

2021-04-02T13:15:57Z

Admin: