IT Answers » Backup Exec 11d

if we just got symantec endpoint protection 11.0 renewal do we also need a backup exec 2010?

Sssdna — Fri, 09 Jul 2010 18:09:49 +0000

I was wondering if we just got symantec endpoint protection 11.0 renewal do we also need a backup exec 2010?

Back up Exec 11d:Backup device error

Mary81 — Mon, 07 Jun 2010 14:18:24 +0000

I ask for your ideas:I am using an Ultrium lto 3 tape drive .It is not working with the Symantec backup exec 11d installed in the DELL Poweredge 2970 with Windows server 2003 standard SP 2.If I launch the application ie symantec and loadind the job after starting the backup it displays the error msg ‘Can not locate the specified media or backup device .this backup operation will terminate. Physical volume library drive not found. Please, I request for a help so as I can rescue the situation.

I look forward for your response.

Thanks,

Robi

Disk Backup using eSata removable disks

Eddacker — Wed, 21 Oct 2009 11:17:47 +0000

I am thinking about using eSata removable disks for backup using BackUp Exec 11d. And I would like to hear from anyone who has done this.
I am also considering CPS across the LAN using a NAS hot swapable device.
I currently use SDLT tape and process 500GB+ for a full backup; 14GB on a daily differential. 2 tapes soon to be 3!

ADAMM error with BackupExec 11d

Lonewolfbw — Wed, 05 Aug 2009 14:05:07 +0000

Good morning,

I have just taken over the position of backup operator in my department, so please forgive any seemingly obvious questions. I have received several puzzling errors in the past few days, and hope I can get some answers as to what is causing them. First, this is the setup I am using:

We have a Dell PowerEdge 2950 as our backup server, using BackupExec 11d (Media Server version 11.0, Rev. 7170) – installed updates Service Pack 4, Hot Fixes 62, 63, 64, 65.

Our current configuration is to run a full backup of our main disk array/fileserver on Friday, at 11:00PM. Then, a differential backup will run on M, T, W, Th at 11:00PM. I first noticed a problem when I came in on Saturday and found the following error after the full backup job had ‘finished’:

Job ended: Saturday, August 01, 2009 at 12:28:00 PM
Completed status: Failed
Final error: 0xe00084ec – A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.
Final error category: Backup Media Errors

For additional information regarding this error refer to link V-79-57344-34028

Backup- \\192.168.0.152\M: LRDCVOLStorage device “Drive 1″ reported an error on a request to write data to media.
Error reported:
A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.
V-79-57344-34028 – A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.

Having seen this, I immediately ran the cleaning job. Normally we schedule a cleaning job once a month, and it was due to run in 6 more days anyway. I ran the cleaning job at 1:08PM on Saturday. When I arrived at work Monday morning, BackupExec told me that the cleaning job ran normally and completed. However, I found the following three errors in Windows Event Viewer on the backup server, in the Application log:

Error #1)
Date: 8/1/2009
Time: 1:16:58PM
Type: Warning
User: N/A
Computer: BackupServer
Source: Backup Exec
Category: Devices
Event ID: 33152

Adamm Mover Error: Unload Status Retry!
Error = ERROR_NOT_READY
Drive = “Drive 1″
{A2B872F4-4681-4D45-B6BB-4FDE132C962E}
Media = “”
{00000000-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)

Error #2)
Date: 8/1/2009
Time: 1:17:13PM
Type: Warning
User: N/A
Computer: BackupServer
Source: BackupExec
Category: Devices
Event ID: 33152

Error #3)
Date: 8/1/2009
Time: 1:17:28PM
Type: Error
User: N/A
Computer: BackupServer
Source: BackupExec
Category: Devices
Event ID: 33152

Adamm Mover Error: Unload Status Failure!
Error = ERROR_NOT_READY
Drive = “Drive 1″
{A2B872F4-4681-4D45-B6BB-4FDE132C962E}
Media = “”
{00000000-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)

I ran a second cleaning job on the same autoloader, at 8:41 Monday morning. Three identical errors appeared again in Event Viewer. I have checked back through the event logs and it seems to happen consistently when the cleaning jobs run. By comparison, I have had successfull differential and full backups run (even one last night) and this error does not occur.

What exactly is behind this? Is there a particular issue I need to address? The tape should not be attempting to unload, as we have defined the last slot in the autoloader’s magazine as a cleaning slot and the cleaning tape is left in there.

I have already posted on Symantec’s forum and got nothing, they told me to call their pay support line (and that’s not really an option right now.)

DBCC

Terrywilson — Wed, 22 Apr 2009 20:25:30 +0000

An unknown or unexpected database error occurred while attempting a DBCC

Backup Exec 11d error message on Information Store backup

ITKE — Thu, 26 Feb 2009 14:49:26 +0000

i get “Access is denied” errors in Backup Exec 11d when it attempts to backup a Information Store for Exchange 2007 using a windows server 2003

User submitted question

Backup Exec 11d with Exchange 2007

Jdjetz — Wed, 18 Feb 2009 12:56:46 +0000

I’m running Symantec Backup Exec 11d on Server 2003 Standard, and Exchange 2007 on Server 2003 R2 x64. When I try to Enable individual mailbox message restore I get a Successful backup with the following exception: “To support individual mailbox message and folder restores from Information Store backups, you must download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server. This package can be found on the Microsoft web site” I uninstalled and reinstalled the MAPI/CDO with reboots but continue to get the same msg. When I go to restore a mailbox it actually shows them, but does not allow the restore. How do I get past this so I can backup and restore indivual mailboxes and messages?

Backup Exec 11d on Windows Server 2003 SBS is hanging

ITKE — Wed, 21 Jan 2009 15:27:38 +0000

I have a Windows 2003 SBS server running Backup Exec 11d SP3 After installing MS updates from the most recent cycle, the BE Server service hangs in a “starting…”
state. I have performed a full uninstall and reinstall, testing with
each listed patch level to no avail. I enabled debugging in BE, and
log_beserver.txt goes through the startup and then outputs the
following once per minute:

[7292] 12/30/08 21:35:09 00 Entering DeleteExpiredVSNS()
[7292] 12/30/08 21:35:09 00 Leaving DeleteExpiredVSNS()

Exchange server 2003 Backup Exec 11d error message

ITKE — Wed, 10 Dec 2008 15:35:32 +0000

User submitted
I am receiving the following error with some backup jobs

e000fe39 – The path is too long and cannot be processed.

The job was using the local drives for selecting what
to back up. [Our BE software is installed on the same box as the
exchange server]

Backup Exec 11D error after Exchange Server 2007 SP1 upgrade

ITKE — Mon, 08 Dec 2008 21:09:59 +0000

This is the issue i am running into my Backup Exec 11D jobs fail since Exchange Server 2007 SP1 upgrade was completed get this message in my logs Unable to complete the operation for the selected resource using the specified options. The following error was returned when opening the Exchange Database file: -514 The version of the log file is not compatible with the ESE version.