A Duplicate Backup job of a Sharepoint Content Database hangs at the 'Updating Catalogs' Stage
|Article:TECH155288|||||Created: 2011-03-10|||||Updated: 2011-03-11|||||Article URL http://www.symantec.com/docs/TECH155288|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
A duplicate backup job of Sharepoint content databases may hang or take excessively long during the 'updating catalogs' stage as displayed in the Job Monitor view.
The 'updating catalogs' phase of a Sharepoint duplicate backup is where the content database(s) is/are browsed to determine all the granular objects and containers within the database. The catalogs are created from this information and from the catalogs restore selections can be displayed for restore jobs. In some cases where there are large numbers of containers, especially empty ones, the 'updating catalogs' phase can hang or take an excessively long time.
This issue has been resolved in Hotfix 148347 for Backup Exec 2010 R2. See Related Articles below for more information.
SPSV3: Set copy of content DB GRT backup from disk to tape hangs at updating catalogs
Article URL http://www.symantec.com/docs/TECH155288