Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup and Recovery Known Issues

Show:
RSS
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Backup Exec, Backup Exec - 2010
Severity: Non-data threatening / major functionality
Status: Public fix available
Tech Note: More Information

Beremote.exe process can crash when restoring a VMware virtual machine from a differentia/incremental backup set using Agent for VMWare Infrastructure (AVVI.)

Reported: 24 Jan 2011 by DanielBickford
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Minor functionality
Status: Investigating/gathering information
Tech Note: More Information

When using BESRMS and assigning a filter of "All Computers without Backup Exec System Recovery Installed", this filter does not work. When viewing the filter, it is working against summary information in the database and should be using “computer”.

Reported: 22 Jan 2011 by David F
0
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Minor functionality
Status: Investigating/gathering information
Tech Note: More Information

1. Install BESR 9.0.2 (O.S. irrelevant).

2. Install the LOR. LOR adds boot menu for 10 seconds to choose LOR or Windows

OS). Boot machine to test LOR is working correctly.

3. On same machine, install Altiris DS automation folder, which installs in the

same “BOOT” directory as LOR.

Reported: 22 Jan 2011 by David F
8
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery) - SSR 2011, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Investigating/gathering information
Tech Note: More Information

Run an All drive backup on BESR 9.0.2 for 1 or 2 weeks.
The job configuration is as follows:
a) Schedule for every 15 minutes.
b) Automatically optimize: Never/4hours/12hours.
c) The destination should be a Network Location.

At some point the Backup job hangs at 95% saying 'Updating History'.

Reported: 22 Jan 2011 by David F | <span class="field-content">2</span> comments - last comment 04 May 2011 by Chris Riley
3
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Private fix ready
Tech Note: More Information

 Backup policies created in BESR-MS on or after 1st January 2011 show an
incorrect start date. For example, a job configured to start today (12th Jan)
shows a next run of 1st December.

Any backup policy that is modified on or after 1st Jan 2011 also shows this
problem.

Reported: 22 Jan 2011 by David F
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 8.x, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Private fix ready
Tech Note: More Information

 Incremental backup job fails with Error EBAB0013: A test that safeguards the
integrity of the program failed unexpectedly.

This error only occur on
- incremental backup job (not base backup)
- backup for drive D:\ (not for drive C:\)

Reported: 22 Jan 2011 by David F
7
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 8.x, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Minor functionality
Status: Private fix ready
Tech Note: More Information

 When viewing the backup status on a BESR client, the 'Last Run' date/time is
incorrect. This only applies to backups that are centrally managed by BESR-MS.

Reported: 22 Jan 2011 by David F
0
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Private fix ready
Tech Note: More Information

 After applied SP2 on a server with BESRMS 9.0.1, users are unable to
open "Manage Tasks".  Getting  'Error when reading user preferences'

Reported: 22 Jan 2011 by David F
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 8.x, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Public fix available
Tech Note: More Information

 EI creation fails with "Unable to create Easy Installer.  Unable to generate
GUID."

Reported: 22 Jan 2011 by David F | <span class="field-content">1</span> comments - last comment 10 Feb 2011 by bastwin
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 8.x, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Minor functionality
Status: Private fix ready
Tech Note: More Information

 When the schedule backup fails because network is disconnected, the error
message below is logged to Event log and BESR’s log file.

Reported: 22 Jan 2011 by David F | <span class="field-content">1</span> comments - last comment 11 Feb 2011 by Rodeo720
Show Listings per page