OpsDB runs on two servers, named appropriately xxxxxxprod-opsdb01.geant.net and xxxxxprod-opsdb02.geant.net where xxxxx = prod, uat, or test
...
Change the Domain Name System (DNS) entry for OpsDB (i.e. Move from one instance to another)
Currently
...
the
...
URL OpsDB.dante.net resolves to our primary instance of our OpsDB Server (which we call ‘Primary’, or ‘01’) – Prod01.geant.net.
If for any reason the primary instance of OpsDB becomes unavailable we need to change the OPDSB.dante.net URL to resolve to our secondary instance of our OpsDB server (which we call ‘Secondary’. or ‘02’) - Prod02.geant.net.
Software development would not normally be involved in this, the exception being if we noticed ’01’ had gone down we would perhaps request the switch via DevOps.
The action taken by devOps would be as follows:
‘Change the CNAME opsdb.dante.net in Infoblox, to point either to prod-opsdb01.geant.net or to prod-opsdb02.geant.net depending on which instance you wish to point to.’
...
If required (i.e. the 01 instance of a VM is down) we can change the DNS to point our public domain URI to the 02 VM (the ‘Secondary;’ Instance) whilst the 01 VM is being fixed – this should ensure they service continues to be available to the public.
To do this will require changes to be made by the systems administrator and is explained in the document below - this may require assistance from IT.
...
Once this has been done the system should then be available to the users once again whilst more detailed investigation takes place into why the Primary instance has become unavailable.
Please do not forget to inform the users that OpsDB is back up once this has been done.
Further Investigation
The following points may help troubleshot any issues that arise with this application.
...
To restore any of these instances of data, locate the appropriate DB dump and go through the mysql restore procedure (documented elsewhere in MySQL documentation)
Security Updates with underlying software and operating systems
...