This condition is occurrring on a verify job of DeDuplication data, as it does not affect 100% of data sets we encourage custoemrs to log support cases as we need to narrow down the specific cause.
Reported: 21 Apr 2011 by Colin Weaver | <span class="field-content">4</span> comments - last comment 01 Mar 2012 by KeirL
When running a backup job the backup fails to backup valid directories if a directory level wildcard exclusion using double asterisk (**) is defined in the Backup selection list or Global Excludes list in Backup Exec
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - SSR 2011, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
During installation of Symantec System Recovery Management Solution (SSR-MS) 2011, the install readiness check for 'RootAutoUpdate' fails.
Cause
This issue is seen when the server where SSR-MS is being installed does not have an internet connection.
Reported: 20 Apr 2011 by Chris Riley | <span class="field-content">3</span> comments - last comment 22 Aug 2011 by it wasn't me it...
If media is retired and deleted from a Deduplication Folder using the Backup Exec user interface, that media will show up again after the Backup Exec services are restarted. When an inventory operation is run, Backup Exec ends up with multiple copies of the media it its database.
When re-directing an Oracle Database and Archived Logs to another Orace Server with an ASM Configuration, the Redirected Oracle File paths will point to the ASM DiskGroup and is typically referenced with a (+) symbol.