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:YOUSECURE
(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!
==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.
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)