My organization has just transitioned from Backup Exec 12.5 with all tape backups to Backup Exec 2010 R3. Since the changeover, our sharepoint backup has become incredibly slow. On the older system, the nightly full backup of sharepoint would take roughly 8 hours. Currently, we are doing a full backup of our sharepoint farm nightly, and it is backing up to a dedup folder which resides on 7200RPM drives. The most current backup took 23 hours, 30 minutes.
Our sharepoint farm is around 700GB.
A couple issues that I think could be an issue are the following:
On a side note, we are doing a media side backup, we have tried client side but it is even slower.
Has anyone heard of any issues occuring between Sharepoint and dedup backups? Any suggestions on troubleshooting the issue?
I am surprised that you are asking the user to use AOFO for his database backup. This is contrary to what is stated in the Admin Guide which is NOT to use AOFO when backing up databases.
There is no problem using AOFO/VSS with any Sharepoint 2003 or later backup, but with it enabled the amount of data backed up will be more than what a non-AOFO backup would be (a VSS backup gets snapshots of each of the database files rather than a streamed composite dump of the DB).
More than likely the culprit is the larger number of GRT objects supported for restore in Backup Exec 2010 R3 Sharepoint agent vs. 12.5 causing the 'updating catalog' phase to be longer for each content DB. There is a known issue with the updating catalogs phase taking excessively long that is in line for a hotfix- http://www.symantec.com/docs/TECH155718
Note that depending on the size of the content database and the number of objects within it, the 'updating catalogs' phase can take a long time to complete.