Why does BMR Utility collect all disks information?
I have couple of comments regarding BMR options,
1. The basic reason to have BMR is to protect OS , other file systems are taken care by other FS/DB/ Application backups then why do we need to have all disks information collection in BMR? Usually whenever we take BMR backups we are either very specific to OS partitions or use exclude_list to avoaid big chunk of ( mostly inconsistent e.g. database ) backup data as we all know that other policies will take care of other types of data. I do understand that BMR gives us option while restoration that we can only restore OS disks but still what is the purpose to collect irrelevent information?
2. Due to above mention irrelevent data collection, there are alot of applied or hidden limitations we usually come across when having a setup of BMR. One example is of multipathing as mentioned in the technote http://www.symantec.com/business/support/index?page=content&id=TECH204180 . It becomes most interesting when Symantec support says , "Symantec has not tested it yet so N/A" isn't it funny to say this to customer.
However I do understand due to varied and unique configurations that are possible, combined with vendor specific / OS restrictions it would be one of the biggest challenege but still I would request Symantec to perform all types of tests possible, or openly say Not supported to avoid ambiguity. Or may be if we change BMR data collection design to be specific to OS , that may give us a BIG help.
3. In addition to existing directives, there should be another directive specific to BMR , intelligent enough to understand related client OS Level file systems mount points or partitions rather to use ALL_LOCAL_DISK which collects all disks information and then we have to use of exclude_list to avoid other data or specific mount points declaration in the policy. I think , we can put such intelligence in client software easily.