Firstly let me start by saying I am aware that there are some older threads that have covered this issue. I have tried posting some questions to those but they appear to closed, hence I am opening a new thread.
In one of these previous threads (44503) John Chisari stated, wrt altering the location of the MSSQL$BKUPEXEC data files:
It can be done, but not during the installation.
I tested this with the default MSDE instance, but it should be the same with SQL.
1. Install BE as normal.
2. Stop all the BE services and the MSSQL service to the instance which the BE Database was installed to.
3. Change HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Misc\Data Path to whatever you want it to be.
4. Move the contents of the original Data Path ie. \Backup Exec\NT\Data to the new directory.
5. Start all BE services.
I have tested this and it works a treat (apart from one glitch I have discovered - see below). However my question is: How does SQL know where the data files are once they have been moved? Does BE update the Master DB when the services start?
Also the one glitch (that I have discovered) is that it does not update the JobLogFileName column in the JobHistorySummary table which means that BE cannot find any of the old logs. Does anyone know of a utility that interrogates the Data Path registry entry and modifies this column accordingly?
I am using BE 10.0 5520.
Cheers,
Warren
