did they ever answer you?
Yes, I was given an article on the proper method to move the database. The article is this.
http://support.veritas.com/docs/291026
I still ran into one problem when I did this. Out of 450 computers running the agent, I had about 115 that did not transfer correctly. That was a 25% failure rate. The problem is one of the steps has you disable the computers before you begin to migrate. Once you have everything migrated, the article really doesn't tell you what you need to do to reactivate the computers. I assumed you go into the new server and enable them. It worked for the majority of those systems. What I ran into, I really could not determine what computers transitioned fine verses which ones didn't. They only way to know was to watch the alerts and see who wasn't backing up. If you went into the registry of the agents that weren't working, you would see that the file server name did not transition over. To get around this, I tried to use config manager to push the new agent (with the new server info) to the computers not working. The agent would install, but would not change the dlo server name. I ended up figuring out that I had to do a three step install to fix the problem. First I ran the install with the agent that had the correct server info. I then ran an uninstall program to remove the DLO agent. I finally re-ran the install that installed the agent properly. One more thing, I had to force the client computers to log off and back on to get the agent to start up. For some reason it would not start up. I know this was wordy and had a lot of steps, but I ran into so many goofy things that took so much time to figure out. I feel this may help others who are thinking on moving the database server.
