Backup Exec error: (0xE0008520): Device could not be snapped because it contains an active cache file

Posted on 17/11/2015 by Migrated

KB ID 0000265

Problem

You are trying to perform a snapshot using Backup Exec Open File Option and there is already a snapshot file there.

Error:
V-79-57344-34110 – AOFO: Initialization failure on: “C:”. Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP).
Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file.
Check the Windows Event Viewer for details.

Solution

1. Firstly and most importantly make sure there is no backup running at the moment.

2. Go the the server that you were backing up (i.e. if its a remote server, go and logon to that one NOT the media server).

3. Navigate to C:Backup Exec AOFO Store, Delete any files you find there, (Note: Its possible your OFO store may be in a different location, if so look for files called _BEVspCacheFile_0.*)

4. When you have located the file(s) delete them.

5. If it will not let you delete the files because they are in use you can “unlock” them with Unlocker.

Backup Exec Error – Exchange Backup “The VSS Writer failed 0x800423f3”

Posted on 17/11/2015 by Migrated

KB ID 0000307

Problem

Backup Exec Exchange Backup fails with the following error,

Final error: 0xe000fed1 – A failure occurred querying the Writer status. Final error category: Resource ErrorsWriter Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during freeze

Solution

The Microsoft VSS writer that Backup Exec is using is in a failed state.

1. Drop to command line > Start > run > cmd.

2. Issue the following command,

[box]vssadmin list writers[/box]

3. Look for the Exchange writer – and see what state its in.

4. As you can see this one has failed – Reboot the server, 99% of the time that wil fix the error, if not see here.

Backup Exec – Cannot Display Job Logs “{name} contains an invalid path”

Posted on 17/11/2015 by Migrated

KB ID 0000334

Problem

While attempting to open a Backup Exec job log, you see the following error.

Error
C:DOCUMEN~1ADMINI~1.COMLOCALS~1Temp1hist{logname} contains an invalid path.

Solution

1. Nice quick one, update the Microsoft XML Parser to a version greater than Version 6 SP 2.

2. If that fails to resolve the problem, click Start > run > appwiz.cpl {enter} > Locate Backup exec > Change.

3. Next > Select Repair > Follow the onscreen instructions.

Backup Exec – Error “0xe0009585 – Unable to open a disk of the virtual machine”

Posted on 17/11/2015 by Migrated

KB ID 0000349

Problem

Seen while using Backup Exec 2010 R2, while attempting to backup an Exchange 2010 server (on Windows server 2008 R2) in a VMware virtualised environment (using the VMware Backup Exec Agent).

Click for Larger Image

Errors Read

Job Completion Status

Completed status: Failed
Final error: 0xe0009585 – Unable to open a disk of the virtual machine.
Final error category: Resource Errors

Errors

Backup- VMVCB::”Virtual infrastructure”
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file

Solution

This involves two reboots of the target machine start planning downtime, or warning your users.

1. Go to the Virtual Machine that you are trying to backup (in my case the Exchange server)

2. Start > run > appwiz.cpl > Locate and uninstall the VMware tools > when prompted to > reboot.

3. Reinstall the VMware tools but this time choose “CUSTOM INSTALL” > Locate the “Volume shadow Copy Service”.

4. Change the drop down so that this option will not be installed > complete the VMware tools installation and reboot when prompted.

Backup Exec Job Fails With an E000FE30 Error

Posted on 17/11/2015 by Migrated

KB ID 0000382

Problem

A common error on Backup Exec version 12, essentially the media server is losing communication to the Backup Exec remote agent Note: Even if you only have one server it will still be running a remote agent!

Errors:
Final error: 0xe000fe30 – A communication failure has occurred
Final error category: Server Errors

V-79-57344-65072 – The Exchange Store service is not responding. Backup set canceled.

V-79-57344-3844 – The media server was unable to connect to the Remote Agent on machine {server name}

Remote Agent not detected on {server name}

Note: You may also see error E0000F04

Solution

1. Firstly make sure the Backup Exec Remote Agent service is running under the local system account. Start > run > services.msc.

2. Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). The one you pick depends on weather your running 32 bit or 64 bit software. Open the appropriate folder.

3. On a x32 bit server run double click the following two files, setupaa.cmd and setupaofo.cmd (noting will happen other than a command window will flash up).

3. On a x64 bit server run double click the following two files, setupaax64.cmd and setupaofox64.cmd (noting will happen other than a command window will flash up).

4. Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished.

Backup Exec Error – ” The backup-to-disk folder that was specified for this job must be on a local NTFS volume”

Posted on 17/11/2015 by Migrated

KB ID 0000574

Problem

I got this when backing up to an HP RDX removable disk backup system. The drive WAS formatted as NTFS, but the job failed with the following error;

Error:

V-79-57344-4608 – 0xe0001200 – This operation requires a backup-to-disk folder on a local NTFS volume on the media server. Check the job log for details

V-79-57344-4608 – The backup-to-disk folder that was specified for this job must be on a local NTFS volume. Create a new backup-to-disk folder on a local NTFS volume or modify the current folder, and then submit the job again.

Note: Seen on Backup Exec 10.x and 11.x

Solution

In my case the problem was because I was backing up Exchange (2003 on an SBS 2003 server) and it had the GRT option enabled. (Though in these older versions of Backup Exec they didn’t call it GRT).

With Removable Backup to disk Folders you cannot use GRT. Sorry either use a tape or a normal backup to disk folder. And that’s for Exchange, Active Directory and Sharepoint.

1. From within Backup Exec > Tools > Options > Microsoft Exchange > Remove the tick from “Enable the restore of individual mail messages and folders from Information Store backups” > OK.

2. That’s fine for all NEW jobs but if you already have your backup job create you need to edit it. Navigate to Job Monitor > Right click the relevant job> Properties > Microsoft Exchange > Remove the tick from “Enable the restore of individual mail messages and folders from Information Store backups” > Submit > OK.

Backup Exec – Using RDX Drives

Posted on 17/11/2015 by Migrated

KB ID 0000578

Problem

While I like RDX drives, (they have advantages over magnetic tape), but they do have a drawback, throughput.

As you can see the removable drive/cartridges are just 1TB SATA Drives in a protective jacket, with a “write protection switch” on them.

So they should be perfect as a backup medium, the problem is, the drive carrier itself runs off the USB bus, so they can’t run faster than 48MB a second (I’ve not seen a server that has USB 3 on it yet). HP literature says that its backup rate is 108GB an hour. However for a small business that can be more than acceptable. It’s advantage, if it keeps the client that wants to take his backups home with them on a “Tape” happy (Because that’s what they have always done).

So the other week I found myself with a shiny new RDX Drive and an old SBS 2003 Server running Backup Exec 11d.

Solution

Note: If you are running Backup Exec versions 10 or 11 you CANNOT perform backups with GRT. If you want this functionality then you need to upgrade to a newer version (GRT to RDX drive works fine with Backup Exec 2010 R3).

1. Once you have physically installed the drive and connected it to the servers internal USB interface, you should see the drive listed below disk drives.

2. With an RDX Cartridge loaded it behaves just like a 1TB Drive (because that’s exactly what it is).

3. To use the drive in Backup Exec you need to create a new “Removable Backup-to-Disk Folder”.

4. Give the removable folder a sensible name, and I set the maximum size to 1023GB to make sure it can’t try and outgrow the drive.

5. Once complete it will create “Media” in the removable folder that it names incrementally as it sees new cartridges, in the FLDR000001, FLDR000002, etc, format. Treat these the same as any other backup media, i.e. you can add them to media groups for different backup jobs.

Symantec Backup Exec 2012 – Restore Option ‘Greyed Out’

Posted on 17/11/2015 by Migrated

KB ID 0000721

Problem

Seen when trying to carry out a restore in Bexec 2012, when you select the server you wish to restore, (on the Backup and restore tab), both the restore icon, and restore on the right click menu, are greyed out and cannot be selected.

Solution

1. Double click the server in question to open its properties. Select the job history tab and locate either the last good backup, or the backup you wish to restore from. Double click that job to open the job log. Expand the ‘Device and Media Information’ Tab, and locate the tapes/media that this job used. In this case its a tape called 000188L3.

2. In this example I’m using an autoloader and the tape is still in the carousel. If you have a single tape drive insert the tape/media in question. locate the media, right click it and select catalog.

3. To see it’s progress, you can select the jobs tab.

4. When the job is complete, you should now be able to select the restore option.

Backup Exec Job Failed Error ‘A device attached to the system is not functioning’

Posted on 17/11/2015 by Migrated

KB ID 0000871

Problem

I Replaced a tape drive for a customer a couple of weeks ago. With the new one fitted I backed up a few files and restored them to make sure the new drive was OK, and checked the backups the following morning. They had failed with the following on the job log. (Click for larger image).

Job ended: xxxxxxxxxxxxxxxx
Completed status: Failed
Final error: 0xe00084f4 - An unknown error has occurred.
Final error category: System Errors
For additional information regarding this error refer to link V-79-57344-34036
Backup- C:Storage device "HP 0003" reported an error on a request to write data to media.
Error reported:
A device attached to the system is not functioning.
V-79-57344-34036 - An unknown error has occurred.
Backup
A selection on device DC3SQL2008 was skipped because of previous errors with the job.
A selection on device Shadow?Copy?Components was skipped because of previous errors 
with the job.
A selection on device System?State was skipped because of previous errors with the job.

At first it appears that the replacement drive is causing problems so I had a look in the servers event log and found the following;

Event ID 34113

Log Name: Application
Source: Backup Exec
Date: xxxxxxxxxxxxxxxxxx
Event ID: 34113
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxx
Description:
Backup Exec Alert: Job Failed
(Server: "DC3") (Job: "DC3- Daily") DC3- Daily -- The job failed with the following error: 
An unknown error has occurred.

Event ID 57665

Log Name: Application
Source: Backup Exec
Date: xxxxxxxxxxxxxxxxx
Event ID: 57665
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxxxxxxx
Description:
Storage device "HP 0003" reported an error on a request to write data to media.

Error reported:
A device attached to the system is not functioning.

Event ID 10

Log Name: Application
Source: Microsoft-Windows-WMI
Date: xxxxxxxxxxxxxxx
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxx
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE 
TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" 
could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. 
Events cannot be delivered through this filter until the problem is corrected.

Solution

It’s been such a long time since I’ve seen this happen that I struggled with it for a while. The reason I was seeing these errors was, this was an HP Server and Tape Drive. When you install all the HP Insight monitoring agents and software, it can cause this problem with Backup Exec.

1. Start > Run Services.msc {enter}

2. Locate and disable the services shown below.

3. Retry your backup job.

Exchange Install Error ‘Setup cannot continue with the upgrade because the ‘beremote’

Posted on 17/11/2015 by Migrated

KB ID 0000475

Problem

Seen when attempting to install Service Pack 3 on Exchange 2007. On a server that’s also running Symantec Backup Exec.

Hub Transport Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.
Client Access Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.

Mailbox Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.

Solution

1. First make sure you are not currently running any backups with Backup Exec.

2. Click Start > In the Search/Run box type services.msc {enter} >The services console will open.

3. Locate the “Backup Exec Remote Agent for Windows” Service > Right Click and stop it. (Note: In the example above I’ve stopped all the Backup Exec Services, just to be on the safe side).

4. Now try again to install the service pack.

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Event ID 34113

Event ID 57665

Event ID 10

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links