We are currently operating out of two separate data centers.

So we have one master server, called master which is a robotic control
host for the library at Data center 1.

Then at data center 2, I have another media server there, we'll call is
media1, that is also a robotic control host.

Everything is working well, backups are running, etc, no global device
conflicts, etc.

However, when the operators use vltopmenu (on the master server, vault
is only installed on the master server) to try and do the ejects for the
library at data center 2, we have problems.  The ejects never happen and
the session never comes back to them.

I noticed the vault jobs for the library at the second data center were
failing.  So I typed vltadm and checked and sure enough the robotic
control host for the library is listed as master, and not media1.  I
changed this, saved it, even checked in vault.xml to make sure the
change took, re-ran the vault job and bingo, vault runs perfectly.

A couple of hours later, checking with vltadm and now the robotic
control host for the library at data center 2 is back to master.  Its
getting changed somehow.

Does anyone know what I need to do to make sure this change is
permanent?

Tpconfig -d on the master and media server show robotic control host is
media server for the 2nd library...

Thanks,
Taylor