Thanks guys, both of your answers were somewhat helpful.
It is worth noting that if apply the configuration settings from two servers to one new server, using BEUTILITY, it appends the settings not replaces them therefore it can be used to consolidate media server settings.
The one drawback is that both methods do NOT translate local selections into remote selections based upon the server name of the resource.
Hypothetical Scenario: I installed BEMS on my primary file server. Most of the jobs on this BEMS are for local data. Due to the data structure (i.e. its all on one disk in hundreds of evenly sized directories) and BE's inability to utilise more than one tape drive per resource/job, I have had to break the jobs into smaller chunks using the directories via includes and excludes. This leaves me with lots of complex selection lists but very manageable backups.
The file server has grown significantly and my tape devices are causing havoc with my file server during production hours. Management have decreed that I can no longer connect the libraries to this server so I am forced to implement a dedicated BEMS.
So I need to migrate my selections (which specify local data) to the new server where upon they will need to be converted to remote selections.
This is a hypothetical scenario just to prove my point so please ignore all issues to do with remote network-based backups being slower, fixing the issues instead of circumventing etc etc etc...
If you dump the selections using BEMCMD -o507 all of the data is there but it is not in a format that is acceptable to BEMCMD -o220. What would be great is if Veritas (or any clever script kiddie) came up with a utility for parsing the output from the BEMCMD -o507 command so that it could be used by the BEMCMD -o220 command.
Cheers, Warren