Breaking with your back-up supplier is a sticky business
How to dissolve the glue
Backup is like software superglue with three sticking points: the backup software installation; its operation; and the longevity of the stored backup data vault, which can be needed for years after the last piece of data has been written to it.
Let's take an imaginary product, BackNetVaultExec Pro. It is a typical enterprise backup product which utilises a media server and has agents in all the servers with data to be backed up.
The servers run different operating systems and exist in both physical and virtual forms. The data is stored on a target disk array and restored from it too. The idea is to protect files and virtual machines.
Let's think of the backup software as a lens through which we can see the data. It knows the format the data is stored in and understands the metadata – the data about the stored data.
In the dark
Without this lens we cannot make sense of the backed-up data. We can't see into it and pull out the bits we need to restore, such as files, folders, emails and so on, because the originals have been lost, deleted or corrupted.
Let's run BackNetVaultExec Pro for a year and then decide we want to change it because, say, it has been acquired by another vendor we love to hate, or our only backup admin left us, or we are enamoured of the latest startup, or, best one, we had to do a restore and could not.
And by that time it is too late and you realize that what you thought you had turns out to be rubbish. You now have no choice.
Our hypothetical product also handles snapshots and replication badly. Let's further imagine we switch to WonderBackupPro, another hypothetical product, which remedies these ills. What happens?
We faced three challenges, one big, one medium and one comparatively minor. First, our new product cannot use the backed-up files because it does not understand their formats and metadata and so cannot access their content.
A backup storage vault is stuck fast to the software that writes content to it and reads content from it. So long as that vault exists you must use the original software to access it. This has to be recognised and managed. There is, in general, no silver bullet for backup vault migration.
The mid-level difficulty is that you probably have to install the new backup software agents on all the servers needing backup.
That means you still have the burden of maintaining and updating backup agent software as the server operating system environment gets patched and updated.
Since you must maintain the original backup software as long as access to the content in its storage vault is needed then you now face even more work in this area, not less.
The comparatively minor issue is that you have to learn how to use the new software.
Where does this leave us? We have an even bigger backup software problem than before and it is long-lived.
Even if we switch all backups to the new product from a start date and use the old backup software only to provide read and restore access to the backup storage vault, we still have to keep the original backup software current. It is probably a mandatory condition for getting support.
So now we are running two different backup environments in parallel. Does this mean it is impossible or impractical to change?
Not at all, but we should appreciate that a change will take a while and that we will be running two environments for as long as the first product’s stored content is needed. That could be five years or more.
The implication is that the return on investment (ROI) of a backup software migration and the timescale over which it occurs has to be properly understood.
Let's summarise the basic software migration issues identified so far:
1. Concurrent old and new backup software agent versioning for the host operating systems involved;
2. Need to keep old backup software current during the period we need access to its stored data;
3. Need to understand how to operate the new software.
One way, in theory, to resolve these issues is to migrate the old backup data vault to the new one. In theory that's fine; you restore the entire original backed-up data and then back it up a second time with the new product. A moment’s thought, however, shows this is wholly impractical.
Vast amounts of data spanning several years of operation can be involved and such a migration would require lots of minutely detailed planning.
Also, the servers you need for the task are likely to be running production applications, which makes it hard to justify effectively taking them out of commission for the exercise