This issue is currently under investigation
Backup Exec 2012 remote agent service (BEREMOTE.EXE) terminates in Faulting module MSVCR100.DLL
Convert to Virtual Machine (B2V) option only recovers critical drives but not all drives in the original system
Please reveiw the TECH article for more information.
When attempting to restore a virtual machine from a duplicate backup set stored on a MMS the restore may fail with "V-79-57344-38277 - Unable to open a disk of the virtual machine."
This issue is currently under investigation.
Some .bkf files are not deleted by DLM(Data Lifecycle Management) after retention period of backup set expires if it is spanned across multiple disk storages
Some .bkf files are not deleted by DLM after the retention period of the backup set expires when it is spanned across multiple disk storages.
When a backup job runs to a storage device pool which contains multiple disk storages, the backup set can be spanned across multiple disk storages. After the retention period of the backup set expires, the .bkf files on a disk storage which is firstly used are deleted by DLM. However, the .bkf files on the other disk storages are not deleted.
This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH204553
GRT Restore of Sharepoint List Items corrupts data in Calculated Field
Using Backup Exec 2010 R3, GRT restores of Sharepoint 2010 List Items that have a Calculated Field column defined, will leave corrupted data in that field and the Item Properties will show no information. The Calculated Field data will appear correct, except for the 1st character which will be replaced by a random ASCII character. This occurs regardless whether the field is defined to combine text or numeric data.
The same backup data has been successfully restored when using Backup Exec 2012.
AVVI GRT backup of an Active Directory Virtual Machine completes with exception “V-79-57344-38747"
AVVI GRT backup of an Active Directory VM completes with exception “V-79-57344-38747 - Backup Exec was unable to prepare Microsoft Active Directory resources for Granular Recovery Technology (GRT) operations. Therefore you will be unable to perform GRT-enabled restores of Microsoft Active Directory data from this backup”
For more details please refer to the following article:
Synthesized full backup sets miss some data if incremental backup and synthetic backup are executed after upgrading to Backup Exec 2012
When the Backup Exec is upgraded to Backup Exec 2012 with synthetic backup policy and an incremental backup and the synthetic backup are executed after the upgrade, the synthesized full backup sets miss some data. This issue reproduces only with remote server synthetic backups.
Please execute the baseline backup after the upgrade to Backup Exec 2012 in order to avoid this issue.
This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH205079
Backups of system reserved partition fail with 'VSS_E_INSUFFICIENT_STORAGE'.
Problem
Backups of the system reserved partition on Windows 7 client machines are failing with 'VSS_E_INSUFFICIENT_STORAGE'.
All other volumes are backing up successfully.
Error
E4F3000E error: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: VSS_E_INSUFFICIENT_STORAGE (-2147212513). 0xE4F3000E (Symantec System Recovery)
(UMI: V-281-3215-6071)
Environment
Windows 7 Professional x86
Solution
Currently, there is no workaround available.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Exchange 2010 Granular Recovery Technology (GRT) restores to a mailbox that contains [] in the display name fail.
Please see http://www.symantec.com/docs/TECH205156 for the latest updates on this issue.
PVLSVR.exe crash during VMware multiple recovery (convert and restore) operations running in parallel
Please see text of technore for more details
Exchange 2010 DAG GRT incremental backup to tape fails with VFF Open Failure error 'V-79-57344-759'
Exchange 2010 DAG GRT incremental backup to tape fails with VFF Open Failure error. Full backup to tape completes successfully but Incremental backup to tape fails.
For more details please refer to the following article:
Upgrading agent remotely fails with 'Agent installer files missing' if connection to console is made via SSR Monitor.
Problem
Upgrading a Symantec System Recovery (SSR) client remotely fails with the error listed below.
This only occurs when connection to the SSR console is made via SSR Monitor (right-click on remote machine and choose 'Connect to Console').
Error
Cannot deploy the Agent to machine name / ip address
Error E0D3EBC0: Cannot deploy the Agent
Agent installer files missing
Solution
The current workaround is to launch the SSR console manually outsided of SSR Monitor and then upgrade the agent.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Server names not sortable in 2012 GUI
Sort of "Server" column not working. Please see the technote for more details
Exchange 2010 DAG GRT incremental backup job runs very slow and fails with error "V-79-57344-862" and "V-79-57344-936"
Exchange 2010 DAG GRT incremental backup job runs very slow and finally fails with error "V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup" and "V-79-57344-936 - The Backup Exec Virtual File Filter cannot complete a background process because of an internal error. (Minor errorcode: 0.0)"
For more details please refer to the following article:
When attempting to backup two servers with the same netbios name but different FQDN, the job will fail with "0xe0000383 - Failed to log on to Microsoft Windows"
This issue is currently under investigation.
During an Exchange 2010 Granular Recovery Technology (GRT) restore, the Backup Exec Remote Agent (beremote.exe) crashes on edbprov.dll
Please see http://www.symantec.com/docs/TECH205932 for the latest information on this issue.
Optimized duplication job marks destination OST media with bogus image size of 16,777,216.0 TB
With BE 2010 R3, running an Optdup backup job marks the destination OST media size as 16,777,216.0 TB. The source client side backup job and its optimized duplication job completes successfully but will mark the destination OST media with such bogus image size.
For more details please refer to the following article:
Granular Recovery Technology (GRT) restore of Exchange 2010 Public Folder items completes successfully with 0 byte count, and required items are not restored.
Please see http://www.symantec.com/docs/TECH205967 for the latest information on this issue.
Backup Exec 2012 console crashes when attempting to access Backup Exec settings.
Click more information link for details. Please subscribe to TechNote for updates.
Backups of virtual machines running on Citrix XenServer 6.1 fail with Symantec System Recovery (SSR) 2013.
Problem
Backups of virtual machines running on Citrix XenServer 6.1 are failing with the errors listed below.
Error
High Priority Error: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\).
Error E7D1001F: Unable to write to file.
Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Insufficient system resources exist to complete the requested service.'
Error E7C3000F: Device \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 cannot read 8192 sectors starting at LBA 10223200.
Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Incorrect function.' 0xEBAB0005 (Symantec System Recovery) (UMI:V-281-3215-6071)
Environment
Virtual machines (Windows 2003, 2008 and 2008 R2) running on Citrix XenServer 6.1
Solution
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.