Congratulations! You finally have the go ahead from Management to expand your Logscape environment. You need to scale up from a few test machines to a larger environment. Unfortunately, you ran your proof of concept from Steve’s Dev machine. Or perhaps you underestimated the volume of data and urgently need faster disks to improve performance. You’re going to need to migrate your Logscape Manager to a new server, which is precisely why you’re reading this guide…
Migrations are hard
Preparation – What you will need:
Source Manager: The manager you are migrating from.
Target Manager: The manager you are migrating to.
LDAP Credentials (Optional but recommended)
SSL Certificates and Credentials (Optional but recommended)
Make sure that you are running the same version of Logscape on the Source and Target – as always we recommend using the latest version.
The following guide assumes you are using 3.1 or greater – if not, upgrade to 3.1 before you start.
Why Everything I Have Is Broken
Computers break… it’s a fact of life! Sometimes it’s a nice quick fix, such as the one cunningly suggested by Randall Munroe. Sometimes it can take hours of trawling through logs. Regardless of the reason, in an ideal world,you want to fix the problem as soon as possible; but the next best thing is to have a Failover – another server that works just as well!
In a Logscape environment, your Management agent is the central point of your environment. It controls alerts, provides users access and runs the entire system: without it, you have nothing. So how do you make sure that your environment is resilient against a Management Agent failure? Simple… you add another one!
The recent 3.2 Logscape release has added new and improved Failover capabilities, making it easier to provide a seamless environment for your users. Having recently implemented this feature in my environment, I thought I’d share with you both the benefits – and the possible pitfalls – of installing this useful bit of kit.
You will need:
- An existing Logscape Environment with a subscription (Failover is not supported without a license) running at least version 3.2.
- A server you wish to make your new Failover Agent.
- A little bit of understanding about ports
- A pinch of bravery.