Recent content by bettyb

I recently upgraded from version 9 to 11.5. I've noticed in d:\program files\ca\brightstor backup agent for exchange. I have an EXCESSIVE amount of files. The pattern is at#number.number. such as, AT#77569.6160; AT#7757.3604. The date and time stamps appear to coincide with the brick level...

So I have 1 recommmendation for the SMSME add-on. Anyone else? We have a 2-man IT department, so I really need a product that requires LITTLE IT intervention. thank you

If anyone out there is using this, would you give me your opinion on this product? I am going to install a trial version. I am looking for a product where I don't have to do a lot of monitoring and reviewing but I want good spam filtering. I tried to talk to a Symantec sales rep and a...

A few years ago we migrated from Exchange 5.5 to exchange 2003. I now have a need to restore a mailbox using a backup that has exchange 5.5 bricks. I no longer have a 5.5 server around and hate to rebuild one. I am using arcview 9, build 2020. I believe when we upgraded I had to upgrade the...

I currently run exchange 2003 with Symantec SMSE 4.6. I have always used the default basic rule to "Repair attachment/message body". In the past, it was possible to get real email with a bad attachment, now it appears that the most infected emails are garbage anyway . What I would really...

AND thanks again oggywan. I have the same issue for weeks. I never hit this link during my symantec searches. I can't wait to try it out.

As promised, here is my current progress. Updating symevent appears to have fixed the server crashing problem. And remember the one server I said never crashed during backup? well it did between these posts. I patched that one too. I've gone 3 days without crashes so I hope this is a good...

I am using Brightstor 9, Build 2020. I had the bsod issue on 2 Windows 2003 servers (don't have service pak1). Another WIndows 2003 server is fine - - go figure! I tested the symevent fix on one server and have run several backups. After updating the symevent.sys went from rev 11.6.2.4 to rev...

I updated from 10 to 10.1 to help with the rtvscan overhead issues. From a client perspective, this is much improved. I also wanted to turn off do scan at login, since it was very annoying - - I do full system scans daily on clients. One outstanding issue I still have - - my parent server...

I ran the symevent update. Noticed that symevent.sys changed from rev level 11.6.2.4 to 11.6.4.1. I've run 4 consecutive full backups without a crash. this was our Win2003 Secondary Domain Controller. I am going to let this run for a few days and see. the other server is a heavily used...

Sorry, I did not read this post thoroughly before I posted a new one that sounds the same. I have the same issue BSOD with brighstor. I went to SAV10.1 this past weekend and 2 servers get bsod everytime backup started. Another sav10.1 server is fine. these are all Windows2003 servers. I am...

This is two different servers. One is a backup domain controller, the other is a file and print server. Most of the time, when it crashed it was caused by ofant.sys. So I removed the open file agent from one server just to test. I have seen bug check 0x000000c2; 0x000000d1; 0x00000044...

thank you. I saw this post KB article on Symantec's site, and wasn't sure if it related to my issues, since I was not getting that exact stop message. of course, at this point, trying that could not hurt (much!). I will check it out and post here once I know the results. thx

I wasn't sure which forum to post this in. I had Symantec Antivirus 10.0.359 running for 2 months without any brightstor issues. this weekend, I upgraded to Symantec Antivirus 10.0.1.1000 - -and all of a sudden 2 Dell PE1750 servers crash everytime the backup starts. I believe it's related to...

Have you tried loading the registry hive cleanup on a Windows2003 server? Why I am asking: I've been running Sav10 for about a month. all of a sudden I am having a terrible time on my primary server with rtvscan service crashing - - and I am wondering if the registry issue is related. I am...