Recent content by dogmata

another tip: if you have the open file option installed, remove it and see if the issues occur. Ta Dog

try repairing the MSDE DB backup exec has running behind it, you would do his via the beutility.exe check that you have the VRTS drivers installed check your system logs (Event viewers) , check to see if you are getting any errors reported from the tape drive ie. ID 7,9,11,15's > if so, you...

Sqeak: - OFO is a subject i know a bit about. First: what version and build of BE (backup ex.) is it ie. 8.6 rev 3878, or 9.0 rev 4454 ? - What is the exact entire error are you getting and, is it for a local or remote BU(backup) which fails ? Also, does it fail for all volumes on that server...

pctekk: the answer is no. Only the updated build of 9.0 (rev 4454 is the new one, rev 4367 is the older build) supports 2003 fully.

There could be many reasons why it wont backup an open file a) The file is in use and BE is not able to lock the file in order to back it up(BU). b) you are trying to backup some DB like SQL, exchange (pub/priv.edb) etc etc. by selecting it at file level. c) if you want to backup the above...

Shrubble: I cant remember exactly where you click etc, but I think you do via the system manager tools, just keep drilling down until you see you mailbox stores > I think you right click and run something like the "cleanup wizard" which will then mark any orphaned mailboxes with a red...

Shrubble: - I understand you deleted those exchange objects but did you actually purge them from the system manger tools prior to running the backup? Exchange 2000 will tombstone objects (30 or 60 days or something , but is configurable), so they are actually still present on your system, and...

FL22980: Apologies NortonES2, but with 9.0 you do NOT require the exchange admin tools for exchange 5.5 or the system manager tools for exchange 200 on the media server even if exchange is remote. You also do not need to install a mapi client on the media server again, regardless if its remote...

MEGAWICKED: I forgot to add, before starting all BE services > remove the read only attribute from the pvl, as this file is going to be constantly written to BE. If it works, you will have to either recreate all your media settings ie media sets etc or you can try and repair the access DB (which...

MEGAWICKED: Stop all of the backup exec services > Go in to your veritas\backup exec\nt directory > rename only the pvl.mdb > copy a new pvl.mdb from the backup exec CD and past it back into nt directory > start all backup exec services (you will have lost your media settings but can always be...

Update your Veritas drivers and SCSI drivers Check the system logs for the ID's 7,9,11 and 15's if you are getting any you have SCSI timeout issues. Why the description is missing in your event viewers i dont know but what you would expect to see is an error desription along the lines...

PACKDRAGON: Yep, sorry a/c stands for account ie. the new user account Cheers Dog

Do you have identical hardware though, including the NIC's and NIC drivers, same scsi card and driver etc ? Cheers Dog

RGILBERT2323: for system state issue see: http://www.tek-tips.com/gviewthread.cfm/lev2/7/lev3/49/pid/481/qid/598972 You may also find above thread useful for exchange mailboxes > try changing the restrict anonymous support value > see the case to find out more Good detailed error description...

PAckdragon : forgot to mention that the above was assuming you are using Backup Exec 9.0 ? If not forget about point D) ( point E doesnt really apply either but still create a new job for the test)and do this instead - stop all services and change them to start witht the new a/c but dont...