08-11-2010 09:00 AM
Solved! Go to Solution.
08-13-2010 12:39 AM
08-11-2010 09:35 AM
08-11-2010 09:48 AM
That wouldn't work though as the Backup Exec Active File Exclusion excludes mdf files - just like it does with edb files for Exchange. I could add registry entries for bypass the Active File Exclusion, but this again is getting admin intensive.
Non of this is difficult, but Backup Exec is 'sold' as THE backup system to use. The problem is, you don't know that your backups aren't 'complete' until you do test DR's like I am, or everything has gone wrong. Backup Exec doesn't alert you it is not backing up the Windows Internal Database which is one of my worries - what else may I be missing??
08-12-2010 03:25 AM
08-12-2010 04:20 AM
08-12-2010 06:15 AM
08-12-2010 09:33 AM
Hi both,
Thanks for your input and comments - I completely agree that Backup Exec should charge for extra functionality - Exchange, SQL, VMware etc and I don't expect that for free.
However, as SQL Express is free to use and a lot of applications use it (as I've listed above) I do believe that these backups should be included when you do a full backup using Backup Exec. Maybe something to consider for a future version?
If certain items (like mdf and edb files) are not to be included in a backup I think that Backup Exec should alert you to the fact and give you options (whether purchasing agents or something else).
I will of course consider scripting my SQL backups to .BAK files and as this backup is for disaster recovery, I expect a little work getting everything up and running again if the worst was to happen. It has opened my eyes though to the fact that my Full System backups aren't actually full backups at all!
Thanks
Rob
08-13-2010 12:39 AM