Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Service URL - http://opsdb.dante.net/ 

OpsDB runs on two servers, named appropriately axxxVMs on each environment (Prod, UAT and Test)


First Steps

If for any reason the system becomes unavailable:

...

    • switch the DNS entry for OPSDB from the ‘Primary(01)’ instance

...

    • to the ‘Secondary(02)’ instance. This will allow the general user to continue working on OpsDB whist we continue with our investigations as to why it initially went down.

If we find that both instances have become unavailable, then contact with IT / SWD is of the upmost urgency as further investigation, steps, and decisions will have to be taken across departments (i.e. IT / SWD / OC) as to the best way forward to resolve these issues

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.

The action usually taken by devOps would be as follows, which you would need to do:

...

OpsDB 

...

...

...

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.

...

If the machine is running follow steps below:

...

Check Apache.

  • Has apache failed? Is it running?

...

       Currently MySQL data backups are stored in the /opt/vackupsbackups/mysql folder within each VM.

...