After performing a client-side deduplication operation, followed by an optimized duplicate operation to a deduplication folder, the object NULL-SERVER may show up in the Backup / Restore dialogs. The backup sets resulting from this set can not be restored.
- Peform a client side deduplication backup of a server to a deduplication folder or a PureDisk device.
- Set copy the resulting backup set from step 1 to another deduplication folder or a PureDisk device.
- The catalogs for the copied set are shown under the server name NULL-SERVER.
- Attempting to restore the sets under the NULL-SERVER fail.
Backup Exec 2010 R3 Hotfix 159965 introduced a code path where the NULL-SERVER object ends up in the Backup Exec catalogs.
Note : This issue is also present in Backup Exec 2010 R3 SP1.
Applying the Backup Exec 2010 R3 revision 5204 Service Pack 2 http://www.symantec.com/docs/TECH178798
will resolve this problem for backups created after applying the hotfix. Backups created prior to the hotfix will still not be restorable. If Backup Exec is being used to create optimized duplicate sets as described above, Symantec recommends immediately performing a new source backup followed by a duplicate job.
Note: As for the media that had this issue prior to installation of Service Pack 2 for Backup Exec 2010 R2 revision 5204, that can be erased to be used again for backup, or if left as is, once the associated overwrite protection period configured for that has expired the media will be available for new backups. If one were to moved the media to scratch, since it is <NUL-SERVER> it is treated as unrecognized media and would be associated to Backup Exxec Windows NT Backup Media and would be available for backups. So again, it is recommended that media that had the issue, be erased and made available for new backups.