Quantcast
Channel: Symantec Connect - Backup and Recovery - Known Issues
Viewing all 178 articles
Browse latest View live

OptDup backups between Backup Exec servers fail with '0xe00084ec - A backup storage read/write error has occurred' and error 2060016 recorded in Event Log

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
201309

 

Optimized Duplicate (OptDup) backups, between Backup Exec Deduplication folders, fail with '0xe00084ec - A backup storage read/write error has occurred'. The error discusses 'tape based storage' but both source and target storage are disk based. 

Application Event logs indicate a sequence of errors;
 
 ostutil:Opdup Phantom Image PEOST_0000xxxx could not be written because of error 2060016

 ostutil(OstCancelCopyImage):Async cancel failed because of error 2060001.

 ostutil(OstCopyExtentImage):Copy image failed because of error 2060018

 


Reports not using regional date formats

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201346

Reports within Backup Exec 2012 that contain date fields, display these fields in American format of MM/DD/YYYY even if the operating system of the media server is set to a regional date format (such as DD/MM/YYYY for UK)

VMware Backup job fails with 0xe000942a - Backup Exec did not find any resources to include in the backup

$
0
0
Severity: 
Data threat/Security vulnerability
Status: 
Investigating/gathering information
Tech Note: 
201391

Error is caused by a conflicting Exclude statement in the jobs selections - see the Tech article for more details.

When deleting a job from job history its associated job log is not deleted

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201425

When deleting a job from the job history its associated job log file is not deleted, even though a warning window pops up and it says it is deleted.
Please be noted that the job logs are deleted during database maintenance when the number of days to keep job logs exceeds.

This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH201425

Restore from an incremental backup of a virtual machine fails with V-79-57344-38721 - Failed to mount one or more virtual disk images

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
201706

This issue is currently under investigation

During policy based backups of Exchange, bengine.exe may crash on kernel32.dll

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201716

This issue is currently under investigation

Scrolling in backup sets shows multiple instances of backup sets

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201817

See Tech article for details

Backup of a vitual machine to a CIFS device fails with "V-79-57344-38721 - Failed to mount one or more virtual disk images" after the Backup Exec services are restarted

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201830

This issue is currently under investigation


OptDup backups between Backup Exec servers fail with '0xe00084ec - A backup storage read/write error has occurred' and errors 2060018\2060001 recorded in Event Log

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
201867

 

Optimized Duplicate (OptDup) backups, between Backup Exec Deduplication folders, fail with '0xe00084ec - A backup storage read/write error has occurred'. The error discusses 'tape based storage' but both source and target storage are disk based. 

Application Event logs indicate a sequence of errors;
 
 Adamm Mover Error: DeviceIo: ostutil(OstCopyExtentImage):Copy image failed because of error 2060018
 Adamm Mover Error: DeviceIo: ostutil(OstCancelCopyImage):Async cancel failed because of error 2060001

Backup Exec Services will not start if IPLOps.log reaches 4GB

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
202018

Backup Exec Services will not start if IPLOps.log reaches 4GB

 

unable to create restore job when restore type is to individual backup set if backup set is encrypted

$
0
0
Severity: 
Data threat/Security vulnerability
Status: 
Investigating/gathering information
Tech Note: 
200767

See technote for more information

GUI is not showing the proper targeted device pool for Duplicate jobs.

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
202079

See technote for details

RAWS crashes in iplops.dll on start up if sep or mail security SLF files are found on W2K3 server

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
201676

Workaround available

See technote for details

P2V fails with error 0xe000a416: Failed to format a volume from the virtual disks

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
194072

See technote for details

Error "Server application error - unable to insert policy" while trying to create any new backup jobs after upgrading to Backup Exec 2012

$
0
0
Severity: 
Minor functionality
Status: 
Will not fix
Tech Note: 
195128

See technote for soulution


Bkupexec.exe crashes on launch

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
202083

See technote for workaround

Duplicate of a full VMware backup fails with 0xe0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
202082

Duplicate of a full VMware backup fails with 0xe0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted

bkupexec crashes on clr.dll when clicking restore button in BE 2012

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
202091

See technote for details

MIDDLEWARE: Exchange transaction logs are not being purged/truncated after successfully reported SSR 2013 backup.

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
202093
Title
Exchange transaction logs are not being purged / truncated after a successfully reported Symantec System Recovery (SSR) 2013 backup.
 
Problem

After a successfully reported Symantec System Recovery (SSR) 2013 backup the Windows event message below occurs and the Exchange transaction logs were not purged / truncated. 

 
Error

SOURCE: MSExchangeIS
Category: Exchange VSS Writer
Event ID: 9782
Description: Exchange VSS Writer (instance <GUID>) has unsuccessfully completed the backup of storage group <STORAGE GROUP NAME>. No log files have been truncated for this storage group.

 
Environment

Windows based systems

Microsoft Exchange

 
Cause

Under investigation.

 

IP address is not retained after remote Simplified Disaster Recovery(SDR) of Windows 2008 x86 hosted on Hyper-V

$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
202046

The network configuration and display settings are not retained after the remote SDR of a Windows 2008 x86 virtual machine hosted on Hyper-V. Please modify network configuration and display settings manually after remote SDR.

This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH202046

Viewing all 178 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>