Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:NEWSNATION
(section)
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==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.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)