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

Filters to check Plug-in version in Symantec System Recovery Management Solution (SSR-MS) return incorrect results.

November 14, 2012, 6:21 am
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
199712

Problem

The following filters in Symantec System Recovery Management Solution (SSR-MS) return incorrect results:

All computers with latest Symantec System Recovery Plug-in installed
All computers with outdated Symantec System Recovery Plug-in installed

This means that the first filter will list all client machines, regardless of their Plug-in version. The second filter will list no client machines.

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.

↧
Search

During a redirected restore of Microsoft Exchange GRT data the Backup Exec Remote Agent may crash on the the Microsoft Exchange server

November 21, 2012, 8:39 am
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
199991

This issue is currently under investigation.

↧
↧

Active Directory permissions not preserved when restoring files/folders using the Recovery Point Browser.

November 22, 2012, 6:29 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200023

Problem

Active Directory permissions are not preserved when restoring files/folders using the Recovery Point Browser when using Symantec System Recovery (SSR) 2011. The same issue is seen when restoring using the Granular Restore Option (GRO).

Solution

The current workarounds are available:

    If restoring the entire volume; use the Symantec Recovery Disk (SRD) for the restore.
    If restoring certain files/folders; mount the recovery point within Windows and then use Xcopy as per the following Microsoft article: http://support.microsoft.com/kb/323007.

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.

↧

SIS (Single Instance Storage) enabled files are corrupted when performing redirected restore with Backup Exec 2010/2012.

November 26, 2012, 6:46 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200094

Problem

Redirected restores of SIS (Single Instance Storage) enabled files renders the files as corrupt. The error message below is an example of the message that is seen when attempting to open a .pdf file following a redirected restore.

Restores back to the original location are not affected by this issue.

Error

Adobe Reader could not open 'filename' because it is either not a supported file type or beause the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

Environment

Windows Storage Server 2008 R2

Solution

The current workarond is to restore back to the original location.

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.

↧

Verification of a virtual machine backed up during a VMware backup fails with "Unable to open a disk of the virtual machine."

November 26, 2012, 12:37 pm
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200110

This issue is currently under investigation.

↧
↧

Restore of Russian email Contacts to Exchange 2010 DAG is successful, but leaves no records

November 28, 2012, 5:46 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200190

 

Exchange 2010 DAG servers are backed up using Remote Agent GRT backup job in Backup Exec 2010 R3. This completes successfully and Granular Restore data can be seen after.

Attempting to restore Russian character email Contacts, from this backup, completes successfully, but are not shown in Outlook Contacts after.
English character Contacts can be restored successfully and do show in Outlook after.

↧

Sharepoint GRT Incremental or Differential backup without VSS shows exception - File \WSS_Content was not found, or could not be accessed.

November 28, 2012, 8:05 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200196

Problem
When Granular Restore Technology (GRT) enabled Sharepoint agent backups are performed without the Advanced Open File Options (AOFO) setting, 'Use snapshot technology' enabled, incremental and differential backups will complete with exceptions:
 
Error
Backup- SharePoint - 80\Content-DB 1 (SPS\SHAREPOINT\WSS_Content)
V-79-57344-5890 - The object was not found, or could not be accessed (Share point backup).

The item SharePoint - 80\Content-DB 1 (SPS\SHAREPOINT\WSS_Content)\WSS_Content in use - skipped.

 
Cause
This error occurs because AOFO snapshot backups are required for Sharepoint GRT to work properly for incremental and differential backups.
 
Solution
Edit the backup job properties and in the Backup Options page, click the 'Advanced Open File' selection and apply a check to the 'Use snapshot technology' checkbox.  In general the checkboxes for 'Automatically select snapshot technology' and 'Process logical volumes for backup one at a time' should also be checked as they are by default.

↧

Duplicated differential backup sets are not reclaimed (or overwritten) on disk storage because of SSP being enabled.

November 29, 2012, 5:46 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200263

Duplicate Differential backups with SSP enabled are not reclaimed correctly

↧
Search

Full or Incremental backup job including 'verify' of local media server fails with final error 0xe000848f – Insufficient disk space

November 30, 2012, 12:22 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200311

Full or Incremental backup job including verify of local media server fails with final error 0xe000848f – Insufficient disk space. Backup of all selected resources complete successfully but error occurs only during verify stage.

For more information please check the following article

http://www.symantec.com/docs/TECH200311

↧
↧

Some volumes not available when attempting cold backups using the System Recovery Disk (SRD)

December 4, 2012, 3:02 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200472

Problem

When attempting a 'cold' (offline) backup using the System Recovery Disk (SRD), some volumes are not available for selection. This can occur on a Hyper-V virtual machine with the following layout:

Disk 0: C
Disk 2: D, E, F, H

In the above example, only volume C is available for selection.

Environment

Hyper-V virtual machine

Solution

No workarounds currently exist for cold backups. The only workaround currently available is to perform 'hot' (online) 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.

↧

During Microsoft Sharepoint or Microsoft SQL backups, the Backup Exec Job Engine may crash

December 7, 2012, 10:57 am
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
200665

This issue is currently under investigation

↧

Sharepoint agent content DB verify fails with "Final error: 0xe000fe2d - The backup of the item is bad."

December 7, 2012, 11:07 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200651

Sharepoint agent backup of Content DB fails verify stage with error '0xe000fe2d - The backup of the item is bad'

Problem

A verify stage failure may occur during a content DB bakup job when backing up to disk or dedup folder.  The errors in the job log are below.

Error 
Data for SPS\Content-DB 2 (SQLSERVER\WSS_Content)\WSS_Content is corrupt.

Verify- SPS\Content-DB 2 (SQLSERVER\WSS_Content)
Data for SPS\Content-DB 2 (SQLSERVER\WSS_Content)\WSS_Content is corrupt.

 

 
 
Solution

Workaround: The source of the verify failure has not been found but the data appears to be fully backed and cataloged and may be manually validated with test restores.  To perform this verification, once the backup is complete, determine whether the granular restore technology (GRT) items within the failing content database are browsable and perform a test restore of granular items in order to test the validity of the backed up data. A test database restore may also be run redirecting the database to a SQL instance instead of overwriting the production database.

 

↧

"Encryption Key Not Found" appears when selecting a backup set on tape in the "Where do you want to restore the data from?" screen.

December 12, 2012, 6:41 pm
↧
↧

Maximum file size field on disk storage properties displays 400GB if it is set to larger than 400GB

December 13, 2012, 11:00 pm
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
200857

The maximum file size field on the disk storage properties may not reflect the specified size. It displays 400GB when it is set to larger than 400GB. This is a problem with the user interface and the displayed size does not affect the actual maximum file size on the disk storage.

Please run the Backup Exec diagnostic application (Bediag.exe) and check the Backup-to-Disk Information section for the current maximum file size of each disk storage.

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

↧

Backup Exec Remote Agent service crashes in ntdll.dll with Hotfix 195395 when backing up VMware guest machine

December 16, 2012, 7:15 pm
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
200892

The Backup Exec Remote Agent for Windows Systems service (beremote.exe) on a media server intermittently crashes in ntdll.dll after applying Hotfix 195395 when backing up a VMware guest machine.

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

↧
Search

When attempting to setup a P2V Conversion in a CAS / MMS environment the Server and Disk configuration may not be available

December 17, 2012, 5:58 pm
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
200939

This issue is currently under investigation.

↧

Backup Exec Remote Agent crashes during VMware backups

December 18, 2012, 10:30 am
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
200972

This issue is currently under investigation

↧
↧

Unable to create custom Symantec Recovery Disk (SRD) when SSR and PGP Desktop Encryption are both installed.

December 21, 2012, 1:50 am
$
0
0
Severity: 
Non-data threatening / major functionality
Status: 
Investigating/gathering information
Tech Note: 
201054

Problem

The error below is seen when attempting to create a custom System Recovery Disk (SRD) when both Symantec System Recovery (SSR) and PGP Desktop Encryption are installed.

Error

Error ECA307DE: Failed to unmount a previously mounted WIM file. A process or application may have a lock on a file within the mounted WIM content.

The Microsoft platform code is 126.

Environment

Windows 7/2008 R2 x64

PGP Desktop Encryption

Solution

There is currently no workaround to this issue.

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.

↧

Backup selections browse tree does not correctly identify items that will be backed up if a complex exclude is used.

December 21, 2012, 4:08 pm
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201125
Problem

Creating or editing a backup job in Backup Exec 2012 to use a complex exclude condition (e.g Files not accessed in # days) does not accurately show items to be backed up in the browse tree window. Items that meet the exclusion requirements, meaning items that ought to be backup does get backup; this can be confirmed in the job log. This issue did not occur in previous versions of Backup Exec.

 
Error

No error is displayed

 
Environment

Windows based clients

 
Cause

Currently under investigation

 

↧

After a successful P2V conversion, the VM fails to boot with 0xc0000225 The selected entry could not be loaded because the application is missing or corrupt. \windows\system32\winload.exe

December 28, 2012, 12:29 pm
$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
201230

This issue is currently under investigation.

↧
Viewing all 178 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>