Solved! Go to Solution.
By default backup exec dumps it's own database (as BEDB.BAK) at 04:00 every day (to the DATA folder that others have already advised you backup)
BEUtility has an option to recover database from backup - and this option recovers using whatever BEDB.BAK is found in the data folder at the time you run the recover database option.
Because of this process you do not have to actually stop the BE services to backup the data folder (although it might be worth adjusting the time the BEDB.BAK is created to five minutes before you take your backups of the data and catalog folders - so that you always have the most up to date copy in that backup)
In reality using BEUTILITY in the DR process can be useful but it is not a different DR process it is just an extra step that depends on the state of the server when you copied the data and catalog folders (i.e. did you stop services etc)
FYI - I would never backup the BEDB with our SQL Agent as the restore process if you did this is not friendly as how do you restore over a database that the product doing the restore is using. (You would also need an Application and Database agent license, which you do not need for the process of "copy the data and catalogs folders" (with either services stopped or using BEDB.BAK and BEUILITY choice)