Editing Training 2022 Linux team/ (section)

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