Exceptions on SBS 2011 Backup Jobs
I keep getting this exception on my server's full/incremental job pair:
V-79-57344-33925 - Error: ShareWebDb.mdf is a component of a SharePoint server farm. It must be backed up using the Backup Exec Agent for Microsoft SharePoint Portal Server. Select it for backup from the Microsoft Server SharePoint Server Farms node.
I have a Farm job, runs fine.
I do have a support case with Symantec Tech Support, but so far they are dodging the real issue and feeding me busy work.
Months ago when I installed this box, I moved the SharePoint databases and such using the SBS Console, to the "D:" data volume.. among other file shares and such.
Beginning 12/14, the Full job (on Fridays..) threw this exception. That is thrown, as is every DB and log file for SharePoint for CompanyWeb.. which comes with SBS.
The first suggestion by support is to feed them version info and ensure my LiveUpdate is up to date. It is.
The second suggestion was that I should exclude the SharePoint Resources and corresponding SQL instances/dbs from my main job's backup selections.. they already were. Any SQL on this SBS box I don't care about.. my LoB server hosting an ERP product, I do care about.. not an issue to exclude all of it.
The third suggestion was that I should exclude the LDF/MDF pairs from the backup selection.
Okay.. but that turns off SDR. YES, they are on D:, not C:.
As an MSP, I have multiple clients and multiple cases of this problem. Some clients, I have gone so far as uninstall SP from SBS.. a different side-effect which makes SBS cry, but not Symantec's problem I guess.
First problem.. why aren't any of the kb articles current with Backup Exec 2012 issues? Every situation I encounter has articles about former versions.. including the "updated" articles.
Second problem.. As mentioned, this is one among at least six clients with this issue. We using a monitoring/management system and agent.. I really want these backups to SUCCEED.. else I am looking at them daily.. so saying "meh, you know it's alright, deal with it" is not a solution. We are looking at other backup solutions at this point.. we already abandoned Endpoint Protection about two years ago.
While I wait for the next busywork request from Support, anybody got the fix?