Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
202138
See technote for details
↧
Remote server shows multiple times in BELAT report
↧
B2D media being reused for jobs when it should have been deleted by DLM
Severity:
Data threat/Security vulnerability
Status:
Investigating/gathering information
Tech Note:
202148
See teechnote for details
↧
↧
After successful Physical to Virtual Conversion, some volumes may not be available on the converted system
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202153
This issue is current under investigation
↧
After a successful Oracle backup the logon credentials used for the backup are changed to the System Logon account causing subsequent jobs to fail.
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
202195
After a successful Oracle backup the logon credentials used for the backup are changed to the System Logon account causing subsequent jobs to fail.
↧
Sharepoint incremental GRT backup of content DB on SQL 2000 fails
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202240
Problem
Running a Granular Restore Technology (GRT) enabled incremental or differential backup of a Sharepoint content database hosted on a SQL 2000 server may fail with an error related to Advanced Open File Option (AOFO).
This error occurs even though all backups are run with AOFO/VSS enabled in the backup job.
Error
The last Full backup on database WSS_Content was a streaming backup. Block level incremental and differential backups require a VSS snapshot Full backup
Workaround: Perform full backups only.
↧
↧
Only one Hyper-V virtual machine is restored even though multiple virtual machines are selected for restore
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202255
The only one Hyper-V virtual machine (VM) is restored even though multiple VMs are selected for restore if Hyper-V VMs are backed up with Granular Recovery Technology (GRT) option enabled. The restore job completes with 'Successful' status though not all VMs selected are restored.
Please create a restore job for each Hyper-V virtual machine 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/TECH202255
↧
Backup Exec Remote Agent process crashes after starting against KERNELBASE.dll
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202339
BEREMOTE.EXE process crashes just after starting with event log recording the information provided in the technote.
↧
Agent and Option licenses are needed on a CASO server that manages Appliances
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202395
If an appliance configuration is implemented where instead of another appliance being configured as a CASO (ESO Primary) server that a standard Microsoft Windows server running the Backup Exec core server license and the ESO license is used, then even though the appliances, configured as managed Backup Exec (MBE) servers, are fully licensed for the agents and options, the CASO server itself is not licensed for these options. This results in those agents being in evaluation mode on the CASO and, once the evaluation expires, potential problems with creating, editing or distributing jobs from the CASO to run on the Appliances.
↧
GRT restore from a differential backup of VMware backup fails with V-79-57344-38721 - Failed to mount one or more virtual disk images:
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
202405
This issue is currently under investigation
↧
↧
Backup of VMware virtual machine to dedpulication storage folder completes with V-79-57344-38721 exception
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202431
The backup of a VMware virtual machine using the Agent for VMware Virtual Infrastructure (AVVI) to dedpulication storage folder completes with the exception below when Granular Recovery Technology (GRT) is enabled.
V-79-57344-38721 - Failed to mount one or more virtual disk images.
This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH202431
↧
An additional information entry, 6C8F043D, is created after automatic deletion of earlier recovery point image in Symantec System Recovery (SSR) 2013
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
202491
Problem
After the auto deletion of an earlier recovery point to comply with the number of recovery points saved specified within the backup job settings, a second informational entry as shown below is generated under both the Symantec System Recovery (SSR) 2013 console tab ADVANCE | VIEW: Event Log and in the Windows application event logs. This issue occurs when maintaining the recovery point retention period on both the primary and offsite storage locations. This issue occurs more frequently when using removable storage, but it has been reported to occur with other storage mediums as well. Customers reporting systems having this issue state this did not occur with earlier versions of SSR on these systems.
Error
Log Name: Application
Source: Symantec System Recovery
Event ID: 100
Task Category: High Priority
Level: Information
Keywords: Classic
Description:
Info 6C8F043D: Recovery point <PATH_TO_RECOVERY_POINT_FILE> deleted to comply with the number of recovery points to save for each drive.
Environment
Symantec System Recovery 2013
Windows based clients
Cause
Under investigation
↧
An Exchange Mailbox PST restore to a shared folder restores successfully but the PST is not on the share
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
202708
An Exchange Mailbox PST restore to a shared folder restores successfully but the PST is not on the share
↧
Mailbox restores using the Granular Restore Option (GRO) fail with generic 'Restore failed' message.
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202782
Problem
Exchange mailbox restores using the Granular Restore Option (GRO) fail with generic 'Restore failed' message with Symantec System Recovery (SSR) 2013.
Error
Restore failed
CreateMapi32() failed:0x80040154
Environment
Exchange 2003
Workaround:
Use SSR 2011 SP3 (10.0.3) for mailbox restores. SSR 2013 can still be used for Exchange server backups.
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 name changes to a temporary name following a restore anyware using Symantec System Recovery (SSR).
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202910
Problem
Following a restore to different hardware (Restore Anyware) using Symantec System Recovery (SSR), the server name changes to a temporary name.
Error
Restore is successful, no errors are seen.
Environment
Windows 2008 R2
Solution:
This issue is fixed in SSR 2013.
Workaround (applies to SSR 2011):
1. Run restore
2. Do not reboot the machine after restore is complete
3. Go back to the main menu on the SRD and go to Analyze/Open Command Shell Window
4. Run REGEDIT from command prompt
5. Select HKEY_LOCAL_MACHINE registry key
6. Go to File/Load Hive and browse to C:\Windows\System32\Config and double click SYSTEM.HIV
7. Give the hive a temporary name
8. Browse HKEY_LOCAL_MACHINE\temp name\Setup\Status\UnattendPasses
9. Set the DWORD value of ‘specialize’ to 0 (default is 9)
10. Once you have made this change, select the temporary name (HKEY_LOCAL_MACHINE\temp name) and go to File/Unload Hive
11. Reboot machine
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.
↧
SQL agent backups complete successfully, but restore selection does not display databases with names that include a date range.
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202994
Please see http://www.symantec.com/docs/TECH202994 for details on this issue.
↧
beremote intermitanly crashes on msvcr80.dll
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
203055
see technote for details
↧
When attempting a backup of a Microsoft SQL Database the Backup Exec Remote Agent terminates on the SQL Server.
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
203118
This issue is currently under investigation.
↧
↧
Audit logs are deleted based on the time in UTC instead of local time zone
Severity:
Non-data threatening / major functionality
Status:
Investigating/gathering information
Tech Note:
202816
The Backup Exec audit logs are deleted based on the time in UTC instead of local time zone during database maintenance.
For example, if local time zone is Japan Standard Time (JST) which is UTC+9:00 and the number of days to keep audit log data in the database is set to 2 days, the entries are treated as follows during the database maintenance on February 14, 2013 at 4:00 AM JST.
2/12/2013 11:56:11 PM ... Deleted as expected
2/13/2013 0:03:01 AM ... Deleted, though it should not be deleted
.......................................
2/13/2013 8:59:58 AM ... Deleted, though it should not be deleted
2/13/2013 9:00:30 AM ... Not deleted as expected
This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH202816
↧
When attempting to restore a Microsoft SQL Database that had backups targeted to a Device Pool, the restore may fail with "V-79-65323-4305 -An error occurred on a query to database DATABASE NAME"
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
203214
This issue is currently under investigation.
↧
Offsite copy process does not generate email notifications when using Symantec System Recovery (SSR) 2011/2013.
Severity:
Minor functionality
Status:
Investigating/gathering information
Tech Note:
203253
Problem
Offsite copy process does not generate email notifications when using Symantec System Recovery (SSR) 2011/2013. The primary backup itself does generate email notifications.
This is seen even when the SMTP Email options are configured to send 'All messages' (Errors/Warnings/Information).
Solution
There is no workaround currently 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.
↧