Backup Exec Slow to Response then Communication Stalled
As of 1/14/2010, BE(vers. 11d) takes forever to do anything, then eventually (most of the time) returns with various errors. The most common error is "Communication Stalled". Sometimes it gets stuck for so long Ihave to reset the PC. We've been using this system for some time, and the only difference is Windows patches that were installed on 1/13/2010. I found some help guides on your site that suggest pausing the media server and restarting the BE services. This helped some, and Iwas able to inventory the drive, as well as do a quick erase provided that I pause/restart EVERY time I do something. It however has not helped with a backup. Misc. Info... Drive is Sony AIT 150 GB SATA using Symantec Driver (dated 3/23/2007, driver version 5.1) Thanks in advance!
Backup exec 11 conflicts with Peachtree
Looking for so help, running Backup exec 11 with all updates, MS server 2003, sql 2005, intel zeon, and peachtree 2008, on Dell T100 server.After updating to peachtree 2008 the back ups now fail with errors pointing at Peachtrees pervasive sql. This seems to be new for Peachtree it was not in any previous years only in the 2008. So does anyone know how to get Symantec backup exec to work with this?
Backup Exec 2010
Hi All, I'm constantly getting the error of "a tape read/write error has occured" (http://www.symantec.com/business/support/index?page=content&id=TECH148527&actp=search&viewlocale=en_US&searchid=1336401552565) Here are the specifics: - Windows Server 2008 Standard SP2 - Symantec Backup Exec 2010, Media Server Version 13.0 Rev. 2896 (64-bit) - Old tapes used for differential always work fine, no errors - Slightly used tapes (used for full/differential backups once or twice) receive the above error - Brand new tapes receive the above error - Tried using two different brands of tapes - Used a tape cleaning cartridge to clean the tape drive I've read up about this error and it said if it's not the tape drive that's dirty, it may be because of the hardware, cables, etc.-- however, the backups work fine when using the older tapes, so it wouldn't have anything to do with the hardware. We have old (1-2 yrs) tapes from full backups, and I've tried using those tapes as well, but I receive the same error. I tried a newer driver for the tape drive, but the same error comes up for the new/slight used tapes. It's hard to believe it's something to do with the tape drive hardware, cables, internal, or software since I'm not getting this error for all of the tapes I use. Thanks.