Top 20 Most Valued Backup Exec Articles

Updated: 30 Sep 2010 | 2 comments

Admin

+2 2 Votes

Here is the list of the top 20 Knowledge Base articles.The list is determined by various factors that prove the article's value to our customers. Therefore, please make it a point to check this list first to see if your issue has already been addressed. And FYI, this list would be updated on a quarterly basis.

Good luck!

Rank	Article ID	Article Title
1	191736	The error message “Error 1068: The dependency service or group failed to start” is displayed when attempting to start any of the Backup Exec for Windows NT services
2	274102	Backup Exec Device and Media service fails to start with the message "Database specified does not exist."
3	274993	The backup of shadow copy components fails with the error "0xe000fed1 - A failure occurred querying the Writer status."
4	298300	Best practices for Backup Exec 12 Agent for Microsoft Exchange Server
5	286794	Granular Restore Technology (GRT) used with a Backup-to-Disk (B2D) device results in the disk or the reserved disk space being filled up with overwriteable image (IMG) folders before the oldest IMG media will be overwritten.
6	280508	A backup or restore job fails with the error "Final error: 0xe00084ed - A hardware error occurred."
7	308627	The Utility jobs in Backup Exec will not run until the server is paused/unpaused in the Backup Exec console.
8	288037	The error, "V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine" is returned when attempting to backup the remote user share without the Remote Agent for Windows Servers (RAWS) service installed
9	315592	A job warning alert "The Symantec ThreatCon Level is not up-to-date" is generated in Backup Exec 12.5
10	294957	Exchange 2003 and Exchange 2007 Granular Restore Technology (GRT) Backups to Tape appears to hang in "Updating Catalogs" stage.
11	229898	When performing a backup operation, the following error:"WARNING: "\*\\\*.pst" is a corrupt file. This file cannot verify." is generated
12	193940	How to prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding Microsoft Exchange files)
13	191594	Device jobs remain in a "pending" or "Queued" state indefinitely and "scheduled" jobs do not run at their appropriate time.
14	192319	When attempting to run a cleaning job from the Jobs \| New Clean Drive Job menu, stand-alone tape drives are not displayed under "Select a drive to Clean" and the Run Now and Schedule buttons are grayed out.
15	276639	Backup job fails with the error 0xe00084f4 An unknown error has occurred when running a backup job to a backup-to-disk folder or to a tape device.
16	237737	Network Attached Storage (NAS) appliance compatibility with Backup Exec 9.x, 10.x, 11.x, and 12.x (NON NDMP)
17	267107	How to find out why a Backup Exec for Windows Servers (BEWS) backup or restore job has failed
18	296168	How to backup the Windows Distributed File System (DFS) and File Replication Server (FRS) Data with Backup Exec for Windows Servers version 10d and above
19	295394	Error: e0008821: Job was recovered as a result of Backup Exec RPC service starting. No user action is required.
20	231488	Reasons why the data throughput rate can be slower than the theoretical maximum when backing up to or restoring from tape media or disk (B2D) & how to troubleshoot or improve backup performance

discussion Filed Under:

Backup and Archiving, Backup Exec, Basics, Tip/How to

Comments RSS Feed

Comments

Mar

2010

1 Vote -1

FarHorizons

BackupExec 12.5 Remote Agent for Windows Server Install Issue

I am in the process of converting from BackupExec 9.1 to BackupExec 12.5. I am phasing in the 12.5 installation in our domain. I have the media server installed fine. I uninstalled the early version of the Backup Exec Remote Agent for Windows Server that was running under the 9.1 install on one of our servers, and attempted to install the new version via the Media Server push, "Tools" "Install Agents & Media Servers on other servers". I select "Windows Remote Agents" then "Add" and enter IP address and domain for the Win 2000 server SP 4 computer in question. I enter logon credentials for the push and click OK. I select "Remote Agent for Windows Servers" as well as the OFA. I say "No" to the reboot warning, as I plan to reboot the server later tonight. I enter the IP address for the media server and click "OK". I review and confirm all settings and click "Next", then "Install". Conection is established. It appears as though the first part of the push / install goes fine, but the second fails. The install log has the following RED entry, I assume to be the problem:

ERROR: error 1327. Invalid drive M:

Drive M: is the remapping of the users "My Documents" folder to a network volume for backup purposes via an AD policy.

I have created a Selection List, and included some data from the server in question. Data is being backed up, though with exceptions; The media server was unable to connect to the remote agent on machine racersweb.gbe.local. The media server will use the local agent to try to complete the operation.

Any direction that can be offered on this would be appreciated.

Thank you & have a great day.

Mar

2010

1 Vote +1

Ken Putnam

Trusted Advisor

As this has absolutely

As this has absolutely nothing to do with Swathi's original post, this should be a new topic

That said, you cannot backup mapped drives. You need to backup the server share that the map connects to

If this response answers your concern, please mark it as a "solution"

Top 20 Most Valued Backup Exec Articles

Comments

BackupExec 12.5 Remote Agent for Windows Server Install Issue

As this has absolutely

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats